WO2023142695A1 - 基于切片的通信方法及其装置 - Google Patents

基于切片的通信方法及其装置 Download PDF

Info

Publication number
WO2023142695A1
WO2023142695A1 PCT/CN2022/137158 CN2022137158W WO2023142695A1 WO 2023142695 A1 WO2023142695 A1 WO 2023142695A1 CN 2022137158 W CN2022137158 W CN 2022137158W WO 2023142695 A1 WO2023142695 A1 WO 2023142695A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
network slice
terminal device
access
slice
Prior art date
Application number
PCT/CN2022/137158
Other languages
English (en)
French (fr)
Inventor
李卓明
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023142695A1 publication Critical patent/WO2023142695A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • the present application relates to the communication field, and more specifically, to a slice-based communication method and device thereof.
  • each logical network can be provided through network slicing, and each logical network serves a specific service type, industry or user, and can meet the differentiated requirements of different services, industries or users.
  • the service of the terminal device may be affected, or the network slicing that the terminal device can access may be restricted.
  • the solution for the terminal device to access the network slicing still needs to be improved, and the user experience still needs to be improved. space.
  • the embodiment of the present application provides a communication method based on slicing, which can improve the service stability of the terminal device, and prevent the terminal device from Services transmitted through activated sessions are affected, improving user experience.
  • a slice-based communication method including: a first access and mobility management functional network element acquires information about a target network slice of a terminal device; the first access and mobility management functional network element determines At least one network slice in the target network slice corresponds to an active session of the terminal device; the first access and mobility management function network element sends the first access network device to switch the active session to Indication information of cells supporting the tracking area of the target network slice.
  • the first network element with the access and mobility management function can acquire the auxiliary information attribute of the session that the terminal device has established in a single network slice of the current service network from the context of the terminal device, that is, the session has been established The network slice corresponding to the session.
  • the first access and mobility management functional network element may obtain the status of the established session of the terminal device from the registration request of the terminal device (for example, the status of the session may include being active, in the deactivated state, deactivated or released state).
  • the first access and mobility management function network element may determine that at least one network slice in the target network slice corresponds to the active session according to the active session and the target network slice.
  • the first access and mobility management functional network element may send a message to the first access network device that will be in the active state
  • the indication information of the session handover to the cell supporting the tracking area of the target network slice.
  • the service stability of the terminal device can be improved, and the active session of the terminal device is prevented from being interrupted when the terminal device accesses a cell that supports the target network slice of the terminal device and registers for the network slice, thereby improving user experience.
  • the indication information is information of the target network slice.
  • the first access and mobility management functional network element sends the information of the target network slice to the first access network device.
  • the first access and mobility management functional network element may send information about the target network slice to the terminal device, where the information about the target network slice is used to indicate that the active session is switched to a tracking area that supports the target network slice
  • the first access and mobility management functional network element may send to the terminal device instruction information to switch the active session to a cell supporting the tracking area of the target network slice, and also send information about the target network slice.
  • the first access and mobility management functional network element acquires information about the target network slice of the terminal device, including: the first access and mobility management The functional network element determines the target network slice according to the network slices already used in the first permitted network slice of the UE.
  • the first access and mobility management function network element determines that the terminal device has established a session through one or more network slices (for example, ⁇ network slice #4 ⁇ ) in the first permitted network slice (ie , the network slices already used by the terminal device), then it is determined that the one or more network slices (for example, ⁇ network slice #4 ⁇ ) belong to a part of the target network slice (for example, the target network slice).
  • one or more network slices for example, ⁇ network slice #4 ⁇
  • the target network slice for example, the target network slice
  • the first access and mobility management function network element determines the target network slice according to the network slices already used in the first permitted network slice, including: the The first access and mobility management functional network element determines the target network slice according to the network slices already used in the first permitted network slice and the network slice to be used by the UE.
  • the network element with the first access and mobility management function may be based on the already used network slice (for example, ⁇ network slice #3, network slice #4 ⁇ ) or the network slice to be used (for example, ⁇ network slice #4 ⁇ ) of the terminal device network slice #2 ⁇ ), determine the target network slice of the terminal device (for example, the target network slice can be ⁇ network slice #2, network slice #3, network slice #4 ⁇ ).
  • the first access and mobility management function network element acquires information about the target network slice of the UE, including: the first access and mobility management function The network element receives the information of the target network slice from the network slice selection functional network element.
  • the terminal device can also implement After the active session is handed over, it is re-registered with the second access and mobility management function network element supporting the target network slice, so as to prevent the active session of the terminal device from being affected and improve user experience.
  • the first access and mobility management function network element saves the target network slice in the context of the terminal device; after the active session is completed After the handover, the first access and mobility management function network element receives the registration request of the terminal device, and determines the second allowed network slice of the terminal device according to the target network slice in the context.
  • the first access and mobility management function network element may save the target network slice in the context of the terminal device, and after the active session completes the handover, the first access and mobility management function network element
  • the unit receives the registration request initiated by the terminal device in the tracking area supporting the target network slice, and determines the second allowed network slice of the terminal device according to the requested network slice carried in the registration request and the target network slice in the context.
  • the second allowed network slice is used by the terminal device to establish a session subsequently.
  • the first access and mobility management function network element saves the target network slice in the context of the terminal device; the first access and mobility The management function network element sends the context information to the second access and mobility management function network element, wherein the access network device responsible for managing the cell supporting the tracking area of the target network slice and the second access and mobility management function Network element connection, the target network slice in the context information is used to determine the second allowed network slice of the terminal device after the active session completes the handover and initiates a registration request.
  • the first access and mobility management functional network element sends the radio frequency selection priority (Radio access technology/frequency selection priority, RFSP) information, the RFSP information is used to determine the wireless measurement instruction, and the wireless measurement instruction is used for the terminal device to discover the tracking area supporting the target network slice before switching the active session (Tracking area, TA) cell.
  • RFSP Radio access technology/frequency selection priority
  • the RFSP information is determined by the first access and mobility management functional network element according to a local configuration policy.
  • the RFSP information is obtained by the first access and mobility management functional network element requesting the policy control network element.
  • a slice-based communication method including: a first access network device receiving information about a target network slice of a terminal device from a first access and mobility management function network element; the first access The network device determines to switch at least one network slice in the target network slice corresponding to an active session of the terminal device; the first access network device switches the active session to a cell of the TA that supports the target network slice .
  • the terminal device can be re-registered Go to the second access and mobility management function network element that supports the above target network slicing, so that the terminal device can re-register with the network in the new tracking area, and the new tracking area supports the network slice that has already been used and the network slice that will be used soon, This prevents the active session of the terminal device from being affected during the handover process, improves service stability of the terminal device, and enhances user experience.
  • the first access network device determining to switch at least one network slice in the target network slice corresponding to an active session of the terminal device includes: the first An access network device receives instruction information from the first access and mobility management function network element to switch the active session to a cell of the TA that supports the target network slice; the first access network device according to The indication information determines to switch the active session.
  • the first access and mobility management functional network element may send an N2 interface message to the first access network device, where the N2 interface message carries an active session handover to a cell that supports the tracking area of the target network slice At least one of the indication information of the target network slice and the information of the target network slice.
  • the N2 message may also carry a registration response message sent by the first access and mobility management function network element to the terminal device through the first access network device, and the registration response message indicates that the terminal device has already registered in the first access and mobility The network element with the property management function is successfully registered.
  • the indication information is information of the target network slice.
  • the first access network device receives the indication information and the information of the target network slice from the first access and mobility management functional network element.
  • the first access network device determining to switch at least one network slice in the target network slice corresponding to an active session of the terminal device includes: the first An access network device determines to switch the active session according to at least one network slice in the target network slice corresponding to the active session.
  • the first access network device determines a wireless measurement instruction of the terminal device, and the wireless measurement instruction is used to discover the The cell of the TA that supports the target network slice.
  • the first access network device determining the radio measurement instruction of the terminal device includes: the first access network device determining the Wireless measurement commands.
  • the first access network device determining the wireless measurement instruction includes: the first access network device receiving a request from the first access and mobility management function RFSP information corresponding to the target network slice of the network element; the first access network device determines the wireless measurement instruction according to the RFSP information.
  • the first access network device may send a wireless measurement instruction of the terminal device to the terminal device through a radio resource management configuration (RRMconfiguration) message, and the terminal device sends the wireless measurement report to the first access network device, if The radio measurement report indicates that the signal strength of the cell supporting the tracking area of the target network slice reaches a preset threshold, and the first access network device decides to start the handover.
  • RRMconfiguration radio resource management configuration
  • a slice-based communication method including: a network device acquires at least one item of information about a network slice that has been used by a terminal device or a network slice that is about to be used by the terminal device, and a request from the terminal device Network slice information; the network device determines the first allowed network slice of the terminal device according to at least one of the already used network slice or the soon-to-be-used network slice, and the requested network slice; the network device sends the first allowed network slice Network slice information.
  • the network device may send to the terminal device a registration response message indicating that the registration of the terminal device is successful, where the registration response message carries information about first allowed network slicing.
  • the network device After the network device obtains at least one item of information about the network slice that the terminal device has already used or the network slice that the terminal device will use soon, and the requested network slice information of the terminal device, it can determine the terminal according to the above information.
  • the device first allows network slicing, and sends information about the first allowed network slicing. Due to the processing in this embodiment, the number of network slices included in the first allowed network slice is reduced, so an appropriate allowed network slice can be determined according to the communication requirements of the terminal device, and the range of the registration area corresponding to the allowed network slice can be as large as possible. Larger, reducing the signaling load during the mobile process of the terminal equipment.
  • the network device acquires information about network slices supported by the TA where the terminal device is located; if the TA does not support at least one network slice in the network slice to be used In the case of , the network device determines the target network slice of the terminal device according to at least one of the already used network slice or the soon-to-be-used network slice, and the requested network slice; the network device sends the target network slice information.
  • the network device determines the target of the terminal device according to at least one of the network slice that has been used or the network slice to be used, and the requested network slice
  • the network slice includes: the network device selects a network slice belonging to at least one of the used network slice or the soon-to-be-used network slice, and the network slice belonging to the requested network slice to form the target network slice.
  • the target network slice includes the requested network slice of the terminal device, which is not supported by the current tracking area of the terminal device, but can be used by other tracking areas (for example, a tracking area of another frequency band that overlaps with the current tracking area of the terminal device) ) supported network slices.
  • the information of the target network slice can be target NSSAI.
  • the target network slice includes the network slice that the terminal device has used in the allowed network slice saved in the context, and the network slice that will be used soon, wherein the network slice that has been used may be the network slice corresponding to the session that the terminal device has established.
  • the network slice used can be the network slice of the session that the terminal device expects to establish; in addition, the session that the terminal device expects to establish can be a session that the terminal device expects to establish and has not yet been established, or it can be released, but the terminal device The session to be established (for example, a Business Continuity Mode 2 or Mode 3 session).
  • the network device can obtain the previously saved allowed network slices of the terminal device, if one or more of the requested network slices carried in the registration request message initiated by the terminal device If the network slice does not belong to the above allowed network slices, then the one or more network slices are the network slices to be used, and the network device can choose to request at least one of the network slices that have already been used or the network slices that will be used. The network slices of items that make up the target network slice.
  • At least one network slice in the target network slice does not belong to a network slice supported by the TA.
  • the network slice supported by the TA where the terminal device is currently located is ⁇ network slice #2, network slice #3, network slice #4 ⁇
  • the allowed network slices of the terminal device previously saved by the network device are ⁇ network slice #3, Network slice #4 ⁇
  • the requested network slice is ⁇ network slice #1, network slice #2, network slice #4 ⁇ .
  • the network device determines that the network slice to be used is ⁇ network slice #1, network slice #2 ⁇ , the already used network slice is ⁇ network slice #3 ⁇ , and the target network slice is ⁇ network slice #1, network slice #2, Network slicing #3 ⁇ .
  • the network device determines the terminal device's first An allowed network slice, comprising: the network device selects a network slice belonging to at least one of the already used network slice or the soon-to-be-used network slice, and a network slice belonging to the requested network slice to form the first allowed network slice.
  • the first access and mobility management function network element can (e.g., ⁇ network slice #3 ⁇ ) and the network slice to be used (e.g., ⁇ network slice #2 ⁇ ), and the requested network slice ⁇ e.g., network slice #1, network slice #2, network slice #3 ⁇ ,
  • a first allowed network slice (for example, ⁇ network slice #2, network slice #3 ⁇ ) of the terminal device is determined.
  • the TA where the terminal device is currently located also supports network slice #1 in the requested network slice, it is not included in the first allowed network slice because it does not belong to the network slice that has been used or the network slice to be used.
  • the network device determines the first permission It is also excluded when the network slice is used, or it can also be understood as filtering it, so that each network slice in the finally determined first allowed network slice belongs to the network slice or terminal device that has been used by the terminal device The network slice to be used.
  • the allowed network slices determined in this way include a smaller number of network slices than the allowed network slices determined in the prior art.
  • the network device includes a first network slice selection function network element.
  • the network device acquires at least one item of information about the network slice that the terminal device has used or the network slice that the terminal device will use, including: the network The device receives at least one piece of information of the used network slice and the to-be-used network slice from the access and mobility management functional network element.
  • the network device when the network device includes a network element with a network slice selection function, the network device receives a network slice selection from an access and mobility management function network element (hereinafter referred to as the first access and mobility management function network element) After the request, if the network device judges that the tracking area where the terminal device is currently located supports the network slice requested by the terminal device, but the first access and mobility management function network element does not support the network slice requested by the terminal device, the network device can determine a connection A new access and mobility management function network element (subsequently referred to as a second access and mobility management function network element) that is in the tracking area where the terminal device is currently located and supports the terminal device's request for network slicing, and sends the first The information of the second access and mobility management function network element is sent to the first access and mobility management function network element; after that, the first access and mobility management function network element forwards the registration request message of the terminal device to the second Access and mobility management function network elements for processing; finally, if the network device judges that the tracking area where the terminal device is
  • the network device includes an access and mobility management functional network element.
  • the network device receives the second allowed network slice of the terminal device from the second network slice selection function network element; the network device receives from the second allowed network slice Selecting at least one network slice that belongs to the network slice that has been used or the network slice that is about to be used from the slices to form a third allowed network slice; the network device sends the information of the third allowed network slice to the terminal device information.
  • the second allowed network slice may be determined by the second network slice selection function network element through the existing technology, that is, the second network slice selection function network element according to the requested network slice carried in the registration request message of the terminal device, and the terminal device It is determined by the network slicing supported by the registration area where it is located.
  • the network device acquires information about the first rejected network slice of the terminal device; the network device deletes the registration area of the terminal device in the first rejected network slice ( Registration Area, RA) in the network slice supported by any TA, obtain the second rejected network slice of the terminal device, wherein the RA is determined according to the second permitted network slice; the network device sends the terminal device the The second rejects information about network slicing.
  • the network device deletes the registration area of the terminal device in the first rejected network slice ( Registration Area, RA) in the network slice supported by any TA, obtain the second rejected network slice of the terminal device, wherein the RA is determined according to the second permitted network slice; the network device sends the terminal device the The second rejects information about network slicing.
  • Registration Area RA
  • the first rejected network slice is ⁇ network slice #1, network slice #2, network slice #3, network slice #4 ⁇ , and the network slice supported by a certain tracking area existing in the registration area is ⁇ network slice# 2.
  • Network slice #3 ⁇ then the second rejected network slice is ⁇ network slice #1, network slice #4 ⁇ .
  • the foregoing manner of determining the rejection of the network slice is not limited to determining the third permitted network slice through the foregoing manner.
  • the network device may send a registration response message to the terminal device, where the registration response message indicates that the terminal device has registered successfully, and may also carry information that the second network slice is rejected.
  • the second rejected network slice can be obtained, which can make the rejected network slice of the terminal device contain fewer network slices, and expand the range of network slices that the terminal device can use as much as possible. Further, the scope of the corresponding registration area is expanded, and the signaling load during the terminal moving process is reduced.
  • the network device obtains at least one item of information on the network slice that has been used or the network slice to be used, including at least one of the following methods: the network device determining the information of the already used network slice according to the session state information of the terminal device; or determining the information of the network slice to be used by the network device according to the requested network slice and the fourth allowed network slice in the context of the terminal device; Or the network device receives the communication analysis result information of the terminal device from the network element with the network data analysis function, and determines the information of the network slice to be used according to the communication analysis result information.
  • a communication device configured to execute the method provided in the first aspect, the second aspect, or the third aspect.
  • the device may include the first aspect or any of the above-mentioned implementations of the first aspect, or the second aspect or any of the above-mentioned implementations of the second aspect, or the third aspect or any of the above-mentioned implementations of the third aspect.
  • a unit and/or module implementing the method provided by the manner such as a processing unit and/or a communication unit.
  • the device is a first access and mobility management functional network element.
  • the communication unit may be a transceiver, or an input/output interface;
  • the processing unit may be at least one processor.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • the device is a chip, a chip system or a circuit used in the network element with the first access and mobility management function.
  • the communication unit may be an input/output interface, interface circuit, or output circuit on the chip, chip system or circuit , input circuits, pins or related circuits, etc.; the processing unit may be at least one processor, processing circuit or logic circuit, etc.
  • the apparatus is a first access network device.
  • the communication unit may be a transceiver, or an input/output interface;
  • the processing unit may be at least one processor.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • the apparatus is a chip, a chip system or a circuit used in the first access network device.
  • the communication unit may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pipe on the chip, a chip system or a circuit feet or related circuits, etc.
  • the processing unit may be at least one processor, processing circuit or logic circuit, etc.
  • the apparatus is a network device.
  • the communication unit may be a transceiver, or an input/output interface;
  • the processing unit may be at least one processor.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • the apparatus is a chip, a chip system or a circuit used in a network device.
  • the communication unit may be an input/output interface, interface circuit, output circuit, input circuit, pin or Relevant circuits and the like;
  • the processing unit may be at least one processor, processing circuit or logic circuit and the like.
  • a communication device which includes: a memory for storing programs; at least one processor for executing the computer programs or instructions stored in the memory, so as to perform the above-mentioned first aspect or any of the above-mentioned first aspects.
  • An implementation, or the second aspect or any of the above-mentioned implementations of the second aspect, or the third aspect or any of the above-mentioned implementations of the third aspect, or the fourth aspect or any of the above-mentioned implementations of the fourth aspect The implementation manner, or the fifth aspect or any one of the above-mentioned implementation manners of the fifth aspect provides a method.
  • the device is a first session management function network element.
  • the device is a chip, a chip system or a circuit used in the network element with the first session management function.
  • the apparatus is a terminal device.
  • the apparatus is a chip, a chip system, or a circuit used in a terminal device.
  • the device is a core network element.
  • the device is a chip, a chip system or a circuit used in a core network element.
  • the device is an access and mobility management functional network element.
  • the device is a chip, a chip system or a circuit used in an access and mobility management functional network element.
  • the present application provides a processor configured to execute the methods provided in the foregoing aspects.
  • the processor's output and reception, input and other operations can also be understood as the sending and receiving operations performed by the radio frequency circuit and the antenna, which is not limited in this application.
  • a computer-readable storage medium where the computer-readable medium stores program code for execution by a device, and the program code includes the above-mentioned first aspect or any one of the above-mentioned implementation methods or The second aspect or any of the above-mentioned implementations of the second aspect or the third aspect or any of the above-mentioned implementations of the third aspect or the fourth aspect or any of the above-mentioned implementations of the fourth aspect or the fifth aspect or the first The method provided by any one of the above-mentioned implementation manners of the five aspects.
  • a computer program product containing instructions is provided, and when the computer program product is run on a computer, it causes the computer to execute the above-mentioned first aspect or any one of the above-mentioned implementations of the first aspect or the second aspect or the second aspect.
  • Any of the above implementations of the third aspect or any of the above implementations of the third aspect or the third aspect or the fourth aspect or any of the above implementations of the fourth aspect or the fifth aspect or any of the above implementations of the fifth aspect A method provided by an implementation.
  • a chip in the eleventh aspect, there is provided a chip, the chip includes a processor and a communication interface, the processor reads the instructions stored in the memory through the communication interface, and executes the above-mentioned first aspect or any one of the above-mentioned implementation methods of the first aspect or the second Aspect or any of the above implementations of the second aspect or the third aspect or any of the above implementations of the third aspect or the fourth aspect or any of the above implementations of the fourth aspect or the fifth aspect or the fifth aspect The method provided by any of the above implementations.
  • the chip further includes a memory, in which computer programs or instructions are stored, and the processor is used to execute the computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, the processor is used to execute
  • a multicast/broadcast communication system including the first session management function network element and the access and mobility management function network element above.
  • Fig. 1 shows a schematic diagram of a network architecture.
  • Fig. 2 shows a schematic diagram of network slice deployment.
  • Fig. 3 shows another schematic diagram of network slice deployment.
  • FIG. 4 shows a schematic diagram of a slice-based communication method 400 provided by an embodiment of the present application.
  • FIG. 5 shows a schematic diagram of a slice-based communication method 500 provided by an embodiment of the present application.
  • FIG. 6 shows a schematic diagram of a method 600 for determining a slice provided by an embodiment of the present application.
  • FIG. 7 shows a schematic diagram of a slice-based communication method 700 provided by an embodiment of the present application.
  • FIG. 8 shows a schematic diagram of a slice-based communication method 800 provided by an embodiment of the present application.
  • FIG. 9 shows a schematic diagram of a method 900 for determining a slice provided by an embodiment of the present application.
  • FIG. 10 shows a schematic diagram of a method 1000 for determining a slice provided by an embodiment of the present application.
  • Fig. 11 shows a schematic block diagram of a communication device 1100 provided by an embodiment of the present application.
  • Fig. 12 shows a schematic block diagram of a communication device 1200 provided by an embodiment of the present application.
  • FIG. 13 shows a schematic structural diagram of a simplified network device 1300 .
  • the technical solution provided by this application can be applied to various communication systems, such as: the fifth generation (5th generation, 5G) or new radio (new radio, NR) system, long term evolution (long term evolution, LTE) system, LTE frequency division Duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD) system, etc.
  • 5G fifth generation
  • NR new radio
  • long term evolution long term evolution
  • LTE long term evolution
  • LTE frequency division Duplex frequency division duplex
  • FDD frequency division duplex
  • TDD time division duplex
  • the technical solution provided by this application can also be applied to device to device (device to device, D2D) communication, vehicle to everything (vehicle-to-everything, V2X) communication, machine to machine (machine to machine, M2M) communication, machine type Communication (machine type communication, MTC), and Internet of things (internet of things, IoT) communication system or other communication systems.
  • D2D device to device
  • V2X vehicle-to-everything
  • M2M machine to machine
  • M2M machine type Communication
  • MTC machine type communication
  • IoT Internet of things
  • Fig. 1 shows a schematic diagram of a network architecture.
  • the network architecture takes the 5G system (the 5th generation system, 5GS) as an example.
  • the network architecture may include but not limited to: network slice selection function (network slice selection function, NSSF), next generation base station node (next generation Node Base station, gNB), unified data management (unified data management, UDM), policy control function (policy control function, PCF), access and mobility management function (access and mobility management function, AMF), session management function (session management function, SMF), user equipment (user equipment, UE), user plane function (user plane function, UPF), data network (data network, DN), network data analysis function (Network data analytics function, NWDAF), unified data repository (unified data repository, UDR).
  • DN can be the Internet
  • NSSF the Internet
  • NWDAF the Home Location Function
  • UDR the Home Location Function
  • UDM the Physical Downlink Control Function
  • PCF Packet Control Function
  • AMF the Home Streaming Function
  • SMF the Home Streaming Function
  • UPF the User Plane Function
  • Figure 1 takes the 5G system as an example, the core network can be called a 5G core network ( 5G core network, 5GC or 5GCN).
  • 5G core network 5G core network, 5GC or 5GCN
  • Each network element shown in FIG. 1 is briefly introduced below.
  • UE can be called user equipment, terminal equipment, access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device.
  • a terminal device may be a device that provides voice/data to a user, for example, a handheld device with a wireless connection function, a vehicle-mounted device, and the like.
  • some terminals are: mobile phone (mobile phone), tablet computer, notebook computer, palmtop computer, mobile internet device (mobile internet device, MID), wearable device, virtual reality (virtual reality, VR) device, augmented reality (augmented reality, AR) equipment, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical surgery, smart grid Wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, cellular phones, cordless phones, session initiation protocol , SIP) phones, wireless local loop (wireless local loop, WLL) stations, personal digital assistants (personal digital assistant, PDA), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, Wearable devices, terminal devices in a 5G network, or terminal devices in a future evolving public land mobile network (PLMN), etc., are not limited in this
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices, which is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not only a hardware device, but also achieve powerful functions through software support, data interaction, and cloud interaction.
  • Generalized wearable smart devices include full-featured, large-sized, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, etc., and only focus on a certain type of application functions, and need to cooperate with other devices such as smart phones Use, such as various smart bracelets and smart jewelry for physical sign monitoring.
  • the terminal device can also be the terminal device in the IoT system.
  • IoT is an important part of the development of information technology in the future. Its main technical feature is to connect items to the network through communication technology, so as to realize Interconnection, an intelligent network that interconnects things.
  • a certain air interface technology such as NR or LTE technology
  • a certain air interface technology may also be used to communicate with each other between terminal devices.
  • the terminal device may be replaced with a device for realizing the function of the terminal device, or may be a device capable of supporting the terminal device to realize the function, such as a chip system or a chip, and the device may be installed in the terminal device.
  • a system-on-a-chip may consist of chips, or may include chips and other discrete devices.
  • gNB It can provide terminal equipment with the function of accessing the communication network. Specifically, it may include a wireless network device in a third generation partnership project (3rd generation partnership project, 3GPP) network, and may also include an access point in a non-3GPP (non-3GPP) network. In addition, the gNB may also be called an access network (Access network, AN) device.
  • 3GPP third generation partnership project
  • AN access network
  • the gNB equipment may adopt different radio access technologies.
  • 3GPP access technologies for example, wireless access technologies used in third generation (3rd generation, 3G), fourth generation (4th generation, 4G) or 5G systems
  • non- 3GPP (non-3GPP) access technology refers to the access technology that complies with the 3GPP standard specifications.
  • the gNB in the 5G system can be called an access network device or a RAN device.
  • Non-3GPP access technologies may include air interface technology represented by access point (AP) in wireless fidelity (WiFi), worldwide interoperability for microwave access (WiMAX), code Multiple access (code division multiple access, CDMA), etc.
  • AP access point
  • WiFi wireless fidelity
  • WiMAX worldwide interoperability for microwave access
  • CDMA code Multiple access
  • the gNB equipment can enable the interconnection and intercommunication between the terminal equipment and the 3GPP core network using non-3GPP technology.
  • the gNB device can also be responsible for functions such as wireless resource management, quality of service (QoS) management, data compression and encryption on the air interface side.
  • QoS quality of service
  • the gNB equipment provides access services for the terminal equipment, and then completes the forwarding of control signals and user data between the terminal equipment and the core network.
  • gNB equipment may include but not limited to: macro base station, micro base station (also called small station), radio network controller (radio network controller, RNC), node B (Node B, NB), base station controller (base station controller, BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (baseband unit, BBU), AP in WiFi system, wireless relay node , wireless backhaul node, transmission point (transmission point, TP) or sending and receiving point (transmission and reception point, TRP), etc., can also be the transmission point (TRP or TP) in the 5G (eg, NR) system, 5G system
  • One or a group (including multiple antenna panels) antenna panels of the base station in the base station or it can also be a network node that constitutes a gNB or a transmission point, such as a distributed unit (distributed unit, DU), or in the next generation communication 6
  • AMF It is mainly used for terminal registration, mobility management, and tracking area update process in the mobile network.
  • the access management network element terminates the non-access stratum (NAS) message, completes registration management, and connection management And reachability management, allocation tracking area list (track area list, TA list) and mobility management, etc., and transparent routing of session management (session management, SM) messages to session management network elements.
  • NAS non-access stratum
  • reachability management allocation tracking area list (track area list, TA list) and mobility management, etc.
  • session management session management
  • the access management network element may be the access and mobility management function.
  • SMF mainly used for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning an Internet protocol (internet protocol, IP) address to the terminal, selecting a user plane network element that provides a packet forwarding function, and the like.
  • IP Internet protocol
  • the session management network element may be a session management function.
  • UPF It is mainly responsible for processing user packets, such as forwarding, billing, legal interception, etc.
  • the UPF can receive user plane data from the DN, and send the user plane data to the terminal device through the AN device.
  • UPF can also receive user plane data from terminal equipment through AN equipment and forward it to DN.
  • the user plane network element may also be called a protocol data unit (protocol data unit, PDU) session anchor (PDU session anchor, PSA).
  • PDU protocol data unit
  • PSA protocol data unit
  • the user plane network element can be a user plane function (UPF), connecting gNB and data network.
  • UPF user plane function
  • PCF including user subscription data management function, policy control function, charging policy control function, quality of service (quality of service, QoS) control, etc.
  • the policy control network element may be a policy control function. It should be pointed out that the PCF in the actual network may also be divided into multiple entities according to the level or function, such as the global PCF and the PCF in the slice, or the session management PCF (Session Management PCF, SM-PCF) and the access management PCF ( Access Management PCF, AM-PCF).
  • Network slice selection function (network slice selection function, NSSF): mainly used to select a suitable network slice for the terminal business.
  • UDM responsible for managing terminal signing information. It is mainly used for UE subscription data management, including storage and management of UE ID, UE access authorization, etc.
  • DN mainly used for the operator's network that provides data services for the UE.
  • the Internet Internet
  • a third-party service network IP multimedia service (IP multi-media service, IMS) network, and the like.
  • IP multimedia service IP multi-media service, IMS
  • UDR user data is stored and retrieved through UDM
  • policy data is stored and retrieved by PCF
  • structured data and application data (including data packets used for application detection) of network capability opening functional entities are stored and retrieved.
  • NWDAF from each network function (network function, NF), such as policy control network element, session management network element, user plane network element, access management network element, application function network element (through network capability opening function network element ) to collect data, analyze and forecast.
  • network function such as policy control network element, session management network element, user plane network element, access management network element, application function network element (through network capability opening function network element ) to collect data, analyze and forecast.
  • the network functional entities of the control plane of the same network slice can discover each other through NRF, obtain the access address information of the other party, and pass the control
  • the plane signaling bus communicates directly with each other.
  • various network elements can communicate through interfaces.
  • the UE is connected to the gNB device through the radio resource control (radio resource control, RRC) protocol
  • the UPF, the gNB device, and the DN are connected through the user plane, and other devices can be connected through the control plane.
  • RRC radio resource control
  • the network architecture shown in Figure 1 may also include other network elements, such as authentication server function (authentication server function, AUSF) and other network elements or devices, which are not specifically limited in this application;
  • authentication server function authentication server function, AUSF
  • AUSF authentication server function
  • the network architecture shown in FIG. 1 is only an illustration, and the network architecture applicable to the embodiment of the present application is not limited thereto. Any network architecture capable of realizing the functions of the above-mentioned network elements is applicable to the embodiment of the present application;
  • the functions or network elements in the network architecture shown in FIG. 1 can be understood as network elements used to implement different functions, for example, they can be combined into network slices as required. These network elements can be independent devices, or can be integrated in the same device to achieve different functions, or can be network elements in hardware devices, or software functions running on dedicated hardware, or platforms (for example, cloud platform), this application does not limit the specific form of the above-mentioned network elements;
  • the mobile network can be divided into multiple tracking areas, and multiple cells with similar geographical location and frequent terminal movement are divided into the same tracking area (TA), and each TA can be distinguished from each other by tracking area identity (TAI).
  • TAI consists of mobile country code (MCC), mobile network code (mobile network code, MNC) and tracking area code (tracking area code, TAC).
  • MCC mobile country code
  • MNC mobile network code
  • TAC tracking area code
  • the network device responsible for mobility management will determine a registration area (RA) for the user equipment based on factors such as the wireless base station equipment it is connected to and the tracking area included in its own management scope.
  • RA may include one or more TAs, and in terms of form, RA is a list of one or more TAs.
  • the core network equipment When the user equipment is in the idle state, the core network equipment is not notified of cell handover. After the user equipment arrives at the target cell, if the user equipment detects that the TA where the target cell is located no longer belongs to the original RA, it initiates a registration update process. Notify the network equipment responsible for mobility management to leave the original registration area. Thereafter, the network device in charge of mobility management assigns a new RA to the user equipment after accepting the registration update of the user equipment.
  • network slice is a logical network with specific network characteristics, which can make the 5G mobile communication system meet the needs of network differentiation.
  • the 5G physical network can be abstractly divided into multiple network slices, and each network slice constitutes an end-to-end logical network, which is logically isolated from each other and does not affect each other.
  • the network characteristics of different network slices are different.
  • enhanced mobile broadband (eMBB) type network slices require the characteristics of supporting large bandwidth and low latency services; massive machine type connections (massive machine type connections) type connection (mMTC) network slice supports massive access and small bandwidth; ultra-high reliability and low latency connection (uRLLC) type slice has high reliability and low latency feature.
  • the services of each network slice are identified by Single-network slice selection assistance information (S-NSSAI).
  • S-NSSAI Single-network slice selection assistance information
  • the 5G network selects a network slice for the service according to the S-NSSAI carried in the registration request of the terminal device and the session establishment request, and transmits the customer's business data on the selected network slice.
  • a customer may order multiple network slices from an operator, and a terminal device may request access to multiple network slices at the same time.
  • an Internet of Vehicles terminal can simultaneously access three network slices of mMTC, eMBB, and uRLLC.
  • mMTC slices are used for daily vehicle failures.
  • eMBB slices are used for passenger instant message communication and online on-demand entertainment applications
  • uRLLC slices are used for non-line-of-sight communication applications for autonomous driving.
  • the terminal device may first choose to camp in a cell, and then send a registration request message to the core network device through the wireless device (eg, gNB), where the registration request message carries the network slice information (Requested NSSAI) of the terminal device to request access.
  • the Requested NSSAI is composed of one or more S-NSSAIs, which belong to the configured network slice (Configured NSSAI) configured for the terminal device in the current public land mobile network (PLMN). If the current PLMN is a Home public land mobile network (HPLMN), the S-NSSAI in the Configured NSSAI is the network slice (Subscribed S-NSSAI) signed by the terminal device.
  • vS-NSSAI public land mobile network
  • the communication service provided by the network slice in the VPLMN identified by the vS-NSSAI is the same or similar to the communication service provided by the network slice in the HPLMN identified by the contracted S-NSSAI of the terminal device in the HPLMN.
  • the terminal The Configured NSSAI of the device in the VPLMN includes one or more vS-NSSAI, and the Subscribed S-NSSAI of the HPLMN to which they are respectively mapped (Mapping).
  • the NSSF or AMF in the core network first confirms that the Requested NSSAI carried in the registration request message of the terminal device is the contracted network slice of the terminal device or the vS-NSSAI mapped to the contracted network slice; then, the NSSF or AMF in the core network According to the network slices supported by the TA currently accessed by the terminal device, the information of the network slice allowed to be accessed by the terminal device (Allowed NSSAI) can be determined, where the Allowed NSSAI includes one or more S-NSSAIs.
  • the base station will report to AMF the TAI of the tracking area to which the cell it manages belongs, and the list of S-NSSAI supported by this TA, so that AMF can obtain the network supported by each TA within its service range slice. Furthermore, each AMF sends the network slice supported by each TA within its service range to the NSSF, and the NSSF can obtain the network slice information supported by each TA in the entire PLMN and the TA information connected by each AMF.
  • AMF or NSSF can take the intersection of the S-NSSAI set supported by the TA where the UE is currently located and the Requested NSSAI of the UE, and determine it as the Allowed NSSAI. Finally, the terminal device can be successfully registered to the network slices included in the Allowed NSSAI. Subsequent terminal devices can establish Protocol data unit sessions (PDU sessions) through these network slices, and use these network slices to transmit service packets.
  • PDU sessions Protocol data unit sessions
  • the NSSF or AMF can also determine an RA for the terminal device, and the RA is a TA list including the currently accessed TA. For example, if the adjacent TA of the currently accessed TA can also support each network slice in the Allowed NSSAI, the adjacent TA and the currently accessed TA are included in the list of TAs that support the Allowed NSSAI, and finally the TA The list is determined as the RA registered by the UE this time. When the terminal device moves within the RA range, it can use the network slice in the Allowed NSSAI to establish a PDU session at any time. When a terminal device moves out of the RA range, or accesses a cell outside the RA range, it needs to re-register with the network.
  • the current agreement defines the working frequency bands used by 5G networks, of which N41, N78 and N79 are the three most commonly used 5G working frequency bands.
  • the N41 ranges around 2.5GHz
  • the N78 ranges around 3.5GHz
  • the N79 ranges around 4.8 to 4.9GHz.
  • the N41 and N78 frequency bands are relatively mature in technology, with wide penetration and coverage, and are the mainstream civilian 5G frequency bands.
  • the N41 can cover a large area in the way of macro base station deployment, and provide wireless access to eMBB network slices and mMTC network slices.
  • the N78 can be superimposed on the coverage of the N41 frequency band to provide wireless access to eMBB network slices with greater bandwidth for densely populated hotspot areas.
  • the N79 is suitable for use in special industrial scenarios and places, but its penetration and coverage capabilities are not as good as the previous two. It mainly provides wireless access to uRLLC network slices in parks and factories.
  • a wireless base station can access services through a wireless network provided by one or more divided cells (Cell). Each cell can only work on one frequency band, and each cell can only belong to one TA.
  • the network slicing capabilities supported by all cells in a TA may be the same. In other words, although different cells in a TA may work in different frequency bands, they should support the same one or more S-NSSAIs. Due to the limitation of the ability of cells in a TA to support network slicing, it often happens that a terminal device can access the network slice that the terminal device wants to use only when it registers with the network through a cell in a specific TA.
  • the slice tenant enterprise may also cause different AMFs in the same geographical area to support different network slices, such as the carrier's AMF support
  • the AMF of the enterprise can support the first network slicing to the third network slicing. Since the terminal device can only be registered with one AMF, it often happens that the terminal device can only be connected to the terminal when it is registered with a specific AMF. The network slice that the device wishes to use.
  • FIG. 2 is a schematic diagram of network slice deployment.
  • the network slice supported by TA#1 is ⁇ network slice 1, network slice 2 ⁇
  • the network slice supported by TA#2 is ⁇ network slice 1, network slice 2, network slice 3 ⁇
  • TA#3 supports The network slice of is ⁇ network slice 2, network slice 3 ⁇ . If the terminal device accesses the network to register through TA#1, the requested NSSAI of the terminal device is ⁇ network slice 1, network slice 2, network slice 3 ⁇ , then the Allowed NSSAI is ⁇ network slice 1, network slice 2 ⁇ , and RA is ⁇ TA #1,TA#2 ⁇ .
  • TA#2 Although TA#2 also supports network slice 3, the UE cannot use network slice 3 to establish a PDU session within the RA range. If the terminal device accesses the network to register through TA#2, the Allowed NSSAI is ⁇ network slice 1, network slice 2, network slice 3 ⁇ , and RA is ⁇ TA#2 ⁇ . At this time, the range of RA is relatively small, and the terminal device is in a small range. For internal mobility, frequent network registration is required, and the signaling load is heavy. It can be seen that the larger the number of slices contained in the allowed NSSAI, the smaller the corresponding RA. On the contrary, the smaller the number of slices included in the allowed NSSAI, the larger the corresponding RA, and the less likely it is to cause frequent network registration for small-scale movement.
  • FIG. 3 is another schematic diagram of network slice deployment.
  • TA#1 and TA#2 can be TAs covered by two access network devices working in different frequency bands.
  • network slice 1 is the public service network slice provided by the public network
  • network slice 2 is the campus
  • AMFs the coverage area is only the campus, and they are managed by two different AMFs.
  • RFSP radio access technology/frequency selection priority
  • the terminal device will be associated with a group of frequency points on the wireless device side according to the specific RFSP information, so that the terminal device performs cell selection or reselection according to the reselection priority of the specified group of frequency points, instead of relying on the information broadcast by the cell system
  • the signal strength of each frequency band is used for cell selection or reselection, so as to ensure that the terminal device can camp on the specified frequency according to the RFSP information. Therefore, after returning to the campus, the terminal devices in the campus can preferentially choose to camp in the cell of TA#2, while other non-campus terminal devices still camp in the cell of TA#1 in the same geographic location.
  • a terminal device in the campus has established a PDU session through network slice 1, and the terminal device wants to use network slice 2 at the same time in the campus, it needs to use ⁇ network slice 1, network slice 2 ⁇ as Requested NSSAI Initiate a registration request.
  • the first AMF can instruct the cell of TA#1 to carry the radio parameters corresponding to the above RFSP information in the radio resource control release (RRC Release) message, and then the terminal device can select TA#2 according to these parameters reside in the community.
  • the terminal device will first disconnect the radio resource control connection with the cell in TA#1, enter the RRC idle state, and then camp on the cell in TA#2 again.
  • the PDU session established through network slice 1 will be deactivated or interrupted. Therefore, when a terminal device wants to access a new network slice through re-registration, it may be necessary to replace the currently accessed TA or change the currently accessed AMF. At this time, the PDU session that the terminal device has established will be affected. Furthermore, the service of the terminal equipment will be affected.
  • the present application provides a method for determining a slice and an apparatus thereof, which can improve a scheme for a terminal device to access network slices during the process of a terminal device registering with a network, and improve user experience.
  • the AMF network element may be referred to as AMF
  • the NSSF network element may be referred to as NSSF
  • the UDM network element may be referred to as UDM
  • the PCF network element may be referred to as PCF
  • the NWDAF network element may be referred to as NWDAF
  • the SMF network element It can be referred to as SMF for short. That is, the AMF described in this application can be replaced by the mobility and access management function network element
  • the NSSF can be replaced by the network slice selection function network element
  • the UDM can be replaced by the unified data management network element
  • the NWDAF can be replaced by the network element.
  • the data analysis function network element and SMF can be replaced by the session management function network element.
  • FIG. 4 shows a schematic diagram of a slice-based communication method 400 provided by an embodiment of the present application.
  • the scenario corresponding to Figure 4 is: there is at least one network slice corresponding to (or associated with) the active session of the terminal device in the target network slice of the terminal device, and the tracking area before the handover of the terminal device does not fully support the terminal
  • the requested network slice carried by the device in the registration request message includes the following steps:
  • the first access and mobility management functional network element acquires information about a target network slice of a terminal device.
  • the target network slice includes the requested network slice of the terminal device, which is not supported by the current tracking area of the terminal device, but can be used by other tracking areas (for example, a tracking area of another frequency band that overlaps with the current tracking area of the terminal device) ) supported network slices.
  • the information of the target network slice can be target NSSAI.
  • the first access and mobility management functional network element may determine by itself, or receive the information of the target network slice from the network slice selection functional network element.
  • the first network element with the access and mobility management function may determine the target network slice according to the already used network slice in the first allowed network slice of the terminal device, and the used network slice may be The network slice for which the session has been established, the first allowed network slice is the allowed network slice saved by the first access and mobility management functional network element in the context of the terminal device.
  • the first access and mobility management functional network element adds the network slices in the first allowed network slices with established sessions, especially the network slices corresponding to the sessions with activated user planes, to the target network slices.
  • the network element with the first access and mobility management function can determine the target network slice according to the network slice to be used by the terminal device. network slices.
  • the first access and mobility management functional network element adds the network slice to be used to the target network slice. This will be further described in conjunction with FIG. 6 below.
  • the first access and mobility management function network element determines that at least one network slice in the target network slice corresponds to an active session of the terminal device.
  • the session in the active state may refer to the session in the active state on the user plane.
  • At least one network slice of the target network slice corresponds to an active session of the terminal device, and does not specifically mean that all network slices in the target network slice correspond to the active session of the terminal device.
  • a network slice corresponds to an active session of an end device.
  • the first network element with the access and mobility management function can acquire the auxiliary information attribute of the session that the terminal device has established in a single network slice of the current service network from the context of the terminal device, that is, the session has been established The network slice corresponding to the session.
  • the first access and mobility management function network element may obtain session status (for example, PDU session status) information from the registration request of the terminal device, and then determine the terminal according to the session status information
  • session status for example, PDU session status
  • the state of the established session of the device for example, the state of the session may include an activated state, a deactivated state, an activated state or a released state).
  • the first access and mobility management function network element may determine that at least one network slice in the target network slice corresponds to the active session according to the active session and the target network slice.
  • the network slice corresponding to the session in the active state combined with the network slices included in the target network slice, if at least one network slice corresponding to the session in the active state belongs to the target network slice, determine the At least one network slice of corresponding to an active session.
  • the allowed network slice is ⁇ network slice #1, network slice #2, network slice #3 ⁇
  • the network slice corresponding to the active session is ⁇ network slice #3 ⁇
  • the target network slice is ⁇ network slice #3, network slice #4 ⁇ , since network slice #3 in the network slice corresponding to the active session belongs to the target network slice, it can be determined that at least one network slice in the target network slice corresponds to the active session.
  • the network slice of the active session in the target network slice is from the allowed network slices, determining that at least one network slice in the target network slice corresponds to an active session is equivalent to determining that at least one of the allowed network slices A network slice corresponds to an active session.
  • the first access and mobility management function network element may also determine that at least one network slice in the allowed network slice corresponds to an active session through any of the above possible implementation methods according to the allowed network slice (allowed NSSAI). Acquiring the target network slice may be performed together with or after determining that at least one network slice in the allowed network slice corresponds to an active session.
  • the first access and mobility management functional network element sends instruction information to the first access network device to handover the active session to the cell supporting the tracking area of the target network slice.
  • the first access network device receives instruction information from the first access and mobility management function network element to hand over the active session to the cell supporting the tracking area of the target network slice.
  • the indication information is information of the target network slice, and at this time, the information of the target network slice implicitly indicates that the active session is handed over to a cell supporting the tracking area of the target network slice.
  • the indication information is independent indication information, and may be indicated by means of an indication bit of the indication information or the like.
  • the first access and mobility management functional network element may also send the information of the target network slice to the first access network device.
  • the indication information may be a handover indication (handover indication).
  • the first access and mobility management function network element will send the information of the target network slice to the first access network device.
  • the first access and mobility management function network element may use the information of the target network slice as implicit indication information, or additionally carry displayed indication information (for example, handover indication), so that the first access network device that receives the information It may be known that a handover needs to be initiated, so that the active session is handed over to a cell supporting the tracking area of the target network slice.
  • the network element with the first access and mobility management function can send the first access
  • the network device sends the information of the target network slice and the above handover instruction.
  • the first access and mobility management functional network element may send an N2 interface message to the first access network device, where the N2 interface message carries an active session handover to a cell that supports the tracking area of the target network slice The instruction information of and the information of the target network slice.
  • the N2 message may also carry a registration response message or a terminal device configuration update message sent by the first access and mobility management functional network element to the terminal device through the first access network device.
  • the registration response message indicates that the terminal device has successfully registered with the first access and mobility management functional network element.
  • the terminal device configuration update message is used to provide at least one of the latest allowed network slice and RA to the terminal.
  • the indication information does not indicate the specific session to be switched, but only indicates that the session needs to be switched. In other words, when there is a session that needs to be switched, the indication information will be sent, and the specific session to be switched is determined by the first access network device after receiving the indication information (for the detailed determination method, please refer to the relevant description in S502 below ).
  • the indication information may also instruct the first access network device to keep the terminal device in the current TA when it cannot find the target cell that satisfies the handover condition, and not to control the terminal device to reselect a cell that supports the target network slice through redirection, so as to Ensure that active sessions cannot be deactivated and interrupted.
  • the first access and mobility management function network element may send a message to the first access network device that the session will be active Stated session handover to the indication information of the cell supporting the tracking area of the target network slice.
  • the terminal device in the process of redirecting the session in which the terminal device is in an active state, the terminal device needs to disconnect and redirect the previous The RRC connection of the cell in the tracking area enters the RRC idle state, and then re-resides in the cell in the tracking area after redirection, so that the established session of the terminal device will be activated or interrupted.
  • This solution does not need to release RRC connection, but after the first access and mobility management function network element determines that at least one network slice in the target network slice corresponds to the active session of the terminal device, it sends the active session to the first access network device The session is handed over to the indication information of the cell supporting the tracking area of the target network slice, so as to complete the session handover. Therefore, this solution can improve the service stability of the terminal device, prevent the session of the terminal device in the active state from being interrupted when the terminal device accesses the cell that supports the target network slice of the terminal device and registers the network slice, and improves user experience.
  • the method 400 may also include any of the following manners:
  • the first access and mobility management functional network element may save the target network slice in the context of the terminal device, and after the session in the active state completes handover, the first access and mobility The management function network element receives the registration request message of the terminal device, and determines the second allowed network slice of the terminal device according to the requested network slice carried in the registration request message and the target network slice saved in the context of the terminal device.
  • a network slice belonging to both the requesting network slice and the target network slice may be selected to form a second permitted network slice.
  • the requested network slice carried in the registration request message is ⁇ network slice #1, network slice #2, network slice #3 ⁇ , and the network slice supported by the new current TA that the terminal enters after switching is ⁇ network slice #1 , network slice #2, network slice #3 ⁇ , the target network slice saved in the context of the terminal device is ⁇ network slice #2, network slice #3 ⁇ , then the second allowed network slice is ⁇ network slice #2, network slice #3 ⁇ , do not add network slice #1, which is also supported by the UE's new current TA in the requested network slice, to the second permitted network slice. That is to say, even if the current TA supports network slice #1, since the target network slice saved in the context of the terminal device does not include network slice #1, the second allowed network slice does not include network slice #1.
  • the second allowed network slicing is used by the terminal device to subsequently establish a session.
  • the first network element with the access and mobility management function saves the target network slice in the context of the terminal device, and then, the network element with the first access and mobility management function sends The entry and mobility management function network element sends context information.
  • the target network slice in the context information is used for the second access and mobility management functional network element to determine the second permitted network slice after the terminal device in the active state completes the handover and initiates a registration request.
  • the method 400 further includes: the first access and mobility management function network element sends RFSP information corresponding to the target network slice to the first access network device.
  • the first access network device receives RFSP information corresponding to the target network slice from the first access and mobility management functional network element.
  • the RFSP information is an RFSP index (index).
  • the RFSP information is used to determine a radio measurement instruction
  • the radio measurement instruction is used for the terminal device to discover a cell supporting the tracking area of the target network slice before switching an active session.
  • the RFSP information is determined by the first access and mobility management functional network element according to a local configuration policy.
  • the RFSP information is obtained by the first access and mobility management functional network element requesting the policy control network element.
  • the first access and mobility management function network element may also determine the allowed network slice, and then determine the corresponding registration area according to the allowed network slice, and set the target The network slice, the allowed network slice, or at least one piece of information in the registration area corresponding to the allowed network slice is sent to the terminal device.
  • the first access and mobility management functional network element may send a registration response message to the terminal device, where the registration response message carries at least one of the target network slice, the allowed network slice, or the registration area corresponding to the allowed network slice item information.
  • FIG. 5 shows a schematic diagram of a slice-based communication method 500 provided by an embodiment of the present application. As described below, the method 500 includes the following steps:
  • the first access network device receives information about a target network slice of a terminal device of a first access and mobility management functional network element.
  • the first access and mobility management function network element sends the information of the target network slice of the terminal device to the first access network device.
  • the first access and mobility management functional network element may send the information of the target network slice to the first access network device.
  • the first access network device determines an active session of a terminal device corresponding to at least one network slice in the handover target network slice.
  • the first access network device may receive indication information from the first access and mobility management function network element to switch the active session to a cell supporting the tracking area of the target network slice, and determine according to the indication information A session in an active state corresponding to at least one network slice in the target network slice is switched.
  • the indication information can be the information of the target network slice.
  • the information of the target network slice can be used as a trigger condition to trigger the first access network device that receives the target network slice information according to the context of the terminal device maintained by itself. , to determine whether there is currently an active session. If it exists, the first access network device may determine an active session of the terminal device corresponding to at least one network slice in the handover target network slice. Therefore, it can be understood that the information of the target network slice implicitly indicates that the active session is handed over to the cell supporting the tracking area of the target network slice.
  • the indication information may be an independent indication information, and may be indicated through an indication bit in the indication information or the like.
  • the indication information may be a handover indication (handover indication). Therefore, the first access network device can directly determine the active session of the terminal device corresponding to at least one network slice in the handover target network slice according to the indication information.
  • the first access and mobility management functional network element may send an N2 interface message to the first access network device, where the N2 interface message carries an active session handover to a cell that supports the tracking area of the target network slice The instruction information of and the information of the target network slice.
  • the N2 message may also carry a registration response message or a terminal device configuration update message sent by the first access and mobility management functional network element to the terminal device through the first access network device.
  • the registration response message indicates that the terminal device has successfully registered with the first access and mobility management functional network element.
  • the terminal device configuration update message indicates at least one of RA for providing the latest allowed network slice to the terminal.
  • the indication information does not indicate the specific session to be switched, but only indicates that the session needs to be switched. In other words, when there is a session that needs to be switched, the indication information will be sent.
  • the first access network device may determine to initiate a handover procedure.
  • the first access network device may obtain the network slice corresponding to the active session of the terminal device according to the context of the terminal device maintained by itself, and determine according to at least one network slice in the target network slice corresponding to the active session Switch active sessions, that is, determine which session needs to be switched. If the first access network device still keeps the terminal device in the current TA when it cannot find the target cell that satisfies the handover conditions, it does not control the terminal device to reselect a cell that supports target network slicing through redirection to ensure that the cell in the active state Sessions are not deactivated and interrupted.
  • the first access network device may determine that at least one network slice in the target network slice belongs to the network slice corresponding to the active session of the terminal device, and determine to switch the active session.
  • the target network slice is ⁇ network slice #1, network slice #2, network slice #3 ⁇ , and the network slice corresponding to the active session of the terminal device is ⁇ network slice #2 ⁇ , then the network slice can be determined
  • the session corresponding to #2 is an active session to be switched.
  • the first access network device may send the wireless measurement instruction of the terminal device to the terminal device (for example, send the wireless measurement instruction of the terminal device to the terminal device through a radio resource management reconfiguration message), and the terminal device sends the wireless measurement report to the first An access network device, if the wireless measurement report indicates that the signal strength of the cell supporting the tracking area of the target network slice reaches a preset threshold, the first access network device decides to start the handover.
  • the method 500 further includes: the first access network device determining the radio measurement instruction of the terminal device.
  • the radio measurement instruction is used to discover cells supporting the tracking area of the target network slice before switching the active session.
  • the first access network device determines the wireless measurement instruction according to the information of the target network slice.
  • the first access network device receives RFSP information corresponding to the target network slice from the first access and mobility management function network element, and then the first access network device Determine the wireless measurement command.
  • the registration response message sent by the first access and mobility management functional network element to the first access network device may carry the RFSP information corresponding to the target network slice.
  • the first access network device switches the active session to a cell supporting the tracking area of the target network slice.
  • the first access network device may send a handover request to the first access and mobility management function network element, which carries the information of the session to be handed over and the information of the target cell to be handed over, wherein the session to be handed over
  • the information of is the information of the active session
  • the information of the handover target cell is the cell supporting the tracking area of the target network slice.
  • the first access and mobility management function network element determines that the second access network device that manages the cell that supports the tracking area of the target network slice is connected to the second access and mobility management function network element, Then, a request message for creating a terminal device context is sent to the second access and mobility management function network element, wherein the context of the terminal device includes information about the target network slice, and then the second access and mobility management function network element sends a request message to the second access and mobility management function network element An access and mobility management functional network element sends a response message indicating that the context of the terminal device is created successfully.
  • the first access network device, the second access network device, the first access and mobility management function network element, and the second access and mobility management function network element jointly set the context of the active session Handover from the first access network device and the first access and mobility management functional network element to the second access network device and the second access and mobility management functional network element, so that the active session is switched to the supporting target A cell in the Tracking Area of a network slice.
  • the user plane path of the active session can still normally transmit the service packets of the terminal device during the handover process from the first access network device to the second access network device without interruption.
  • the first access network device determines the terminal device corresponding to at least one network slice in the handover target network slice after receiving information about the target network slice of the terminal device from the first access and mobility management function network element the active session of the terminal device, and hand over the active session of the terminal device to the cell supporting the tracking area of the target network slice. Furthermore, compared with the prior art (for example, through the method described in FIG. 2 or FIG. 3 above), in the process of redirecting the session in which the terminal device is in an active state, the terminal device needs to disconnect and redirect the previous The RRC connection of the cell in the tracking area enters the RRC idle state, and then re-resides in the cell in the tracking area after redirection, so that the established session of the terminal device will be activated or interrupted.
  • This solution does not need to release RRC connection, but the first access network device switches the active session of the terminal device to the tracking area supporting the target network slice after determining that at least one network slice in the target network slice corresponds to the active session of the terminal device district. Therefore, this solution can improve the service stability of the terminal device, prevent the active session of the terminal device from being interrupted when the terminal device accesses the cell that supports the target network slice of the terminal device and registers the network slice, and improves user experience.
  • FIG. 6 shows a schematic diagram of a slice-based communication method 600 provided by an embodiment of the present application. As follows, the method 600 includes the following steps:
  • the network device acquires at least one item of information about a network slice that has been used by the terminal device or a network slice that is about to be used by the terminal device, and information about a network slice requested by the terminal device.
  • the network device may include a network element with network slice selection function, or a network element with access and mobility management function.
  • the network device acquires at least one item of information on the network slice that has been used or the network slice to be used, which may include at least one of the following methods:
  • the network device can determine the information of the used network slice according to the session state information of the terminal device, where the session state information can be carried in the registration request message sent by the terminal device to the access and mobility management function network element among.
  • the network device may determine the established session through the session state information, that is, determine that the terminal device has established the session. For example, when the session status information indicates active (active), it means that the terminal device has established a session. Then, the network device may determine the network slice corresponding to the established session according to the context of the terminal device, that is, the network slice that has been used.
  • the network equipment includes network elements with access and mobility management functions.
  • the network device can determine the information of the network slice to be used according to the requested network slice (requested NSSAI) of the terminal device and the fourth network slice in the context of the terminal device stored by the network device; or, the network device can also select a function from the network slice
  • the network element requests the information of the fourth allowed network slice, and determines the information of the network slice to be used according to the requested network slice of the terminal device and the fourth allowed network slice; wherein, the requested network slice can be carried in the terminal device to access and mobility In the registration request message sent by the management function network element.
  • the network device may select a network slice that does not belong to the fourth allowed network slice among the requested network slices to form a network slice to be used.
  • the network device can determine that it is about to use The network slice of is ⁇ network slice #1 ⁇ .
  • the network device may receive communication analysis result information from the terminal device of the network element with the network data analysis function, and determine the information of the network slice to be used according to the communication analysis result information.
  • the network device when the network device includes a network element with the network slice selection function, the network device may receive the network slice already used by the terminal device or the network slice to be used by the terminal device from the network element with the access and mobility management function. At least one item of information in the network slice.
  • the network device when the network device includes a network element with a network slice selection function, the network device receives a network slice selection from an access and mobility management function network element (hereinafter referred to as the first access and mobility management function network element) After the request, if the network device judges that the tracking area where the terminal device is currently located supports the network slice requested by the terminal device, but the first access and mobility management function network element does not support the network slice requested by the terminal device, the network device can determine a connection A new access and mobility management function network element (subsequently referred to as a second access and mobility management function network element) that is in the tracking area where the terminal device is currently located and supports the terminal device's request for network slicing, and sends the first The information of the second access and mobility management function network element is sent to the first access and mobility management function network element; after that, the first access and mobility management function network element forwards the registration request message of the terminal device to the second access and mobility management function network element to process, wherein, the description of the registration request message can refer to the description of the
  • the network device determines a first allowed network slice of the terminal device according to at least one of the already used network slice or the soon to be used network slice, and the requested network slice.
  • the network device may determine the first network slice according to at least one of the network slice that the terminal device has used or the network slice that the terminal device will use, and the requested network slice carried in the registration request message of the terminal device. Allows for network slicing.
  • the network device may select the network slices in the requested network slice that belong to the already used network slice or the network slice to be used to form the first permitted network slice.
  • the network device can use the network slice (for example, ⁇ network slice #3 ⁇ ) and the network slice to be used (eg, ⁇ network slice #2 ⁇ ), and the requested network slice ⁇ eg, network slice #1, network slice #2, network slice #3 ⁇ , determines the first allowed network slice for the end device (eg, ⁇ network slice #2, network slice #3 ⁇ ).
  • the TA where the terminal device is currently located also supports network slice #1 in the requested network slice, it is not included in the first allowed network slice because it does not belong to the network slice that has been used or the network slice to be used.
  • the network device determines the first permission It is also excluded when the network slice is used, or it can also be understood as filtering it, so that each network slice in the finally determined first allowed network slice belongs to the network slice or terminal device that has been used by the terminal device The network slice to be used.
  • the allowed network slices determined in this way comprise a smaller number of network slices than the allowed network slices determined in the prior art manner.
  • the network device may determine the first allowed network slice according to the requested network slice carried in the registration request message of the terminal device, the network slice already used by the terminal device, and the network slice supported by the current tracking area of the terminal device.
  • the network device may select a network slice that belongs to at least one of the already used network slice or the network slice to be used, and the network slice that belongs to the current tracking area support of the terminal device to form the first allowed network slice.
  • the network device can track according to the network slice that the terminal device has used (for example, ⁇ network slice #3 ⁇ ) and the network slice that will be used (for example, ⁇ network slice #2 ⁇ ), and the current location of the terminal device
  • the network slice supported by the zone is ⁇ network slice #3, network slice #4 ⁇ , and the first allowed network slice (for example, ⁇ network slice #3 ⁇ ) of the terminal device is determined.
  • the terminal device has completed network registration with the network device, at least one network slice in the requested network slice carried in the network registration update request sent by the terminal device to the network device is not included in the previously determined (saved in the context of the terminal device) allowed network slices, then at least one network slice that is not included in the previously determined (stored in the context of the terminal device) allowed network slices in the request network slice is used as the terminal device
  • the network slice that is expected to be used for example, the tracking area before the handover of the terminal device only supports the requested network slice that contains the previously determined allowed network slice, but the tracking area after the handover of the terminal device supports the previously determined allowed network slice, then the Contains at least one network slice in the previously determined request network slice that allows network slices as the network slice that the terminal device expects to use), that is, the network slice that is about to be used, added to the previously determined (saved in the context of the terminal device) Allowed network slicing, get the first allowed network slice.
  • the third possible implementation can be combined with the first two possible implementations.
  • the allowed network slices received by the terminal device after the last network registration include ⁇ network slice #1, network slice #3 ⁇ .
  • the last registered TA does not support network slice 4, so network slice 4 is not included in the allowed network slices.
  • the terminal device initiates a registration update process in the new TA, and the requested network slice carried in the registration update message is ⁇ network slice #3, network slice #4 ⁇ ). Since the new TA supports network slice 3 and network slice 4, the network device can use the requested network slice carried in the network registration update message, the allowed network slice received by the terminal device after the last network registration, and the current location of the terminal device.
  • Network slices supported by the tracking area determine the network slice to be used (for example, ⁇ network slice #4 ⁇ ), and then add it to the previously determined allowed network slices including ⁇ network slice #1, network slice #3 ⁇ , determine the terminal The device's latest first allowed network slice (eg, ⁇ network slice #1, network slice #3, network slice #4 ⁇ ).
  • the terminal device still uses the network slice contained in the requested network slice to initiate a registration request, and the network device can determine that before The determined (saved in the context of the terminal device) allowed network slice in the network slice does not have an ongoing session. If the release time of the above-mentioned released session exceeds the preset threshold, the network device will use the network slice The first allowed network slice is obtained by deleting or eliminating the previously determined allowed network slices (stored in the context of the terminal device).
  • the third possible implementation can be combined with the first three possible implementations.
  • the network device may use the network slice corresponding to the released session (for example, ⁇ network slice #3 ⁇ ), the network slice ⁇ network slice #3, network slice #4 ⁇ requested by the terminal device, and the previously determined allowed Among the network slices (for example, ⁇ network slice #3, network slice #4 ⁇ ), determine the first allowed network slice (for example, ⁇ network slice #4 ⁇ ) of the terminal device.
  • the TA where the terminal device is currently located also supports network slice #3 in the requested network slice, it is not included in the first permitted network slice because it does not belong to the network slice that has been used or the network slice to be used.
  • the network device may obtain the first allowed network slice through the network element with the network slice selection function.
  • the network device may further determine the registration area corresponding to the first allowed network slice according to the first allowed network slice and the tracking area where the terminal device is currently located, where the registration area is the tracking area where the terminal device is currently located, and the tracking area corresponding to the The tracking areas are adjacent or similar to other tracking areas that support the first permitted network slice.
  • the network device sends first information allowing network slicing.
  • the network device may send the first network slicing-allowed information to the access and mobility management function network element;
  • the network device may send the first information allowing network slicing to the terminal device.
  • the network device may send a registration response message or a terminal device configuration update message to the terminal device, where the registration response message or the terminal device configuration update message carries the first allowed network slice or at least an item of information.
  • the method 600 further includes: the network device acquiring information about network slices supported by the tracking area where the terminal device is located.
  • the network device can acquire information about the network slice supported by the tracking area where the terminal device is located through the access and mobility management function network element.
  • the network device can obtain information about network slices supported by the tracking area where the terminal device is located through the access network device.
  • the method 600 further includes: the network device according to at least one of the network slices already used or the network slices to be used, and Requesting a network slice determines the target network slice for the end device.
  • This approach is also applicable to the scenario of determining the target network slice in other embodiments of the present application. That is to say, in step 401 in FIG. 4 , the access and mobility management network element can also obtain the information of the target network slice in the following manner.
  • the network device may select network slices that belong to at least one of the network slices that have been used or the network slices that will be used in the requested network slices to form the target network slices.
  • the target network slice includes the requested network slice of the terminal device, which is not supported by the current tracking area of the terminal device, but can be used by other tracking areas (for example, a tracking area of another frequency band that overlaps with the current tracking area of the terminal device) ) supported network slices.
  • the information of the target network slice can be target NSSAI.
  • the target network slice includes the network slice that the terminal device has used in the allowed network slice saved in the context, and the network slice that will be used soon, wherein the network slice that has been used may be the network slice corresponding to the session that the terminal device has established.
  • the network slice used can be the network slice of the session that the terminal device expects to establish; in addition, the session that the terminal device expects to establish can be a session that the terminal device expects to establish and has not yet been established, or it can be released, but the terminal device The session to be established (for example, a Business Continuity Mode 2 or Mode 3 session).
  • the network device can obtain the previously saved allowed network slices of the terminal device, if one or more of the requested network slices carried in the registration request message initiated by the terminal device If the network slice does not belong to the above allowed network slices, then the one or more network slices are the network slices to be used, and the network device can choose to request at least one of the network slices that have already been used or the network slices that will be used. The network slices of items that make up the target network slice.
  • the target network slice may also include at least one network slice not supported by the current tracking area of the terminal device.
  • the network slice supported by the TA where the terminal device is currently located is ⁇ network slice #2, network slice #3, network slice #4 ⁇
  • the allowed network slices of the terminal device previously saved by the network device are ⁇ network slice #3, Network slice #4 ⁇
  • the requested network slice is ⁇ network slice #1, network slice #2, network slice #4 ⁇ .
  • the network device determines that the network slice to be used is ⁇ network slice #1, network slice #2 ⁇ , the already used network slice is ⁇ network slice #3 ⁇ , and the target network slice is ⁇ network slice #1, network slice #2, Network slicing #3 ⁇ .
  • the network device may determine the target network slice according to the network slices already used in the allowed network slices saved in the context of the terminal device.
  • the network device can select the network slice that belongs to the network slice already used by the terminal device in the allowed network slice saved in the context of the terminal device as the target network slice, or the network device can exclude the allowed network slice saved in the context of the terminal device In the network slice that does not belong to the network slice already used by the terminal device, determine the target network slice.
  • the network device may determine the target network slice according to the network slices already used in the allowed network slices stored in the context of the terminal device, and the network slices to be used by the terminal device.
  • the network slice supported by the TA where the terminal device is currently located is ⁇ network slice #2, network slice #3, network slice #4 ⁇
  • the allowed network slice of the terminal device previously saved by the network device is ⁇ network slice #3, network slice #4 ⁇ Slice #4 ⁇
  • the requested network slice is ⁇ network slice #1, network slice #2, network slice #3, network slice #4 ⁇ .
  • the network device determines that the network slice to be used is ⁇ network slice #1, network slice #2 ⁇ , the already used network slice is ⁇ network slice #3 ⁇ , and the target network slice is ⁇ network slice #1, network slice #2, Network slicing #3 ⁇ .
  • the network device excludes the network slices that do not belong to the network slices already used by the terminal device and the network slices that do not belong to the network slices to be used (for example, ⁇ network slice#4 ⁇ ) saved in the context of the terminal device. , forming the target network slice.
  • the network device may also receive the information of the target network slice from the network element with the network slice selection function.
  • the terminal device determines the target network slice in the current registration area. If the terminal device changes the tracking area and the changed tracking area fully supports the target network slice, then the target network slice and the changed tracking area
  • the (first) allowed network slices of the end devices are the same. Therefore, the implementation manner of determining the target network slice may be similar to the above manner of determining the allowed network slice, which will not be repeated here.
  • the method 600 further includes: the network device receives a second permitted network slice from a terminal device of a second network slice selection function network element, Afterwards, the network device selects a network slice belonging to at least one of the already used network slice or the network slice to be used from the second permitted network slice to form a third permitted network slice of the terminal device.
  • the second allowed network slice may be determined by the second network slice selection function network element through the existing technology, that is, the second network slice selection function network element according to the requested network slice carried in the registration request message of the terminal device, and the terminal device It is determined by the network slicing supported by the registration area where it is located.
  • the network device may send information about the third allowed network slicing to the terminal device.
  • the second allowed network slice is ⁇ network slice #1, network slice #2, network slice #3, network slice #4 ⁇
  • the already used network slice is ⁇ network slice #2, network slice #3 ⁇
  • the network slice to be used is ⁇ network slice #1 ⁇
  • the third allowed network slice is ⁇ network slice #1, network slice #2, network slice #3 ⁇ .
  • At least one of the network slices that have been used by the terminal device or the network slices that are about to be used by the terminal device refers to the situation that only the network slices that have been used by the terminal device are included, and At the same time, it includes the network slices that have been used by the terminal device and the network slices that will be used by the terminal device.
  • the network device After the network device obtains at least one item of information about the network slice that the terminal device has already used or the network slice that the terminal device will use soon, and the requested network slice information of the terminal device, it can determine the terminal according to the above information.
  • the first allowed network slicing or the third allowed network slicing of the device and sends the information of the first allowed network slicing or the third allowed network slicing information. Due to the processing in this embodiment, the number of network slices contained in the first allowed network slice or the third allowed network slice is reduced, so the appropriate allowed network slice can be determined according to the communication requirements of the terminal device, and the corresponding allowed network slice can be realized.
  • the range of the registration area is as large as possible to reduce the signaling load during the movement of the terminal equipment.
  • the method 600 may further include: the network device acquires information about the first rejected network slice of the terminal device, and then the network device deletes the network slice supported by any tracking area in the registration area of the terminal device in the first rejected network slice , to obtain the second rejected network slice of the terminal device, wherein the registration area is determined according to the above-mentioned third allowed network slice, and the second rejected network slice indicates that the terminal device is denied access to the second rejected network slice in the current registered area Network slicing.
  • the network device may directly determine the information of the second rejected network slice without first obtaining the information of the first rejected network slice of the terminal device.
  • the information of the second rejected network slice is used to indicate that the terminal device is rejected in the current registration area to request access to the network slice in the second rejected network slice, and the information of the second rejected network slice excludes the information in the registered area of the terminal device Network slicing supported by any tracking area of .
  • the first rejected network slice is ⁇ network slice #1, network slice #2, network slice #3, network slice #4 ⁇
  • the network slice supported by a tracking area in the registration area is ⁇ network slice #2 , network slice #3 ⁇
  • the second rejected network slice is ⁇ network slice #1, network slice #4 ⁇ .
  • the foregoing manner of determining the rejection of the network slice is not limited to determining the third permitted network slice through the foregoing manner.
  • the network device may send the second network slicing rejection information to the terminal device.
  • the network device may send a registration response message or a configuration update message of the terminal device to the terminal device, where the registration response message indicates that the terminal device has registered successfully, and may also carry information about the second network slice rejection.
  • the terminal device configuration update message indicates that it is used to provide the terminal with at least one of the latest allowed network slice and RA, and may also carry information about the second denied network slice.
  • the rejected network slice of the terminal device can contain fewer network slices, and the range of network slices that the terminal device can use can be expanded as much as possible, thereby expanding The range of the corresponding registration area reduces the signaling load during the mobile process of the terminal.
  • FIG. 7 shows a schematic diagram of a slice-based communication method 700 provided by an embodiment of the present application.
  • FIG. 7 will be described in conjunction with FIG. 4 and FIG. 5 .
  • the method 700 includes the following steps:
  • the terminal device sends a first registration request message to a first access and mobility management functional network element.
  • the first access and mobility management function network element receives the first registration request message from the terminal device.
  • the first registration request message may include a requested network slice (requested NSSAI) of the terminal device.
  • requested NSSAI requested network slice
  • the first access and mobility management functional network element sends a slice selection request message to the network slice selection functional network element.
  • the network element with the network slice selection function receives the slice selection request message from the first access and mobility management function network element.
  • the network element with the first access and mobility management function may confirm that each network slice in the requested network slice is a network slice subscribed by the terminal device, or that the network slice subscribed by the terminal device is mapped to the network slice that the terminal device currently visits.
  • the first access and mobility management function network element may determine the network slice that has been used by the terminal device or the network slice to be used by the terminal device;
  • the first access and mobility management function network element may Send a slice selection request message to the network element with the network slice selection function, and request the network element with the network slice selection function to determine the target network slice (target NSSAI) and the allowed network slice (allowed NSSAI) of the terminal device for the terminal device, wherein the slice selection request message not only It carries information such as the current tracking area of the terminal device and the network slice requested by the terminal device, and may also carry at least one item of information about the network slice that has been used or the network slice that is about to be used.
  • the first access and mobility management function network element can determine the description of the network slice that has been used or the network slice to be used, and can refer to the network device in S601 to obtain the related description of the network slice that has been used or the network slice to be used , for the sake of brevity, this application does not repeat them here.
  • the first access and mobility management functional network element independently performs the step of network slicing to determine the allowed network slice and target network slice of the terminal device, the first access and mobility management will not be performed
  • the functional network element sends a slice selection request message to the network slice selection functional network element.
  • the first access and mobility management function network element or the network slice selection function network element determines a target network slice of the terminal device.
  • the first access and mobility management function network element or the network slice selection function network element may determine the terminal device according to at least one of the network slice that has been used by the terminal device or the network slice that will be used soon, and requests the network slice The target network slice of .
  • the network element with network slice selection function may send at least one item of information in the target network slice to the first access and mobility management function network element through a network slice selection response message .
  • the network slicing selection response message may also include information about the allowed network slicing of the terminal device requesting registration this time.
  • the first access and mobility management functional network element or the network slice selection functional network element may determine the terminal device For the description of the target network slice, refer to the relevant description of the network device determining the target network slice of the terminal device according to at least one of the already used network slice or the network slice to be used in the above S603, and requesting the network slice. For the sake of brevity, This application does not repeat it here. If the network slice selection function network element determines the target network slice of the terminal device, then the first access and mobility management function network element obtains the target network slice of the terminal device from the network slice selection function network element through the network slice selection response message.
  • the first access and mobility management functional network element may record the target network slice in the context of the terminal device.
  • the network element with the network slice selection function determines that the tracking area where the terminal device is currently located supports the network slicing requested by the terminal device, but the network element with the first access and mobility management function does not support the network slice requested by the terminal device.
  • the network element with the network slice selection function can determine a second access and mobility management function network element that connects to the tracking area where the terminal device is currently located and supports the terminal device's request for network slicing.
  • the information of the access and mobility management function network element is sent to the first access and mobility management function network element; after that, the first access and mobility management function network element forwards the registration request message of the terminal device to the second access and the mobility management function network element for processing; if the network slice selection function network element judges that the tracking area where the terminal device is currently located does not support the network slice requested by the terminal device, the network slice selection function network element can determine the target network slice of the terminal device, and The information of the target network slice of the terminal device is returned to the first access and mobility management functional network element.
  • the first access and mobility management function network element determines that at least one network slice in the target network slice corresponds to an active session of the terminal device.
  • the first access and mobility management functional network element determines the active session of the terminal device corresponding to at least one network slice in the target network slice.
  • the functional network element determines that at least one network slice in the target network slice corresponds to the relevant description of the session in the active state of the terminal device. For the sake of brevity, this application does not repeat it here.
  • the first access and mobility management functional network element sends instruction information to the first access network device to switch the active session to the cell supporting the tracking area of the target network slice.
  • the first access network device receives instruction information from the first access and mobility management function network element to hand over the active session to the cell supporting the tracking area of the target network slice.
  • the first access and mobility management functional network element may also send a first registration response message to the terminal device through the first access network device, the first registration response message indicates that the terminal device has successfully registered, and may carry the current Allowed network slice of the terminal device requesting registration, or at least one item of information in the registration area.
  • the registration response message may also carry a network slice rejection. For example, rejecting a network slice is a network slice that is not supported by the current registration area of the terminal device in the requested network slice, which means rejecting the terminal device's continued request to access the network slice in the rejected network slice in the current registration area.
  • the first access and mobility management function network element sends an N2 interface message to the first access network device, and sends the first registration response message to the terminal device, which may be encapsulated in the N2 interface message for transmission.
  • the N2 interface message carries the target network slice.
  • the N2 interface message may also carry at least one item of indication information and RFSP information corresponding to the target network slice.
  • the RFSP information corresponding to the target network slice is determined by the first access and mobility management function network element according to the local configuration policy, or is obtained by the first access and mobility management function network element requesting the policy control function network element .
  • the RFSP information is an RFSP index (index).
  • the first access network device determines to switch the active session of the terminal device to the cell supporting the tracking area of the target network slice.
  • the first access network device may receive an instruction from the first access and mobility management functional network element to switch the active session of the terminal device to a cell that supports the tracking area of the target network slice through the above step S705 information, and according to the indication information, it is determined to hand over the active session of the terminal device to the cell supporting the tracking area of the target network slice.
  • the present application does not repeat the relevant description of the indication information of the cell in the district.
  • the first access network device determines, according to the indication information carried in the N2 interface message, to switch the active session of the terminal device to the cell supporting the tracking area of the target network slice.
  • the first access network device may generate a measurement configuration message for the terminal device according to the RFSP index corresponding to the target network slice carried in the N2 interface message.
  • the first access network device sends a measurement configuration message to the terminal device.
  • the terminal device receives the measurement configuration message from the first access network device.
  • the first access network device may send a measurement configuration message to the terminal device through a radio resource management reconfiguration message, in which the wireless parameters carried instruct the terminal device to measure the frequency band of the adjacent tracking area cell of the tracking area where the terminal device is located. Signal quality. ,
  • the first access and mobility management function network element or the network slice selection function network element determines that the tracking area #3 where the terminal device is currently located does not support the target network slice, but covers the same area as the tracking area #3 or surrounding areas Tracking area #4 and tracking area #5 support target network slicing, or tracking area #4 and tracking area #5 adjacent to tracking area #3 support target network slicing, then the wireless parameters carried in the measurement configuration message instruct the terminal device to measure and track The signal quality of the frequency band where the cell in area #4 or the cell in tracking area #5 is located.
  • the terminal device sends a measurement result message to the first access network device.
  • the first access network device receives the measurement result message from the terminal device.
  • the first access network device makes a handover decision.
  • the first access network device may decide to start handover.
  • the first access network device sends a handover request message to the first access and mobility management functional network element.
  • the first access and mobility management function network element receives the handover request message from the first access network device.
  • the first access network device determines that switching the active session of the terminal device to the target cell needs to be controlled by a network element of the core network, and sends a handover request to the first access and mobility management function network element, which carries a wait
  • the information of the handover session and the information of the handover target cell (for example, the information of the handover target cell includes the identification of the tracking area TA to which the target cell belongs and the identification of the second access network device that manages the ownership of the target cell).
  • the session may be information of sessions that have been respectively established through network slice #3 and network slice #4.
  • the first access and mobility management function network element transfers the context of the terminal device to the second access and mobility management function network element.
  • the first access and mobility management function network element After the first access and mobility management function network element receives the handover request message, it determines the second access network device and the second The access and mobility management function network element is connected, and then a request message for creating a terminal device context is sent to the second access and mobility management function network element, wherein the message carries the terminal device context, and the terminal device context includes For information about the target network slice, the second access and mobility management function network element responds to the first access and mobility management function network element with a response message that the context of the terminal device is successfully created.
  • the first access network device, the second access network device, the first access and mobility management function network element, the second access and mobility management function network element, and the session management function network element jointly perform activation Stateful session switching.
  • the first access network device, the second access network device, the first access and mobility management functional network element, the second access and mobility management functional network element, and the session management functional network element may cooperate to The context of the active session is switched from the first access network device and the first access and mobility management functional network element to the second access network device and the second access and mobility management functional network element.
  • the session management function network element controls the first access network device, the second access network device, and the user plane function network element to switch the user plane path of the active session from the first access network device to the second access network device. network equipment. Therefore, the session in the active state can still transmit the service packets of the terminal device normally during the switching process, and the session will not be interrupted.
  • the first access and mobility management function network element may send a message to the first access network device that the session will be active Stated session handover to the indication information of the cell supporting the tracking area of the target network slice.
  • the terminal device in the process of redirecting the session in which the terminal device is in an active state, the terminal device needs to disconnect and redirect the previous The RRC connection of the cell in the tracking area enters the RRC idle state, and then re-resides in the cell in the tracking area after redirection, so that the established session of the terminal device will be activated or interrupted.
  • This solution does not need to release RRC connection, but after the first access and mobility management function network element determines that at least one network slice in the target network slice corresponds to the active session of the terminal device, it sends the active session to the first access network device The session is handed over to the indication information of the cell supporting the tracking area of the target network slice, so as to complete the session handover. Therefore, this solution can improve the service stability of the terminal device, prevent the session of the terminal device in the active state from being interrupted when the terminal device accesses the cell that supports the target network slice of the terminal device and registers the network slice, and improves user experience.
  • the method also includes:
  • the terminal device sends a second registration request message to the second network element with the access and mobility management function.
  • the second access and mobility management function network element receives the second registration request message from the terminal device.
  • the terminal device finds that the currently accessed cell does not belong to the original registration area, so it sends a second registration request message to the second access and mobility management functional network element through the second access network device.
  • the registration request message carries the requested network slice. After the terminal device leaves the original registration area, it can try to register as many network slices as possible.
  • the second network element with the access and mobility management function or the network element with the network slice selection function determines the allowed network slice of the terminal device.
  • the second access and mobility management function network element receives the registration request after the handover of the terminal device, and uses the target network slice recorded in the context of the terminal device to determine the network slice or terminal already used by the terminal device At least one of the network slices to be used by the device, and then according to at least one of the network slices already used by the terminal device or the network slices to be used by the terminal device, and requesting network slices to determine the first allowed network slice of the terminal device, and then Determine the tracking area corresponding to the allowed network slice, and the registration area corresponding to the allowed network slice.
  • the network element with the second access and mobility management function or the network slice selection function determines the terminal device according to at least one of the network slice that the terminal device has used or the network slice that the terminal device will use, and requests the network slice
  • the relevant description of the network device determining the first allowed network slice of the terminal device according to at least one of the already used network slice or the network slice to be used in S602 above, and requesting the network slice , for the sake of brevity, the present application will not repeat them here.
  • the second access and mobility management functional network element sends a second registration response message to the terminal device.
  • the terminal device receives the second registration response message from the second access and mobility management functional network element.
  • the second access and mobility management function network element may send a second registration response message to the terminal device through the second access network device, and the registration response message may carry information allowing network slicing, or information allowing network slicing Information about the registration area corresponding to the allowed network slicing.
  • FIG. 8 shows a schematic diagram of a slice-based communication method 800 provided by an embodiment of the present application.
  • the difference between Fig. 8 and Fig. 7 is that the method shown in Fig. 7 is applicable to the solution that needs to change the access and mobility management function network element, and the method shown in Fig. 8 is applicable to the solution that does not need to change the access and mobility management function network element. Yuan plan.
  • the first access and mobility management function network element may determine the active session of the terminal device corresponding to at least one network slice in the handover target network slice.
  • the method 800 includes the following steps:
  • the terminal device sends a first registration request message to a network element with an access and mobility management function.
  • the access and mobility management functional network element receives the first registration request message from the terminal device.
  • the first registration request message may include the request network slice of the terminal device.
  • the access and mobility management functional network element sends a slice selection request message to the network slice selection functional network element.
  • the network element with the network slice selection function receives the slice selection request message from the network element with the access and mobility management function.
  • the access and mobility management function network element may confirm that each network slice in the requested network slice is a network slice subscribed by the terminal device, or that the network slice subscribed by the terminal device is mapped to the network slice of the network currently visited by the terminal device ; After that, the access and mobility management function network element can determine the network slice that has been used or the network slice to be used; finally, the access and mobility management function network element can send a slice selection request message to the network slice selection function network element, Request the network slice selection function network element to select a network slice for the terminal device.
  • the slice selection request message not only carries information such as the current tracking area of the terminal device and the requested network slice of the terminal device, but also carries the network slice that has been used or will be used soon. At least one item of information in the network slice.
  • the access and mobility management function network element can determine the description of the network slice that has been used or the network slice to be used, and can refer to the network device in S601 to obtain the related description of the network slice that has been used or the network slice to be used. For brevity, this application will not repeat them here.
  • the network element that does not perform the access and mobility management function sends a slice selection request to the network element with the network slice selection function information.
  • the access and mobility management function network element or the network slice selection function network element determines a target network slice of the terminal device.
  • the access and mobility management function network element or the network slice selection function network element may determine the target of the terminal device according to at least one of the network slice that the terminal device has used or the network slice that will be used, and request the network slice Network slicing.
  • the access and mobility management function network element or the network slice selection function network element determines the target network of the terminal device according to at least one of the network slice that the terminal device has used or the network slice that is about to be used, and requests the network slice
  • the access and mobility management function network element or the network slice selection function network element determines the target network of the terminal device according to at least one of the network slice that the terminal device has used or the network slice that is about to be used, and requests the network slice
  • the description of slicing refer to the relevant descriptions of the network device determining the target network slicing of the terminal device according to at least one of the network slicing already used or the network slicing to be used in S603 above, and requesting the network slicing. I won't go into details here.
  • the access and mobility management function network element or the network slice selection function network element may also determine that the allowed network slice of the terminal device requesting registration this time remains unchanged, and the registration area corresponding to the allowed network slice does not change. Change.
  • the access and mobility management function network element or the network slice selection function network element may also determine that the allowed network slice of the terminal device registered this time no longer includes the network slice of the session that has been released for a long time , containing only network slices that still have ongoing sessions.
  • the specific description of the access and mobility management functional network element or the network slice selection functional network element determining the allowed network slicing of the terminal device registered this time can refer to the network device in S602 above according to the network slice that has been used or the network slice that is about to be used. For the sake of brevity, the present application will not describe in details about at least one item in the network slice and the related description of requesting the network slice to determine the first allowed network slice of the terminal device.
  • the access and mobility management function network element or the network slice selection function network element may also use the network slice of the soon-to-be-released session as the network slice to be used by the terminal device (that is, it may be used to establish a new The network slice of the session), at least one of the network slice that the terminal device has used and the network slice that is about to be used, and the request network slice determine the allowed network slice of the terminal device.
  • the registration area corresponding to the allowed network slice no longer includes a tracking area that supports the target network slice, and at the same time, the allowed network slice that supports the terminal device but does not match any tracking area in the registered area Adjacent tracking areas are also not included in the registration area.
  • the access and mobility management function network element obtains the RFSP information corresponding to the target network slice by the policy control function network element.
  • the access and mobility management function network element may request the policy control function network element to acquire the RFSP information corresponding to the target network slice.
  • the RFSP information corresponding to the target network slice is determined by the access and mobility management functional network element according to a local configuration policy, and S804 does not need to be performed.
  • this step can also be applied in the method 700 .
  • it may be executed after S703 in FIG. 7 .
  • the access and mobility management functional network element sends target network slice information to the first access network device.
  • the first access network device receives the target network slice information from the access and mobility management functional network element.
  • the first access network device receiving the target network slice information from the first access and mobility management function network element
  • the present application does not describe in the instruction information of switching the active session to the cell supporting the tracking area of the target network slice that the instruction information is the information of the target network slice.
  • the first access network device determines an active session of the terminal device corresponding to at least one network slice in the handover target network slice.
  • the first access network device may determine the terminal device corresponding to at least one network slice in the handover target network slice Active session.
  • the first access network device determines that there is at least one network slice corresponding to the session in the active state of the terminal device Belongs to the target network slice.
  • the access and mobility management functional network element may send the first registration response message to the terminal device through the first access network device.
  • the terminal device receives the first registration response message from the access and mobility management functional network element through the first access network device.
  • the access and mobility management functional network element may also send a first registration response message to the terminal device through the first access network device, the first registration response message indicates that the terminal device has registered successfully, and may carry the registration request message of this request.
  • the registration response message may also carry a rejected network slice, and the rejected network slice is a network slice not supported by the current registration area of the terminal device in the requested network slice, indicating that the terminal device is rejected to continue to request access to the rejected network slice in the current registered area network slices.
  • the access and mobility management function network element can also send an N2 interface message to the first access network device, and the N2 interface message carries the target network slice.
  • the N2 interface message can also carry indication information and the target network slice corresponding At least one item of the RFSP information.
  • the RFSP information corresponding to the target network slice is determined by the first access and mobility management function network element according to the local configuration policy, or is obtained by the first access and mobility management function network element requesting the policy control function network element .
  • the RFSP information is an RFSP index (index).
  • the first access network device sends a measurement configuration message to the terminal device.
  • the terminal device receives the measurement configuration message from the first access network device.
  • the first access network device may send a measurement configuration message to the terminal device through a radio resource management reconfiguration message, in which the wireless parameters carried instruct the terminal device to measure the frequency band of the adjacent tracking area cell of the tracking area where the terminal device is located. Signal quality.
  • the first access and mobility management function network element or the network slice selection function network element determines that the tracking area #3 where the terminal device is currently located does not support the target network slice, but covers the same area as the tracking area #3 or surrounding areas Tracking area #4 and tracking area #5 support target network slicing, or tracking area #4 and tracking area #5 adjacent to tracking area #3 support target network slicing, then the wireless parameters carried in the measurement configuration message instruct the terminal device to measure and track The signal quality of the frequency band where the cell in area #4 or the cell in tracking area #5 is located.
  • the terminal device sends a measurement result message to the first access network device.
  • the first access network device receives the measurement result message from the terminal device.
  • the first access network device makes a handover decision.
  • the first access network device may decide to start handover.
  • the first access network device sends a handover request message to the second access network device.
  • the second access network device receives the handover request message from the first access network device.
  • the first access network device determines that switching the active session of the terminal device to the target cell needs to be controlled by a network element of the core network, and sends a switching request to the access and mobility management function network element, which carries the waiting for switching
  • the information of the session and the information of the handover target cell, for example, the session may be the information of the session established respectively through the network slice #3 and the network slice #4.
  • the first access network device, the second access network device, the access and mobility management function network element, and the session management function network element jointly perform switching of an active session.
  • the first access network device, the second access network device, the network element with the access and mobility management function, and the network element with the session management function may cooperate to transfer the context of the active session from the first access network device to Switch to the second access network device.
  • the session management function network element controls the first access network device, the second access network device, and the user plane function network element to switch the user plane path of the active session from the first access network device to the second access network device. network equipment. Therefore, the session in the active state can still transmit the service packets of the terminal device normally during the switching process, and the session will not be interrupted.
  • the access and mobility management functional network element may send the active session to the first access network device Indication information for session handover to a cell supporting the tracking area of the target network slice.
  • the terminal device needs to disconnect and redirect the previous The RRC connection of the cell in the tracking area enters the RRC idle state, and then re-resides in the cell in the tracking area after redirection, so that the established session of the terminal device will be activated or interrupted.
  • this solution does not need to release RRC Instead, the access and mobility management function network element sends the instruction information to the first access network device to hand over the active session to the cell supporting the tracking area of the target network slice, thereby completing the session handover. Therefore, this solution can improve the service stability of the terminal device, prevent the session of the terminal device in the active state from being interrupted when the terminal device accesses the cell that supports the target network slice of the terminal device and registers the network slice, and improves user experience.
  • the method also includes:
  • the terminal device sends a second registration request message to the access and mobility management functional network element.
  • the terminal device finds that the currently accessed cell does not belong to the original registration area, so it sends a second registration request message to the access and mobility management functional network element through the second access network device, and the second registration
  • the request message carries the requested network slice, which can be ⁇ network slice #1, network slice #2, network slice #3, network slice #4, network slice #5 ⁇ , in other words, the terminal device leaves the original registration area After that, you can try to register as many network slices as possible.
  • the access and mobility management function network element or the network slice selection function network element determines a second allowed network slice of the terminal device.
  • the present application does not repeat the relevant description of the network element with the network slice selection function determining the allowed network slice of the terminal device.
  • the access and mobility management functional network element sends a second registration response message to the terminal device.
  • the terminal device receives the second registration response message from the access and mobility management functional network element.
  • the access and mobility management function network element may send a second registration response message to the terminal device through the second access network device, and the registration response message may carry information allowing network slicing, or information allowing network slicing and allowing Information about the registration area corresponding to the network slice.
  • FIG. 9 shows a schematic diagram of a slice-based communication method 900 provided by an embodiment of the present application. As follows, the method 900 includes the following steps:
  • the terminal device sends a registration request message to the access and mobility management functional network element.
  • the access and mobility management functional network element receives the registration request message from the terminal device.
  • the registration request message may include the requested network slice of the terminal device.
  • a terminal device accesses the network after it is turned on, or because it moves to a new tracking area that does not belong to the original registration area, or periodically updates its registration with the network, it can report to the access and mobility management through the access network device.
  • the functional network element sends a registration request message, which carries the requested network slice.
  • the registration request message may also carry status information (PDU session status) of the established session of the terminal device.
  • PDU session status status information
  • the terminal device registers with the current network for the first time, or the terminal device has left the original registration area (for example, the tracking area of the cell where it currently resides has exceeded the original registration area), the terminal device may be in the
  • the requested network slice carries all network slices in the configured network slice except the network slices rejected within the scope of the current public land mobile network.
  • the tracking area where the terminal device is currently located still belongs to the registration area of the last network registration, and the terminal device wishes to use one or more specific network slices to establish a session. If these specific network slices (such as , which can be the network slice to be used by the terminal device), the single network slice selection auxiliary information is not included in the requested network slice, and the terminal device can carry the network slice to be used by these terminal devices in addition to the allowed network slice in the requested network slice Single network slice selection auxiliary information for network slices.
  • these specific network slices such as , which can be the network slice to be used by the terminal device
  • the single network slice selection auxiliary information is not included in the requested network slice, and the terminal device can carry the network slice to be used by these terminal devices in addition to the allowed network slice in the requested network slice Single network slice selection auxiliary information for network slices.
  • the access and mobility management function network element obtains the information of the subscribed network slice of the terminal device from the unified data management function network element.
  • the access and mobility management function network element can obtain the network slice subscription information of the terminal device through the unified data management function network element, and confirm that each network slice carried by the requested network slice is a network slice subscribed by the terminal device, or The contracted network slice is mapped to the network slice of the network currently visited by the terminal device. Otherwise, the terminal device does not subscribe to the relevant network slicing service, and this network slicing will be deleted by the network element with access and mobility management functions.
  • the access and mobility management function network element can also determine from the network slice subscription information of the terminal device which network slice is the default contracted network slice of the terminal device, or which network slice is mapped to the current visited network by the default contracted network slice.
  • the access and mobility management function network element determines the network slice that has been used by the terminal device or the network slice that is about to be used by the terminal device.
  • the access and mobility management function network element determines the network slice that has been used by the terminal device or the network slice that the terminal device will use soon.
  • the relevant description of the network slice that has been used or the network slice that will be used may be determined, and for the sake of brevity, the present application does not repeat it here.
  • the access and mobility management functional network element sends a slice selection request message to the network slice selection functional network element.
  • the network element with the network slice selection function receives the slice selection request message from the network element with the access and mobility management function.
  • the access and mobility management functional network element may send a slice selection request message to the network slice selection functional network element, where the slice selection request message is used to request the network slice selection functional network element to determine the allowed network slice of the terminal device.
  • the slice selection request message may not only carry information such as the current tracking area of the terminal device and the network slice requested by the terminal device, but may also carry at least one of the network slices already used by the terminal device or the network slices to be used by the terminal device. item.
  • the access and mobility management function network element or the network slice selection function network element determines the allowed network slice of the terminal device.
  • the access and mobility management function network element or the network slice selection function network element determining the allowed network slice of the terminal device you can refer to the network device in S602 above according to the network slice that has been used or the network slice that is about to be used. For the sake of brevity, this application will not repeat them here.
  • the access and mobility management functional network element sends a registration response message to the terminal device.
  • the terminal device receives the registration response message from the access and mobility management functional network element.
  • the access and mobility management functional network element may send a registration response message to the terminal device through the access network device, and the registration response message may carry at least one item of information in the allowed network slice and the registration area corresponding to the allowed network slice.
  • the terminal device can To determine the appropriate allowed network slicing according to the communication requirements, compared with the existing technology to determine the allowed network slicing, it can effectively reduce the number of network slices included in the allowed network slices, and achieve the largest possible range of registration areas corresponding to the allowed network slices , to reduce the signaling load during the mobile process of the terminal equipment.
  • FIG. 10 shows a schematic diagram of a method 1000 for determining a slice provided by an embodiment of the present application.
  • the method 1000 includes the following steps:
  • the terminal device sends a registration request message to a network element with an access and mobility management function.
  • the access and mobility management functional network element receives the registration request message from the terminal device.
  • a terminal device that has registered to the network may periodically send a registration request message to the access and mobility management functional network element through the access network device, or when the terminal device expects to establish a session on a specific network slice, the terminal device may use the access network
  • the network access device sends a registration request message to the access and mobility management functional network element, where the registration request message may include the requested network slice of the terminal device.
  • the terminal device can include other network slices in the configured network slice in the request network slice middle. In this way, the terminal device does not request to access the network slice according to the need to establish a session. We call this kind of behavior that the terminal device registers with the network slice in a way of "registering as much as possible”.
  • the terminal device only includes the network slices that are clearly allowed by the access and mobility management function network element in the last network registration, and the network slices that the terminal device wants to establish a session in the request to access the network slice middle. In this way, the terminal device requests to access the network slice according to the need to establish a session. We call this kind of behavior that the terminal device registers with the network slice in a way of "registering as needed".
  • the access and mobility management function network element determines a registration mode of the terminal equipment.
  • the access and mobility management functional network element may determine the manner in which the terminal device registers with the network slice according to any of the following manners.
  • the access and mobility management function network element determines whether the terminal device may pass Request network slices in network slices that do not belong to allowed network slices to establish a session.
  • the access and mobility management function network element can determine whether other network slices in the configured network slice except the rejected network slice and the permitted network slice are included in the requested network slice, and if not, determine that the terminal device registers with the network
  • the way of slicing is to register network slices in the way of "registration as needed".
  • the access and mobility management function network element obtains the registration behavior analysis result information of the terminal device from the network data analysis function network element.
  • the access and mobility management function network element can obtain the registration behavior analysis result information of the terminal device through the network data analysis function network element, and the registration behavior analysis result information includes whether the terminal device's registration network slice conforms to the registration" method.
  • the specific method is as follows:
  • the access and mobility management functional network element may send an analysis request message or an analysis subscription request message to the network data analysis functional network element, requesting to obtain the registration behavior analysis result of the terminal device, wherein, the analysis request message or the analysis subscription request message It carries the analysis identification information for terminal device registration behavior analysis, and also carries identity information such as the user permanent identification of the terminal device.
  • the network data analysis function network element can collect the requested network slice information carried in the previous registration request of the terminal device from each access and mobility management function network element according to the identity information of the terminal device, as well as the information obtained from the previous registration result. Allow network slicing information, deny network slicing information, and configure network slicing information for terminal devices.
  • the network data analysis function network element may also collect the attribute information of the network slice of the session previously established by the terminal device from the access and mobility management function network element or the session management function network element (that is, the Network slicing), the network element with network data analysis function can correlate the above data to confirm whether the terminal device adds the corresponding network slice to the requested network slice when it needs to establish a session. In other words, the network element with the network data analysis function can analyze whether the registration behavior of the output terminal device conforms to the "registration as required" method.
  • the network data analysis function network element can send the analysis result of whether the registration behavior of the terminal device conforms to the "registration as required” method to the access and mobility management function network element.
  • the access and mobility management functional network element selects a network slice for the terminal device.
  • the access and mobility management function network element can select a network slice for the terminal device in any of the following ways:
  • the access and mobility The network element with the permanent management function can obtain the network slice subscription information of the terminal device through the unified data management function network element, whether the network slice included in the network slice subscription information is the default network slice, and further, the network slice subscription information can also include the network slice
  • the network elements with access and mobility management functions can assign different priorities to the contracted network slices according to the service importance of the network slice used by the terminal equipment, or the frequency of use, and then according to the default network slice Or the priority of the contracted network slice, determine the default network slice or the corresponding network slice of the visited network mapped to it as the network slice that may establish a session (that is, the network slice to be used by the terminal device), or determine a high-priority network slice
  • the corresponding network slice of the visited network to which it is mapped is a network slice where a session may be established (that is, a network slice
  • the access and mobility management function network element can obtain the communication behavior analysis result information of the terminal device through the network data analysis function network element.
  • the communication behavior analysis result information includes the information that the terminal device may use to establish a session at the current location.
  • Network slice information The specific method is as follows:
  • the access and mobility management functional network element may send an analysis request message or an analysis subscription request message to the network data analysis functional network element, requesting to obtain the communication behavior analysis result of the terminal device, wherein, the analysis request message or the analysis subscription request message Carry the analysis identification information for the analysis of the communication behavior of the terminal equipment, and at the same time carry the identity information such as the permanent identification of the user of the terminal equipment;
  • the network data analysis function network element can collect information such as the time, location, and network slice attributes of the terminal device from the access and mobility management function network elements or session management function network elements of the terminal device based on the identity information of the terminal device. .
  • Network data analysis function The network element can analyze and predict the probability that a terminal device establishes a session through each network slice in at least one network slice at a specified location and/or within a specified time by associating the above data;
  • the network data analysis function network element sends the analysis and prediction result of the probability that the terminal device establishes a session through each network slice in at least one network slice to the access and mobility management function network element, and the access and mobility management function network element
  • the unit may determine that a network slice whose probability of establishing a session reaches or exceeds a preset threshold is a network slice that may establish a session (that is, a network slice to be used by the terminal device).
  • the access and mobility management function network element can obtain the access management policy (AM-policy) information through the policy control function network element, and the access management policy information includes the network slice where the terminal device may establish a session in the current geographic location (that is, information about the network slice to be used by the terminal device).
  • the specific method is as follows:
  • the network element with the access and mobility management function may send a request message for establishing a management policy connection to the network element with the policy control function, and the request message may carry the identification information of the tracking area where the terminal device is currently located or the geographic location information of the terminal device, Further, the request message may also carry at least one item of information of the requested network slice or the subscribed network slice carried by the terminal device in the registration request;
  • the network element with the policy control function can determine the network slice information on which the terminal device may establish a session in the current geographical location according to the policy information of the terminal device acquired through the user database. For example, when the terminal device is in the current location, the network slice where the terminal device may establish a session includes the network slice included in the user routing policy issued by the terminal device; while the terminal device is in another location, the network slice where the terminal device may establish a session does not include The current location of the terminal device does not belong to the network slice allowed by the service area.
  • the policy control function network element sends the network slice information that the terminal device may establish a session in the current geographical location to the access and mobility management function network element through the establishment management policy establishment message or the establishment management policy modification message, in other words, the access and mobility
  • the network element with the performance management function may determine the network slice that may establish a session in the current geographical location as the network slice that may be used.
  • step S1003 After the network element with the access and mobility management function determines that the registration behavior of the terminal device conforms to the "registration as required" method through step S1003, then the network element with the access and mobility management function will take the information carried by the terminal device in step S1001 Request all network slices in the network slice as possible network slices to use.
  • the access and mobility management functional network element sends a slice selection request message to the network slice selection functional network element.
  • the network element with the network slice selection function receives the slice selection request message from the network element with the access and mobility management function.
  • the slice selection request message can not only carry the current tracking area of the terminal device, or at least one piece of information in the requested network slice of the terminal device, but also carry the network elements with the access and mobility management functions in S1004 mentioned above, respectively through the unified data management Information obtained by functional network elements, network data analysis functional network elements, or policy control functional network elements.
  • the network element with the access and mobility management function or the network element with the network slice selection function determines the allowed network slice of the terminal device.
  • the access and mobility management function network element or the network slice selection function network element can determine each network slice where the terminal device may establish a session, and according to each network slice where the terminal device may establish a session, the current tracking area of the terminal device, terminal At least one item in the requested network slice of the device determines the allowed network slice of the terminal device, and then determines the corresponding registration area of the allowed network slice of the terminal device.
  • the specific method is as follows:
  • the access and mobility management function network element or the network slice selection function network element can take the intersection of the set of network slices that may establish a session and the set of network slices supported by the current tracking area of the terminal device as an allowed network slice;
  • the entry and mobility management function network element or the network slice selection function network element can determine whether each tracking around the TA where the terminal device is currently located supports the allowed network slicing. Include in the registration area, and finally determine the registration area corresponding to the allowed network slice.
  • the network element with the network slice selection function may send the allowed network slice information of the terminal device to the access and mobility management function network element.
  • the access and mobility management functional network element sends a registration response message to the terminal device.
  • the terminal device receives the registration response message from the access and mobility management functional network element.
  • the access and mobility management functional network element may send a registration response message to the terminal device through the access network device, and the registration response message may carry at least one item of information in the allowed network slice and the registration area corresponding to the allowed network slice.
  • the allowed network slice of the terminal device is determined according to the network slice that has been used or the network slice to be used by the terminal device, and the information of the allowed network slice is sent. Furthermore, compared with the method of determining the allowed network slice in the prior art, This solution can determine the appropriate allowed network slice according to the communication requirements of the terminal device, reduce the number of network slices contained in the allowed network slice as low as possible, realize the expansion of the registration area corresponding to the allowed network slice as much as possible, and reduce the movement process of the terminal device signaling load in .
  • the methods and operations implemented by the terminal equipment can also be implemented by components (such as chips or circuits) that can be used in the terminal equipment, and the methods and operations implemented by the network equipment can also be implemented by A component (such as a chip or a circuit) implementation that can be used in a network device.
  • components such as chips or circuits
  • a component such as a chip or a circuit
  • each network element such as a transmitting end device or a receiving end device, includes a corresponding hardware structure and/or software module for performing each function in order to realize the above functions.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.
  • the embodiment of the present application can divide the functional modules of the transmitting end device or the receiving end device according to the above method example, for example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module middle.
  • the above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic, and is only a logical function division, and there may be other division methods in actual implementation. In the following, description will be made by taking the division of each functional module corresponding to each function as an example.
  • Fig. 11 is a schematic block diagram of a communication device 1100 provided by an embodiment of the present application.
  • the communication device 1100 includes a transceiver unit 1110 and a processing unit 1120 .
  • the transceiver unit 1110 can implement a corresponding communication function, and the processing unit 1110 is used for data processing.
  • the transceiver unit 1110 may also be called a communication interface or a communication unit.
  • the communication device 1100 may further include a storage unit, which may be used to store instructions and/or data, and the processing unit 1120 may read the instructions and/or data in the storage unit, so that the communication device implements the foregoing method Example.
  • a storage unit which may be used to store instructions and/or data
  • the processing unit 1120 may read the instructions and/or data in the storage unit, so that the communication device implements the foregoing method Example.
  • the communication device 1100 may be used to perform the actions performed by the first access and mobility management function network element in the above method embodiments, and at this time, the communication device 1100 may be the first access and mobility management function network element Or it can be configured in the first access and mobility management function network element, the transceiver unit 1110 is used to perform the operations related to the transmission and reception on the side of the first access and mobility management function network element in the method embodiment above, and the processing unit Step 1120 is configured to perform operations related to processing on the side of the first access and mobility management function network element in the above method embodiment.
  • the communication device 1100 is used to execute the actions performed by the first access and mobility management functional network element in the embodiment shown in FIG. 4 above, and the transceiver unit 1110 is used for: S403; : S401, S402.
  • the communication device 1100 is configured to execute actions performed by the first access and mobility management functional network element in the embodiment shown in FIG. 5 above, and the transceiver unit 1110 is configured to: S501.
  • the communication device 1100 can be used to perform the actions performed by the first access network device in the above method embodiments.
  • the communication device 1100 can be the first access network device or can be configured in the first access network device components of network equipment
  • the transceiving unit 1110 is configured to perform operations related to transceiving on the side of the first access network device in the method embodiments above
  • the processing unit 1120 is configured to perform operations on the side of the first access network device in the method embodiments above Handle related operations.
  • the communication apparatus 1100 is configured to execute the actions executed by the first access network device in the embodiment shown in FIG. 4 above, and the transceiver unit 1110 is configured to: S403.
  • the communication device 1100 is used to execute the actions performed by the first access network device in the embodiment shown in FIG. 5 above, the transceiver unit 1110 is used for: S501; the processing unit 1120 is used for: S502, S503 .
  • the communication device 1100 may be used to perform the actions performed by the network device in the method embodiments above.
  • the processing unit 1120 is configured to perform operations related to processing on the network device side in the above method embodiments.
  • the communication device 1100 is used to execute the actions performed by the network device in the embodiment shown in FIG. 6 above, the transceiver unit 1110 is used for: S603; the processing unit 1120 is used for: S601, S602.
  • the communication device 1100 can implement the steps or processes corresponding to the first access and mobility management function network element in the method 400 and the method 500 according to the embodiment of the present application, and the communication device 1100 can include a function for executing Elements of the method performed by the first access and mobility management functional network element in the method 400 in FIG. 4 and the method 500 in FIG. 5 .
  • each unit in the communication device 1100 and the above-mentioned other operations and/or functions are respectively intended to implement corresponding processes of the method 400 in FIG. 4 and the method 500 in FIG. 5 .
  • the communication apparatus 1100 can implement the steps or processes corresponding to the first access network device in the method 400 and the method 500 according to the embodiment of the present application, and the communication apparatus 1100 can include a method for executing the Elements of the methods executed by the first access network device in the method 400 and the method 500 in FIG. 5 .
  • each unit in the communication device 1100 and the above-mentioned other operations and/or functions are respectively intended to implement corresponding processes of the method 400 in FIG. 4 and the method 500 in FIG. 5 .
  • the communication device 1100 can implement the steps or processes corresponding to the execution of the network device in the method 600 according to the embodiment of the present application, and the communication device 1100 can include the network device execution method for executing the method 600 in FIG. 6 .
  • the unit of the method Moreover, each unit in the communication device 1100 and the above-mentioned other operations and/or functions are respectively intended to implement a corresponding flow of the method 600 in FIG. 6 .
  • the processing unit 1120 in the above embodiments may be implemented by at least one processor or processor-related circuits.
  • the transceiver unit 1110 may be implemented by a transceiver or transceiver-related circuits.
  • the transceiver unit 1110 may also be called a communication unit or a communication interface.
  • the storage unit can be realized by at least one memory.
  • the embodiment of the present application further provides a communication device 1200 .
  • the communication device 1200 includes a processor 1210, the processor 1210 is coupled with a memory 1220, the memory 1220 is used for storing computer programs or instructions and/or data, and the processor 1210 is used for executing the computer programs or instructions and/or data stored in the memory 1220, The methods in the above method embodiments are executed.
  • the communication device 1200 includes one or more processors 1210 .
  • the communication device 1200 may further include a memory 1220 .
  • the communication device 1200 may include one or more memories 1220 .
  • the memory 1220 may be integrated with the processor 1210, or set separately.
  • the communication device 1200 may further include a transceiver 1230, and the transceiver 1230 is used for receiving and/or sending signals.
  • the processor 1210 is configured to control the transceiver 1230 to receive and/or send signals.
  • the communication device 1200 is configured to implement the operations performed by the first access and mobility management functional network element in the above method embodiments.
  • the processor 1210 is used to implement the processing-related operations performed by the first access and mobility management functional network element in the above method embodiment
  • the transceiver 1230 is used to implement the processing related operations performed by the first access and mobility management function network element in the above method embodiment. Operations related to sending and receiving performed by network elements with mobility management functions.
  • the communications apparatus 1200 is configured to implement the operations performed by the first access network device in the above method embodiments.
  • the processor 1210 is used to implement the processing-related operations performed by the first access network device in the above method embodiments
  • the transceiver 1230 is used to implement the transceiving operations performed by the first access network device in the above method embodiments related operations.
  • the communications apparatus 1200 is configured to implement the operations performed by the network device in the above method embodiments.
  • the processor 1210 is configured to implement processing-related operations performed by the network device in the above method embodiments
  • the transceiver 1230 is configured to implement transceiving-related operations performed by the network device in the above method embodiments.
  • the embodiment of the present application provides a communication device 1300, and the communication device 1300 may be a network device or a chip.
  • the communication apparatus 1300 may be configured to perform the operations performed by the network device in the foregoing method embodiments.
  • the network device may include the first access and mobility management functional network element, the first access network device, or the network device in the above embodiments.
  • FIG. 13 shows a schematic structural diagram of a simplified network device 1300 .
  • the network device includes part 1310 and part 1320 .
  • Part 1310 is mainly used for transmitting and receiving radio frequency signals and conversion between radio frequency signals and baseband signals; part 1320 is mainly used for baseband processing and controlling network equipment.
  • Part 1310 may generally be called a transceiver unit, a transceiver, a transceiver circuit, or a transceiver.
  • the part 1320 is usually the control center of the network device, which can usually be referred to as a processing unit, and is used to control the network device to perform the first access and mobility management function in the above method embodiment.
  • the transceiver unit in part 1310 may also be referred to as a transceiver or a transceiver, etc., and includes an antenna and a radio frequency circuit, wherein the radio frequency circuit is mainly used for radio frequency processing.
  • the device used to realize the receiving function in part 1310 can be regarded as a receiving unit
  • the device used to realize the sending function can be regarded as a sending unit, that is, part 1310 includes a receiving unit and a sending unit.
  • the receiving unit may also be called a receiver, receiver, or receiving circuit, etc.
  • the sending unit may be called a transmitter, transmitter, or transmitting circuit, etc.
  • Section 1320 may include one or more single boards, each single board may include one or more processors and one or more memories.
  • the processor is used to read and execute programs in the memory to realize baseband processing functions and control the base station. If there are multiple single boards, each single board can be interconnected to enhance the processing capability. As an optional implementation, it is also possible that multiple single boards share one or more processors, or that multiple single boards share one or more memories, or that multiple single boards share one or more processors at the same time. device.
  • the transceiver unit in part 1310 is used to execute the steps related to sending and receiving performed by the first access network device in the embodiment shown in FIG. 4 or FIG. 5; Steps related to processing performed by the first access network device in the embodiment shown in 5.
  • the network device 1300 is used to execute the actions performed by the first access and mobility management function network element in the embodiment shown in FIG. 4 above, and the transceiver unit 1310 is used for: S403; : S401, S402.
  • the network device 1300 is configured to execute actions performed by the first access and mobility management functional network element in the embodiment shown in FIG. 5 above, and the transceiver unit 1310 is configured to: S501.
  • the transceiver unit in part 1310 is used to execute the steps related to sending and receiving performed by the first access network device in the embodiment shown in FIG. 4 or FIG. 5; Steps related to processing performed by an access network device in the embodiment shown in 5.
  • the network device 1300 is configured to perform the actions performed by the first access network device in the embodiment shown in FIG. 4 above, and the transceiver unit 1310 is configured to: S403.
  • the network device 1300 is used to execute the actions performed by the first access network device in the embodiment shown in FIG. 5 above, the transceiver unit 1310 is used for: S501; the processing unit 1320 is used for: S502, S503 .
  • the transceiver unit in part 1310 is used to execute the steps related to sending and receiving performed by the network device in the embodiment shown in FIG. 6; The processing-related steps performed.
  • the network device 1300 is used to execute the actions performed by the network device in the embodiment shown in FIG. 6 above, the transceiver unit 1310 is used for: S603; the processing unit 1320 is used for: S601, S602.
  • FIG. 13 is only an example rather than a limitation, and the foregoing network device including a transceiver unit and a processing unit may not depend on the structure shown in FIG. 13 .
  • the chip When the communication device 1300 is a chip, the chip includes a transceiver unit and a processing unit.
  • the transceiver unit may be an input-output circuit or a communication interface;
  • the processing unit is a processor or a microprocessor or an integrated circuit integrated on the chip.
  • the embodiment of the present application also provides a computer-readable storage medium, on which is stored the method executed by the first access and mobility management functional network element in the foregoing method embodiment, or executed by the first access network device method, or computer instructions for a method executed by a network device.
  • the computer when the computer program is executed by a computer, the computer can implement the method performed by the first access and mobility management function network element in the above method embodiments, or the method performed by the first access network device, or the method performed by the first access network device.
  • the embodiment of the present application also provides a computer program product containing instructions.
  • the computer implements the method performed by the first access and mobility management function network element in the above method embodiment, or the first access and mobility management function network element.
  • An embodiment of the present application further provides a communication system, which includes the first access and mobility management function network element and the first access network device in the above embodiments.
  • a terminal device or a network device may include a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer.
  • the hardware layer may include hardware such as a central processing unit (central processing unit, CPU), a memory management unit (memory management unit, MMU), and memory (also called main memory).
  • the operating system of the operating system layer can be any one or more computer operating systems that realize business processing through processes, for example, Linux operating system, Unix operating system, Android operating system, iOS operating system, or windows operating system.
  • the application layer may include applications such as browsers, address books, word processing software, and instant messaging software.
  • the embodiment of the present application does not specifically limit the specific structure of the execution subject of the method provided in the embodiment of the present application, as long as the program that records the code of the method provided in the embodiment of the present application can be executed according to the method provided in the embodiment of the present application Just communicate.
  • the subject of execution of the method provided by the embodiment of the present application may be a terminal device or a network device, or a functional module in the terminal device or network device that can call a program and execute the program.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server, a data center, etc. integrated with one or more available media.
  • Usable media may include, but are not limited to, magnetic media or magnetic storage devices (for example, floppy disks, hard disks (such as removable hard disks), magnetic tapes), optical media (for example, optical disks, compact discs, etc.) , CD), digital versatile disc (digital versatile disc, DVD, etc.), smart cards and flash memory devices (such as erasable programmable read-only memory (EPROM), card, stick or key drive, etc. ), or semiconductor media (such as solid state disk (solid state disk, SSD), U disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), etc. can store programs The medium of the code.
  • Various storage media described herein can represent one or more devices and/or other machine-readable media for storing information.
  • the term "machine-readable medium” may include, but is not limited to, wireless channels and various other media capable of storing, containing and/or carrying instructions and/or data.
  • processors mentioned in the embodiment of the present application may be a central processing unit (central processing unit, CPU), and may also be other general purpose processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits ( application specific integrated circuit (ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • a general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.
  • the memory mentioned in the embodiments of the present application may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories.
  • the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM).
  • RAM can be used as an external cache.
  • RAM may include the following forms: static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM) , double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synchlink DRAM, SLDRAM) and Direct memory bus random access memory (direct rambus RAM, DR RAM).
  • static random access memory static random access memory
  • dynamic RAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM synchronous DRAM
  • double data rate SDRAM double data rate SDRAM
  • DDR SDRAM double data rate SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous connection dynamic random access memory
  • Direct memory bus random access memory direct rambus RAM, DR RAM
  • the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components
  • the memory storage module may be integrated in the processor.
  • memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.
  • the disclosed devices and methods may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the above units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components can be combined or can be Integrate into another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.
  • the units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to implement the solutions provided in this application.
  • each functional unit in each embodiment of the present application may be integrated into one unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • a computer can be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer can be a personal computer, a server, or a network device, etc.
  • Computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, e.g. Coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) to another website site, computer, server or data center.
  • DSL digital subscriber line
  • wireless such as infrared, wireless, microwave, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供了一种基于切片的通信方法以及装置，包括：第一接入和移动性管理功能网元获取终端设备的目标网络切片的信息之后，可以确定目标网络切片中的至少一个网络切片对应终端设备的处于激活状态的会话，然后，第一接入和移动性管理功能网元可以向第一接入网设备发送将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区的指示信息。进而，可以改善终端设备的业务的稳定性，避免终端设备在接入到支持终端设备的目标网络切片的小区并注册网络切片的过程中终端设备的处于激活状态的会话受到中断影响，提升用户的体验。

Description

基于切片的通信方法及其装置
本申请要求于2022年01月27日提交中国专利局、申请号为202210103156.7、申请名称为“基于切片的通信方法及其装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，更具体地，涉及一种基于切片的通信方法及其装置。
背景技术
当前，在移动通信网络中，可以通过网络切片提供多个逻辑网络，每个逻辑网络服务特定的业务类型、行业或者用户，可以满足不同业务、行业或者用户的差异化需求。
然而，终端设备在注册网络的过程中，终端设备的业务可能受到影响，或者终端设备接入的网络切片可能受到限制，终端设备接入网络切片的方案仍有待改进，用户的体验依然有提高的空间。
发明内容
本申请实施例提供一种基于切片的通信方法，可以改善终端设备的业务的稳定性，避免终端设备在接入至支持终端设备的目标网络切片的小区并注册网络切片的过程中，终端设备的通过激活的会话所传送的业务受到影响，提升用户的体验。
第一方面，提供了一种基于切片的通信方法，包括：第一接入和移动性管理功能网元获取终端设备的目标网络切片的信息；该第一接入和移动性管理功能网元确定该目标网络切片中的至少一个网络切片对应该终端设备的处于激活状态的会话；该第一接入和移动性管理功能网元向第一接入网设备发送将该处于激活状态的会话切换至支持该目标网络切片的跟踪区的小区的指示信息。
在可能实现的一种方式中，第一接入和移动性管理功能网元可以从终端设备的上下文中获取终端设备已经建立的会话在当前服务网络的单个网络切片选择辅助信息属性，即已经建立的会话对应的网络切片。
在可能实现的另一种方式中，第一接入和移动性管理功能网元可以从终端设备的注册请求中获得终端设备的已经建立的会话的状态(例如会话的状态可以包括处于激活状态、处于去激活状态，去活或者已经释放的状态)。
在可能实现的再一种方式中，第一接入和移动性管理功能网元可以根据处于激活状态的会话以及目标网络切片，确定目标网络切片中的至少一个网络切片对应处于激活状态的会话。
基于上述方案，第一接入和移动性管理功能网元在确定目标网络切片中的至少一个网络切片对应终端设备的处于激活状态的会话之后，可以向第一接入网设备发送将处于激活 状态的会话切换至支持目标网络切片的跟踪区的小区的指示信息。进而，可以改善终端设备的业务的稳定性，避免终端设备在接入到支持终端设备的目标网络切片的小区并注册网络切片的过程中，终端设备的处于激活状态的会话受到中断影响，提升用户的体验。
结合第一方面，在第一方面的某些实现方式中，该指示信息为该目标网络切片的信息。
结合第一方面，在第一方面的某些实现方式中，第一接入和移动性管理功能网元向该第一接入网设备发送该目标网络切片的信息。
举例而言，第一接入和移动性管理功能网元可以向终端设备发送目标网络切片的信息，该目标网络切片的信息用于指示将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区；或者，第一接入和移动性管理功能网元可以向终端设备发送将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区的指示信息，也发送目标网络切片的信息。
结合第一方面，在第一方面的某些实现方式中，该第一接入和移动性管理功能网元获取该终端设备的目标网络切片的信息，包括：该第一接入和移动性管理功能网元根据该UE的第一允许网络切片中已经使用的网络切片确定该目标网络切片。
举例而言，第一接入和移动性管理功能网元如果确定终端设备已经通过第一允许网络切片中的某一个或多个网络切片(例如，{网络切片#4})建立了会话(即，终端设备已经使用的网络切片)，则确定该一个或多个网络切片(例如，{网络切片#4})属于目标网络切片(例如，目标网络切片)的一部分。
结合第一方面，在第一方面的某些实现方式中，该第一接入和移动性管理功能网元根据该第一允许网络切片中已经使用的网络切片确定该目标网络切片，包括：该第一接入和移动性管理功能网元根据该第一允许网络切片中已经使用的网络切片，以及该UE的即将使用的网络切片，确定该目标网络切片。
举例而言，第一接入和移动性管理功能网元可以根据终端设备的已经使用的网络切片(例如，{网络切片#3,网络切片#4})或即将使用的网络切片(例如，{网络切片#2})，确定终端设备的目标网络切片(例如，目标网络切片可以为{网络切片#2,网络切片#3,网络切片#4})。
结合第一方面，在第一方面的某些实现方式中，该第一接入和移动性管理功能网元获取该UE的目标网络切片的信息，包括：该第一接入和移动性管理功能网元接收来自网络切片选择功能网元的该目标网络切片的信息。
基于上述方案，即使终端设备当前注册的第一接入和移动性管理功能网元存在不支持终端设备即将使用的网络切片的情况，同时，终端设备存在处于激活状态的会话，也可以实现终端设备的处于激活状态的会话完成切换后重新注册到支持上述目标网络切片的第二接入和移动性管理功能网元，避免终端设备的处于激活状态的会话受到影响，提升用户的体验。
结合第一方面，在第一方面的某些实现方式中，该第一接入和移动性管理功能网元将该目标网络切片保存至该终端设备的上下文中；在该处于激活状态的会话完成该切换后，该第一接入和移动性管理功能网元接收该终端设备的注册请求，并根据该上下文中的该目标网络切片确定该终端设备的第二允许网络切片。
举例而言，第一接入和移动性管理功能网元可以将目标网络切片保存至终端设备的上下文中，在处于激活状态的会话完成所述切换之后，第一接入和移动性管理功能网元接收 终端设备在支持目标网络切片的跟踪区发起的注册请求，并根据注册请求中携带的请求网络切片与上下文中的目标网络切片确定终端设备的第二允许网络切片。其中，第二允许网络切片用于终端设备用于在后续建立会话。
结合第一方面，在第一方面的某些实现方式中，该第一接入和移动性管理功能网元将该目标网络切片保存至该终端设备的上下文中；该第一接入和移动性管理功能网元向第二接入和移动性管理功能网元发送该上下文信息，其中，负责管理支持目标网络切片的跟踪区的小区的接入网设备与该第二接入和移动性管理功能网元连接，该上下文信息中的该目标网络切片用于在该处于激活状态的会话完成该切换并发起注册请求之后，确定该终端设备的第二允许网络切片。
结合第一方面，在第一方面的某些实现方式中，该第一接入和移动性管理功能网元向该第一接入网设备发送该目标网络切片对应的无线频率选择优先级(Radio access technology/frequency selection priority,RFSP)信息，该RFSP信息用于确定无线测量指令，该无线测量指令用于在切换该处于激活状态的会话之前，该终端设备发现该支持该目标网络切片的跟踪区(Tracking area,TA)的小区。
在可能实现的一种方式中，该RFSP信息是第一接入和移动性管理功能网元根据本地配置策略确定的。
在可能实现的另一种方式中，该RFSP信息是第一接入和移动性管理功能网元请求策略控制网元获取的。
第二方面，提供了一种基于切片的通信方法，包括：第一接入网设备接收来自第一接入和移动性管理功能网元的终端设备的目标网络切片的信息；该第一接入网设备确定切换该目标网络切片中的至少一个网络切片对应该终端设备的处于激活状态的会话；该第一接入网设备将该处于激活状态的会话切换至支持该目标网络切片的TA的小区。
基于上述方案，即使终端设备当前注册的第一接入和移动性管理功能网元存在不支持终端设备的网络切片的情况，同时，终端设备存在处于激活状态的会话，也可以实现终端设备重新注册到支持上述目标网络切片的第二接入和移动性管理功能网元，实现终端设备在新的跟踪区重新进行网络注册，且新的跟踪区支持已经使用的网络切片以及即将使用的网络切片，避免在切换过程中终端设备的处于激活状态的会话受到影响，改善终端设备的业务的稳定性，提升用户的体验。
结合第二方面，在第二方面的某些实现方式中，该第一接入网设备确定切换该目标网络切片中的至少一个网络切片对应该终端设备的处于激活状态的会话，包括：该第一接入网设备接收来自该第一接入和移动性管理功能网元的将该处于激活状态的会话切换至支持该目标网络切片的TA的小区的指示信息；该第一接入网设备根据该指示信息，确定切换该处于激活状态的会话。
举例而言，第一接入和移动性管理功能网元可以向第一接入网设备发送N2接口消息，该N2接口消息携带将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区的指示信息和目标网络切片的信息中的至少一项。
此外，该N2消息还可以携带第一接入和移动性管理功能网元通过第一接入网设备向终端设备发送的注册响应消息，该注册响应消息指示终端设备已经在第一接入和移动性管理功能网元注册成功。
结合第二方面，在第二方面的某些实现方式中，该指示信息为该目标网络切片的信息。
结合第二方面，在第二方面的某些实现方式中，该第一接入网设备从第一接入和移动性管理功能网元接收到该指示信息和目标网络切片的信息。
结合第二方面，在第二方面的某些实现方式中，该第一接入网设备确定切换该目标网络切片中的至少一个网络切片对应该终端设备的处于激活状态的会话，包括：该第一接入网设备根据该目标网络切片中的至少一个网络切片对应该处于激活状态的会话，确定切换该处于激活状态的会话。
结合第二方面，在第二方面的某些实现方式中，该第一接入网设备确定该终端设备的无线测量指令，该无线测量指令用于在切换该处于激活状态的会话之前，发现该支持该目标网络切片的TA的小区。
结合第二方面，在第二方面的某些实现方式中，该第一接入网设备确定该终端设备的无线测量指令，包括：该第一接入网设备根据该目标网络切片的信息确定该无线测量指令。
结合第二方面，在第二方面的某些实现方式中，该第一接入网设备确定该无线测量指令，包括：该第一接入网设备接收来自该第一接入和移动性管理功能网元的该目标网络切片对应的RFSP信息；该第一接入网设备根据该RFSP信息确定该无线测量指令。
之后，第一接入网设备可以通过无线资源管理配置(Radio resource management configuration,RRMconfiguration)消息向终端设备发送终端设备的无线测量指令，终端设备将无线测量报告发送至第一接入网设备，如果无线测量报告指示支持目标网络切片的跟踪区的小区的信号强度达到预设门限，则第一接入网设备决定启动切换。
第三方面，提供了一种基于切片的通信方法，包括：网络设备获取终端设备的已经使用的网络切片或该终端设备的即将使用的网络切片中的至少一项信息，以及该终端设备的请求网络切片信息；该网络设备根据该已经使用的网络切片或该即将使用的网络切片中的至少一项，以及该请求网络切片确定终端设备的第一允许网络切片；该网络设备发送该第一允许网络切片的信息。
举例而言，网络设备可以向终端设备发送指示终端设备注册成功的注册响应消息，该注册响应消息携带第一允许网络切片的信息。
基于上述方案，网络设备在获取终端设备的已经使用的网络切片或该终端设备的即将使用的网络切片中的至少一项信息，以及该终端设备的请求网络切片信息之后，可以根据上述信息确定终端设备的第一允许网络切片，并发送该第一允许网络切片的信息。由于经过本实施例的处理，对第一允许网络切片包含的网络切片数量进行了缩减，所以能够根据终端设备的通信需求确定合适的允许网络切片，实现允许网络切片对应的注册区的范围尽可能大，减少终端设备移动过程中的信令负荷。
结合第三方面，在第三方面的某些实现方式中，该网络设备获取该终端设备所在的TA支持的网络切片的信息；在该TA不支持该即将使用的网络切片中的至少一个网络切片的情况下，该网络设备根据该已经使用的网络切片或该即将使用的网络切片中的至少一项，以及该请求网络切片确定该终端设备的目标网络切片；该网络设备发送该目标网络切片的信息。
结合第三方面，在第三方面的某些实现方式中，该网络设备根据该已经使用的网络切片或该即将使用的网络切片中的至少一项，以及该请求网络切片确定该终端设备的目标网 络切片，包括：该网络设备选择属于该已经使用的网络切片或该即将使用的网络切片中的至少一项的网络切片，以及属于该请求网络切片的网络切片，组成该目标网络切片。
其中，目标网络切片包括终端设备的请求网络切片中，不被终端设备当前的跟踪区支持，但是可以被其他跟踪区(例如，与终端设备当前的跟踪区有重叠部分的另一个频段的跟踪区)支持的网络切片。例如，目标网络切片的信息可以是target NSSAI。
以及，目标网络切片包括终端设备在上下文保存的允许网络切片中已经使用的网络切片，以及即将使用的网络切片，其中，已经使用的网络切片可以是终端设备已经建立的会话对应的网络切片，即将使用的网络切片可以是终端设备期望建立的会话的网络切片；此外，终端设备期望建立的会话可以是终端设备期望建立，且还从未建立的会话，也可以是已被释放的，但是终端设备期望建立的会话(例如，业务连续性模式2或模式3的会话)。
在一种实现方式中，如果终端设备已经注册到网络设备，网络设备则可以获得之前保存的终端设备的允许网络切片，如果终端设备发起的注册请求消息携带的请求网络切片中的一个或多个网络切片并不属于上述的允许网络切片，则该一个或多个网络切片为即将使用的网络切片，网络设备可以选择请求网络切片中属于已经使用的网络切片或即将使用的网络切片中的至少一项的网络切片，组成目标网络切片。
结合第三方面，在第三方面的某些实现方式中，该目标网络切片中的至少一个网络切片不属于该TA支持的网络切片。
举例而言，假设终端设备当前所在TA支持的网络切片为{网络切片#2、网络切片#3、网络切片#4}，网络设备之前保存的终端设备的允许网络切片为{网络切片#3、网络切片#4}，请求网络切片为{网络切片#1、网络切片#2、网络切片#4}。网络设备确定即将使用的网络切片为{网络切片#1、网络切片#2}，已经使用的网络切片为{网络切片#3}，则目标网络切片为{网络切片#1、网络切片#2、网络切片#3}。
结合第三方面，在第三方面的某些实现方式中，该网络设备根据该已经使用的网络切片或该即将使用的网络切片中的至少一项，以及该请求网络切片确定该终端设备的第一允许网络切片，包括：该网络设备选择属于该已经使用的网络切片或该即将使用的网络切片中的至少一项的网络切片，以及属于该请求网络切片的网络切片，组成该第一允许网络切片。
举例而言，如果终端设备当前所在的TA支持{网络切片#1，网络切片#2，网络切片#3}，第一接入和移动性管理功能网元可以根据终端设备的已经使用的网络切片(例如，{网络切片#3})和即将使用的网络切片(例如，{网络切片#2})，以及请求网络切片{例如，网络切片#1，网络切片#2，网络切片#3}，确定终端设备的第一允许网络切片(例如，{网络切片#2，网络切片#3})。虽然终端设备当前所在TA也支持请求网络切片中的网络切片#1，但是因为它不属于已经使用的网络切片或即将使用的网络切片，所以没有被包含在第一允许网络切片中。换句话说，如果终端设备请求的一个网络切片不属于终端设备已经使用的网络切片或终端设备即将使用的网络切片，那么即便终端设备当前所在TA也支持这个网络切片，网络设备在确定第一允许的网络切片的时候也将其排除，或者，也可以理解成将其过滤，使得最终确定的第一允许的网络切片的中的每一个网络切片都是属于终端设备已经使用的网络切片或终端设备即将使用的网络切片。这样确定出来的允许的网络切片相比于现有技术方式中确定出来的允许的网络切片，包括更少数量的网络切片。
结合第三方面，在第三方面的某些实现方式中，该网络设备包括第一网络切片选择功能网元。
结合第三方面，在第三方面的某些实现方式中，该网络设备获取该终端设备的已经使用的网络切片或该终端设备的即将使用的网络切片中的至少一项信息，包括：该网络设备接收来自接入和移动性管理功能网元的该已经使用的网络切片和该即将使用的网络切片中的至少一项信息。
此外，在网络设备包括网络切片选择功能网元的情况下，网络设备接收来自接入和移动性管理功能网元(后续称之为第一接入和移动性管理功能网元)的网络切片选择请求之后，如果网络设备判断终端设备当前所在的跟踪区支持终端设备的请求网络切片，但是第一接入和移动性管理功能网元不支持终端设备的请求网络切片，网络设备则可以确定一个连接终端设备当前所在的跟踪区的，并且支持终端设备的请求网络切片的新的接入和移动性管理功能网元(后续称之为第二接入和移动性管理功能网元)，并将第二接入和移动性管理功能网元的信息发送至第一接入和移动性管理功能网元；之后，第一接入和移动性管理功能网元将终端设备的注册请求消息转发至第二接入和移动性管理功能网元进行处理；最后，如果网络设备判断终端设备当前所在的跟踪区不支持终端设备的请求网络切片，网络设备可以确定终端设备的目标网络切片，并向第一接入和移动性管理功能网元返回第二接入和移动性管理功能网元的信息。
结合第三方面，在第三方面的某些实现方式中，该网络设备包括接入和移动性管理功能网元。
结合第三方面，在第三方面的某些实现方式中，该网络设备接收来自第二网络切片选择功能网元的该终端设备的第二允许网络切片；所述网络设备从该第二允许网络切片中选出属于该已经使用的网络切片或属于该即将使用的网络切片的中至少一项的网络切片，组成第三允许网络切片；该网络设备向该终端设备发送该第三允许网络切片的信息。
其中，第二允许网络切片可以是第二网络切片选择功能网元通过现有技术确定的，即，第二网络切片选择功能网元根据终端设备的注册请求消息携带的请求网络切片，以及终端设备所在的注册区支持的网络切片确定的。
结合第三方面，在第三方面的某些实现方式中，该网络设备获取该终端设备的第一拒绝网络切片的信息；该网络设备删除该第一拒绝网络切片中该终端设备的注册区(Registration Area,RA)中的任一TA支持的网络切片，获得该终端设备的第二拒绝网络切片，其中，该RA是根据该第二允许网络切片确定的；该网络设备向该终端设备发送该第二拒绝网络切片的信息。
举例而言，第一拒绝网络切片为{网络切片#1、网络切片#2、网络切片#3、网络切片#4}，注册区中存在的某一跟踪区支持的网络切片为{网络切片#2、网络切片#3}，则第二拒绝网络切片为{网络切片#1、网络切片#4}。
需要说明的是，上述确定拒绝网络切片的方式并不限定要通过如上方式确定第三允许网络切片。例如，也可以通过现有技术的方式或其他方式确定允许的网络切片并确定相应的注册区。只是在确定拒绝网络切片的时候，考虑将注册区中的任一跟踪区支持的网络切片从拒绝的网络切片中剔除掉，从而减少拒绝的网络切片中包含的网络切片的数量。
举例而言，网络设备可以向终端设备发送注册响应消息，该注册响应消息指示终端设 备注册成功，还可以携带第二拒绝网络切片的信息。
基于上述方案，通过对第一拒绝网络切片进一步处理，得到第二拒绝网络切片，可以使得终端设备的拒绝网络切片包含的网络切片更少，尽可能地扩大终端设备可以使用的网络切片的范围，进而扩大相应的注册区的范围，减少终端移动过程中的信令负荷。
结合第三方面，在第三方面的某些实现方式中，该网络设备获取该已经使用的网络切片或该即将使用的网络切片中的至少一项信息，包括以下至少一种方式：该网络设备根据该终端设备的会话状态信息确定该已经使用的网络切片的信息；或该网络设备根据该请求网络切片和该终端设备的上下文中的第四允许网络切片确定该即将使用的网络切片的信息；或该网络设备接收来自网络数据分析功能网元的该终端设备的通信分析结果信息，并根据该通信分析结果信息确定该即将使用的网络切片的信息。
第四方面，提供一种通信装置，该装置用于执行上述第一方面或第二方面或第三方面提供的方法。具体地，该装置可以包括用于执行第一方面或第一方面的上述任意一种实现方式或第二方面或第二方面的上述任意一种实现方式或第三方面或第三方面的上述任意一种实现方式提供的方法的单元和/或模块，如处理单元和/或通信单元。
在一种实现方式中，该装置为第一接入和移动性管理功能网元。当该装置为第一接入和移动性管理功能网元时，通信单元可以是收发器，或，输入/输出接口；处理单元可以是至少一个处理器。可选地，收发器可以为收发电路。可选地，输入/输出接口可以为输入/输出电路。
在另一种实现方式中，该装置为用于第一接入和移动性管理功能网元中的芯片、芯片系统或电路。当该装置为用于第一接入和移动性管理功能网元中的芯片、芯片系统或电路时，通信单元可以是该芯片、芯片系统或电路上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等；处理单元可以是至少一个处理器、处理电路或逻辑电路等。
在一种实现方式中，该装置为第一接入网设备。当该装置为第一接入网设备时，通信单元可以是收发器，或，输入/输出接口；处理单元可以是至少一个处理器。可选地，收发器可以为收发电路。可选地，输入/输出接口可以为输入/输出电路。
在另一种实现方式中，该装置为用于第一接入网设备中的芯片、芯片系统或电路。当该装置为用于第一接入网设备中的芯片、芯片系统或电路时，通信单元可以是该芯片、芯片系统或电路上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等；处理单元可以是至少一个处理器、处理电路或逻辑电路等。
在一种实现方式中，该装置为网络设备。当该装置为网络设备时，通信单元可以是收发器，或，输入/输出接口；处理单元可以是至少一个处理器。可选地，收发器可以为收发电路。可选地，输入/输出接口可以为输入/输出电路。
在另一种实现方式中，该装置为用于网络设备中的芯片、芯片系统或电路。当该装置为用于核心网网元中的芯片、芯片系统或电路时，通信单元可以是该芯片、芯片系统或电路上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等；处理单元可以是至少一个处理器、处理电路或逻辑电路等。
第七方面，提供一种通信装置，该装置包括：存储器，用于存储程序；至少一个处理器，用于执行存储器存储的计算机程序或指令，以执行上述第一方面或第一方面的上述任意一种实现方式，或第二方面或第二方面的上述任意一种实现方式，或第三方面或第三方 面的上述任意一种实现方式，或第四方面或第四方面的上述任意一种实现方式，或第五方面或第五方面的上述任意一种实现方式，提供的方法。
在一种实现方式中，该装置为第一会话管理功能网元。
在另一种实现方式中，该装置为用于第一会话管理功能网元中的芯片、芯片系统或电路。
在一种实现方式中，该装置为终端设备。
在另一种实现方式中，该装置为用于终端设备中的芯片、芯片系统或电路。
在一种实现方式中，该装置为核心网网元。
在另一种实现方式中，该装置为用于核心网网元中的芯片、芯片系统或电路。
在一种实现方式中，该装置为接入和移动性管理功能网元。
在另一种实现方式中，该装置为用于接入和移动性管理功能网元中的芯片、芯片系统或电路。
第八方面，本申请提供一种处理器，用于执行上述各方面提供的方法。
对于处理器所涉及的发送和获取/接收等操作，如果没有特殊说明，或者，如果未与其在相关描述中的实际作用或者内在逻辑相抵触，则可以理解为处理器输出和接收、输入等操作，也可以理解为由射频电路和天线所进行的发送和接收操作，本申请对此不做限定。
第九方面，提供一种计算机可读存储介质，该计算机可读介质存储用于设备执行的程序代码，该程序代码包括用于执行上述第一方面或第一方面的上述任意一种实现方式或第二方面或第二方面的上述任意一种实现方式或第三方面或第三方面的上述任意一种实现方式或第四方面或第四方面的上述任意一种实现方式或第五方面或第五方面的上述任意一种实现方式提供的方法。
第十方面，提供一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行上述第一方面或第一方面的上述任意一种实现方式或第二方面或第二方面的上述任意一种实现方式或第三方面或第三方面的上述任意一种实现方式或第四方面或第四方面的上述任意一种实现方式或第五方面或第五方面的上述任意一种实现方式提供的方法。
第十一方面，提供一种芯片，芯片包括处理器与通信接口，处理器通过通信接口读取存储器上存储的指令，执行上述第一方面或第一方面的上述任意一种实现方式或第二方面或第二方面的上述任意一种实现方式或第三方面或第三方面的上述任意一种实现方式或第四方面或第四方面的上述任意一种实现方式或第五方面或第五方面的上述任意一种实现方式提供的方法。
可选地，作为一种实现方式，芯片还包括存储器，存储器中存储有计算机程序或指令，处理器用于执行存储器上存储的计算机程序或指令，当计算机程序或指令被执行时，处理器用于执行上述第一方面或第一方面的上述任意一种实现方式或第二方面或第二方面的上述任意一种实现方式或第三方面或第三方面的上述任意一种实现方式或第四方面或第四方面的上述任意一种实现方式或第五方面或第五方面的上述任意一种实现方式提供的方法。
第十二方面，提供一种组播/广播通信的系统，包括上文的第一会话管理功能网元和接入和移动性管理功能网元。
附图说明
图1示出了一种网络架构的示意图。
图2示出了网络切片部署的一示意图。
图3示出了网络切片部署的另一示意图。
图4示出了本申请实施例提供的一种基于切片的通信方法400的示意图。
图5示出了本申请实施例提供的一种基于切片的通信方法500的示意图。
图6示出了本申请实施例提供的一种切片确定的方法600的示意图。
图7示出了本申请实施例提供的一种基于切片的通信方法700的示意图。
图8示出了本申请实施例提供的一种基于切片的通信方法800的示意图。
图9示出了本申请实施例提供的一种切片确定的方法900的示意图。
图10示出了本申请实施例提供的一种切片确定的方法1000的示意图。
图11示出了本申请实施例提供的通信装置1100的示意性框图。
图12示出了本申请实施例提供的通信装置1200的示意性框图。
图13示出了一种简化的网络设备1300的结构示意图。
具体实施方式
下面将结合附图，对本申请实施例中的技术方案进行描述。
本申请提供的技术方案可以应用于各种通信系统，例如：第五代(5th generation，5G)或新无线(new radio，NR)系统、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)系统等。本申请提供的技术方案还可以应用于未来的通信系统，如第六代移动通信系统。本申请提供的技术方案还可以应用于设备到设备(device to device，D2D)通信，车到万物(vehicle-to-everything，V2X)通信，机器到机器(machine to machine，M2M)通信，机器类型通信(machine type communication，MTC)，以及物联网(internet of things，IoT)通信系统或者其他通信系统。
首先简单介绍适用于本申请的网络架构，如下。
作为示例，图1示出了一种网络架构的示意图。
如图1所示，该网络架构以5G系统(the 5th generation system，5GS)为例。该网络架构可以包括但不限于：网络切片选择功能(network slice selection function，NSSF)，下一代基站节点(next generation Node Base station，gNB)，统一数据管理(unified data management，UDM)，策略控制功能(policy control function，PCF)，接入和移动性管理功能(access and mobility management function，AMF)，会话管理功能(session management function，SMF)，用户设备(user equipment，UE)，用户面功能(user plane function，UPF)，数据网络(data network，DN)，网络数据分析功能(Network data analytics function,NWDAF)，统一数据存储库(unified data repository,UDR)。
其中，DN可以是互联网；NSSF、NWDAF、UDR、UDM、PCF、AMF、SMF、UPF属于核心网中的网元，由于图1以5G系统为例，那么该核心网可以称为5G核心网(5G core network，5GC或5GCN)。
下面对图1中示出的各网元做简单介绍。
1、UE：可以称用户设备、终端设备、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。
终端设备可以是一种向用户提供语音/数据的设备，例如，具有无线连接功能的手持式设备、车载设备等。目前，一些终端的举例为：手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备，虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、可穿戴设备，5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等，本申请实施例对此并不限定。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
此外，在本申请实施例中，终端设备还可以是IoT系统中的终端设备，IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物物互连的智能化网络。
需要指出的是，终端设备与接入网设备之间可以采用某种空口技术(如NR或LTE技术等)相互通信。终端设备与终端设备之间也可以采用某种空口技术(如NR或LTE技术等)相互通信。
本申请实施例中，终端设备可以替换为用于实现终端设备的功能的装置，也可以是能够支持终端设备实现该功能的装置，例如芯片系统或芯片，该装置可以被安装在终端设备中。此外，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。
2、gNB：可以为终端设备提供接入通信网络的功能。具体可以包括第三代合作伙伴计划(3rd generation partnership project，3GPP)网络中无线网络设备，也可以包括非3GPP(non-3GPP)网络中的接入点。此外，gNB也可以称为接入网(Access network,AN)设备。
gNB设备可以为采用不同的无线接入技术。目前的无线接入技术有两种类型：3GPP接入技术(例如，第三代(3rd generation，3G)、第四代(4th generation，4G)或5G系统 中采用的无线接入技术)和非3GPP(non-3GPP)接入技术。3GPP接入技术是指符合3GPP标准规范的接入技术，例如，5G系统中的gNB可以称为接入网设备或者RAN设备。非3GPP接入技术可以包括以无线保真(wireless fidelity，WiFi)中的接入点(access point，AP)为代表的空口技术、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)、码分多址(code division multiple access，CDMA)等。gNB设备可以使得终端设备和3GPP核心网之间采用非3GPP技术互连互通。
gNB设备还能够负责空口侧的无线资源管理、服务质量(quality of service，QoS)管理、数据压缩和加密等功能。gNB设备为终端设备提供接入服务，进而完成控制信号和用户数据在终端设备和核心网之间的转发。
gNB设备可以包括但不限于：宏基站、微基站(也称为小站)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(baseband unit，BBU)，WiFi系统中的AP、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)等，还可以为5G(如，NR)系统中的传输点(TRP或TP)，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如分布式单元(distributed unit，DU)，或者下一代通信6G系统中的基站等。本申请实施例对gNB设备所采用的具体技术和具体设备形态不做限定。
3、AMF：主要用于移动网络中的终端的注册、移动性管理、跟踪区更新流程，接入管理网元终结了非接入层(non access stratum，NAS)消息、完成注册管理、连接管理以及可达性管理、分配跟踪区列表(track area list，TA list)以及移动性管理等，并且透明路由会话管理(session management，SM)消息到会话管理网元。在第5代(5th generation，5G)通信系统中，接入管理网元可以是接入与移动性管理功能。
4、SMF：主要用于移动网络中的会话管理，如会话建立、修改、释放。具体功能如为终端分配互联网协议(internet protocol，IP)地址、选择提供报文转发功能的用户面网元等。在5G通信系统中，会话管理网元可以是会话管理功能。
5、UPF：主要负责对用户报文进行处理，如转发、计费、合法监听等。例如，UPF可以从DN接收用户面数据，并通过AN设备将用户面数据发送给终端设备。UPF还可以通过AN设备从终端设备接收用户面数据，并转发到DN。
用户面网元也可以称为协议数据单元(protocol data unit,PDU)会话锚点(PDU session anchor,PSA)。在5G通信系统中，用户面网元可以是用户面功能(user plane function,UPF)，连接gNB和数据网络。
6、PCF：包含用户签约数据管理功能、策略控制功能、计费策略控制功能、服务质量(quality of service，QoS)控制等。在5G通信系统中，策略控制网元可以是策略控制功能。需要指出的是，实际网络中PCF还可能按照层次或按功能分为多个实体，例如全局PCF和切片内的PCF，或者会话管理PCF(Session Management PCF，SM-PCF)和接入管理PCF(Access Management PCF，AM-PCF)。
7、网络切片选择功能(network slice selection function，NSSF)：主要用于为终端的业务选择合适的网络切片。
8、UDM：负责管理终端的签约信息。主要用于UE的签约数据管理，包括UE标识的存储和管理，UE的接入授权等。
9、DN：主要用于为UE提供数据服务的运营商网络。例如，因特网(Internet)、第三方的业务网络、IP多媒体服务业务(IP multi-media service,IMS)网络等。
10、UDR：通过UDM存储和检索用户数据，由PCF存储和检索策略数据，存储和检索网络能力开放功能实体的用于开放的结构化数据和应用程序数据(包括用于应用程序检测的数据包流描述信息、多个UE的应用程序请求信息)。
11、NWDAF：可以从各个网络功能(network function,NF)，例如策略控制网元、会话管理网元、用户面网元、接入管理网元、应用功能网元(通过网络能力开放功能网元)收集数据，并进行分析和预测。
服务化使得5G核心网形成一个扁平化的架构，通过控制面的信令总线，同一个网络切片的控制面网络功能实体之间可以通过NRF相互发现对方，获得对方的访问地址信息，并通过控制面信令总线直接相互通信。
在图1所示的网络架构中，各网元之间可以接口通信。例如，UE通过无线资源控制(radio resource control，RRC)协议与gNB设备连接，UPF与gNB设备、DN之间采用用户面连接，其余设备之间可以通过控制面连接。
需要说明的是，根据图1所示的网络架构示意图，还应理解以下几点：
1、图1所示的网络架构还可能包括其他网元，如认证服务器功能(authentication server function,AUSF)等网元或设备，本申请在此不作具体限定；
2、图1所示的网络架构仅是示例性说明，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例；
3、图1所示的网络架构中的功能或者网元，可以理解为用于实现不同功能的网元，例如可以按需组合成网络切片。这些网元可以各自独立的设备，也可以集成于同一设备中实现不同的功能，或者可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能，本申请对于上述网元的具体形态不作限定；
4、图1所示的网络架构中的网元或功能的命名，仅为便于区分不同的功能而定义，不应对本申请构成任何限定。本申请并不排除在6G网络以及未来其它的网络中采用其他命名的可能。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能采用其他名称等。
为便于理解本申请实施例，对本申请中涉及到的术语进行解释：
1、跟踪区
移动网络可以划分为多个跟踪区，地理相近、终端移动频繁的多个小区划分到同一个跟踪区(tracking area,TA)，各个TA可以通过跟踪区标识(tracking area identity,TAI)互相区别。TAI由移动国家码(mobile country code，MCC)、移动网络码(mobile network code，MNC)和跟踪区码(tracking area code,TAC)组成。一个用户设备注册到网络后，负责移动管理的网络设备会根据自身连接的无线基站设备，自身管理范围包括的跟踪区等因素，为用户设备确定一个注册区(registration area,RA)。RA可以包括一个或多个TA，从形式而言，RA是一个或多个TA的列表。用户设备在空闲态的情况下，发生小区切换并不通知核 心网设备，用户设备在到达目标小区之后，如果用户设备检测到目标小区所在的TA已经不属于原来的RA，则发起注册更新流程，通知负责移动管理的网络设备离开原来的注册区。此后，负责移动管理的网络设备接受用户设备的注册更新后，为其分配一个新的RA。
2、网络切片
当前，移动通信系统的设备众多，小区数量也大幅增加，同时还可以有在不同频段支持不同网络切片的场景。其中，网络切片(network slice)是一个具备特定网络特性的逻辑网络，可以使得5G移动通信系统满足网络差异化的需求。5G物理网络可以被抽象划分成多个网络切片，每个网络切片构成一个端到端的逻辑网络，彼此之间在逻辑上是隔离的，互不影响。通常情况下，不同网络切片的网络特征不相同，如增强的移动宽带(enhanced mobile broad band,eMBB)类型的网络切片要求具备支持大带宽、低时延业务的特征；海量机器类型连接(massive machine type connection,mMTC)类型的网络切片支持海量接入，带宽小的特征；超高可靠性超低时延连接(ultra reliability and low latency connection,uRLLC)类型的切片具备高可靠性、低时延的特征。每个网络切片的业务都通过单个网络切片选择辅助信息(Single-network slice selection assistance information,S-NSSAI)来标识。5G网络根据终端设备的注册请求和会话建立请求中携带的S-NSSAI为业务选择网络切片，并在所选择的网络切片传输客户的业务数据。一个客户可能在运营商订购多个网络切片，终端设备可能会同时请求接入多个网络切片，例如车联网终端可以同时接入mMTC、eMBB和uRLLC三个网络切片，mMTC切片用于车辆日常故障检测和保养提醒等应用，eMBB切片用于乘客的及时消息通信和在线点播娱乐的应用，uRLLC切片用于自动驾驶的非视距通信的车联网应用。
终端设备可以首先选择驻留到一个小区，然后通过无线设备(例如，gNB)向核心网设备发送注册请求消息，其中，注册请求消息携带终端设备的请求接入的网络切片信息(Requested NSSAI)。Requested NSSAI是由一个或多个S-NSSAI组成的，这些S-NSSAI属于为终端设备在当前公共陆地移动网络(Public land mobile network,PLMN)配置的配置网络切片(Configured NSSAI)。如果当前PLMN是归属公共陆地移动网络(Home public land mobile network,HPLMN)，Configured NSSAI中的S-NSSAI就是终端设备签约的网络切片(Subscribed S-NSSAI)。如果终端设备发生漫游，在拜访公共陆地移动网络(Visit public land mobile network,VPLMN)只能使用VPLMN的S-NSSAI(为方便起见记为vS-NSSAI)。这个vS-NSSAI所标识的VPLMN中的网络切片能够提供的通信服务，与HPLMN中终端设备的签约S-NSSAI所标识的HPLMN中的网络切片所提供的通信服务是相同或相似的，这时终端设备在VPLMN的Configured NSSAI就包含一个或多个vS-NSSAI，以及它们分别映射(Mapping)的HPLMN的Subscribed S-NSSAI。
举例而言，核心网中的NSSF或AMF首先确认终端设备的注册请求消息中携带的Requested NSSAI是终端设备的签约网络切片或签约网络切片映射的vS-NSSAI；接着，核心网中的NSSF或AMF可以根据终端设备当前接入的TA能够支持的网络切片，确定终端设备允许访问的网络切片的信息(Allowed NSSAI)，其中Allowed NSSAI包括一个或多个S-NSSAI。例如，基站启动的过程中，基站会向AMF报告其管理的小区归属的跟踪区的TAI，以及这个TA支持的S-NSSAI的列表，以此，AMF可以获得其服务范围内各个TA支持的网络切片。进一步地，各个AMF向NSSF发送其服务范围内各个TA支持的网络切片，NSSF 可以获得整个PLMN内各个TA支持的网络切片信息，以及各个AMF连接的TA信息。当终端设备通过某个TA内的小区向AMF发送注册请求消息时，AMF或NSSF可以将UE当前所在TA支持的S-NSSAI的集合与UE的Requested NSSAI取交集，确定为Allowed NSSAI。最后，终端设备可以成功注册到Allowed NSSAI包含的网络切片上，后续终端设备可以通过这些网络切片建立协议数据单元会话(Protocol data unit session,PDU session)，使用这些网络切片来传输业务的报文。
NSSF或AMF还可以为终端设备确定一个RA，RA是包含当前接入的TA在内的一个TA列表。例如，如果当前接入的TA的相邻TA也能支持Allowed NSSAI中的各个网络切片，就将这个相邻TA和当前接入的TA一起纳入到支持Allowed NSSAI的TA列表中，最终将这个TA列表确定为UE此次注册的RA。终端设备在RA范围内移动时，随时可以使用Allowed NSSAI中的网络切片建立PDU会话。终端设备移动到RA范围外，或接入到RA范围外的小区时，需要重新进行网络注册。
3、工作频段
当前协议定义了5G网络使用的工作频段，其中N41、N78和N79是最常用的3个5G工作频段。N41范围在2.5GHz左右，N78范围在3.5GHz左右，N79范围在4.8至4.9GHz左右。N41和N78频段技术较为成熟，穿透能力和覆盖范围广，是主流的民用5G频段。N41可以用宏基站部署的方式覆盖大范围区域，提供eMBB网络切片和mMTC网络切片的无线接入。N78可以在N41频段覆盖范围内叠加覆盖，为人员密集的热点区域提供更大带宽的eMBB网络切片的无线接入。N79适合特殊工业场景和场所使用，但是穿透力和覆盖能力都不如前两者，主要在园区和工厂提供uRLLC网络切片的无线接入。在一个TA内，无线基站可以通过划分的一个或多个小区(Cell)提供的无线网络接入服务。每个小区可以只在一个频段上工作，并且每个小区可以只归属于一个TA。此外，TA内所有小区支持的网络切片的能力可以是相同的，换言之，虽然一个TA内的不同小区可以工作在不同的频段，但是它们应该支持相同的一个或多个S-NSSAI。由于TA内的小区支持网络切片的能力限制，经常出现终端设备只有通过特定TA内的小区注册到网络，才可以接入到终端设备希望使用的网络切片。
此外，由于某些隔离性的要求，或者某些核心网设备是切片租户企业自备的等因素，还可能会造成在同一个地理区域的不同AMF支持不同的网络切片，例如运营商的AMF支持第一网络切片，企业的AMF可以支持第一网络切片至第三网络切片，由于终端设备只能注册到一个AMF上，因此常常会出现终端设备只有注册到特定的AMF时，才能接入到终端设备希望使用的网络切片。
然而，可能会出现如下情况。图2为网络切片部署的一示意图。如图2所示，TA#1支持的网络切片为{网络切片1，网络切片2}，TA#2支持的网络切片为{网络切片1，网络切片2，网络切片3}，TA#3支持的网络切片为{网络切片2，网络切片3}。如果终端设备通过TA#1接入网络注册，终端设备的requested NSSAI为{网络切片1，网络切片2，网络切片3}，则Allowed NSSAI为{网络切片1，网络切片2}，RA为{TA#1,TA#2}。虽然TA#2还支持网络切片3，但是UE在RA范围内无法使用网络切片3建立PDU会话。如果终端设备通过TA#2接入网络注册，Allowed NSSAI为{网络切片1，网络切片2，网络切片3}，RA是{TA#2}，此时RA的范围比较小，终端设备在小范围内移动就需要频繁进行网络注册，信令负荷较 大。由此可见，allowed NSSAI中包含的切片的数量越多，对应的RA越小。相反的，allowed NSSAI中包含的切片的数量越少，对应的RA越大，就越不容易引起小范围内移动就要频繁进行网络注册。
图3为网络切片部署的另一示意图。如图3所示，TA#1和TA#2可以是两个工作在不同频段的接入网设备分别覆盖的TA，例如网络切片1是公共网络提供的公共服务网络切片，网络切片2是园区网络切片，覆盖范围就只有园区，并且它们分别由两个不同的AMF管理。为了让园区的终端设备在园区地理位置能够接入到园区网络切片，会为园区的终端设备配置特定的无线接入技术/频率选择优先级(Radio access technology/frequency selection priority,RFSP)信息。这个终端设备根据特定的RFSP信息在无线设备侧会关联到一组频点，从而终端设备根据指定的这组频点的重选优先级进行小区选择或重新选择，而不再依赖小区系统广播的各个频段信号强度进行小区选择或重新选择，从而可以确保终端设备可以根据RFSP信息驻留到指定的频率。因此，园区的终端设备回到园区后，可以优先选择驻留到TA#2的小区，而其它非园区的终端设备在同样的地理位置仍然驻留在TA#1的小区。
如图3所示，如果园区的终端设备已经通过网络切片1建立了PDU会话，终端设备在园区位置想要同时使用网络切片2，就需要使用{网络切片1，网络切片2}作为Requested NSSAI重新发起注册请求。这时，第一AMF可以指示TA#1的小区在释放无线资源控制(Radio resource control release,RRC Release)消息中携带上述RFSP信息对应的无线参数，然后终端设备才可以根据这些参数选择TA#2的小区进行驻留。在这个过程中，终端设备会先断开和TA#1内小区的无线资源控制连接，进入RRC空闲状态，然后重新驻留到TA#2内小区。期间，已经通网络切片1建立的PDU会话就会被去激活或中断。因此，在终端设备希望通过重新注册接入新的网络切片时，可能出现需要更换当前接入的TA或改变当前接入的AMF的情况，这时会造成终端设备已经建立的PDU会话受到影响，进而，终端设备的业务会受到影响。
有鉴于此，本申请提供一种切片确定的方法及其装置，可以在终端设备注册网络的过程中，改善终端设备接入网络切片的方案，提升用户的体验。
上面对本申请中涉及到的术语做了简单说明，下文实施例中不再赘述。下文将结合附图详细说明本申请实施例提供的基于切片的通信方法。本申请提供的实施例可以应用于上述图1所示的网络架构中，不做限定。
为了更好地理解实施例，在此做出以下几点说明：
1、在本申请中，AMF网元可以简称为AMF，NSSF网元可以简称为NSSF，UDM网元可以简称为UDM，PCF网元可以简称为PCF，NWDAF网元可以简称为NWDAF，SMF网元可以简称为SMF。即本申请所描述的AMF均可替换为移动与接入性管理功能网元，NSSF均可替换为网络切片选择功能网元，UDM均可替换为统一数据管理网元，NWDAF均可替换为网络数据分析功能网元，SMF均可替换为会话管理功能网元。
2、本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
图4示出了本申请实施例提供的一种基于切片的通信方法400的示意图。图4对应的场景为：终端设备的目标网络切片中存在至少一个与终端设备的处于激活状态的会话对应 (或关联)的网络切片，以及，终端设备进行切换之前的跟踪区并不完全支持终端设备在注册请求消息中携带的请求网络切片。如下所述，该方法400包括以下步骤：
S401，第一接入和移动性管理功能网元获取终端设备的目标网络切片的信息。
其中，目标网络切片包括终端设备的请求网络切片中，不被终端设备当前的跟踪区支持，但是可以被其他跟踪区(例如，与终端设备当前的跟踪区有重叠部分的另一个频段的跟踪区)支持的网络切片。例如，目标网络切片的信息可以是target NSSAI。
例如，第一接入和移动性管理功能网元可以自己确定，或接收来自网络切片选择功能网元的目标网络切片的信息。
在可能实现的一种方式中，第一接入和移动性管理功能网元可以根据终端设备的第一允许网络切片中已经使用的网络切片确定目标网络切片，已经使用的网络切片可以是终端设备已经建立会话的网络切片，第一允许网络切片为第一接入和移动性管理功能网元在终端设备的上下文中保存的允许的网络切片。第一接入和移动性管理功能网元将第一允许网络切片中已经建立会话的网络切片，尤其是已经带有激活用户面的会话对应的网络切片添加到目标网络切片中。第一接入和移动性管理功能网元可以根据终端设备即将使用的网络切片确定目标网络切片，即将使用的网络切片是终端设备在请求网络切片中除第一允许网络切片之外新请求接入的网络切片。第一接入和移动性管理功能网元将即将使用的网络切片添加到目标网络切片中。这将结合后面的图6进一步描述。
S402，第一接入和移动性管理功能网元确定目标网络切片中的至少一个网络切片对应终端设备的处于激活状态的会话。
其中，处于激活状态的会话可以是指用户面处于激活状态的会话。
其中，目标网络切片的至少一个网络切片对应终端设备的处于激活状态的会话，并非特指目标网络切片中的所有网络切片对应终端设备的处于激活状态的会话，也可以仅为目标网络切片中的一个网络切片对应终端设备的处于激活状态的会话。
在可能实现的一种方式中，第一接入和移动性管理功能网元可以从终端设备的上下文中获取终端设备已经建立的会话在当前服务网络的单个网络切片选择辅助信息属性，即已经建立的会话对应的网络切片。
在可能实现的另一种方式中，第一接入和移动性管理功能网元可以从终端设备的注册请求中获得会话的状态(例如，PDU session status)信息，进而根据会话的状态信息确定终端设备的已经建立的会话的状态(例如会话的状态可以包括处于激活状态、处于去激活状态，激活或者已经释放的状态)。
在可能实现的再一种方式中，第一接入和移动性管理功能网元可以根据处于激活状态的会话以及目标网络切片，确定目标网络切片中的至少一个网络切片对应处于激活状态的会话。
具体地，可以根据处于激活状态的会话对应的网络切片，结合目标网络切片包括的网络切片，在处于激活状态的会话对应的至少一个网络切片属于目标网络切片中的情况下，确定目标网络切片中的至少一个网络切片对应处于激活状态的会话。
举例而言，允许的网络切片为{网络切片#1，网络切片#2，网络切片#3}，处于激活状态的会话对应的网络切片为{网络切片#3}，目标网络切片为{网络切片#3，网络切片#4}，由于处于激活状态的会话对应的网络切片中的网络切片#3属于目标网络切片，则可以确定 目标网络切片中的至少一个网络切片对应处于激活状态的会话。
应理解，因为目标网络切片中处于激活状态的会话的网络切片是来自允许的网络切片中，所以确定目标网络切片中的至少一个网络切片对应处于激活状态的会话等同于确定允许网络切片中的至少一个网络切片对应处于激活状态的会话。在另一种实现方式中，在终端设备当前的跟踪区并不完全支持终端设备的请求网络切片，第一接入和移动性管理功能网元也未获取终端设备的目标网络切片的情况下，第一接入和移动性管理功能网元也可以根据允许的网络切片(allowed NSSAI)，通过上述可能实现的任一种方式确定允许网络切片中的至少一个网络切片对应处于激活状态的会话。获取目标网络切片可以与确定允许网络切片中的至少一个网络切片对应处于激活状态的会话共同进行，也可以在其之后。
S403，第一接入和移动性管理功能网元向第一接入网设备发送将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区的指示信息。对应地，第一接入网设备接收来自第一接入和移动性管理功能网元的将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区的指示信息。
在可能实现的一种方式中，该指示信息为目标网络切片的信息，此时是通过目标网络切片的信息隐式地指示将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区。
在可能实现的另一种方式中，该指示信息为一个独立的指示信息，可以通过指示信息的指示比特位等方式进行指示。进一步地，第一接入和移动性管理功能网元还可以向第一接入网设备发送目标网络切片的信息。例如，该指示信息可以是切换指示(handover indication)。
也就是说，不管是哪种实现方式，第一接入和移动性管理功能网元都会向第一接入网设备发送目标网络切片的信息。第一接入和移动性管理功能网元可以通过目标网络切片的信息作为隐式的指示信息，或额外携带显示的指示信息(例如，切换指示)，使得收到信息的第一接入网设备可以知道需要发起切换，从而将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区。
因此，在目标网络切片中存在一个网络切片，且与该网络切片相关的任意一个PDU会话的用户面处于激活状态的情况下，第一接入和移动性管理功能网元可以向第一接入网设备发送目标网络切片的信息和上述切换指示。
举例而言，第一接入和移动性管理功能网元可以向第一接入网设备发送N2接口消息，该N2接口消息携带将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区的指示信息和目标网络切片的信息。
此外，该N2消息还可以携带第一接入和移动性管理功能网元通过第一接入网设备向终端设备发送的注册响应消息或终端设备配置更新消息。其中，该注册响应消息指示终端设备已经在第一接入和移动性管理功能网元注册成功。终端设备配置更新消息用于向终端提供最新的允许网络切片、RA中的至少一个。
应理解，在上述方案中，指示信息并不指示切换的具体的会话，仅指示需要进行会话的切换。换言之，当存在会话需要切换时，就会发送该指示信息，切换的具体的会话是由第一接入网设备在接收该指示信息之后确定的(详细确定方式可以参考下述S502中的相关描述)。该指示信息还可以指示第一接入网设备在无法找到满足切换条件时目标小区时，仍然将终端设备留在当前TA，不控制终端设备通过重定向方式重选支持目标网络切片的 小区，以确保处于激活状态的会话不会被去激活和中断。
基于上述方案，第一接入和移动性管理功能网元在确定目标网络切片中的至少一个网络切片对应的终端设备的处于激活状态的会话之后，可以向第一接入网设备发送将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区的指示信息。进而，相较于现有技术(例如，通过上述图2或图3所述的方式)中，在重定向终端设备处于激活状态的会话的过程中，终端设备需要先断开和重定向之前的跟踪区内的小区的RRC连接，进入RRC空闲状态，再重新驻留到重定向之后的跟踪区内的小区，从而终端设备已经建立的会话会被激活或中断的方式，本方案并不用释放RRC连接，而是第一接入和移动性管理功能网元在确定目标网络切片中的至少一个网络切片对应终端设备的处于激活状态的会话之后，向第一接入网设备发送将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区的指示信息，从而完成会话的切换。因此，本方案可以改善终端设备的业务的稳定性，避免终端设备在接入至支持终端设备的目标网络切片的小区之后并注册网络切片时终端设备处于激活状态的的会话受到中断影响，提升用户的体验。
可选地，为了确定终端设备用于在后续建立会话的网络切片，该方法400还可以包括下任一种方式：
在可能实现的一种方式中，第一接入和移动性管理功能网元可以将目标网络切片保存至终端设备的上下文中，在处于激活状态的会话完成切换之后，第一接入和移动性管理功能网元接收终端设备的注册请求消息，并根据注册请求消息中携带的请求网络切片与终端设备的上下文中保存的目标网络切片确定终端设备的第二允许网络切片。
具体地，在处于激活状态的会话完成切换之后，可以选择同时属于请求网络切片与目标网络切片的网络切片，组成第二允许网络切片。
举例而言，注册请求消息中携带的请求网络切片为{网络切片#1，网络切片#2，网络切片#3}，终端切换后进入的新的当前TA支持的网络切片为{网络切片#1，网络切片#2，网络切片#3}，终端设备的上下文中保存的目标网络切片为{网络切片#2，网络切片#3}，则第二允许网络切片为{网络切片#2，网络切片#3}，并不将UE在请求网络切片中同时新的当前所在TA也支持的网络切片#1加入到第二允许网络切片。也就是说，即便当前TA支持网络切片#1，由于终端设备的上下文中保存的目标网络切片不包括网络切片#1，所以第二允许网络切片不包括网络切片#1。
其中，第二允许网络切片用于终端设备在后续建立会话。
在可能实现的另一种方式中，第一接入和移动性管理功能网元将目标网络切片保存至终端设备的上下文中，之后，第一接入和移动性管理功能网元向第二接入和移动性管理功能网元发送上下文信息。
其中，上下文信息中的目标网络切片用于在终端设备处于激活状态的会话完成切换并发起注册请求之后，第二接入和移动性管理功能网元确定第二允许网络切片。
可选地，该方法400还包括：第一接入和移动性管理功能网元向第一接入网设备发送目标网络切片对应的RFSP信息。对应地，第一接入网设备接收来自第一接入和移动性管理功能网元的目标网络切片对应的RFSP信息。例如，RFSP信息为RFSP索引(index)。
其中，该RFSP信息用于确定无线测量指令，该无线测量指令用于在切换处于激活状态的会话之前，终端设备发现支持目标网络切片的跟踪区的小区。
在可能实现的一种方式中，该RFSP信息是第一接入和移动性管理功能网元根据本地配置策略确定的。
在可能实现的另一种方式中，该RFSP信息是第一接入和移动性管理功能网元请求策略控制网元获取的。
可选地，第一接入和移动性管理功能网元除了确定了目标网络切片之外，还可以确定允许的网络切片，进而可以根据该允许的网络切片确定确定相应的注册区，并将目标网络切片、允许的网络切片或允许的网络切片相应的注册区中的至少一项信息发送至终端设备。
举例而言，第一接入和移动性管理功能网元可以向终端设备发送注册响应消息，该注册响应消息携带目标网络切片、允许的网络切片或允许的网络切片相应的注册区中的至少一项信息。
图5示出了本申请实施例提供的一种基于切片的通信方法500的示意图。如下所述，该方法500包括以下步骤：
S501，第一接入网设备接收来自第一接入和移动性管理功能网元的终端设备的目标网络切片的信息。对应地，第一接入和移动性管理功能网元向第一接入网设备发送终端设备的目标网络切片的信息。
示例地，在第一接入和移动性管理功能网元获得目标网络切片之后，可以将目标网络切片的信息发送至第一接入网设备。
S502，第一接入网设备确定切换目标网络切片中的至少一个网络切片对应的终端设备的处于激活状态的会话。
首先，第一接入网设备可以接收来自第一接入和移动性管理功能网元的将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区的指示信息，并根据该指示信息确定切换目标网络切片中的至少一个网络切片对应的处于激活状态的会话。
一方面，该指示信息可以为目标网络切片的信息，此时可以把目标网络切片的信息作为一个触发条件，触发收到目标网络切片信息的第一接入网设备根据自身维护的终端设备的上下文，去判断目前是否存在处于激活状态的会话。如果存在，则第一接入网设备可以确定切换目标网络切片中的至少一个网络切片对应的终端设备的处于激活状态的会话。因此，可以理解为：通过目标网络切片的信息隐式地指示将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区。
另一方面，该指示信息可以为一个独立的指示信息，可以通过指示信息中的指示比特位等方式进行指示。例如，该指示信息可以是切换指示(handover indication)。因此，第一接入网设备直接根据指示信息就可以确定切换目标网络切片中的至少一个网络切片对应的终端设备的处于激活状态的会话。
举例而言，第一接入和移动性管理功能网元可以向第一接入网设备发送N2接口消息，该N2接口消息携带将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区的指示信息和目标网络切片的信息。
此外，该N2消息还可以携带第一接入和移动性管理功能网元通过第一接入网设备向终端设备发送的注册响应消息或终端设备配置更新消息。其中，该注册响应消息指示终端设备已经在第一接入和移动性管理功能网元注册成功。终端设备配置更新消息指示用于向终端提供最新的允许网络切片、RA中的至少一个。
应理解，在上述方案中，指示信息并不指示切换的具体的会话，仅指示需要进行会话的切换。换言之，当存在会话需要切换时，就会发送该指示信息。
因此，通过上述方式，第一接入网设备可以确定要发起切换流程。
其次，第一接入网设备可以根据自身维护的终端设备的上下文，获取终端设备的处于激活状态的会话对应的网络切片，根据目标网络切片中的至少一个网络切片对应处于激活状态的会话，确定切换处于激活状态的会话，即确定哪个会话需要切换。如果第一接入网设备在无法找到满足切换条件时目标小区时，仍然将终端设备留在当前TA，不控制终端设备通过重定向方式重选支持目标网络切片的小区，以确保处于激活状态的会话不会被去激活和中断。
具体地，第一接入网设备可以确定目标网络切片中的至少一个网络切片属于终端设备的处于激活状态的会话对应的网络切片，确定切换处于激活状态的会话。
举例而言，目标网络切片为{网络切片#1，网络切片#2，网络切片#3}，终端设备的处于激活状态的会话对应的网络切片为{网络切片#2}，则可以确定网络切片#2对应的会话为待切换的处于激活状态的会话。
之后，第一接入网设备可以向终端设备发送终端设备的无线测量指令(例如，通过无线资源管理重新配置消息向终端设备发送终端设备的无线测量指令)，终端设备将无线测量报告发送至第一接入网设备，如果无线测量报告指示支持目标网络切片的跟踪区的小区的信号强度达到预设门限，则第一接入网设备决定启动切换。
可选地，为了确定无线测量指令，该方法500还包括：第一接入网设备确定终端设备的无线测量指令。
其中，无线测量指令用于在切换处于激活状态的会话之前，发现支持目标网络切片的跟踪区的小区。
在可能实现的一种方式中，第一接入网设备根据目标网络切片的信息确定无线测量指令。
在可能实现的另一种方式中，第一接入网设备接收来自第一接入和移动性管理功能网元的目标网络切片对应的RFSP信息，之后，第一接入网设备根据该RFSP信息确定无线测量指令。
举例而言，可以在第一接入和移动性管理功能网元向第一接入网设备发送的注册响应消息中携带目标网络切片对应的RFSP信息。
S503，第一接入网设备将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区。
具体地，第一接入网设备可以向第一接入和移动性管理功能网元发送切换请求，其中携带了待切换的会话的信息，以及切换的目标小区的信息，其中，待切换的会话的信息为处于激活状态的会话的信息，切换的目标小区的信息为支持目标网络切片的跟踪区的小区。
第一接入和移动性管理功能网元收到上述切换请求后，确定管理支持目标网络切片的跟踪区的小区的第二接入网设备与第二接入和移动性管理功能网元连接，于是向第二接入和移动性管理功能网元发送创建终端设备上下文的请求消息，其中终端设备的上下文中包含目标网络切片的信息，之后，第二接入和移动性管理功能网元向第一接入和移动性管理功能网元发送终端设备上下文创建成功的响应消息。
由此，第一接入网设备、第二接入网设备、第一接入和移动性管理功能网元，以及第二接入和移动性管理功能网元共同将处于激活状态的会话的上下文从第一接入网设备和第一接入和移动性管理功能网元切换到第二接入网设备和第二接入和移动性管理功能网元，使得处于激活状态的会话切换至支持目标网络切片的跟踪区的小区。
其中，处于激活状态的会话的用户面路径在从第一接入网设备切换到第二接入网设备的切换过程中仍然可以正常传送终端设备的业务报文，不会中断。
基于上述方案，第一接入网设备在接收来自第一接入和移动性管理功能网元的终端设备的目标网络切片的信息之后，确定切换目标网络切片中的至少一个网络切片对应的终端设备的处于激活状态的会话，并将终端设备的处于激活状态的会话切换至支持目标网络切片的跟踪区的小区。进而，相较于现有技术(例如，通过上述图2或图3所述的方式)中，在重定向终端设备处于激活状态的会话的过程中，终端设备需要先断开和重定向之前的跟踪区内的小区的RRC连接，进入RRC空闲状态，再重新驻留到重定向之后的跟踪区内的小区，从而终端设备已经建立的会话会被激活或中断的方式，本方案并不用释放RRC连接，而是第一接入网设备在确定目标网络切片中的至少一个网络切片对应终端设备的处于激活状态的会话之后，将终端设备的处于激活状态的会话切换至支持目标网络切片的跟踪区的小区。因此，本方案可以改善终端设备的业务的稳定性，避免终端设备在接入至支持终端设备的目标网络切片的小区之后并注册网络切片时终端设备的处于激活状态的会话受到中断影响，提升用户的体验。
图6示出了本申请实施例提供的一种基于切片的通信方法600的示意图。如下，该方法600包括以下步骤：
S601，网络设备获取终端设备的已经使用的网络切片或终端设备的即将使用的网络切片中的至少一项信息，以及终端设备的请求网络切片信息。
其中，网络设备可以包括网络切片选择功能网元，或者接入和移动性管理功能网元。
在网络设备包括接入和移动性管理功能网元的情况下，网络设备获取已经使用的网络切片或即将使用的网络切片中的至少一项信息，可以包括以下至少一种方式：
一种可能的方式，网络设备可以根据终端设备的会话状态信息确定已经使用的网络切片的信息，其中，会话状态信息可以携带于终端设备向接入和移动性管理功能网元发送的注册请求消息之中。
具体地，网络设备可以通过会话状态信息确定已经建立的会话，即确定该终端设备已经建立了会话。例如，当会话状态信息指示激活(active),则表示该终端设备已经建立了会话。然后，网络设备可以根据终端设备在上下文确定已经建立的会话对应的网络切片，即，已经使用的网络切片。
另一种可能的方式，网络设备包括接入和移动性管理功能网元的情况下。网络设备可以根据终端设备的请求网络切片(requested NSSAI)和网络设备存储的终端设备的上下文中的第四允许网络切片确定即将使用的网络切片的信息；或者，网络设备也可以向网络切片选择功能网元请求第四允许网络切片的信息，并根据终端设备的请求网络切片和第四允许网络切片确定即将使用的网络切片的信息；其中，请求网络切片可以携带于终端设备向接入和移动性管理功能网元发送的注册请求消息之中。
具体地，网络设备可以选择请求网络切片中，不属于第四允许网络切片的网络切片， 组成即将使用的网络切片。
举例而言，请求网络切片为{网络切片#1，网络切片#2，网络切片#3}，第四允许网络切片为{网络切片#2，网络切片#3}，则网络设备可以确定即将使用的网络切片为{网络切片#1}。
再一种可能的方式，网络设备可以接收来自网络数据分析功能网元的终端设备的通信分析结果信息，并根据通信分析结果信息确定即将使用的网络切片的信息。
另一种可能的方式，在网络设备包括网络切片选择功能网元的情况下，网络设备可以从接入和移动性管理功能网元接收终端设备的已经使用的网络切片或终端设备的即将使用的网络切片中的至少一项信息。
此外，在网络设备包括网络切片选择功能网元的情况下，网络设备接收来自接入和移动性管理功能网元(后续称之为第一接入和移动性管理功能网元)的网络切片选择请求之后，如果网络设备判断终端设备当前所在的跟踪区支持终端设备的请求网络切片，但是第一接入和移动性管理功能网元不支持终端设备的请求网络切片，网络设备则可以确定一个连接终端设备当前所在的跟踪区的，并且支持终端设备的请求网络切片的新的接入和移动性管理功能网元(后续称之为第二接入和移动性管理功能网元)，并将第二接入和移动性管理功能网元的信息发送至第一接入和移动性管理功能网元；之后，第一接入和移动性管理功能网元将终端设备的注册请求消息转发至第二接入和移动性管理功能网元进行处理，其中，该注册请求消息的描述可以参考上述注册请求消息的描述；最后，如果网络设备判断终端设备当前所在的跟踪区不支持终端设备的请求网络切片，网络设备可以确定终端设备的目标网络切片，此时不向第一接入和移动性管理功能网元返回第二接入和移动性管理功能网元的信息。
S602，网络设备根据已经使用的网络切片或即将使用的网络切片中的至少一项，以及请求网络切片确定终端设备的第一允许网络切片。
在可能实现的第一种方式中，网络设备可以根据终端设备已经使用的网络切片或终端设备即将使用的网络切片中的至少一项、以及终端设备的注册请求消息携带的请求网络切片确定第一允许网络切片。
具体地，网络设备可以选择请求网络切片中同时属于已经使用的网络切片或即将使用的网络切片中的网络切片，组成第一允许网络切片。
举例而言，如果终端设备当前所在的TA支持{网络切片#1，网络切片#2，网络切片#3}，网络设备可以根据终端设备的已经使用的网络切片(例如，{网络切片#3})和即将使用的网络切片(例如，{网络切片#2})，以及请求网络切片{例如，网络切片#1，网络切片#2，网络切片#3}，确定终端设备的第一允许网络切片(例如，{网络切片#2，网络切片#3})。虽然终端设备当前所在TA也支持请求网络切片中的网络切片#1，但是因为它不属于已经使用的网络切片或即将使用的网络切片，所以没有被包含在第一允许网络切片中。换句话说，如果终端设备请求的一个网络切片不属于终端设备已经使用的网络切片或终端设备即将使用的网络切片，那么即便终端设备当前所在TA也支持这个网络切片，网络设备在确定第一允许的网络切片的时候也将其排除，或者，也可以理解成将其过滤，使得最终确定的第一允许的网络切片的中的每一个网络切片都是属于终端设备已经使用的网络切片或终端设备即将使用的网络切片。这样确定出来的允许的网络切片相比于现有技术方式中确 定出来的允许的网络切片，包括更少数量的网络切片。
在可能实现的第二种方式中，如果终端设备没有提供请求的网络切片(例如，该终端设备是第一次在网络设备(例如，接入和移动性管理功能网元)进行网络注册)，则网络设备可以根据终端设备的注册请求消息携带的请求网络切片、终端设备已经使用的网络切片，以及终端设备当前的跟踪区支持的网络切片确定第一允许网络切片。
具体地，网络设备可以选择同时属于已经使用的网络切片或即将使用的网络切片中的至少一项的网络切片、以及属于终端设备当前的跟踪区支持的网络切片组成第一允许网络切片。
举例而言，网络设备可以根据终端设备的已经使用的网络切片(例如，{网络切片#3})和即将使用的网络切片(例如，{网络切片#2})，以及终端设备当前所在的跟踪区支持的网络切片为{网络切片#3,网络切片#4}，确定终端设备的第一允许网络切片(例如，{网络切片#3})。
在可能实现的第三种方式中，如果终端设备已经在网络设备已完成网络注册，终端设备向网络设备发送的网络注册更新请求中携带的请求网络切片中的至少一个网络切片不包含在之前确定的(保存在终端设备的上下文中的)允许网络切片中，则将不包含在之前确定的(保存在终端设备的上下文中的)允许网络切片的请求网络切片中的至少一个网络切片作为终端设备期望使用的网络切片(例如，终端设备切换之前的跟踪区仅支持包含在之前确定的允许网络切片的请求网络切片，但是终端设备切换之后的跟踪区支持之前确定的允许网络切片，则可以将不包含在之前确定的允许网络切片的请求网络切片中的至少一个网络切片作为终端设备期望使用的网络切片)，也就是即将使用的网络切片，加入之前确定的(保存在终端设备的上下文中的)允许网络切片，获得第一允许网络切片。
可能实现的第三种方式可以和前两种可能的实现方式相互结合。
举例而言，终端设备上一次注册网络后收到的允许的网络切片包括{网络切片#1,网络切片#3}。上一次注册的TA不支持网络切片4，因此网络切片4不包括在允许的网络切片中。之后，终端设备在新的TA发起注册更新流程，且注册更新消息携带的请求网络切片为{网络切片#3,网络切片#4})。由于新的TA支持网络切片3和网络切片4，网络设备可以根据本次网络注册更新消息携带的请求网络切片、终端设备上一次注册网络后收到的允许的网络切片、和终端设备当前所在的跟踪区支持的网络切片，确定即将使用的网络切片(例如，{网络切片#4})，然后将其加入之前确定的允许的网络切片包括{网络切片#1,网络切片#3}，确定终端设备最新的第一允许网络切片(例如，{网络切片#1,网络切片#3,网络切片#4})。
在可能实现的第四种方式中，如果后续终端设备通过某个网络切片建立的会话被释放，一段时间之后，终端设备仍然使用请求网络切片包含的该网络切片发起注册请求，网络设备可以确定之前确定的(保存在终端设备的上下文中的)允许网络切片中的该网络切片并没有正在进行的会话，假如上述被释放的会话的释放时间超过了预设的阈值，网络设备则将该网络切片从之前确定的(保存在终端设备的上下文中的)允许网络切片中删去或剔除，获得第一允许网络切片。
可能实现的第三种方式可以和前三种可能的实现方式相互结合。
举例而言，网络设备可以根据被释放的会话对应的网络切片(例如，{网络切片#3})，终端设备请求的网络切片{网络切片#3，网络切片#4}，以及之前确定的允许网络切片中(例 如，{网络切片#3，网络切片#4})，确定终端设备的第一允许网络切片(例如，{网络切片#4})。虽然终端设备当前所在TA也支持请求网络切片中的网络切片#3，但是因为它不属于已经使用的网络切片或即将使用的网络切片，所以没有被包含在第一允许网络切片中。
此外，网络设备可以通过网络切片选择功能网元获取第一允许网络切片。
进一步地，网络设备还可以根据第一允许网络切片和终端设备当前所在的跟踪区，进而确定第一允许网络切片对应的注册区，其中该注册区是由终端设备当前所在跟踪区，以及与该跟踪区相邻或相近的支持第一允许网络切片的其它跟踪区组成的。
S603，网络设备发送第一允许网络切片的信息。
在网络设备包括网络切片选择功能网元的情况下，网络设备可以向接入和移动性管理功能网元发送第一允许网络切片的信息；
在网络设备包括接入和移动性管理功能网元的情况下，网络设备可以向终端设备发送第一允许网络切片的信息。
举例而言，网络设备可以向终端设备发送注册响应消息或终端设备配置更新消息，该注册响应消息或终端设备配置更新消息携带第一允许网络切片或第一允许网络切片相应的注册区中的至少一项信息。
应理解，在本方案中确定第一允许网络切片的方法，同样适用于本申请其他实施例确定第一允许网络切片的场景。
可选地，该方法600还包括：网络设备获取终端设备所在的跟踪区支持的网络切片的信息。
在网络设备包括网络切片选择功能网元的情况下，网络设备可以通过接入和移动性管理功能网元获取终端设备所在的跟踪区支持的网络切片的信息。
在网络设备包括接入和移动性管理功能网元的情况下，网络设备可以通过接入网设备获取终端设备所在的跟踪区支持的网络切片的信息。
进一步地，在跟踪区不支持即将使用的网络切片中的至少一个网络切片的情况下，该方法600还包括：网络设备根据已经使用的网络切片或即将使用的网络切片中的至少一项，以及请求网络切片确定终端设备的目标网络切片。该方式同样适用于本申请其他实施例确定目标网络切片的场景。也就是说，图4中的步骤401，接入和移动性管理网元也可以通过如下方式获得目标网络切片的信息。
在可能实现的一种方式中，网络设备可以选择请求网络切片中属于已经使用的网络切片或即将使用的网络切片中的至少一项的网络切片，组成目标网络切片。
其中，目标网络切片包括终端设备的请求网络切片中，不被终端设备当前的跟踪区支持，但是可以被其他跟踪区(例如，与终端设备当前的跟踪区有重叠部分的另一个频段的跟踪区)支持的网络切片。例如，目标网络切片的信息可以是target NSSAI。
以及，目标网络切片包括终端设备在上下文保存的允许网络切片中已经使用的网络切片，以及即将使用的网络切片，其中，已经使用的网络切片可以是终端设备已经建立的会话对应的网络切片，即将使用的网络切片可以是终端设备期望建立的会话的网络切片；此外，终端设备期望建立的会话可以是终端设备期望建立，且还从未建立的会话，也可以是已被释放的，但是终端设备期望建立的会话(例如，业务连续性模式2或模式3的会话)。
在一种实现方式中，如果终端设备已经注册到网络设备，网络设备则可以获得之前保 存的终端设备的允许网络切片，如果终端设备发起的注册请求消息携带的请求网络切片中的一个或多个网络切片并不属于上述的允许网络切片，则该一个或多个网络切片为即将使用的网络切片，网络设备可以选择请求网络切片中属于已经使用的网络切片或即将使用的网络切片中的至少一项的网络切片，组成目标网络切片。
进一步地，目标网络切片还可能包含终端设备当前的跟踪区不支持的至少一个网络切片。
举例而言，假设终端设备当前所在TA支持的网络切片为{网络切片#2、网络切片#3、网络切片#4}，网络设备之前保存的终端设备的允许网络切片为{网络切片#3、网络切片#4}，请求网络切片为{网络切片#1、网络切片#2、网络切片#4}。网络设备确定即将使用的网络切片为{网络切片#1、网络切片#2}，已经使用的网络切片为{网络切片#3}，则目标网络切片为{网络切片#1、网络切片#2、网络切片#3}。
在可能实现的另一种方式中，网络设备可以根据终端设备的上下文中保存的允许网络切片中已经使用的网络切片确定目标网络切片。
举例而言，网络设备可以选择终端设备的上下文中保存的允许网络切片中属于终端设备已经使用的网络切片的网络切片为目标网络切片，或者网络设备可以剔除终端设备的上下文中保存的允许网络切片中不属于终端设备已经使用的网络切片的网络切片，确定目标网络切片。
进一步地，网络设备可以根据终端设备的上下文中保存的允许网络切片中已经使用的网络切片，以及终端设备的即将使用的网络切片确定目标网络切片。
举例而言，终端设备当前所在TA支持的网络切片为{网络切片#2、网络切片#3、网络切片#4}，网络设备之前保存的终端设备的允许网络切片为{网络切片#3、网络切片#4}，请求网络切片为{网络切片#1、网络切片#2、网络切片#3、网络切片#4}。网络设备确定即将使用的网络切片为{网络切片#1、网络切片#2}，已经使用的网络切片为{网络切片#3}，则目标网络切片为{网络切片#1、网络切片#2、网络切片#3}。其中，网络设备剔除了终端设备的上下文中保存的允许网络切片中不属于终端设备已经使用的网络切片的网络切片以及不属于即将使用的网络切片的网络切片(例如，{网络切片#4})，组成目标网络切片。
在可能实现的再一种方式中，网络设备还可以接收来自网络切片选择功能网元的目标网络切片的信息。
应理解，在上述方案中，终端设备在当前注册区确定目标网络切片，如果终端设备发生了跟踪区的改变，改变之后的跟踪区完全支持目标网络切片，则目标网络切片与改变跟踪区之后的终端设备的(第一)允许网络切片是相同的。因此，确定目标网络切片的实现方式可以与上述确定允许的网络切片的方式是类似的，此处不再赘述。
可选地，在该网络设备包括接入和移动性管理功能网元的情况下，该方法600还包括：网络设备接收来自第二网络切片选择功能网元的终端设备的第二允许网络切片，之后，网络设备从第二允许网络切片中选出属于已经使用的网络切片或属于即将使用的网络切片中的至少一项的网络切片，组成终端设备的第三允许网络切片。
其中，第二允许网络切片可以是第二网络切片选择功能网元通过现有技术确定的，即，第二网络切片选择功能网元根据终端设备的注册请求消息携带的请求网络切片，以及终端设备所在的注册区支持的网络切片确定的。
可选地，在确定第三允许网络切片之后，网络设备可以向终端设备发送第三允许网络切片的信息。
举例而言，第二允许网络切片为{网络切片#1、网络切片#2、网络切片#3、网络切片#4}，已经使用的网络切片为{网络切片#2、网络切片#3}，即将使用的网络切片为{网络切片#1}，则第三允许网络切片为{网络切片#1、网络切片#2、网络切片#3}。
应理解，在本申请的各个实施例中，终端设备的已经使用的网络切片或终端设备的即将使用的网络切片中的至少一项是指仅包括终端设备的已经使用的网络切片的情况，以及同时包括终端设备的已经使用的网络切片和终端设备的即将使用的网络切片的情况。
基于上述方案，网络设备在获取终端设备的已经使用的网络切片或该终端设备的即将使用的网络切片中的至少一项信息，以及该终端设备的请求网络切片信息之后，可以根据上述信息确定终端设备的第一允许网络切片或第三允许网络切片，并发送该第一允许网络切片的信息或第三允许网络切片的信息。由于经过本实施例的处理，对第一允许网络切片或第三允许网络切片包含的网络切片数量进行了缩减，所以能够根据终端设备的通信需求确定合适的允许网络切片，实现允许网络切片对应的注册区的范围尽可能大，减少终端设备移动过程中的信令负荷。
进一步地，该方法600还可以包括：网络设备获取终端设备的第一拒绝网络切片的信息，之后，网络设备删除第一拒绝网络切片中终端设备的注册区中的任一跟踪区支持的网络切片，获得终端设备的第二拒绝网络切片，其中，注册区是根据上述第三允许网络切片确定的，第二拒绝网络切片指示在当前注册区内拒绝终端设备请求接入第二拒绝网络切片中的网络切片。或者，在另一种实现方式中，网络设备可以不用先获取终端设备的第一拒绝网络切片的信息，而是直接确定第二拒绝网络切片的信息。其中，第二拒绝网络切片的信息用于指示在当前注册区内拒绝终端设备请求接入第二拒绝网络切片中的网络切片，且第二拒绝网络切片的信息中剔除了终端设备的注册区中的任一跟踪区支持的网络切片。
举例而言，第一拒绝网络切片为{网络切片#1、网络切片#2、网络切片#3、网络切片#4}，注册区中存在某一跟踪区支持的网络切片为{网络切片#2、网络切片#3}，则第二拒绝网络切片为{网络切片#1、网络切片#4}。
需要说明的是，上述确定拒绝网络切片的方式并不限定要通过如上方式确定第三允许网络切片。例如，也可以通过现有技术的方式或其他方式确定允许的网络切片并确定相应的注册区。只是在确定拒绝网络切片的时候，考虑将注册区中的任一跟踪区支持的网络切片从拒绝的网络切片中剔除掉，从而减少拒绝的网络切片中包含的网络切片的数量。
更进一步地，网络设备可以向终端设备发送第二拒绝网络切片的信息。
举例而言，网络设备可以向终端设备发送注册响应消息或终端设备配置更新消息，该注册响应消息指示终端设备注册成功，还可以携带第二拒绝网络切片的信息。终端设备配置更新消息指示用于向终端提供最新的允许网络切片、RA中的至少一个，还可以携带第二拒绝网络切片的信息。
因此，通过对第一拒绝网络切片进一步处理，得到第二拒绝网络切片，可以使得终端设备的拒绝网络切片包含的网络切片更少，尽可能地扩大终端设备可以使用的网络切片的范围，进而扩大相应的注册区的范围，减少终端移动过程中的信令负荷。
图7示出了本申请实施例提供的一种基于切片的通信方法700的示意图。图7将结合图4 和图5进行描述。如下，该方法700包括以下步骤：
S701，终端设备向第一接入和移动性管理功能网元发送第一注册请求消息。对应地，第一接入和移动性管理功能网元接收来自终端设备的第一注册请求消息。
其中，第一注册请求消息可以包括终端设备的请求网络切片(requested NSSAI)。
S702，第一接入和移动性管理功能网元向网络切片选择功能网元发送切片选择请求消息。对应地，网络切片选择功能网元接收来自第一接入和移动性管理功能网元的切片选择请求消息。
示例地，第一接入和移动性管理功能网元可以确认请求网络切片中的每个网络切片都是终端设备签约的网络切片，或者是终端设备签约的网络切片映射到终端设备当前拜访网络的网络切片；之后，第一接入和移动性管理功能网元可以确定终端设备的已经使用的网络切片或终端设备的即将使用的网络切片；最后，第一接入和移动性管理功能网元可以向网络切片选择功能网元发送切片选择请求消息，请求网络切片选择功能网元为终端设备确定终端设备的目标网络切片(target NSSAI)和允许网络切片(allowed NSSAI)，其中，切片选择请求消息不仅携带终端设备当前的跟踪区、终端设备的请求网络切片等信息，还可以携带已经使用的网络切片或即将使用的网络切片中的至少一项信息。
其中，第一接入和移动性管理功能网元可以确定已经使用的网络切片或即将使用的网络切片的描述，可以参考S601中网络设备获取已经使用的网络切片或即将使用的网络切片的相关描述，为了简洁，本申请在此不做赘述。
应理解，在上述方案中，如果由第一接入和移动性管理功能网元独立执行网络切片确定终端设备的允许网络切片和目标网络切片的步骤，则不执行第一接入和移动性管理功能网元向网络切片选择功能网元发送切片选择请求消息。
S703，第一接入和移动性管理功能网元或网络切片选择功能网元确定终端设备的目标网络切片。
示例地，第一接入和移动性管理功能网元或网络切片选择功能网元可以根据终端设备的已经使用的网络切片或即将使用的网络切片中的至少一项，以及请求网络切片确定终端设备的目标网络切片。
其中，如果是网络切片选择功能网元执行切片选择，网络切片选择功能网元可以将目标网络切片中的至少一项信息通过网络切片选择响应消息发送给第一接入和移动性管理功能网元。
进一步地，网络切片选择响应消息还可以包括此次请求注册的终端设备的允许网络切片的信息。
具体地，第一接入和移动性管理功能网元或网络切片选择功能网元可以根据终端设备的已经使用的网络切片或即将使用的网络切片中的至少一项，以及请求网络切片确定终端设备的目标网络切片的描述，可以参考上述S603中网络设备根据已经使用的网络切片或即将使用的网络切片中的至少一项，以及请求网络切片确定终端设备的目标网络切片的相关描述，为了简洁，本申请在此不做赘述。如果是网络切片选择功能网元确定终端设备的目标网络切片，那么第一接入和移动性管理功能网元通过网络切片选择响应消息从网络切片选择功能网元获得终端设备的目标网络切片。
之后，第一接入和移动性管理功能网元可以在终端设备的上下文中记录目标网络切片。
在可能实现的另一种方式中，如果网络切片选择功能网元判断终端设备当前所在的跟踪区支持终端设备的请求网络切片，但是第一接入和移动性管理功能网元不支持终端设备的请求网络切片，网络切片选择功能网元则可以确定一个连接终端设备当前所在的跟踪区的，并且支持终端设备的请求网络切片的第二接入和移动性管理功能网元，并将第二接入和移动性管理功能网元的信息发送至第一接入和移动性管理功能网元；之后，第一接入和移动性管理功能网元将终端设备的注册请求消息转发至第二接入和移动性管理功能网元进行处理；如果网络切片选择功能网元判断终端设备当前所在的跟踪区不支持终端设备的请求网络切片，网络切片选择功能网元可以确定终端设备的目标网络切片，并向第一接入和移动性管理功能网元返回终端设备的目标网络切片的信息。
S704，第一接入和移动性管理功能网元确定目标网络切片中的至少一个网络切片对应终端设备的处于激活状态的会话。
具体地，关于第一接入和移动性管理功能网元确定目标网络切片中的至少一个网络切片对应终端设备的处于激活状态的会话的描述，可以参考上述S402中第一接入和移动性管理功能网元确定目标网络切片中的至少一个网络切片对应终端设备的处于激活状态的会话的相关描述，为了简洁，本申请在此不做赘述。
S705，第一接入和移动性管理功能网元向第一接入网设备发送将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区的指示信息。对应地，第一接入网设备接收来自第一接入和移动性管理功能网元的将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区的指示信息。
具体地，关于第一接入和移动性管理功能网元向第一接入网设备发送将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区的指示信息的描述，可以参考上述S403中第一接入和移动性管理功能网元向第一接入网设备发送将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区的指示信息的相关描述，为了简洁，本申请在此不做赘述。
可选地，第一接入和移动性管理功能网元还可以通过第一接入网设备向终端设备发送第一注册响应消息，该第一注册响应消息指示终端设备注册成功，可以携带此次请求注册的终端设备的允许网络切片，或者注册区中的至少一项信息。进一步地，注册响应消息还可以携带拒绝网络切片。例如，拒绝网络切片为请求网络切片中当前终端设备的注册区不支持的网络切片，表示拒绝终端设备在当前注册区内继续请求接入拒绝网络切片中的网络切片。
具体的，第一接入和移动性管理功能网元向第一接入网设备发送N2接口消息，向终端设备发送第一注册响应消息可以封装在N2接口消息中传递。N2接口消息携带目标网络切片，可选地，N2接口消息还可以携带指示信息以及目标网络切片对应的RFSP信息中的至少一项。其中，目标网络切片对应的RFSP信息是第一接入和移动性管理功能网元根据本地配置策略确定的，或者是由第一接入和移动性管理功能网元请求策略控制功能网元获取的。例如，RFSP信息为RFSP索引(index)。
S706，第一接入网设备确定将终端设备的处于激活状态的会话切换至支持目标网络切片的跟踪区的小区。
示例地，第一接入网设备可以通过上述步骤S705接收来自第一接入和移动性管理功能 网元的将终端设备的处于激活状态的会话切换至支持目标网络切片的跟踪区的小区的指示信息，根据该指示信息确定将终端设备的处于激活状态的会话切换至支持目标网络切片的跟踪区的小区。
具体地，关于将终端设备的处于激活状态的会话切换至支持目标网络切片的跟踪区的小区的指示信息的描述，可以参考上述S403中关于将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区的指示信息的相关描述，为了简洁，本申请在此不做赘述。
示例地，第一接入网设备根据N2接口消息携带的指示信息确定将终端设备的处于激活状态的会话切换至支持目标网络切片的跟踪区的小区。第一接入网设备可以根据N2接口消息携带的目标网络切片对应的RFSP索引为终端设备生成测量配置消息。
S707，第一接入网设备向终端设备发送测量配置消息。对应地，终端设备接收来自第一接入网设备的测量配置消息。
示例地，第一接入网设备可以通过无线资源管理重新配置消息向终端设备发送测量配置消息，其中携带的无线参数指示终端设备测量终端设备所在的跟踪区的相邻跟踪区的小区所在频段的信号质量。，
举例而言，第一接入和移动性管理功能网元或网络切片选择功能网元确定终端设备当前所在的跟踪区#3不支持目标网络切片，但是覆盖跟踪区#3相同区域或周边区域的跟踪区#4和跟踪区#5支持目标网络切片，或者和跟踪区#3相邻的跟踪区#4和跟踪区#5支持目标网络切片，则测量配置消息携带的无线参数指示终端设备测量跟踪区#4的小区或跟踪区#5的小区所在频段的信号质量。
S708，终端设备向第一接入网设备发送测量结果消息。对应地，第一接入网设备接收来自终端设备的测量结果消息。
S709，第一接入网设备进行切换决策。
示例地，如果终端设备当前的小区的相邻小区(位于跟踪区#4或跟踪区#5中)的信号强度达到满足切换标准的指定门限，第一接入网设备可以决定启动切换。
S710，第一接入网设备向第一接入和移动性管理功能网元发送切换请求消息。对应地，第一接入和移动性管理功能网元接收来自第一接入网设备的切换请求消息。
示例地，第一接入网设备确定切换终端设备处于激活状态的会话到目标小区需要经过核心网网元的控制，向第一接入和移动性管理功能网元发送切换请求，其中携带了等待切换的会话的信息，以及切换的目标小区的信息(例如，切换的目标小区的信息包括目标小区所属的跟踪区TA的标识，以及管理目标小区归属的第二接入网设备的标识)。例如，该会话可以是已经通过网络切片#3和网络切片#4分别建立的会话的信息。
S711，第一接入和移动性管理功能网元向第二接入和移动性管理功能网元传递终端设备的上下文。
示例地，第一接入和移动性管理功能网元收到切换请求消息之后，根据目标小区的信息中的第二接入网设备的标识确定管理目标小区的第二接入网设备与第二接入和移动性管理功能网元连接，于是向第二接入和移动性管理功能网元发送创建终端设备上下文的请求消息，其中，该消息中携带了终端设备上下文，终端设备的上下文中包含目标网络切片的信息，第二接入和移动性管理功能网元向第一接入和移动性管理功能网元回应终端设备上下文创建成功的响应消息。
S712，第一接入网设备、第二接入网设备、第一接入和移动性管理功能网元、第二接入和移动性管理功能网元，以及会话管理功能网元共同进行处于激活状态的会话的切换。
示例地，第一接入网设备、第二接入网设备、第一接入和移动性管理功能网元、第二接入和移动性管理功能网元，以及会话管理功能网元可以协同将处于激活状态的会话的上下文从第一接入网设备和第一接入和移动性管理功能网元切换到第二接入网设备和第二接入和移动性管理功能网元。
之后，会话管理功能网元控制第一接入网设备、第二接入网设备和用户面功能网元将处于激活状态的会话的用户面路径从第一接入网设备切换到第二接入网设备。因此，处于激活状态的会话在切换过程中仍然可以正常传送终端设备的业务报文，会话不会中断。
基于上述方案，第一接入和移动性管理功能网元在确定目标网络切片中的至少一个网络切片对应的终端设备的处于激活状态的会话之后，可以向第一接入网设备发送将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区的指示信息。进而，相较于现有技术(例如，通过上述图2或图3所述的方式)中，在重定向终端设备处于激活状态的会话的过程中，终端设备需要先断开和重定向之前的跟踪区内的小区的RRC连接，进入RRC空闲状态，再重新驻留到重定向之后的跟踪区内的小区，从而终端设备已经建立的会话会被激活或中断的方式，本方案并不用释放RRC连接，而是第一接入和移动性管理功能网元在确定目标网络切片中的至少一个网络切片对应终端设备的处于激活状态的会话之后，向第一接入网设备发送将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区的指示信息，从而完成会话的切换。因此，本方案可以改善终端设备的业务的稳定性，避免终端设备在接入至支持终端设备的目标网络切片的小区之后并注册网络切片时终端设备处于激活状态的的会话受到中断影响，提升用户的体验。
可选的，该方法还包括：
S713，终端设备向第二接入和移动性管理功能网元发送第二注册请求消息。对应地，第二接入和移动性管理功能网元接收来自终端设备的第二注册请求消息。
示例地，完成切换后，终端设备发现目前接入的小区不属于原来的注册区，于是通过第二接入网设备向第二接入和移动性管理功能网元发送第二注册请求消息，第二注册请求消息携带请求网络切片。终端设备在离开原来的注册区之后，可以尝试尽可能多地注册网络切片。
S714，第二接入和移动性管理功能网元或网络切片选择功能网元确定终端设备的允许网络切片。
在可能实现的一种方式中，第二接入和移动性管理功能网元接收终端设备切换后的注册请求，使用终端设备的上下文中记录的目标网络切片确定终端设备已经使用的网络切片或终端设备即将使用的网络切片中的至少一项，然后根据终端设备已经使用的网络切片或终端设备即将使用的网络切片中的至少一项，以及请求网络切片确定终端设备的第一允许网络切片，进而确定允许网络切片对应的跟踪区，以及允许网络切片对应的注册区。
在可能实现的另一种方式中，第二接入和移动性管理功能网元在确定终端设备已经使用的网络切片或终端设备即将使用的网络切片中的至少一项之后，可以将终端设备已经使用的网络切片或终端设备即将使用的网络切片中的至少一项，以及请求网络切片发送至网络切片选择功能网元，由网络切片选择功能网元根据终端设备已经使用的网络切片或终端 设备即将使用的网络切片中的至少一项，以及请求网络切片确定终端设备的第一允许网络切片，进而确定第一允许网络切片对应的跟踪区，以及第一允许网络切片对应的注册区。
其中，关于第二接入和移动性管理功能网元或网络切片选择功能网元根据终端设备已经使用的网络切片或终端设备即将使用的网络切片中的至少一项，以及请求网络切片确定终端设备的第一允许网络切片的描述，可以参考上述S602中网络设备根据已经使用的网络切片或即将使用的网络切片中的至少一项，以及请求网络切片确定终端设备的第一允许网络切片的相关描述，为了简洁，本申请在此不再赘述。
S715，第二接入和移动性管理功能网元向终端设备发送第二注册响应消息。对应地，终端设备接收来自第二接入和移动性管理功能网元的第二注册响应消息。
示例地，第二接入和移动性管理功能网元可以通过第二接入网设备向终端设备发送第二注册响应消息，该注册响应消息可以携带允许网络切片的信息，或者允许网络切片的信息和允许网络切片对应的注册区的信息。
通过上述方案，可以根据终端设备的通信需求确定终端设备合适的允许网络切片，使得允许网络切片的网络切片数量减少，实现允许网络切片对应的注册区的范围尽可能扩大，减少终端设备移动过程中的信令负荷。
图8示出了本申请实施例提供的一种基于切片的通信方法800的示意图。图8和图7的差别在于，图7所示的方法适用于需要变化接入和移动性管理功能网元的方案，图8所示的方法适用于不需要变化接入和移动性管理功能网元的方案。此外，作为替代步骤704的另外一种可能的实现方式，如果第一接入和移动性管理功能网元并未确定目标网络切片中的至少一个网络切片对应终端设备的处于激活状态的会话，那么在图8所示的方法就可以由第一接入网设备确定切换目标网络切片中的至少一个网络切片对应的终端设备的处于激活状态的会话。该方法800包括以下步骤：
S801，终端设备向接入和移动性管理功能网元发送第一注册请求消息。对应地，接入和移动性管理功能网元接收来自终端设备的第一注册请求消息。
其中，第一注册请求消息可以包括终端设备的请求网络切片。
S802，接入和移动性管理功能网元向网络切片选择功能网元发送切片选择请求消息。对应地，网络切片选择功能网元接收来自接入和移动性管理功能网元的切片选择请求消息。
示例地，接入和移动性管理功能网元可以确认请求网络切片中的每个网络切片都是终端设备签约的网络切片，或者是终端设备签约的网络切片映射到终端设备当前拜访网络的网络切片；之后，接入和移动性管理功能网元可以确定已经使用的网络切片或即将使用的网络切片；最后，接入和移动性管理功能网元可以网络切片选择功能网元发送切片选择请求消息，请求网络切片选择功能网元为终端设备选择网络切片，其中，切片选择请求消息不仅携带终端设备当前的跟踪区、终端设备的请求网络切片等信息，还可以携带已经使用的网络切片或即将使用的网络切片中的至少一项信息。
其中，接入和移动性管理功能网元可以确定已经使用的网络切片或即将使用的网络切片的描述，可以参考S601中网络设备获取已经使用的网络切片或即将使用的网络切片的相关描述，为了简洁，本申请在此不做赘述。
应理解，在上述方案中，如果由接入和移动性管理功能网元独立执行网络切片选择的步骤，则不执行接入和移动性管理功能网元向网络切片选择功能网元发送切片选择请求消 息。
S803，接入和移动性管理功能网元或网络切片选择功能网元确定终端设备的目标网络切片。
示例地，接入和移动性管理功能网元或网络切片选择功能网元可以根据终端设备的已经使用的网络切片或即将使用的网络切片中的至少一项，以及请求网络切片确定终端设备的目标网络切片。
具体地，接入和移动性管理功能网元或网络切片选择功能网元根据终端设备的已经使用的网络切片或即将使用的网络切片中的至少一项，以及请求网络切片确定终端设备的目标网络切片的描述，可以参考上述S603中网络设备根据已经使用的网络切片或即将使用的网络切片中的至少一项，以及请求网络切片确定终端设备的目标网络切片的相关描述，为了简洁，本申请在此不做赘述。
在另一种实现方式中，接入和移动性管理功能网元或网络切片选择功能网元还可以确定此次请求注册的终端设备的允许网络切片不变，允许网络切片对应的注册区也不变。
在另一种实现方式中，接入和移动性管理功能网元或网络切片选择功能网元还可以确定此次注册的终端设备的允许网络切片不再包含已经释放很长时间的会话的网络切片，只包含仍然有正在进行的会话的网络切片。其中，接入和移动性管理功能网元或网络切片选择功能网元确定此次注册的终端设备的允许网络切片的具体描述，可以参考上述S602中网络设备根据已经使用的网络切片或即将使用的网络切片中的至少一项，以及请求网络切片确定终端设备的第一允许网络切片的相关描述，为了简洁，本申请在此不做赘述。
在另一种实现方式中，接入和移动性管理功能网元或网络切片选择功能网元还可以将释放不久的会话的网络切片作为终端设备即将使用的网络切片(即，可能用于建立新的会话的网络切片)，通过终端设备已经使用的网络切片和即将使用的网络切片中的至少一项，以及请求网络切片确定终端设备的允许网络切片。
在上述的任一另一种实现方式中，允许网络切片对应的注册区不再包含支持目标网络切片的跟踪区，同时，支持终端设备的允许网络切片但不和注册区中的任一跟踪区相邻的跟踪区，也不被包含在注册区内。
S804，接入和移动性管理功能网元由策略控制功能网元获取目标网络切片对应的RFSP信息。
可选地，接入和移动性管理功能网元可以请求策略控制功能网元获取目标网络切片对应的RFSP的信息。
在另外一种实现方式中，目标网络切片对应的RFSP信息是接入和移动性管理功能网元根据本地配置策略确定的，则不用执行S804。
应理解，本步骤也可应用于方法700之中。例如，可以在图7的S703之后执行。
S805，接入和移动性管理功能网元向第一接入网设备发送目标网络切片信息。对应地，第一接入网设备接收来自接入和移动性管理功能网元的目标网络切片信息。
关于第一接入网设备接收来自第一接入和移动性管理功能网元的目标网络切片信息的描述，可以参考上述S502中第一接入网设备可以接收来自第一接入和移动性管理功能网元的将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区的指示信息中，关于该指示信息为目标网络切片的信息的描述，为了简洁，本申请在此不做赘述。
S806，第一接入网设备确定切换目标网络切片中的至少一个网络切片对应的终端设备的处于激活状态的会话。
示例地，第一接入网设备在接收将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区的指示信息之后，可以确定切换目标网络切片中的至少一个网络切片对应的终端设备的处于激活状态的会话。
具体地，关于第一接入网设备确定切换目标网络切片中的至少一个网络切片对应的终端设备的处于激活状态的会话的描述，可以参考上述S502中关于第一接入网设备确定切换目标网络切片中的至少一个网络切片对应的终端设备的处于激活状态的会话的相关描述。第一接入网设备根据接收到的终端设备的目标网络切片，以及第一接入网设备保存的终端设备的上下文中会话状态信息，确定终端设备处于激活状态的会话对应的网络切片至少有一个属于目标网络切片。
可选地，接入和移动性管理功能网元可以通过第一接入网设备向终端设备发送第一注册响应消息。对应地，终端设备通过第一接入网设备接收来自接入和移动性管理功能网元的第一注册响应消息。
可选地，接入和移动性管理功能网元还可以通过第一接入网设备向终端设备发送第一注册响应消息，该第一注册响应消息指示终端设备注册成功，可以携带此次请求注册的终端设备的允许网络切片，或者注册区中的至少一项信息。进一步地，注册响应消息还可以携带拒绝网络切片，拒绝网络切片为请求网络切片中当前终端设备的注册区不支持的网络切片，表示拒绝终端设备在当前注册区内继续请求接入拒绝网络切片中的网络切片。
此外，接入和移动性管理功能网元还可以向第一接入网设备发送N2接口消息，N2接口消息携带目标网络切片，可选地，N2接口消息还可以携带指示信息以及目标网络切片对应的RFSP信息中的至少一项。其中，目标网络切片对应的RFSP信息是第一接入和移动性管理功能网元根据本地配置策略确定的，或者是由第一接入和移动性管理功能网元请求策略控制功能网元获取的。例如，RFSP信息为RFSP索引(index)。
S807，第一接入网设备向终端设备发送测量配置消息。对应地，终端设备接收来自第一接入网设备的测量配置消息。
示例地，第一接入网设备可以通过无线资源管理重新配置消息向终端设备发送测量配置消息，其中携带的无线参数指示终端设备测量终端设备所在的跟踪区的相邻跟踪区的小区所在频段的信号质量。
举例而言，第一接入和移动性管理功能网元或网络切片选择功能网元确定终端设备当前所在的跟踪区#3不支持目标网络切片，但是覆盖跟踪区#3相同区域或周边区域的跟踪区#4和跟踪区#5支持目标网络切片，或者和跟踪区#3相邻的跟踪区#4和跟踪区#5支持目标网络切片，则测量配置消息携带的无线参数指示终端设备测量跟踪区#4的小区或跟踪区#5的小区所在频段的信号质量。
S808，终端设备向第一接入网设备发送测量结果消息。对应地，第一接入网设备接收来自终端设备的测量结果消息。
S809，第一接入网设备进行切换决策。
示例地，如果终端设备当前的小区的相邻小区(位于跟踪区#4或跟踪区#5中)的信号强度达到满足切换标准的指定门限，第一接入网设备可以决定启动切换。
S810，第一接入网设备向第二接入网设备发送切换请求消息。对应地，第二接入网设备接收来自第一接入网设备的切换请求消息。
示例地，第一接入网设备确定切换终端设备处于激活状态的会话到目标小区需要经过核心网网元的控制，向接入和移动性管理功能网元发送切换请求，其中携带了等待切换的会话的信息和切换的目标小区的信息，例如，该会话可以是已经通过网络切片#3和网络切片#4分别建立的会话的信息。
S811，第一接入网设备、第二接入网设备、接入和移动性管理功能网元，以及会话管理功能网元共同进行处于激活状态的会话的切换。
示例地，第一接入网设备、第二接入网设备、接入和移动性管理功能网元，以及会话管理功能网元可以协同将处于激活状态的会话的上下文从第一接入网设备切换到第二接入网设备。
之后，会话管理功能网元控制第一接入网设备、第二接入网设备和用户面功能网元将处于激活状态的会话的用户面路径从第一接入网设备切换到第二接入网设备。因此，处于激活状态的会话在切换过程中仍然可以正常传送终端设备的业务报文，会话不会中断。
基于上述方案，接入和移动性管理功能网元在确定目标网络切片中的至少一个网络切片对应的终端设备的处于激活状态的会话之后，可以向第一接入网设备发送将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区的指示信息。进而，相较于现有技术(例如，通过上述图2或图3所述的方式)中，在重定向终端设备处于激活状态的会话的过程中，终端设备需要先断开和重定向之前的跟踪区内的小区的RRC连接，进入RRC空闲状态，再重新驻留到重定向之后的跟踪区内的小区，从而终端设备已经建立的会话会被激活或中断的方式，本方案并不用释放RRC连接，而是接入和移动性管理功能网元向第一接入网设备发送将处于激活状态的会话切换至支持目标网络切片的跟踪区的小区的指示信息，从而完成会话的切换。因此，本方案可以改善终端设备的业务的稳定性，避免终端设备在接入至支持终端设备的目标网络切片的小区之后并注册网络切片时终端设备处于激活状态的的会话受到中断影响，提升用户的体验。
可选的，该方法还包括：
S812，终端设备向接入和移动性管理功能网元发送第二注册请求消息。
示例地，完成切换后，终端设备发现目前接入的小区不属于原来的注册区，于是通过第二接入网设备向接入和移动性管理功能网元发送第二注册请求消息，第二注册请求消息携带请求网络切片，该请求网络切片可以为{网络切片#1,网络切片#2,网络切片#3,网络切片#4，网络切片#5}，换言之，终端设备在离开原来的注册区之后，可以尝试尽可能多地注册网络切片。
S813，接入和移动性管理功能网元或网络切片选择功能网元确定终端设备的第二允许网络切片。
示例地，关于接入和移动性管理功能网元或网络切片选择功能网元确定终端设备的第二允许网络切片的描述，可以参考上述S714中的第二接入和移动性管理功能网元或网络切片选择功能网元确定终端设备的允许网络切片的相关描述，为了简洁，本申请在此不做赘述。
S814，接入和移动性管理功能网元向终端设备发送第二注册响应消息。对应地，终端 设备接收来自接入和移动性管理功能网元的第二注册响应消息。
示例地，接入和移动性管理功能网元可以通过第二接入网设备向终端设备发送第二注册响应消息，该注册响应消息可以携带允许网络切片的信息，或者允许网络切片的信息和允许网络切片对应的注册区的信息。
此外，通过上述方案，可以根据终端设备的通信需求确定终端设备合适的允许网络切片，使得允许网络切片的网络切片数量减少，实现允许网络切片对应的注册区的范围尽可能扩大，减少终端设备移动过程中的信令负荷
图9示出了本申请实施例提供的一种基于切片通信的方法900的示意图。如下，该方法900包括以下步骤：
S901，终端设备向接入和移动性管理功能网元发送注册请求消息。对应地，接入和移动性管理功能网元接收来自终端设备的注册请求消息。
其中，注册请求消息可以包括终端设备的请求网络切片。
具体地，终端设备在开机后接入网络，或因为移动到一个不属于原来注册区的新跟踪区，或周期性的向网络注册更新时，可以通过接入网设备向接入和移动性管理功能网元发送注册请求消息，其中携带请求网络切片。
进一步地，该注册请求消息还可能携带终端设备的已经建立的会话的状态信息(PDU session status)。终端设备在进行网络注册时，可能存在如下两种情况：
在可能实现的一种方式中，终端设备首次向当前网络注册，或者终端设备已经离开原来的注册区(例如，当前所驻留小区归属的跟踪区已经超出原来的注册区)，终端设备可能在请求网络切片中携带配置网络切片中的除了当前公共陆地移动网范围内拒绝的网络切片之外的所有网络切片。
在可能实现的另一种方式中，终端设备当前所在的跟踪区仍然属于上次网络注册的注册区，终端设备希望使用特定的一到多个网络切片建立会话，如果这些特定的网络切片(例如，可以是终端设备的即将使用的网络切片)的单个网络切片选择辅助信息不在请求网络切片中，终端设备则可以在请求网络切片中除了携带允许网络切片之外，还携带这些终端设备的即将使用的网络切片的单个网络切片选择辅助信息。
S902，接入和移动性管理功能网元从统一数据管理功能网元获取终端设备的签约的网络切片的信息。
示例地，接入和移动性管理功能网元可以通过统一数据管理功能网元获取终端设备的网络切片签约信息，确认请求网络切片携带的每个网络切片都是终端设备签约的网络切片，或者是签约网络切片映射到终端设备当前拜访网络的网络切片。否则，终端设备就没有签约相关网络切片业务，这个网络切片就会被接入和移动性管理功能网元删除。
此外，接入和移动性管理功能网元还可以从终端设备的网络切片签约信息确定哪个网络切片是终端设备的默认签约网络切片，或者是默认签约网络切片在当前拜访网络映射的网络切片。
S903，接入和移动性管理功能网元确定终端设备的已经使用的网络切片或终端设备的即将使用的网络切片。
具体地，关于接入和移动性管理功能网元确定终端设备的已经使用的网络切片或终端设备的即将使用的网络切片的描述，可以参考上述S402中第一接入和移动性管理功能网元 可以确定已经使用的网络切片或即将使用的网络切片的相关描述，为了简洁，本申请在此不做赘述。
S904，接入和移动性管理功能网元向网络切片选择功能网元发送切片选择请求消息。对应地，网络切片选择功能网元接收来自接入和移动性管理功能网元的切片选择请求消息。
示例地，接入和移动性管理功能网元可以向网络切片选择功能网元发送切片选择请求消息，该切片选择请求消息用于请求网络切片选择功能网元确定终端设备的允许网络切片。其中，该切片选择请求消息不仅可以携带终端设备当前的跟踪区、终端设备的请求网络切片等信息，还可以携带终端设备的已经使用的网络切片或终端设备的即将使用的网络切片中的至少一项。
应理解，如果由后续由接入和移动性管理功能网元独立执行网络切片选择，则不执行S904。
S905，接入和移动性管理功能网元或网络切片选择功能网元确定终端设备的允许网络切片。
具体地，关于接入和移动性管理功能网元或网络切片选择功能网元确定终端设备的允许网络切片的描述，可以参考上述S602中网络设备根据已经使用的网络切片或即将使用的网络切片中的至少一项，以及请求网络切片确定终端设备的第一允许网络切片的相关描述，为了简洁，本申请在此不再赘述。
S906，接入和移动性管理功能网元向终端设备发送注册响应消息。对应地，终端设备接收来自接入和移动性管理功能网元的注册响应消息。
示例地，接入和移动性管理功能网元可以通过接入网设备向终端设备发送注册响应消息，该注册响应消息可以携带允许网络切片和允许网络切片对应的注册区中的至少一项信息。
基于上述方案，根据终端设备的已经使用的网络切片或即将使用的网络切片中的至少一项，以及请求网络切片确定终端设备的允许网络切片，并发送该允许网络切片的信息，可以根据终端设备的通信需求确定合适的允许网络切片，相较于现有技术确定允许网络切片的方案，可以有效减少允许网络切片包含的网络切片的数量，实现尽可能大的允许网络切片对应的注册区的范围，减少终端设备移动过程中的信令负荷。
图10示出了本申请实施例提供的一种切片确定的方法1000的示意图。如下，该方法1000包括以下步骤：
S1001，终端设备向接入和移动性管理功能网元发送注册请求消息。对应地，接入和移动性管理功能网元接收来自终端设备的注册请求消息。
示例地，已经注册到网络的终端设备可以周期性通过接入网设备向接入和移动性管理功能网元发送注册请求消息，或者终端设备期望在特定网络切片建立会话时，终端设备可以通过接入网设备向接入和移动性管理功能网元发送注册请求消息，其中，注册请求消息可以包括终端设备的请求网络切片。
在可能实现的一种方式中，除上一次网络注册明确被接入和移动性管理功能网元拒绝的网络切片之外，终端设备可以将配置网络切片中其它的网络切片都包含在请求网络切片中。通过此种方式，终端设备不是按照建立会话的需要请求接入网络切片，我们称这类行为是终端设备“尽可能多注册”的方式注册网络切片。
在可能实现的另一种方式中，终端设备只将上一次网络注册明确被接入和移动性管理功能网元允许的网络切片，以及终端设备希望建立会话的网络切片包含在请求接入网络切片中。通过此种方式，终端设备是按照建立会话的需要请求接入网络切片，我们称这类行为是终端设备“按照需要注册”的方式注册网络切片。
S1002，接入和移动性管理功能网元确定终端设备的注册方式。
示例地，接入和移动性管理功能网元在接收注册请求消息之后，可以根据以下任一种方式确定终端设备注册网络切片的方式。
接入和移动性管理功能网元根据注册请求消息携带的请求网络切片，以及接入和移动性管理功能网元的终端设备的上下文中的允许网络切片和配置网络切片，确定终端设备是否可能通过请求网络切片中不属于允许网络切片的网络切片建立会话。
举例而言，接入和移动性管理功能网元可以判断配置网络切片中除去拒绝网络切片和允许网络切片的其它网络切片是否都包含在请求网络切片中，如果为否，则确定终端设备注册网络切片的方式为“按照需要注册”的方式注册网络切片。
S1003，接入和移动性管理功能网元从网络数据分析功能网元获取终端设备的注册行为分析结果信息。
示例地，接入和移动性管理功能网元可以通过网络数据分析功能网元获得终端设备的注册行为分析结果信息，该注册行为分析结果信息包含终端设备的注册网络切片的方式是否符合“按照需要注册”的方式。具体的方法如下：
首先，接入和移动性管理功能网元可以向网络数据分析功能网元发送分析请求消息或分析订阅请求消息，请求获取终端设备的注册行为分析结果，其中，分析请求消息或分析订阅请求消息中携带为终端设备注册行为分析的分析标识信息，同时携带终端设备的用户永久标识等身份信息。
其次，网络数据分析功能网元可以根据终端设备的身份信息从各个接入和移动性管理功能网元收集该终端设备之前的注册请求中携带的请求网络切片信息，以及通过之前的注册结果得到的允许网络切片信息、拒绝网络切片信息，以及终端设备的配置网络切片信息。可选地，网络数据分析功能网元还可以从接入和移动性管理功能网元或会话管理功能网元收集该终端设备之前建立的会话的网络切片的属性信息(即，终端设备已经使用的网络切片)，网络数据分析功能网元可以关联上述数据确认终端设备是否在需要建立会话时才将对应的网络切片加入到请求网络切片之中。换言之，网络数据分析功能网元可以分析输出终端设备的注册行为是否符合“按照需要注册”的方式。
最后，网络数据分析功能网元可以将终端设备的注册行为是否符合“按照需要注册”的方式的分析结果发送至接入和移动性管理功能网元。
应理解，在上述方案中，如果S1002被执行，则可以不执行S1003；如果S1002不被执行，则可以执行S1003。
S1004，接入和移动性管理功能网元为终端设备选择网络切片。
具体地，接入和移动性管理功能网元可以通过以下任一种方式，为终端设备选择网络切片：
(1)在终端设备进行初始网络注册的情况下，或者接入和移动性管理功能网元无法从上一个接入和移动性管理功能网元获得终端设备的上下文的情况下，接入和移动性管理 功能网元可以通过统一数据管理功能网元获得终端设备的网络切片签约信息，该网络切片签约信息包含的网络切片是否为默认网络切片，进一步地，该网络切片签约信息还可以包括网络切片的优先级信息；之后，接入和移动性管理功能网元可以根据终端设备使用网络切片的业务重要性，或使用频率的大小，将签约的网络切片分别不同的优先级，然后根据默认网络切片或签约网络切片的优先级，确定默认网络切片或其映射的拜访网络的相应网络切片为可能建立会话的网络切片(即，终端设备的即将使用的网络切片)，或者确定高优先级的网络切片或其映射的拜访网络的相应网络切片为可能建立会话的网络切片(即，终端设备的即将使用的网络切片)。
(2)接入和移动性管理功能网元可以通过网络数据分析功能网元获得终端设备的通信行为分析结果信息，该通信行为分析结果信息包括终端设备在当前位置的用于建立会话可能使用的网络切片的信息。具体的方法如下：
首先，接入和移动性管理功能网元可以向网络数据分析功能网元发送分析请求消息或分析订阅请求消息，请求获取终端设备的通信行为分析结果，其中，分析请求消息或分析订阅请求消息中携带为终端设备通信行为分析的分析标识信息，同时携带终端设备的用户永久标识等身份信息；
其次，网络数据分析功能网元可以根据终端设备的身份信息从各个接入和移动性管理功能网元或会话管理功能网元收集的该终端设备以往建立会话的时间、位置和网络切片属性等信息。网络数据分析功能网元关联上述数据可以分析预测终端设备在指定位置和/或指定时间内分别通过至少一个网络切片中的每个网络切片建立会话的概率；
最后，网络数据分析功能网元将终端设备通过至少一个网络切片中的每个网络切片建立会话的概率的分析预测结果发送至接入和移动性管理功能网元，接入和移动性管理功能网元可以确定建立会话概率达到或超过预设门限的网络切片为可能建立会话的网络切片(即，终端设备的即将使用的网络切片)。
(3)接入和移动性管理功能网元可以通过策略控制功能网元获得接入管理策略(AM-policy)信息，该接入管理策略信息包括终端设备在当前地理位置可能建立会话的网络切片(即，终端设备的即将使用的网络切片)的信息。具体的方法如下：
首先，接入和移动性管理功能网元可以向策略控制功能网元发送建立管理策略连接的请求消息，该请求消息可以携带终端设备的当前所在的跟踪区标识信息或终端设备的地理位置信息，进一步地，该请求消息还可以携带终端设备在注册请求中携带的请求网络切片或签约网络切片中的至少一项信息；
其次，策略控制功能网元可以根据通过用户数据库获取的终端设备的策略信息，确定终端设备在当前地理位置可能建立会话的网络切片信息。例如，终端设备在当前位置时，终端设备可能建立会话的网络切片包括终端设备下发的用户路由选择策略包含的网络切片；而终端设备在其他位置时，终端设备可能建立会话的网络切片不包括终端设备当前所在位置，不属于服务区域允许的网络切片。
最后，策略控制功能网元通过建立管理策略建立消息或建立管理策略修改消息向接入和移动性管理功能网元发送终端设备在当前地理位置可能建立会话的网络切片信息，换言之，接入和移动性管理功能网元可以确定在当前地理位置可能建立会话的网络切片为可能使用的网络切片。
(4)接入和移动性管理功能网元在通过步骤S1003确定终端设备的注册行为符合“按照需要注册”的方式，那么接入和移动性管理功能网元将终端设备在步骤S1001中携带的请求网络切片中的所有网络切片作为可能使用的网络切片。
S1005，接入和移动性管理功能网元向网络切片选择功能网元发送切片选择请求消息。对应地，网络切片选择功能网元接收来自接入和移动性管理功能网元的切片选择请求消息。
其中，切片选择请求消息不仅可以携带终端设备当前的跟踪区，或终端设备的请求网络切片中的至少一项信息，还可以携带上述S1004中接入和移动性管理功能网元分别通过统一数据管理功能网元、网络数据分析功能网元，或策略控制功能网元获取的信息。
应理解，在上述方案中，如果接入和移动性管理功能网元向网络切片独立完成为终端设备选择网络切片，则不用执行S1005。
S1006，接入和移动性管理功能网元或网络切片选择功能网元确定终端设备的允许网络切片。
示例地，接入和移动性管理功能网元或网络切片选择功能网元可以确定终端设备可能建立会话的各个网络切片，根据终端设备可能建立会话的各个网络切片，终端设备的当前跟踪区、终端设备的请求网络切片中的至少一项确定终端设备的允许网络切片，进而确定终端设备的允许网络切片相应的注册区。具体的方法如下：
接入和移动性管理功能网元或网络切片选择功能网元可以将可能建立会话的各个网络切片的集合与终端设备当前跟踪区支持的网络切片的集合取交集，作为允许网络切片；之后，接入和移动性管理功能网元或网络切片选择功能网元可以确定终端设备当前所在的TA周边的各个跟踪是否支持该允许网络切片，如果支持，就将终端设备当前所在的TA周边的各个跟踪区纳入注册区内，最终确定允许网络切片对应的注册区。
应理解，如果是网络切片选择功能网元确定的终端设备的允许网络切片，网络切片选择功能网元可以将终端设备的允许网络切片信息发送至接入和移动性管理功能网元。
S1007，接入和移动性管理功能网元向终端设备发送注册响应消息。对应地，终端设备接收来自接入和移动性管理功能网元的注册响应消息。
示例地，接入和移动性管理功能网元可以通过接入网设备向终端设备发送注册响应消息，该注册响应消息可以携带允许网络切片和允许网络切片对应的注册区中的至少一项信息。
基于上述方案，根据终端设备的已经使用的网络切片或即将使用的网络切片确定终端设备的允许网络切片，并发送该允许网络切片的信息进而，相较于现有技术确定允许网络切片的方法，本方案可以根据终端设备的通信需求确定合适的允许网络切片，尽可能低减少允许网络切片中包含的网络切片的数量，实现允许网络切片对应的注册区的范围尽可能扩大，减少终端设备移动过程中的信令负荷。
本文中描述的各个实施例可以为独立的方案，也可以根据内在逻辑进行组合，这些方案都落入本申请的保护范围中。
可以理解的是，上述各个方法实施例中，由终端设备实现的方法和操作，也可以由可用于终端设备的部件(例如芯片或者电路)实现，由网络设备实现的方法和操作，也可以由可用于网络设备的部件(例如芯片或者电路)实现。
以上，结合图4至图10详细说明了本申请实施例提供的方法。以下，结合图11至图13 详细说明本申请实施例提供的通信装置。应理解，装置实施例的描述与方法实施例的描述相互对应，因此，未详细描述的内容可以参见上文方法实施例，为了简洁，这里不再赘述。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，各个网元，例如发射端设备或者接收端设备，为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对发射端设备或者接收端设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。下面以采用对应各个功能划分各个功能模块为例进行说明。
图11是本申请实施例提供的通信装置1100的示意性框图。该通信装置1100包括收发单元1110和处理单元1120。收发单元1110可以实现相应的通信功能，处理单元1110用于进行数据处理。收发单元1110还可以称为通信接口或通信单元。
可选地，该通信装置1100还可以包括存储单元，该存储单元可以用于存储指令和/或数据，处理单元1120可以读取存储单元中的指令和/或数据，以使得通信装置实现前述方法实施例。
该通信装置1100可以用于执行上文方法实施例中第一接入和移动性管理功能网元所执行的动作，这时，该通信装置1100可以为第一接入和移动性管理功能网元或者可配置于第一接入和移动性管理功能网元的部件，收发单元1110用于执行上文方法实施例中第一接入和移动性管理功能网元侧的收发相关的操作，处理单元1120用于执行上文方法实施例中第一接入和移动性管理功能网元侧的处理相关的操作。
作为一种设计，该通信装置1100用于执行上文图4所示实施例中第一接入和移动性管理功能网元所执行的动作，收发单元1110用于：S403；处理单元1120用于：S401、S402。
作为另一种设计，该通信装置1100用于执行上文图5所示实施例中第一接入和移动性管理功能网元所执行的动作，收发单元1110用于：S501。
或者，该通信装置1100可以用于执行上文方法实施例中第一接入网设备所执行的动作，这时，该通信装置1100可以为第一接入网设备或者可配置于第一接入网设备的部件，收发单元1110用于执行上文方法实施例中第一接入网设备侧的收发相关的操作，处理单元1120用于执行上文方法实施例中第一接入网设备侧的处理相关的操作。
作为一种设计，该通信装置1100用于执行上文图4所示实施例中第一接入网设备所执行的动作，收发单元1110用于：S403。
作为另一种设计，该通信装置1100用于执行上文图5所示实施例中第一接入网设备所执行的动作，收发单元1110用于：S501；处理单元1120用于：S502、S503。
或者，该通信装置1100可以用于执行上文方法实施例中网络设备所执行的动作，这时， 该通信装置1100可以为网络设备或者可配置于网络设备的部件，收发单元1110用于执行上文方法实施例中网络设备侧的收发相关的操作，处理单元1120用于执行上文方法实施例中网络设备侧的处理相关的操作。
作为一种设计，该通信装置1100用于执行上文图6所示实施例中网络设备所执行的动作，收发单元1110用于：S603；处理单元1120用于：S601、S602。
一方面，该通信装置1100可实现对应于根据本申请实施例的方法400和方法500中的第一接入和移动性管理功能网元执行的步骤或者流程，该通信装置1100可以包括用于执行图4中的方法400和图5中方法500中的第一接入和移动性管理功能网元执行的方法的单元。并且，该通信装置1100中的各单元和上述其他操作和/或功能分别为了实现图4中的方法400和图5中方法500的相应流程。
另一方面，该通信装置1100可实现对应于根据本申请实施例的方法400和方法500中的第一接入网设备执行的步骤或者流程，该通信装置1100可以包括用于执行图4中的方法400和图5中方法500中的第一接入网设备执行的方法的单元。并且，该通信装置1100中的各单元和上述其他操作和/或功能分别为了实现图4中的方法400和图5中方法500的相应流程。
再一方面，该通信装置1100可实现对应于根据本申请实施例的方法600中的网络设备执行的步骤或者流程，该通信装置1100可以包括用于执行图6中的方法600中的网络设备执行的方法的单元。并且，该通信装置1100中的各单元和上述其他操作和/或功能分别为了实现图6中的方法600的相应流程。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
上文实施例中的处理单元1120可以由至少一个处理器或处理器相关电路实现。收发单元1110可以由收发器或收发器相关电路实现。收发单元1110还可称为通信单元或通信接口。存储单元可以通过至少一个存储器实现。
如图12所示，本申请实施例还提供一种通信装置1200。该通信装置1200包括处理器1210，处理器1210与存储器1220耦合，存储器1220用于存储计算机程序或指令和/或数据，处理器1210用于执行存储器1220存储的计算机程序或指令和/或数据，使得上文方法实施例中的方法被执行。
可选地，该通信装置1200包括的处理器1210为一个或多个。
可选地，如图12所示，该通信装置1200还可以包括存储器1220。
可选地，该通信装置1200包括的存储器1220可以为一个或多个。
可选地，该存储器1220可以与该处理器1210集成在一起，或者分离设置。
可选地，如图12所示，该通信装置1200还可以包括收发器1230，收发器1230用于信号的接收和/或发送。例如，处理器1210用于控制收发器1230进行信号的接收和/或发送。
作为一种方案，该通信装置1200用于实现上文方法实施例中由第一接入和移动性管理功能网元执行的操作。
例如，处理器1210用于实现上文方法实施例中由第一接入和移动性管理功能网元执行的处理相关的操作，收发器1230用于实现上文方法实施例中由第一接入和移动性管理功能网元执行的收发相关的操作。
作为另一种方案，该通信装置1200用于实现上文方法实施例中由第一接入网设备执行 的操作。
例如，处理器1210用于实现上文方法实施例中由第一接入网设备执行的处理相关的操作，收发器1230用于实现上文方法实施例中由第一接入网设备执行的收发相关的操作。
作为再一种方案，该通信装置1200用于实现上文方法实施例中由网络设备执行的操作。
例如，处理器1210用于实现上文方法实施例中由网络设备执行的处理相关的操作，收发器1230用于实现上文方法实施例中由网络设备执行的收发相关的操作。
本申请实施例提供一种通信装置1300，该通信装置1300可以是网络设备也可以是芯片。该通信装置1300可以用于执行上述方法实施例中由网络设备所执行的操作。其中，网络设备可以包括上文实施例中的第一接入和移动性管理功能网元、第一接入网设备，或网络设备。
当该通信装置1300为网络设备时，图13示出了一种简化的网络设备1300的结构示意图。网络设备包括1310部分以及1320部分。1310部分主要用于射频信号的收发以及射频信号与基带信号的转换；1320部分主要用于基带处理，对网络设备进行控制等。1310部分通常可以称为收发单元、收发机、收发电路、或者收发器等。1320部分通常是网络设备的控制中心，通常可以称为处理单元，用于控制网络设备执行上述方法实施例中第一接入和移动性管理功能网元侧、第一接入网设备侧，或网络设备侧的处理操作。
1310部分的收发单元，也可以称为收发机或收发器等，其包括天线和射频电路，其中射频电路主要用于进行射频处理。可选地，可以将1310部分中用于实现接收功能的器件视为接收单元，将用于实现发送功能的器件视为发送单元，即1310部分包括接收单元和发送单元。接收单元也可以称为接收机、接收器、或接收电路等，发送单元可以称为发射机、发射器或者发射电路等。
1320部分可以包括一个或多个单板，每个单板可以包括一个或多个处理器和一个或多个存储器。处理器用于读取和执行存储器中的程序以实现基带处理功能以及对基站的控制。若存在多个单板，各个单板之间可以互联以增强处理能力。作为一种可选的实施方式，也可以是多个单板共用一个或多个处理器，或者是多个单板共用一个或多个存储器，或者是多个单板同时共用一个或多个处理器。
例如，在一种实现方式中，1310部分的收发单元用于执行图4或图5所示实施例中由第一接入网设备执行的收发相关的步骤；1320部分用于执行图4或图5所示实施例中由第一接入网设备执行的处理相关的步骤。
作为一种设计，该网络设备1300用于执行上文图4所示实施例中第一接入和移动性管理功能网元所执行的动作，收发单元1310用于：S403；处理单元1320用于：S401、S402。
作为另一种设计，该网络设备1300用于执行上文图5所示实施例中第一接入和移动性管理功能网元所执行的动作，收发单元1310用于：S501。
例如，在又一种实现方式中，1310部分的收发单元用于执行图4或图5所示实施例中第一接入网设备执行的收发相关的步骤；1320部分用于执行图4或图5所示实施例中由一接入网设备执行的处理相关的步骤。
作为一种设计，该网络设备1300用于执行上文图4所示实施例中第一接入网设备所执行的动作，收发单元1310用于：S403。
作为另一种设计，该网络设备1300用于执行上文图5所示实施例中第一接入网设备所 执行的动作，收发单元1310用于：S501；处理单元1320用于：S502、S503。
例如，在再一种实现方式中，1310部分的收发单元用于执行图6所示实施例中由网络设备执行的收发相关的步骤；1320部分用于执行图6所示实施例中由网络设备执行的处理相关的步骤。
作为一种设计，该网络设备1300用于执行上文图6所示实施例中网络设备所执行的动作，收发单元1310用于：S603；处理单元1320用于：S601、S602。
应理解，图13仅为示例而非限定，上述包括收发单元和处理单元的网络设备可以不依赖于图13所示的结构。
当该通信装置1300为芯片时，该芯片包括收发单元和处理单元。其中，收发单元可以是输入输出电路、通信接口；处理单元为该芯片上集成的处理器或者微处理器或者集成电路。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述方法实施例中由第一接入和移动性管理功能网元执行的方法，或由第一接入网设备执行的方法，或由网络设备执行的方法的计算机指令。
例如，该计算机程序被计算机执行时，使得该计算机可以实现上述方法实施例中由第一接入和移动性管理功能网元执行的方法，或由第一接入网设备执行的方法，或由网络设备执行的方法。
本申请实施例还提供一种包含指令的计算机程序产品，该指令被计算机执行时使得该计算机实现上述方法实施例中由第一接入和移动性管理功能网元执行的方法，或由第一接入网设备执行的方法，或由网络设备执行的方法。
本申请实施例还提供一种通信系统，该通信系统包括上文实施例中的第一接入和移动性管理功能网元和第一接入网设备。
所属领域的技术人员可以清楚地了解到，为描述方便和简洁，上述提供的任一种通信装置中相关内容的解释及有益效果均可参考上文提供的对应的方法实施例，此处不再赘述。
在本申请实施例中，终端设备或网络设备可以包括硬件层、运行在硬件层之上的操作系统层，以及运行在操作系统层上的应用层。其中，硬件层可以包括中央处理器(central processing unit，CPU)、内存管理单元(memory management unit，MMU)和内存(也称为主存)等硬件。操作系统层的操作系统可以是任意一种或多种通过进程(process)实现业务处理的计算机操作系统，例如，Linux操作系统、Unix操作系统、Android操作系统、iOS操作系统或windows操作系统等。应用层可以包含浏览器、通讯录、文字处理软件、即时通信软件等应用。
本申请实施例并未对本申请实施例提供的方法的执行主体的具体结构进行特别限定，只要能够通过运行记录有本申请实施例提供的方法的代码的程序，以根据本申请实施例提供的方法进行通信即可。例如，本申请实施例提供的方法的执行主体可以是终端设备或网络设备，或者，是终端设备或网络设备中能够调用程序并执行程序的功能模块。
本申请的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技术的制品。本文中使用的术语“制品”可以涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。
其中，计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或 多个可用介质集成的服务器、数据中心等数据存储设备。可用介质(或者说计算机可读介质)例如可以包括但不限于：磁性介质或磁存储器件(例如，软盘、硬盘(如移动硬盘)、磁带)、光介质(例如，光盘、压缩盘(compact disc，CD)、数字通用盘(digital versatile disc，DVD)等)、智能卡和闪存器件(例如，可擦写可编程只读存储器(erasable programmable read-only memory，EPROM)、卡、棒或钥匙驱动器等)、或者半导体介质(例如固态硬盘(solid state disk，SSD)等、U盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)等各种可以存储程序代码的介质。
本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”可以包括但不限于：无线信道和能够存储、包含和/或承载指令和/或数据的各种其它介质。
应理解，本申请实施例中提及的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中提及的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)。例如，RAM可以用作外部高速缓存。作为示例而非限定，RAM可以包括如下多种形式：静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)可以集成在处理器中。
还需要说明的是，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅是示意性的，例如，上述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。此外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
上述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络 单元上。可以根据实际的需要选择其中的部分或者全部单元实现本申请提供的方案。
另外，在本申请各个实施例中的各功能单元可以集成在一个单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。
当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。例如，计算机可以是个人计算机，服务器，或者网络设备等。计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。关于计算机可读存储介质，可以参考上文描述。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求和说明书的保护范围为准。

Claims (30)

  1. 一种基于切片的通信方法，其特征在于，包括：
    第一接入和移动性管理功能网元获取终端设备的目标网络切片的信息；
    所述第一接入和移动性管理功能网元确定所述目标网络切片中的至少一个网络切片对应所述终端设备的处于激活状态的会话；
    所述第一接入和移动性管理功能网元向第一接入网设备发送将所述处于激活状态的会话切换至支持所述目标网络切片的跟踪区TA的小区的指示信息。
  2. 根据权利要求1所述的方法，其特征在于，所述指示信息为所述目标网络切片的信息。
  3. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一接入和移动性管理功能网元向所述第一接入网设备发送所述目标网络切片的信息。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述第一接入和移动性管理功能网元获取所述终端设备的目标网络切片的信息，包括：
    所述第一接入和移动性管理功能网元根据所述终端设备的第一允许网络切片中已经使用的网络切片获取所述目标网络切片。
  5. 根据权利要求4所述的方法，其特征在于，所述第一接入和移动性管理功能网元根据所述第一允许网络切片中已经使用的网络切片获取所述目标网络切片，包括：
    所述第一接入和移动性管理功能网元根据所述第一允许网络切片中已经使用的网络切片，以及所述终端设备的即将使用的网络切片，确定所述目标网络切片。
  6. 根据权利要求1至3中任一项所述的方法，其特征在于，所述第一接入和移动性管理功能网元获取所述终端设备的目标网络切片的信息，包括：
    所述第一接入和移动性管理功能网元接收来自网络切片选择功能网元的所述目标网络切片的信息。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一接入和移动性管理功能网元将所述目标网络切片保存至所述终端设备的上下文中；
    在所述处于激活状态的会话完成所述切换后，所述第一接入和移动性管理功能网元接收所述终端设备的注册请求，并根据所述上下文中的所述目标网络切片确定所述终端设备的第二允许网络切片。
  8. 根据权利要求1至6中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一接入和移动性管理功能网元将所述目标网络切片保存至所述终端设备的上下文中；
    所述第一接入和移动性管理功能网元向第二接入和移动性管理功能网元发送所述上下文信息，所述上下文信息中的所述目标网络切片用于在所述处于激活状态的会话完成所述切换并发起注册请求之后，确定所述终端设备的第二允许网络切片。
  9. 根据权利要求1至8中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一接入和移动性管理功能网元向所述第一接入网设备发送所述目标网络切片对应的无线频率选择优先级RFSP信息，所述RFSP信息用于确定无线测量指令，所述无线测量指令用于在切换所述处于激活状态的会话之前，所述终端设备发现所述支持所述目标网络切片的TA的小区。
  10. 一种基于切片的通信的方法，其特征在于，包括：
    第一接入网设备接收来自第一接入和移动性管理功能网元的终端设备的目标网络切片的信息；
    所述第一接入网设备确定切换所述目标网络切片中的至少一个网络切片对应所述终端设备的处于激活状态的会话；
    所述第一接入网设备将所述处于激活状态的会话切换至支持所述目标网络切片的跟踪区TA的小区。
  11. 根据权利要求9所述的方法，其特征在于，所述第一接入网设备确定切换所述目标网络切片中的至少一个网络切片对应所述终端设备的处于激活状态的会话，包括：
    所述第一接入网设备接收来自所述第一接入和移动性管理功能网元的将所述处于激活状态的会话切换至支持所述目标网络切片的TA的小区的指示信息；
    所述第一接入网设备根据所述指示信息，确定切换所述处于激活状态的会话。
  12. 根据权利要求11所述的方法，其特征在于，所述指示信息为所述目标网络切片的信息。
  13. 根据权利要求10所述的方法，其特征在于，所述第一接入网设备确定切换所述目标网络切片中的至少一个网络切片对应所述终端设备的处于激活状态的会话，包括：
    所述第一接入网设备根据所述目标网络切片中的至少一个网络切片对应所述处于激活状态的会话，确定切换所述处于激活状态的会话。
  14. 根据权利要求10至13中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一接入网设备确定所述终端设备的无线测量指令，所述无线测量指令用于在切换所述处于激活状态的会话之前，发现所述支持所述目标网络切片的TA的小区。
  15. 根据权利要求14所述的方法，其特征在于，所述第一接入网设备确定所述终端设备的无线测量指令，包括：
    所述第一接入网设备根据所述目标网络切片的信息确定所述无线测量指令。
  16. 根据权利要求15所述的方法，其特征在于，所述第一接入网设备确定所述无线测量指令，包括：
    所述第一接入网设备接收来自所述第一接入和移动性管理功能网元的所述目标网络切片对应的无线频率选择优先级RFSP信息；
    所述第一接入网设备根据所述RFSP信息确定所述无线测量指令。
  17. 一种基于切片的通信方法，其特征在于，包括：
    网络设备获取终端设备的已经使用的网络切片或所述终端设备的即将使用的网络切片中的至少一项信息，以及所述终端设备的请求网络切片信息；
    所述网络设备根据所述已经使用的网络切片或所述即将使用的网络切片中的至少一项，以及所述请求网络切片确定所述终端设备的第一允许网络切片；
    所述网络设备发送所述第一允许网络切片的信息。
  18. 根据权利要求17所述的方法，其特征在于，所述方法还包括：
    所述网络设备获取所述终端设备所在的跟踪区TA支持的网络切片的信息；
    在所述TA不支持所述即将使用的网络切片中的至少一个网络切片的情况下，所述网络设备根据所述已经使用的网络切片或所述即将使用的网络切片中的至少一项，以及所述请求网络切片确定所述终端设备的目标网络切片；
    所述网络设备发送所述目标网络切片的信息。
  19. 根据权利要求18所述的方法，其特征在于，所述网络设备根据所述已经使用的网络切片或所述即将使用的网络切片中的至少一项，以及所述请求网络切片确定所述终端设备的目标网络切片，包括：
    所述网络设备选择属于所述已经使用的网络切片或所述即将使用的网络切片中的至少一项的网络切片，以及属于所述请求网络切片的网络切片，组成所述目标网络切片。
  20. 根据权利要求18或19所述的方法，其特征在于，所述目标网络切片中的至少一个网络切片不属于所述TA支持的网络切片。
  21. 根据权利要求17至20中任一项所述的方法，其特征在于，所述网络设备根据所述已经使用的网络切片或所述即将使用的网络切片中的至少一项，以及所述请求网络切片确定所述终端设备的第一允许网络切片，包括：
    所述网络设备选择属于所述已经使用的网络切片或所述即将使用的网络切片中的至少一项的网络切片，以及属于所述请求网络切片的网络切片，组成所述第一允许网络切片。
  22. 根据权利要求17至21中任一项所述的方法，其特征在于，所述网络设备包括第一网络切片选择功能网元。
  23. 根据权利要求22所述的方法，其特征在于，所述网络设备获取所述终端设备的已经使用的网络切片或所述终端设备的即将使用的网络切片中的至少一项信息，包括：
    所述网络设备接收来自接入和移动性管理功能网元的所述已经使用的网络切片和所述即将使用的网络切片中的至少一项信息。
  24. 根据权利要求17至21中任一项所述的方法，其特征在于，所述网络设备包括接入和移动性管理功能网元。
  25. 根据权利要求24所述的方法，其特征在于，所述方法还包括：
    所述网络设备接收来自第二网络切片选择功能网元的所述终端设备的第二允许网络切片；
    所述网络设备从所述第二允许网络切片中选出属于所述已经使用的网络切片或属于所述即将使用的网络切片的中至少一项的网络切片，组成所述终端设备的第三允许网络切片；
    所述网络设备向所述终端设备发送所述第三允许网络切片的信息。
  26. 根据权利要求25所述的方法，其特征在于，所述方法还包括：
    所述网络设备获取所述终端设备的第一拒绝网络切片的信息；
    所述网络设备删除所述第一拒绝网络切片中所述终端设备的注册区RA中的任一TA支持的网络切片，获得所述终端设备的第二拒绝网络切片，其中，所述RA是根据所述第二允许网络切片确定的；
    所述网络设备向所述终端设备发送所述第二拒绝网络切片的信息。
  27. 根据权利要求24至26中任一项所述的方法，其特征在于，所述网络设备获取所述已经使用的网络切片或所述即将使用的网络切片中的至少一项信息，包括以下至少一种方式：
    所述网络设备根据所述终端设备的会话状态信息确定所述已经使用的网络切片的信息；或
    所述网络设备根据所述请求网络切片和所述终端设备的上下文中的第三允许网络切片确定所述即将使用的网络切片的信息；或
    所述网络设备接收来自网络数据分析功能网元的所述终端设备的通信分析结果信息，并根据所述通信分析结果信息确定所述即将使用的网络切片的信息。
  28. 一种通信装置，其特征在于，包括：
    存储器，用于存储计算机程序；
    处理器，用于执行存储器中存储的计算机程序，以使得所述装置执行如权利要求1至9，或如权利要求10至16，或如权利要求17至27中任一项所述的方法。
  29. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1至9，或如权利要求10至16，或如权利要求17至27中任一项所述的方法。
  30. 一种通信系统，其特征在于，包括：第一接入和移动性管理功能网元和第一接入网设备；
    所述第一接入和移动性管理功能网元，用于执行如权利要求1至9中任一项所述的方法；
    所述第一接入网设备，用于执行如权利要求10至16中任一项所述的方法。
PCT/CN2022/137158 2022-01-27 2022-12-07 基于切片的通信方法及其装置 WO2023142695A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210103156.7 2022-01-27
CN202210103156.7A CN116567782A (zh) 2022-01-27 2022-01-27 基于切片的通信方法及其装置

Publications (1)

Publication Number Publication Date
WO2023142695A1 true WO2023142695A1 (zh) 2023-08-03

Family

ID=87470336

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/137158 WO2023142695A1 (zh) 2022-01-27 2022-12-07 基于切片的通信方法及其装置

Country Status (2)

Country Link
CN (1) CN116567782A (zh)
WO (1) WO2023142695A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200128450A1 (en) * 2017-06-12 2020-04-23 China Academy Of Telecommunications Technology Method for inserting smf and amf entity
CN112913279A (zh) * 2021-01-26 2021-06-04 北京小米移动软件有限公司 信息发送方法和装置、信息接收方法和装置
WO2021168647A1 (zh) * 2020-02-25 2021-09-02 华为技术有限公司 提供网络切片的方法和通信装置
CN113950111A (zh) * 2020-07-17 2022-01-18 华为技术有限公司 一种会话切换方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200128450A1 (en) * 2017-06-12 2020-04-23 China Academy Of Telecommunications Technology Method for inserting smf and amf entity
WO2021168647A1 (zh) * 2020-02-25 2021-09-02 华为技术有限公司 提供网络切片的方法和通信装置
CN113950111A (zh) * 2020-07-17 2022-01-18 华为技术有限公司 一种会话切换方法及装置
CN112913279A (zh) * 2021-01-26 2021-06-04 北京小米移动软件有限公司 信息发送方法和装置、信息接收方法和装置

Also Published As

Publication number Publication date
CN116567782A (zh) 2023-08-08

Similar Documents

Publication Publication Date Title
CN112087734B (zh) 通信方法及装置
US11139887B2 (en) System and method for radio link sharing
US20100220687A1 (en) Spectrum management across diverse radio access technologies
US20240089789A1 (en) Method and device for transmitting data in wireless communication system
CN113891427B (zh) 通信方法和装置
CN114667765A (zh) 无线通信系统中选择网络切片的方法和装置
US20220377659A1 (en) Network Slice Aware Cell Selection
WO2022199451A1 (zh) 会话切换的方法和装置
CN115915093A (zh) 一种eplmn列表的设置方法、核心网设备及介质
KR20210058479A (ko) 무선 통신 시스템에서 네트워크 슬라이스의 인터워킹을 제공하기 위한 장치 및 방법
US11606730B2 (en) Method and apparatus for improving voice service quality in wireless communication system
CN113747605B (zh) 通信方法和通信装置
WO2023142695A1 (zh) 基于切片的通信方法及其装置
KR20240060670A (ko) 통신 방법 및 장치
WO2022022082A1 (zh) 通信方法和通信装置
CN114915958A (zh) 一种灾难漫游的方法、装置和系统
CN114423074A (zh) 一种通信方法及装置
WO2023185561A1 (zh) 通信方法和通信装置
US20230239828A1 (en) Network registration method for traffic steering and device supporting the same
CN115004633B (zh) 连接云端的方法和终端设备
US12004022B2 (en) Method and apparatus for improving voice service quality in wireless communication system
WO2023142717A1 (zh) 一种确定用户设备路由选择策略的方法和装置
WO2023160199A1 (zh) 一种接入通信网络的方法和装置
WO2023123218A1 (zh) 网络切片的请求方法、设备、存储介质及程序产品
WO2022259830A1 (en) Method of user equipment (ue) and user equipment (ue)

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22923485

Country of ref document: EP

Kind code of ref document: A1