WO2020168753A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2020168753A1
WO2020168753A1 PCT/CN2019/117588 CN2019117588W WO2020168753A1 WO 2020168753 A1 WO2020168753 A1 WO 2020168753A1 CN 2019117588 W CN2019117588 W CN 2019117588W WO 2020168753 A1 WO2020168753 A1 WO 2020168753A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
slice
information
location
registration area
Prior art date
Application number
PCT/CN2019/117588
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 WO2020168753A1 publication Critical patent/WO2020168753A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • 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
    • 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
    • H04W76/11—Allocation or use of connection identifiers

Definitions

  • This application relates to the field of mobile communication technology, and in particular to a communication method and device.
  • the terminal device After the terminal device carries the requested network slice set and successfully registers to the network, the terminal device obtains the allowed access network slice set and registration area from the network side, then the terminal device can access any tracking area in the registered area.
  • the operator can decide at any time whether to change the state of the network slice deployed in a certain tracking area. Then, once the state of the network slice indicated by a certain network slice identifier in the set of allowed access network slices of the terminal device changes, it may cause the network slice corresponding to some tracking areas in the registration area of the terminal device to no longer Available. If the core network does not notify the terminal device in time, it may happen that the terminal device requests access to the network slice in a tracking area where the network slice is not available in the registration area, which will cause failure and affect the service experience of the terminal device. So how does the core network determine There is no corresponding mechanism to resolve the need to notify the terminal device.
  • the present application provides a communication method and device for notifying the terminal device in time after the status of the network slice changes in a certain tracking area, so that the terminal device can maintain correct and effective communication with the network side.
  • the present application provides a communication method, including: the first slice is unavailable in the first location and available in the second location, the terminal device receives the updated registration area of the terminal device, and the terminal device is updated before the update.
  • the registration area of includes the information of the first location and the information of the second location, the set of allowed access network slices of the terminal device includes the information of the first slice; the terminal device updates the registration area of the terminal device.
  • the network side can update the registration area of the terminal device and notify the terminal device to update the registration area, which helps to ensure that the terminal device can access the "available" slice from any location within the updated registration area, and realize the terminal device and network Maintain correct and effective communication on the other side, or, understood as helping to prevent the terminal device from initiating a service request associated with the first slice at the first location caused by the terminal device’s failure to update the registration area in a timely manner.
  • the terminal device receives the updated set of allowed access network slices of the terminal device; the terminal device updates the set of allowed access network slices of the terminal device.
  • the current location of the terminal device is the first location
  • the updated set of allowed access network slices of the terminal device does not include the information of the first slice
  • the updated registration area of the terminal device The information of the first location is included, and the information of the second location is not included.
  • the terminal device sends a request message, the request message is used to request the establishment or activation of the session associated with the first slice; the terminal device receives the request rejection message, the request rejection message includes a reason value, and the reason value is used for Indicates that the first slice is not available.
  • the terminal device receives the information of the rejected network slice, and the information of the rejected network slice includes the identification information of the first slice.
  • the current location of the terminal device is the second location
  • the updated registration area of the terminal device includes the information of the second location and does not include the information of the first location.
  • the terminal device receives instruction information, and the instruction information is used to instruct the terminal device to initiate a re-registration process.
  • the present application provides a communication method, including: a mobility management network element determines that a first slice is unavailable at a first location and is available at a second location, and the mobility management network element updates the registration area of the terminal device;
  • the pre-update registration area of the terminal device includes the information of the first location and the information of the second location, and the set of allowed access network slices of the terminal device includes the information of the first slice; the mobility management network element sends the information to the terminal device The updated registration area of the terminal device.
  • the network side can update the registration area of the terminal device and notify the terminal device to update the registration area, which helps to ensure that the terminal device can access the "available" slice from any location within the updated registration area, and realize the terminal device and network Maintain correct and effective communication on the other side, or, understood as helping to prevent the terminal device from initiating a service request associated with the first slice at the first location caused by the terminal device’s failure to update the registration area in a timely manner.
  • the mobility management network element updates the set of allowed access network slices of the terminal device; the mobility management network element sends the updated set of allowed access network slices of the terminal device to the terminal device.
  • the current location of the terminal device is the first location
  • the updated set of allowed access network slices of the terminal device does not include the information of the first slice
  • the updated registration area of the terminal device The information of the first location is included, and the information of the second location is not included.
  • the mobility management network element triggers the release of the session associated with the first slice.
  • the mobility management network element receives a request message from the terminal device, and the request message is used to request the establishment or activation of a session associated with the first slice; the mobility management network element sends a request rejection to the terminal device Message, the request rejection message includes a reason value, which is used to indicate that the first slice is unavailable.
  • the mobility management network element sends the information of the rejected network slice to the terminal device, and the information of the rejected network slice includes the identification information of the first slice.
  • the mobility management network element stores the information of the rejected network slice in the context of the terminal device, the information of the rejected network slice includes the information of the first slice, and the information of the rejected network slice is used for Indicates that the first slice is not available in the updated registration area of the terminal device.
  • the current location of the terminal device is the second location
  • the updated registration area of the terminal device includes the information of the second location and does not include the information of the first location.
  • the present application provides a communication device that has the function of implementing the communication method of any of the foregoing aspects or the implementation method in any aspect.
  • This function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the present application provides a communication device, including: a processor and a memory; the memory is used to store computer-executable instructions, and when the device is running, the processor executes the computer-executable instructions stored in the memory to enable the The device executes the communication method as described in any aspect or the implementation method in any aspect.
  • the present application provides a communication device, including: a unit or means for performing each step of any of the above aspects.
  • the present application provides a communication device including a processor and an interface circuit.
  • the processor is configured to communicate with other devices through the interface circuit and execute any method provided in any of the above aspects.
  • the processor includes one or more.
  • the present application provides a communication device, including a processor, configured to be connected to a memory, and configured to call a program stored in the memory to execute the method in any implementation manner of any of the foregoing aspects.
  • the memory can be located inside the device or outside the device.
  • the processor includes one or more.
  • the present application also provides a computer-readable storage medium having instructions stored in the computer-readable storage medium, which when run on a computer, cause a processor to execute the method described in any of the foregoing aspects.
  • the present application also provides a computer program product including instructions, which when run on a computer, causes the computer to execute the method described in any of the foregoing aspects.
  • the present application also provides a chip system, including a processor, configured to execute the methods described in the foregoing aspects.
  • the present application also provides a communication system, including a terminal device for executing any implementation method of the first aspect or the first aspect, and a terminal device for executing any implementation of the second aspect or the second aspect Method of mobility management network element.
  • Figure 1 is a schematic diagram of 5G network architecture
  • FIG. 2 is a schematic diagram of a sliced service area provided by this application.
  • FIG. 3 is a schematic flow chart of a communication method provided by this application.
  • FIG. 4 is a schematic flowchart of another communication method provided by this application.
  • FIG. 5 is a schematic flowchart of another communication method provided by this application.
  • FIG. 6 is a schematic flowchart of another communication method provided by this application.
  • FIG. 7 is a schematic flowchart of another communication method provided by this application.
  • FIG. 8 is a schematic flow diagram of another communication method provided by this application.
  • FIG. 9 is a schematic flowchart of another communication method provided by this application.
  • FIG. 10 is a schematic flowchart of another communication method provided by this application.
  • FIG. 11 is a schematic flowchart of another communication method provided by this application.
  • FIG. 12 is a schematic flowchart of another communication method provided by this application.
  • FIG. 13 is a schematic flowchart of another communication method provided by this application.
  • FIG. 14 is a schematic diagram of a communication device provided by this application.
  • FIG. 15 is a schematic diagram of another communication device provided by this application.
  • FIG. 16 is a schematic diagram of another communication device provided by this application.
  • FIG. 1 it is a schematic diagram of the 5th generation (5G) network architecture.
  • the figure shows some network elements in the 5G architecture.
  • the user plane function (UPF) network elements including data packet routing and transmission, packet inspection, service usage reporting, quality of service (QoS) processing, lawful monitoring, upstream packet inspection, and downstream data packets Storage and other user-related functions.
  • UPF user plane function
  • the access and mobility management function (AMF) network element is responsible for the mobility management of users, including mobility status management, allocation of user temporary identities, authentication and authorization of users.
  • Session management function network elements, including session management (such as session establishment, modification and release, including tunnel maintenance between UPF and AN), UPF network element selection and control, service and session continuity ( Service and Session Continuity (SSC) mode selection, roaming and other session-related functions.
  • session management such as session establishment, modification and release, including tunnel maintenance between UPF and AN
  • UPF network element selection and control service and session continuity ( Service and Session Continuity (SSC) mode selection, roaming and other session-related functions.
  • SSC Service and Session Continuity
  • Network slice selection function (Network Slice Selection Function, NSSF) network elements are responsible for determining network slice instances, selecting AMF network elements, and so on.
  • the mobility management network element in this application may be the AMF network element shown in FIG. 1, or may be a network element having the function of the aforementioned AMF network element in a future communication system.
  • the user plane network element in this application may be the UPF network element shown in FIG. 1, or may be a network element having the function of the above-mentioned UPF network element in a future communication system.
  • the session management network element in this application may be the SMF network element shown in FIG. 1, or may be a network element having the function of the above SMF network element in the future communication system.
  • the slice selection network element in this application may be the NSSF network element shown in FIG. 1, or may be a network element having the function of the aforementioned NSSF network element in a future communication system.
  • the access network device (also referred to as a radio access network (RAN) device) in this application is a device that provides a wireless communication function for a terminal.
  • Access network equipment includes, but is not limited to: next-generation base stations (gnodeB, gNB) in 5G, evolved node B (evolved node B, eNB), radio network controller (RNC), node B (node B) B, NB), 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), transmission point (transmitting and receiving point, TRP), transmission point (transmitting point, TP), mobile switching center, etc.
  • next-generation base stations evolved node B, eNB
  • RNC radio network controller
  • node B node B
  • BSC base station controller
  • BTS base transceiver station
  • home base station for example
  • the terminal equipment of the present application (also referred to as user equipment (UE)) is a device with wireless transceiver function, which can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; or on the water (Such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites, etc.).
  • UE user equipment
  • the terminal may be a mobile phone (mobile phone), a tablet computer (pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, an industrial control (industrial control) Wireless terminals in, self-driving (self-driving), wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety, Wireless terminals in a smart city, wireless terminals in a smart home, etc.
  • VR virtual reality
  • AR augmented reality
  • wireless terminals in remote medical wireless terminals in smart grid, wireless terminals in transportation safety, Wireless terminals in a smart city, wireless terminals in a smart home, etc.
  • the mobility management network element is the AMF network element
  • the slice selection network element is the NSSF network element
  • the session management network element is the SMF network element
  • the user plane network element is the UPF network element.
  • AMF network elements are abbreviated as AMF
  • NSSF network elements are abbreviated as NSSF
  • SMF network elements are abbreviated as SMF
  • UPF network elements are abbreviated as UPF
  • terminal equipment is abbreviated as UE
  • access network equipment is abbreviated as RAN.
  • the AMF described later in this application can be replaced with a mobility management network element
  • NSSF can be replaced with a slice selection network element
  • SMF can be replaced with a session management network element
  • SMF can be replaced with a session management network element
  • both UPF It can be replaced with user plane network elements
  • RAN can be replaced with access network equipment
  • UE can be replaced with terminal equipment.
  • network slice and “slice” refer to the same content, and one of the descriptions is used in different places, and the two can be interchanged.
  • 3rd Generation Partnership Project 3rd Generation Partnership Project
  • 3GPP 3rd Generation Partnership Project
  • network slices do not affect each other. For example, a large number of sudden meter reading services should not affect normal mobile broadband services.
  • 3GPP In order to meet diverse needs and isolation between slices, relatively independent management and operation and maintenance between businesses are required, and tailor-made business functions and analysis capabilities are provided. Instances of different types of services are deployed on different network slices, and different instances of the same service type can also be deployed on different network slices.
  • the selection process of the network slice will be triggered.
  • the slice selection process depends on the user's subscription data, local configuration information, roaming agreement, operator's strategy, and so on. In the selection process of the network slice, the above parameters need to be considered comprehensively to select the best slice type for the UE.
  • the UE may provide the requested network slice to the core network for the core network to select a network slice instance for the UE.
  • the network slice requested by the UE may be represented by a requested network slice set, or may also be represented as requested network slice selection assistance information (requested NSSAI).
  • the requested NSSAI is composed of one or more single network slice selection assistance information (S-NSSAI), and each S-NSSAI is used to identify a network slice type, which can also be understood as S-NSSAI.
  • S-NSSAI single network slice selection assistance information
  • the core network element (such as AMF or NSSF) comprehensively judges based on the UE's subscription data, the UE's requested NSSAI, roaming agreement, and local configuration information, and selects the set of network slices that the UE is allowed to access.
  • the set of network slices allowed to be accessed can be represented by allowed NSSAI, and the S-NSSAI included in the allowed NSSAI are all valid S-NSSAIs in the current network.
  • the AMF in an AMF set can provide the NSSF with the slicing capabilities supported by the AMF in a tracking area (TA), and if the slice corresponding to the TA changes subsequently, it can also update to the NSSF The slicing capability supported by the AMF network element under a certain TA.
  • the NSSF can notify the AMF in the AMF set according to the operator's policy or under certain conditions (for example, when network slices are congested): whether the status of the slices deployed under a certain TA has changed.
  • NSSF can notify AMF that the slice deployed under a certain TA is prohibited from being used (it can also be understood that the TA is a restricted area of the slice), that is, the slice is updated from the "available" state to "unavailable".
  • the AMF learns from the NSSF that the slice is "unavailable” under the TA, the AMF will refuse the UE to access the slice.
  • the slice available state refers to that the slice is accessible or accessible;
  • the slice unavailable state refers to the inaccessible or inaccessible state of the slice.
  • the slice can be updated from the "available" state to the "unavailable” state, or from the "unavailable” state to the “available” state.
  • FIG. 2 a schematic diagram of a sliced service area provided by this application.
  • the service areas of slice A (slice-A, identified by S-NSSAI-A) and slice B (slice-B, identified by S-NSSAI-B) are: TA-1, TA-2, TA-3, ..., TA-10 (only TA-1, TA-2, and TA-3 are shown in the figure), and all the 10 TAs are in the "available” state.
  • the operator decides to update the service area TA-3 of slice A from "available" to "unavailable”. Then at location TA-3, the UE is not allowed to access slice A and use slice A service provided.
  • slice A is in the "available” state in TA-1, TA-2, TA-4,..., TA-10, and in the "unavailable” state in TA-3. It can also be understood that TA-1, TA-2, TA-4,..., TA-10 are the available area of slice A, and TA-3 is the unavailable area (or restricted area) of slice A. For the above slice B, the available area remains: TA-1, TA-2, TA-3,..., TA-10, or it can be understood that slice B is in TA-1, TA-2, TA-3, ..., TA-10 remains in the "available" state.
  • this application provides multiple communication methods. Based on this method, when the state of a slice identified by an S-NSSAI in the allowed NSSAI of the UE changes, the core network can determine whether notification is required The UE, and defines what information needs to be notified to the UE in order to achieve correct and effective communication between the UE and the core network.
  • the application scenario targeted by this application is that a certain S-NSSAI-identified slice in the allowed NSSAI of the UE (referred to as the first slice in this application) is in one or more of the registration areas (Registration Area, RA) of the UE.
  • the status within a TA changes (it can be updated from the "available” state to the "unavailable” state, or from the "unavailable” state to the “available” state).
  • the allowed NSSAI of the UE includes: S-NSSAI-A and S-NSSAI-B, where S-NSSAI-A is slice A Identification, S-NSSAI-B is the identification of slice B; UE registration areas include TAI-1, TAI-2 and TAI-3, where TAI refers to the Tracking Area Identity, and TAI-1 is used for Identifies TA-1, TAI-2 is used to identify TA-2, and TAI-3 is used to identify TA-3.
  • the state of the first slice (taking the first slice as slice A as an example) in TA-3 is updated from the "available" state to the "unavailable” state, and the first slice is in TA- The status of 1 and TA-2 remains "available”.
  • the status of the first slice (taking the first slice as slice A as an example) in TA-3 is updated from the "unavailable” state to the "available” state , And the status of the first slice in TA-1 and TA-2 remains "available”.
  • FIG. 2 is an example for illustration, but is not limited to the specific example shown in FIG. 2.
  • this application provides a schematic flow diagram of a communication method, which is used when a certain slice of the allowed NSSAI of the UE (called the first slice) is registered in the UE
  • the status of a certain TA in the area is updated from the "available" status to the "unavailable” status. That is, this method can be used in the first situation mentioned above.
  • the method includes the following steps:
  • Step 301 The AMF determines that the first slice is unavailable at the first location and available at the second location; where the registration area of the UE includes information about the first location and information about the second location, and the network slices that the UE is allowed to access The set includes the information of the first slice.
  • the first position and the second position here can be respectively TAs in the registration area of the UE.
  • the first position can be TA-3
  • the second position can be TA-1 and/or TA-2.
  • the information of the first position may be TAI-3
  • the information of the second position may be TAI-1 and/or TAI-2.
  • the set of allowed network slices of the UE is the allowed NSSAI of the UE.
  • the first slice here may be slice A, for example.
  • AMF determines that the first slice is unavailable at the first location, which means that AMF determines that the state of the first slice at the first location is "unavailable"; AMF determines that the first slice is available at the second location, It means that AMF determines that the status of the first slice at the second position is "available”.
  • the second location refers to any one or more locations other than the first location in the registration area of the UE.
  • Step 302 The AMF updates the registration area of the UE.
  • the AMF can update the registration area of the UE according to the current location of the UE.
  • the AMF can also update the registration area of the UE according to the current location of the UE and other information.
  • the other information of the UE here includes, for example, the state of the UE (connected state, idle state, etc.).
  • Step 303 The AMF sends the UE's updated registration area to the UE.
  • Step 304 The UE updates the registration area of the UE.
  • the UE updates the received UE's updated registration area to the UE's registration area.
  • the network side can update the registration area of the UE and notify the UE to update the registration area, which helps to ensure that the UE can access the "available" slices at any location within the updated registration area, so that the UE and the network side can maintain correct and effective communication , Or, understood as helping to avoid the problem that the UE initiates a service request associated with the first slice at the first location caused by the UE not updating the registration area in time, causing communication failure with the network side.
  • the AMF may send indication information to the UE, the indication information is used to instruct the UE to initiate a re-registration process, and then the AMF performs the foregoing step 303 in the re-registration process initiated by the UE.
  • Allowed NSSAI of UE ⁇ S-NSSAI-A, S-NSSAI-B ⁇ ;
  • RA of UE ⁇ TAI-1, TAI-2, TAI-3 ⁇ ;
  • slice A The first slice: slice A;
  • Second position TA-1 and/or TA-2;
  • the current location of the UE the first location or the second location;
  • the status of the first slice in TA-3 is updated from “available” to "unavailable”.
  • the specific method for AMF to update the registration area of the UE may be, for example, that the updated registration area of the UE includes the information of the first location. , And does not include information about the second location.
  • the updated registration area (new RA) of the UE is: TAI-3. Therefore, in the above step 304, the UE updates the registration area of the UE, specifically: the UE updates the registration area to: TAI-3.
  • Step 305 The AMF updates the set of network slices allowed to be accessed by the UE.
  • the AMF can update the set of network slices that the UE is allowed to access according to the current location of the UE.
  • the AMF can also update the UE's allowed access network slice set according to the current location of the UE and other information.
  • the other information of the UE here includes, for example, the state of the UE (connected state, idle state, etc.).
  • Step 306 The AMF sends the UE's updated set of allowed access network slices to the UE.
  • Step 307 The UE updates the set of network slices allowed to be accessed by the UE.
  • the specific method for the AMF to update the UE's allowed access network slice set may be, for example, that the UE's updated access allowed network slice set does not include the first slice information.
  • the updated allowed access network slice set (new allowed NSSAI) of the UE is: S-NSSAI-B. Therefore, in the above step 307, the UE updates the set of allowed access network slices of the UE, specifically: the UE updates the set of allowed access network slices to: S-NSSAI-B.
  • the updated registration area (new RA) of the UE is: TAI-3;
  • the updated allowable network slice set (new allowed NSSAI) of the UE is: S-NSSAI-B.
  • step 302-step 304 can be performed first, then step 305-step 307; for another example, step 305-step 307 can be performed first, and then step 302-step 304 can be performed; for another example, step 302 and step can be performed in parallel first 305, then execute step 303 and step 306 in parallel, and then execute step 304 and step 307 in parallel, and so on.
  • the AMF may also trigger the release of the session associated with the first slice.
  • the AMF may also refuse to establish or activate the session associated with the first slice.
  • the method shown in FIG. 3 can be executed in the session establishment procedure of the UE, and the following steps can also be executed in the session establishment procedure:
  • Step A The AMF receives a request message from the UE, and the request message is used to request the establishment or activation of a session associated with the first slice.
  • Step B The AMF sends a request rejection message to the UE.
  • the request rejection message includes a reason value, and the reason value is used to indicate that the first slice is not available.
  • the request rejection message may not include a reason value, that is, only the UE is notified of the rejection to establish or activate the session, and the reason for the rejection is not notified.
  • the AMF may also send the information of the rejected network slice to the UE, and the information of the rejected network slice includes the identification information of the first slice. That is, the AMF notifies the UE of the information of the rejected network slice.
  • the information of the rejected network slice may be sent to the UE through step 303, or step 306, or through a separate step.
  • the AMF may store the information of the rejected network slice in the context of the UE, the information of the rejected network slice includes the information of the first slice, and the information of the rejected network slice is used to indicate that the first slice is in The UE is not available in the updated registration area.
  • the specific method for AMF to update the registration area of the UE may be, for example, that the updated registration area of the UE includes the information of the second location, And does not include the information of the first position.
  • the updated registration area of the UE is: TAI-1 and TAI-2. Therefore, in the above step 304, the UE updates the registration area of the UE, specifically: the UE updates the registration area to: TAI-1, TAI-2.
  • Application scenario 1 The UE initiates the session establishment process or the UE has completed the session establishment
  • Application scenario 1.1 The UE requests the establishment of a session, and the session is associated with the above-mentioned first slice.
  • the first slice is unavailable in the first position and available in the second position, and the current position of the UE is the first position (that is, the situation above One)
  • FIG. 4 it is a schematic flow diagram of a communication method for this application scenario 1.1.
  • the method includes the following steps:
  • Step 400 the AMF sends a TAI to the NSSF, and the slice type (identified by S-NSSAI) supported by the AMF under the TA identified by the TAI.
  • the AMF can call the NSSF service operation Nnssf_NSSAIAvailability_Update, which carries the TAI and the slice type (identified by S-NSSAI) that the AMF supports under the TA identified by the TAI.
  • step 401 the UE initiates a registration procedure with a requested NSSAI, the AMF accepts the UE's registration request, and allocates a registration area (RA) to the UE, and the AMF returns allowed NSSAI and RA to the UE.
  • RA registration area
  • the RA contains a TA list composed of multiple TAIs, and any S-NSSAI included in the allowed NSSAI can be accessed by any TA in the RA, or it can be understood that any S-NSSAI included in the allowed NSSAI is in this RA. Any TA in the RA can provide services for the UE.
  • Step 402 at a certain moment, NSSF decides to change the state of the first slice at the first position (for example, because the congestion of the first slice exceeds the threshold), and update the first slice from the "available" state to "unavailable”. use”.
  • step 403 the NSSF notifies the AMF that the first slice is updated to be unavailable at the first location.
  • the NSSF may call the Nnssf_NSSAIAvailability_Notify service operation to notify the AMF that the first slice is updated to be unavailable at the first location.
  • the NSSF can send multiple S-NSSAIs and corresponding unavailable location lists to the AMF. For example, if S-NSSAI-A is in TA-11, TA-12 is updated as unavailable, S-NSSAI-B is in TA-13, and TA-14 is updated as unavailable, then NSSF can send to AMF: (S-NSSAI- A, (TA-11, TA-12)), (S-NSSAI-B, (TA-13, TA-14)).
  • Step 404 The current position of the UE is the first position, and the UE sends a non-access stratum (NAS) message to the AMF.
  • the NAS message can carry a session establishment request and a session identifier (protocol data unit, PDU). ) session ID) and the corresponding S-NSSAI and Data Network Name (DNN) of the session.
  • PDU protocol data unit
  • DNN Data Network Name
  • the slice identified by S-NSSAI in the NAS message includes the first slice described above.
  • Step 405 After receiving the session establishment request of the UE, the AMF determines that the first slice identified by the S-NSSAI requested by the UE is not available at the current location of the UE.
  • the AMF determines that the first slice associated with the session that the UE requests to establish is not available at the current location of the UE (ie, the first location).
  • step 406 the AMF rejects the NAS message sent by the UE, carrying a reason value: the S-NSSAI requested by the UE is not available at the current location of the UE.
  • the AMF rejected the session establishment request of the UE.
  • Step 407 As the session establishment fails, the AMF triggers to update the allowed NSSAI and RA of the UE.
  • Step 408 The AMF sends a configuration update message to the UE, carrying new allowed NSSAI and new RA, where:
  • new allowed NSSAI does not include unavailable S-NSSAI
  • new RA includes the information of the first location. Among them, the slice corresponding to the identifier of the slice in new allowed NSSAI is available in new RA.
  • the configuration update message may also carry the network slice (rejected S-NSSAI in current RA) that is rejected in the current registration area of the UE, to notify the UE that the rejected S-NSSAI is not available in the new RA, that is, rejected S
  • the NSSAI includes the S-NSSAI corresponding to the session requested by the UE in step 404.
  • the configuration update message in step 408 does not carry new allowed NSSAI and new RA, but carries re-registration indication information (or indication information), which is used to instruct the UE to initiate the registration process. .
  • Step 409 The UE returns a configuration update complete message to the AMF.
  • step 410 if the UE receives the re-registration indication information in step 408, the UE initiates a registration process after step 409, the UE sends a registration request message, and the AMF carries new allowed NSSAI and new RA in the registration acceptance message sent to the UE.
  • new allowed NSSAI does not include the unavailable S-NSSAI
  • new RA includes the information of the first location.
  • the slice corresponding to the identifier of the slice in new allowed NSSAI is available in new RA.
  • the registration acceptance message can also carry a network slice (rejected S-NSSAI in current RA) that is rejected in the current registration area of the UE, and is used to notify the UE that the rejected S-NSSAI is not available in the new RA, that is, rejected S-
  • the NSSAI includes the S-NSSAI corresponding to the session establishment requested by the UE in step 404.
  • Step 411 The AMF stores the rejected S-NSSAI in current RA in the context of the UE, which is used to record to which UEs the rejected S-NSSAI has been sent.
  • This step 411 is optional.
  • the network side rejects the UE to establish the session, so that the UE knows that the slice cannot be accessed at the current location, and at the same time updates the registration area of the UE. It helps to ensure that the UE can access the "available" slices at any location in the updated registration area, so that the UE can maintain correct and effective communication with the network side.
  • Application Scenario 1.2 The UE requests the establishment of a session, and the session is associated with the above-mentioned first slice.
  • the first slice is not available at the first location and available at the second location, and the current location of the UE is the second location (ie, the situation above) two)
  • FIG. 5 it is a schematic flow diagram of a communication method for this application scenario 1.2.
  • the method includes the following steps:
  • Step 500 to step 503 are the same as step 400 to step 403 in Embodiment 4. Refer to the foregoing description, and will not be repeated here.
  • the current location of the UE is the second location, and the UE sends a NAS message to the AMF.
  • the NAS message may carry a session establishment request, a session ID (PDU session ID), and the S-NSSAI and DNN corresponding to the session.
  • the slice identified by S-NSSAI in the NAS message is the aforementioned first slice.
  • Step 505 After receiving the session establishment request from the UE, the AMF determines that the first slice identified by the S-NSSAI requested by the UE is available at the current location of the UE, but the registration area of the UE includes the unavailable S-NSSAI requested by the UE TA (that is, the first position).
  • the AMF determines that the first slice associated with the session that the UE requests to establish is available at the current location (ie, the second location) of the UE.
  • the first slice is not available in the TA (that is, the first location) identified by a certain TAI in the registration area of the UE.
  • Step 506 continue with other steps of the session establishment process, for example, including AMF selecting SMF based on S-NSSAI and DNN, SMF selecting UPF based on S-NSSAI and DNN, etc., until the session is successfully established.
  • Step 507 Since the registration area of the UE contains the TA requested by the UE for which the S-NSSAI is unavailable, the AMF decides to trigger an update of the registration area of the UE, and the AMF sends a configuration update message to the UE, carrying new RA.
  • old RA ⁇ TA-1, TA-2, TA-3 ⁇
  • new RA ⁇ TA-1, TA-2 ⁇ .
  • the configuration update message in step 507 above does not carry new RA, but carries re-registration indication information, which is used to instruct the UE to initiate a registration process.
  • Step 508 The UE returns a configuration update complete message to the AMF.
  • step 509 if the UE receives the re-registration indication information in step 507, the UE initiates a registration process after step 508, the UE sends a registration request message, and the AMF carries new RA in the registration acceptance message sent to the UE.
  • old RA ⁇ TA-1, TA-2, TA-3 ⁇
  • new RA ⁇ TA-1, TA-2 ⁇ .
  • the network side accepts the UE to establish the session, so that the UE knows that the slice can be accessed at the current location, and at the same time updates the registration area of the UE. It helps to ensure that the UE can access the "available" slices at any location in the updated registration area, so that the UE can maintain correct and effective communication with the network side.
  • Application Scenario 1.3 The session requested by the UE has been established, and the session is associated with the above-mentioned first slice, which is not available at the first location
  • FIG. 6 it is a schematic flow diagram of a communication method for this application scenario 1.3.
  • the method includes the following steps:
  • Step 600 is the same as step 400 in Embodiment 4, and reference may be made to the foregoing description.
  • step 601a the UE initiates a registration process, carrying a requested NSSAI, the AMF accepts the UE's registration request, and allocates a registration area to the UE, and the AMF returns the allowed NSSAI and the registration area to the UE.
  • step 601b the UE initiates a session establishment process to request the establishment of a session corresponding to the S-NSSAI.
  • the session is successfully established, and the AMF saves the session identifier (PDU session ID), the association relationship between the S-NSSAI and the SMF ID.
  • PDU session ID the session identifier
  • the slice identified by S-NSSAI here is the first slice.
  • Step 602 to step 603 are the same as step 402 to step 403 in Embodiment 4, and reference may be made to the foregoing description.
  • Step 604 If the UE is in the connected state, the current location of the UE is the first location, and the AMF determines that the first slice is not available at the current location of the UE. If the UE is in the idle state, at this time, the AMF is not sure about the specific location of the UE. In this case, the AMF can wait for the UE to update from the idle state to the connected state (for example, the UE initiates a service request and other signaling). Acquire the current location of the UE (the first location), and determine that the first slice is not available at the current location of the UE.
  • step 605 the AMF decides to trigger the release of the session corresponding to the first slice that is not available at the current location.
  • the AMF determines the SMF corresponding to the session according to the context, and then sends a session release request to the SMF to request the release of the session.
  • AMF can call Nsmf_PDUSession_UpdateSMContext, carrying PDU session release request (including reason value: the S-NSSAI corresponding to the session is not available at the current location of the UE).
  • Step 606 Because the UE is currently located in an area where the first slice is not available, the AMF triggers the update of the allowed NSSAI and RA of the UE, and the AMF sends a configuration update message to the UE, carrying new allowed NSSAI and new RA, where:
  • new allowed NSSAI does not include unavailable S-NSSAI; new RA includes information about the first location. Among them, the slice corresponding to the slice identifier in the new allowed NSSAI is available in new RA.
  • the configuration update message may also carry rejected S-NSSAI in current RA, which is used to notify the UE that the rejected S-NSSAI is not available in the new RA, that is, the rejected S-NSSAI includes the S-NSSAI corresponding to the UE's request to establish a session in step 601b. -NSSAI.
  • the configuration update message in step 606 does not carry new allowed NSSAI and new RA, but carries re-registration indication information, which is used to instruct the UE to initiate a registration process.
  • Step 607 The UE returns a configuration update complete message to the AMF.
  • step 608 if the UE receives the re-registration indication information in step 606, the UE initiates a registration process after step 607, the UE sends a registration request message, and the AMF carries new allowed NSSAI and new RA in the registration acceptance message sent to the UE.
  • new allowed NSSAI does not include the unavailable S-NSSAI
  • new RA includes the information of the first location.
  • the slice corresponding to the identifier of the slice in new allowed NSSAI is available in new RA.
  • the registration acceptance message can also carry a network slice (rejected S-NSSAI in current RA) that is rejected in the current registration area of the UE, and is used to notify the UE that the rejected S-NSSAI is not available in the new RA, that is, rejected S-
  • the NSSAI includes the S-NSSAI corresponding to the UE request to establish a session in step 601b.
  • the AMF stores the rejected S-NSSAI in current RA in the context of the UE in the context of the UE to record the rejected S-NSSAI to which UEs have been sent.
  • This step 609 is optional.
  • the network side can release the established session, so that the UE knows that the slice cannot be accessed at the current location, which helps to ensure The UE can access the "available" slice at any location in the updated registration area, so that the UE can maintain correct and effective communication with the network side.
  • NSSF decided to update the service area TA-3 (ie the first location) of slice A (ie the first slice) from “available” to "unavailable”. .
  • the UE initiates the establishment of a session corresponding to the first slice in an area where the first slice is available (such as TA-2), that is, a PDU session is established in the first slice.
  • a session corresponding to the first slice in an area where the first slice is available (such as TA-2), that is, a PDU session is established in the first slice.
  • the UE in the connected state moves from TA-2 to TA-3 (that is, the first position), and the UE switches from the source-RAN (Source-RAN, S-RAN) to the target-side RAN (Target-RAN) through the handover process.
  • RAN, T-RAN where the source-side RAN is located in an area where the first slice is available, and the target-side RAN is located in an area where the first slice is not available.
  • the first slice corresponding to the session established by the UE is available in the TA where the source RAN is located. After the UE is switched to the target RAN, the first slice is not available in the TA where the target RAN is located. Therefore, the network side will release the session.
  • the source-side RAN is located in one or some TAs of the UE's registration area
  • the first slice is available in the source-side RAN
  • the target-side RAN is located in one or some TAs of the UE's registration area
  • the first slice is not available in the target-side RAN, that is, after the UE switches to the target-side RAN, the first slice is not supported in the TA where the target-side RAN is located.
  • FIG. 7 it is a schematic flowchart of a communication method for this application scenario 2. The method includes the following steps:
  • Step 700 to step 703 are the same as step 400 to step 403 in the fourth embodiment, and reference may be made to the foregoing description.
  • Step 704a the source-side RAN initiates the handover of the Xn interface, and determines the target-side RAN according to the measurement report of the UE.
  • Step 704b the target-side RAN sends a Path Switch Request (Path Switch Request) message to the AMF, which carries a list of sessions to be switched (List of PDU Sessions To Be Switched) and the TAI corresponding to the TA where the target-side RAN is located.
  • Path Switch Request Path Switch Request
  • Step 705 The AMF determines the first position of the first slice associated with the PDU session included in the session list according to the PDU session IDs included in the session list to be switched and the S-NSSAI corresponding to each PDU session ID stored in the context unavailable.
  • Table 1 For example, the information contained in the list of sessions to be switched is Table 1:
  • the S-NSSAI corresponding to each PDU session ID stored in AMF is shown in Table 2:
  • the first slice corresponds to S-NSSAI-A, and the first slice corresponding to S-NSSAI-A is not available at the first position.
  • the first position here refers to the TA where the target RAN is located, and the registration area of the UE includes the TAI corresponding to the TA.
  • the TA where the target RAN is located is TA-3, and the registration area of the UE includes TA-3.
  • step 706a the AMF decides to trigger the release of the session corresponding to the first slice that is not available in the first position.
  • the session corresponding to the unavailable first slice is PDU session ID-1.
  • step 706b the AMF determines the SMF corresponding to the session according to the context, and then sends a session release request to the SMF, requesting to release the session.
  • AMF can call Nsmf_PDUSession_UpdateSMContext, carrying PDU session release request (including reason value: the S-NSSAI corresponding to the session is not available on the target RAN).
  • step 706c the AMF sends a Path Switch Request Acknowledgement (Path Switch Request ACK) message to the target-side RAN, which carries the new allowed NSSAI.
  • Path Switch Request ACK Path Switch Request Acknowledgement
  • the path switch request confirmation message also carries a list of PDU sessions for which the switch failed.
  • the PDU session list that failed to switch contains the identifier of the session that failed to switch.
  • Step 707 After the handover is completed, if the UE initiates a mobility registration update procedure with requested NSSAI, AMF determines new allowed NSSAI and new RA according to the UE’s requested NSSAI and the UE’s current location (ie the first location), and sends it to the UE new allowed NSSAI and new RA.
  • new allowed NSSAI does not include the identifier of the first slice, and new RA includes information about the first location.
  • AMF determines that the first slice is not available at the first location where the target RAN is located, and then allocates a new allowed NSSAI by deleting the session corresponding to the first slice that is not available on the target RAN Or RA, so that the UE learns that the slice cannot be accessed under the current location (ie, the first location).
  • Application scenario 3 UE in idle state initiates activation process
  • NSSF decided to update the service area TA-3 (ie the first location) of slice A (ie the first slice) from “available” to "unavailable”. .
  • the UE initiates the establishment of a session corresponding to the first slice in the area where the first slice is available (such as TA-2), that is, a PDU session is established in the first slice.
  • the UE is in an idle state and moves from TA-2 to TA-3, that is, from the area where the first slice is available to the area where the first slice is not available.
  • Application scenario 3.1 The UE in the idle state initiates a service request in an area where the first slice is unavailable (such as TA-3), requesting to activate the PDU session user plane data connection corresponding to the first slice.
  • TA-3 TA-3
  • FIG. 8 it is a schematic flow diagram of a communication method for this application scenario 3.1.
  • the method includes the following steps:
  • Step 800 to step 803 are the same as step 600 to step 603 in the embodiment shown in FIG. 6, and reference may be made to the foregoing description, which will not be repeated here.
  • step 804a the UE in the idle state initiates a service request to the (R)AN, which carries a list of sessions to be activated (List of PDU Sessions To Be Activated), and the list contains the PDU session ID.
  • the list of sessions to be activated contains information as Table 3:
  • step 804b the (R)AN forwards the service request of the UE, and at the same time reports the current location of the UE to the AMF.
  • the current location of the UE can be carried in the service request in step 804a, and then in step 804b, the (R)AN sends the service request to the AMF.
  • the current location of the UE is the first location. Taking the example shown in Figure 2 as an example, the current location of the UE is located at TA-3.
  • Step 805 The AMF determines that the first slice corresponding to the session in the session list to be activated is not available at the current location of the UE.
  • the corresponding relationship between the session identifier (PDU session ID) and the slice identifier (S-NSSAI) is stored on the AMF.
  • the S-NSSAI corresponding to each PDU session ID stored by AMF is shown in Table 4:
  • PDU session ID-1 S-NSSAI-A
  • PDU session ID-2 S-NSSAI-B
  • the first slice corresponds to S-NSSAI-A, and the first slice corresponding to S-NSSAI-A is not available at the first position.
  • step 806a the AMF rejects the service request of the UE and returns a reason value: the first slice is not available at the current location of the UE.
  • step 806b the AMF decides to trigger the release of the session corresponding to the first slice that is not available at the current location.
  • the AMF determines the SMF corresponding to the session according to the context, and then sends a session release request to the SMF to request the release of the session.
  • AMF can call Nsmf_PDUSession_UpdateSMContext, carrying PDU session release request (including reason value: the S-NSSAI corresponding to the session is not available at the current location of the UE).
  • the session corresponding to the first slice that is not available is PDU session ID-1.
  • Step 807 Because the service request fails, the AMF triggers the update of the allowed NSSAI and RA of the UE, and the AMF sends a configuration update message to the UE, which carries new allowed NSSAI and new RA, where:
  • new allowed NSSAI does not include unavailable S-NSSAI (that is, the identifier of the first slice mentioned above); new RA includes information about the first location. Among them, the slice corresponding to the identifier of the slice in new allowed NSSAI is available in new RA.
  • the configuration update message may also carry rejected S-NSSAI in current RA, which is used to notify the UE that the rejected S-NSSAI is not available in the new RA, that is, the rejected S-NSSAI includes the session corresponding to the session that the UE requested to activate in step 804a. S-NSSAI.
  • the configuration update message in step 807 does not carry new allowed NSSAI and new RA, but carries re-registration indication information, which is used to instruct the UE to initiate a registration process.
  • step 808 the UE returns a configuration update complete message to the AMF.
  • step 809 if the UE receives the re-registration indication information in step 807, the UE initiates a registration process after step 808, the UE sends a registration request message, and the AMF carries new allowed NSSAI and new RA in the registration acceptance message sent to the UE.
  • new allowed NSSAI does not include the S-NSSAI requested by the UE (that is, does not include the unavailable S-NSSAI), and new RA includes the information of the first location.
  • the registration acceptance message may also carry a network slice (rejected S-NSSAI in current RA) that is rejected in the current registration area of the UE, and is used to notify the UE that the rejected S-NSSAI is not available in the new RA, that is, rejected S-
  • the NSSAI includes the S-NSSAI corresponding to the session that the UE requests activation in step 804a.
  • Step 810 The AMF stores the rejected S-NSSAI in current RA in the context of the UE in the context of the UE to record the rejected S-NSSAI to which UEs have been sent.
  • This step 810 is optional.
  • AMF determines that the status of the first slice at the UE’s current location (first location) is "unavailable”, and then by rejecting the UE’s service request, it allocates new allowed NSSAI or RA so that the UE knows that it is at the current location
  • the inability to access the first slice is helpful to ensure that the UE can access the "available" slice at any location in the updated registration area, so that the UE can maintain correct and effective communication with the network side.
  • Application Scenario 3.2 The UE in the idle state initiates a service request in the area where the first slice is available (such as TA-2), requesting to activate the PDU session user plane data connection corresponding to the first slice.
  • a service request in the area where the first slice is available (such as TA-2), requesting to activate the PDU session user plane data connection corresponding to the first slice.
  • FIG. 9 it is a schematic flow diagram of a communication method for this application scenario 3.2.
  • the method includes the following steps:
  • Step 900 to step 903 are the same as step 800 to step 803 of the embodiment shown in FIG. 8, and reference may be made to the foregoing description, which will not be repeated here.
  • step 904a the UE in the idle state initiates a service request to the (R)AN, carrying a list of sessions to be activated (List of PDU Sessions To Be Activated), and the list includes the PDU session ID.
  • the list of sessions to be activated contains information as Table 5:
  • Step 904b the (R)AN forwards the service request of the UE, and at the same time reports the current location of the UE to the AMF.
  • the current location of the UE can be carried in the service request in step 904a, and then in step 904b, the (R)AN sends the service request to the AMF.
  • the current location of the UE is the second location.
  • Step 905 The AMF determines that the first slice corresponding to the session in the list of sessions to be activated is available at the current location (second location) of the UE.
  • the corresponding relationship between the session identifier (PDU session ID) and the slice identifier (S-NSSAI) is stored on the AMF.
  • the S-NSSAI corresponding to each PDU session ID stored by AMF is shown in Table 6:
  • the first slice corresponds to S-NSSAI-A
  • the first slice corresponding to S-NSSAI-A is available at the second position.
  • Step 906 Continue other processes of the service request until the process ends successfully.
  • Step 907 Since the registration area of the UE contains the unavailable TA (ie the first position) corresponding to the session to be activated, the AMF decides to trigger the update of the registration area of the UE, and the AMF sends a configuration update message to the UE, carrying new RA.
  • the AMF Since the registration area of the UE contains the unavailable TA (ie the first position) corresponding to the session to be activated, the AMF decides to trigger the update of the registration area of the UE, and the AMF sends a configuration update message to the UE, carrying new RA.
  • old RA ⁇ TA-1, TA-2, TA-3 ⁇
  • new RA ⁇ TA-1, TA-2 ⁇ .
  • the configuration update message in step 907 does not carry new RA, but carries re-registration indication information, which is used to instruct the UE to initiate the registration process.
  • step 908 the UE returns a configuration update complete message to the AMF.
  • step 909 if the UE receives the re-registration indication information in step 907, the UE initiates a registration process after step 908, the UE carries a registration request message, and the AMF carries new RA in the registration acceptance message.
  • old RA ⁇ TA-1, TA-2, TA-3 ⁇
  • new RA ⁇ TA-1, TA-2 ⁇ .
  • the AMF determines that the status of the first slice at the current location (second location) of the UE is "available", and the network side accepts the service request of the UE, so that the UE knows that the slice can be accessed at the current location.
  • updating the registration area of the UE helps to ensure that the UE can access "available" slices at any location within the updated registration area, so that the UE can maintain correct and effective communication with the network side.
  • Application scenario 4 The network side initiates the UE activation process
  • application scenario 3 is a service request process initiated by a UE in an idle state
  • application scenario 4 is a service request process triggered by the network side.
  • NSSF decided to update the service area TA-3 (ie the first location) of slice A (ie the first slice) from “available” to "unavailable”. .
  • the UE initiates the establishment of a session corresponding to the first slice in the area where the first slice is available (such as TA-2), that is, a PDU session is established in the first slice.
  • the UE is in an idle state and moves from TA-2 to TA-3, that is, from the area where the first slice is available to the area where the first slice is not available.
  • Application Scenario 4.1 The UE in the idle state initiates a service request in an area where the first slice is not available (such as TA-3), requesting to activate the PDU session user plane data connection corresponding to the first slice.
  • FIG. 10 it is a schematic flow diagram of a communication method for this application scenario 4.1.
  • the method includes the following steps:
  • Step 1000 to step 1003 are the same as step 800 to step 803 in the embodiment shown in FIG. 8, please refer to the foregoing description, and will not be repeated here.
  • Step 1004a the UE is in an idle state, and the downlink data arrives at the UPF.
  • Step 1004b UPF sends a data arrival notification to SMF.
  • Step 1005 The SMF sends the session identifier (PDU session ID) and the permanent identifier of the UE to the AMF.
  • SMF invokes the Namf_Communication_N1N2MessageTransfer service operation of AMF, which carries the session identifier (PDU session ID) and the permanent identifier of the UE.
  • Step 1006 AMF triggers paging to the UE.
  • Step 1007a After receiving the paging message, the UE sends a service request to the (R)AN.
  • Step 1007b the (R)AN forwards the service request of the UE, and at the same time reports the current location of the UE to the AMF.
  • the current location of the UE can be carried in the service request in step 1007a, and then in step 1007b, the (R)AN sends the service request to the AMF.
  • the current location of the UE is the first location.
  • Step 1008 The AMF determines that the first slice corresponding to the session to be activated is not available at the current location of the UE.
  • the corresponding relationship between the session identifier (PDU session ID) and the slice identifier (S-NSSAI) is stored on the AMF.
  • Step 1009a the AMF rejects the service request of the UE and returns a reason value: the first slice is not available at the current location of the UE.
  • the AMF decides to trigger the release of the session corresponding to the first slice that is not available at the current location.
  • the AMF determines the SMF corresponding to the session according to the context, and then sends a session release request to the SMF to request the release of the session.
  • AMF can call Nsmf_PDUSession_UpdateSMContext, carrying PDU session release request (including reason value: the S-NSSAI corresponding to the session is not available at the current location of the UE).
  • Step 1010 Because the service request fails, the AMF triggers the update of the allowed NSSAI and RA of the UE, and the AMF sends a configuration update message to the UE, carrying new allowed NSSAI and new RA, where:
  • new allowed NSSAI does not include unavailable S-NSSAI (that is, the identifier of the first slice mentioned above); new RA includes information about the first location. Among them, the slice corresponding to the identifier of the slice in new allowed NSSAI is available in new RA.
  • the configuration update message may also carry rejected S-NSSAI in current RA to notify the UE that the rejected S-NSSAI is unavailable in the new RA, that is, rejected S-NSSAI includes the S-NSSAI corresponding to the UE's request to establish a session in step 1001b. -NSSAI.
  • the configuration update message in step 1010 does not carry new allowed NSSAI and new RA, but carries re-registration indication information, which is used to instruct the UE to initiate a registration process.
  • Step 1011 The UE returns a configuration update complete message to the AMF.
  • Step 1012 If the UE receives the re-registration indication information in step 1010, the UE initiates a registration process after step 1011, the UE sends a registration request message, and the AMF carries new allowed NSSAI and new RA in the registration acceptance message sent to the UE.
  • new allowed NSSAI does not include unavailable S-NSSAI (that is, the identifier of the first slice mentioned above); new RA includes the information of the first location.
  • the slice corresponding to the identifier of the slice in new allowed NSSAI is available in new RA.
  • the registration acceptance message may also carry rejected S-NSSAI in current RA, which is used to notify the UE that rejected S-NSSAI is not available in new RA, that is, rejected S-NSSAI includes the S-NSSAI corresponding to the UE's request to establish a session in step 1001b. -NSSAI.
  • Step 1013 The AMF stores the rejected S-NSSAI in current RA in the context of the UE in the context of the UE, so as to record to which UEs the rejected S-NSSAI has been sent.
  • This step 1013 is optional.
  • AMF judges that the status of the first slice at the UE's current location (first location) is "unavailable", and by rejecting the UE's service request, it allocates new allowed NSSAI and RA, so that the UE knows that it is at the current location
  • the inability to access the first slice is helpful to ensure that the UE can access the "available" slice at any location in the updated registration area, so that the UE can maintain correct and effective communication with the network side.
  • Application Scenario 4.2 The UE in the idle state initiates a service request in the area where the first slice is available (such as TA-2), requesting to activate the PDU session user plane data connection corresponding to the first slice.
  • a service request in the area where the first slice is available (such as TA-2), requesting to activate the PDU session user plane data connection corresponding to the first slice.
  • FIG. 11 it is a schematic flowchart of a communication method for this application scenario 4.2.
  • the method includes the following steps:
  • Step 1100 to step 1106 are the same as step 1000 to step 1006 in the embodiment shown in FIG. 10, and reference may be made to the foregoing description, which will not be repeated here.
  • Step 1107a After receiving the paging message, the UE sends a service request to the (R)AN.
  • step 1107b the (R)AN forwards the service request of the UE and at the same time reports the current location of the UE to the AMF.
  • the current location of the UE is the second location.
  • Step 1108 The AMF determines that the first slice corresponding to the session to be activated is available at the current location of the UE.
  • the corresponding relationship between the session identifier (PDU session ID) and the slice identifier (S-NSSAI) is stored on the AMF.
  • Step 1109 Continue other processes of the business request until the process ends successfully.
  • Step 1110 Since the registration area of the UE contains the unavailable TA (that is, the first position) corresponding to the S-NSSAI of the session to be activated, the AMF decides to trigger the update of the registration area of the UE, and the AMF sends a configuration update message to the UE, carrying new RA.
  • the AMF Since the registration area of the UE contains the unavailable TA (that is, the first position) corresponding to the S-NSSAI of the session to be activated, the AMF decides to trigger the update of the registration area of the UE, and the AMF sends a configuration update message to the UE, carrying new RA.
  • old RA ⁇ TA-1, TA-2, TA-3 ⁇
  • new RA ⁇ TA-1, TA-2 ⁇ .
  • the configuration update message in step 1110 does not carry new RA, but carries re-registration indication information, which is used to instruct the UE to initiate a registration process.
  • Step 1111 The UE returns a configuration update complete message to the AMF.
  • Step 1112 If the UE receives the re-registration indication information in step 1110, the UE initiates a registration process after step 1111, the UE sends a registration request message, and the AMF carries new RA in the registration acceptance message sent to the UE.
  • old RA ⁇ TA-1, TA-2, TA-3 ⁇
  • new RA ⁇ TA-1, TA-2 ⁇ .
  • the AMF determines that the status of the first slice at the current location (second location) of the UE is "available", and the network side accepts the service request of the UE, so that the UE knows that the slice can be accessed at the current location.
  • updating the registration area of the UE helps to ensure that the UE can access "available" slices at any location within the updated registration area, so that the UE can maintain correct and effective communication with the network side.
  • the above application scenario 1 to application scenario 4, for the first slice where the state at the first location changes, is the process of establishing, activating, and switching the session corresponding to the first slice when the UE or the network is performing services , Determine whether the first slice is available at the current location of the UE, and then determine the method for updating the RA or allowed NSSAI of the UE.
  • a specific example is given below.
  • FIG. 12 it is a schematic flowchart of another communication method provided by this application. The method includes the following steps:
  • Step 1200 to step 1203 are the same as step 400 to step 403 in Embodiment 4. Refer to the foregoing description, which will not be repeated here.
  • Step 1204 The AMF determines, according to the allowed NSSAI in the context of the UE, that the allowed NSSAI includes the unavailable S-NSSAI (that is, the identifier of the first slice), and the registration area of the UE includes the information of the first location, and the UE is connected state.
  • Step 1205 The AMF judges whether the first slice is available at the current location of the UE.
  • the AMF determines that the first slice is not available at the current location of the UE.
  • the AMF determines that the first slice is available at the current location of the UE.
  • Step 1206 The AMF sends a configuration update message to the UE.
  • the AMF determines that the first slice is not available at the current location of the UE in step 1205, the AMF triggers the update of the allowed NSSAI and RA of the UE, and the AMF sends a configuration update message to the UE, carrying new allowed NSSAI and new RA, Among them, new allowed NSSAI does not include unavailable S-NSSAI; new RA includes information about the first location. Among them, the slice corresponding to the identifier of the slice in new allowed NSSAI is available in new RA.
  • the configuration update message may also carry rejected S-NSSAI in current RA to notify the UE that the rejected S-NSSAI is unavailable in the new RA, that is, the rejected S-NSSAI includes the S-NSSAI notified in step 1203 (ie Identification of the first slice).
  • the AMF determines that the first slice is available at the current location of the UE, the AMF decides to trigger the update of the registration area of the UE, and the AMF sends a configuration update message to the UE, carrying new RA.
  • the configuration update message in step 1206 does not carry new allowed NSSAI and/or new RA, but carries re-registration indication information for instructing the UE to initiate a registration process.
  • Step 1207 The UE returns a configuration update complete message to the AMF.
  • Step 1208 If the UE receives the re-registration indication information in step 1206, the UE initiates a registration process after step 1207, and the UE sends a registration request message.
  • step 1205 the AMF determines that the first slice is not available at the current location of the UE, the AMF triggers the update of the allowed NSSAI and RA of the UE, and the AMF sends a registration acceptance message to the UE, carrying new allowed NSSAI and new RA, Among them, new allowed NSSAI does not include unavailable S-NSSAI; new RA includes information about the first location. Among them, the slice corresponding to the identifier of the slice in new allowed NSSAI is available in new RA.
  • the registration acceptance message may also carry rejected S-NSSAI in current RA to notify the UE that the rejected S-NSSAI is not available in the new RA, that is, the rejected S-NSSAI includes the S-NSSAI notified in step 1203 (ie Identification of the first slice).
  • AMF determines that the first slice is available at the current location of the UE, AMF decides to trigger an update of the UE's registration area, and AMF sends a registration acceptance message to the UE, carrying new RA.
  • old RA ⁇ TA-1, TA-2, TA-3 ⁇
  • new RA ⁇ TA-1, TA-2 ⁇ .
  • Step 1209 The AMF stores the rejected S-NSSAI in current RA in the context of the UE in the context of the UE to record the rejected S-NSSAI to which UEs have been sent.
  • This step 1209 is an optional step.
  • the AMF may perform this step 1209 or not.
  • the AMF does not perform this step 1209.
  • the network side can update the registration area of the UE and notify the UE to update the registration area, and the AMF only judges whether it needs to update the allowed NSSAI or RA of the UE based on the status and current location of the UE, which helps to ensure that the UE is in the updated registration area Any location inside can access the "available" slice, so that the UE can maintain correct and effective communication with the network side, or, understood as helping to prevent the UE from initiating a communication with the first location due to the UE not updating the registration area in time.
  • the service request associated with the first slice causes a communication failure with the network side.
  • Figs. 2 to 12 are implementations for the first situation, that is, the first slice is updated from the "available” state to the "unavailable” state at the first position.
  • An example is given below, which is aimed at the implementation of the second situation, that is, the first slice is updated from the "unavailable" state to the "available” state at the first position.
  • FIG. 13 it is a schematic flowchart of another communication method provided by this application. The method includes the following steps:
  • step 1301 the NSSF determines that the state of the first slice at the first position has changed: it is updated from unavailable to available.
  • NSSF decides to change the state of the first slice at the first position (for example, because the congestion of the slice is lower than the threshold), the first The film is updated from "unavailable" to "available”.
  • step 1302 the NSSF notifies the AMF that the first slice is updated to be available at the first location.
  • the NSSF can call the Nnssf_NSSAIAvailability_Notify service operation to notify the AMF that the first slice is updated to be available at the first location.
  • the NSSF can send multiple S-NSSAIs and corresponding available location lists to the AMF. For example, if S-NSSAI-A is available in TA-11 and TA-12 is updated, S-NSSAI-B is updated in TA-13 and TA-14 is updated to be available, then NSSF can send to AMF: (S-NSSAI-A, (TA-11, TA-12)), (S-NSSAI-B, (TA-13, TA-14)).
  • Step 1303 The AMF judges which UEs have sent S-NSSAI rejected in RA according to the information of the rejected network slice (S-NSSAI rejected in RA) stored in the context of each UE, and the RA of the UE contains the first position Information.
  • Step 1304 if the UE is in an idle state, the AMF pages the UE.
  • step 1305 is executed.
  • step 1304 can be skipped and step 1305 can be executed directly.
  • Step 1305 The UE is in a connected state, and the AMF sends a configuration information message to the UE.
  • the configuration update message carries new allowed NSSAI, and the allowed NSSAI is that the rejected S-NSSAI (that is, the identifier of the first slice) is added to the current allowed NSSAI of the UE.
  • the configuration update message carries a rejected S-NSSAI available (rejected S-NSSAI available) indication, which triggers the UE to construct a new requested NSSAI to try to access the slice (that is, the first slice).
  • a rejected S-NSSAI available indication triggers the UE to construct a new requested NSSAI to try to access the slice (that is, the first slice).
  • Step 1306 The UE returns a configuration update complete message to the AMF.
  • Step 1307 The AMF deletes the identifier of the first slice in the rejected network slice (rejected S-NSSAI in current RA) stored in the context of the UE in the current registration area of the UE.
  • the AMF determines that the slice status of the first slice at the first position is updated to "available”, and uses the Rejected S-NSSAI in current RA stored in the UE context to trigger the AMF to notify the UE that the first slice is in the first position.
  • the location is available, so that the UE knows that the slice can be accessed in the first location, which helps to ensure that the UE can access the "available" slice in time, so that the UE can maintain correct and effective communication with the network side.
  • each network element described above includes hardware structures and/or software modules corresponding to each function.
  • the present invention 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-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered as going beyond the scope of the present invention.
  • the communication device 1400 may exist in the form of software or hardware.
  • the communication device 1400 may include: a processing unit 1402 and a communication unit 1403.
  • the communication unit 1403 may include a receiving unit and a sending unit.
  • the processing unit 1402 is used to control and manage the actions of the communication device 1400.
  • the communication unit 1403 is used to support communication between the communication device 1400 and other network entities.
  • the communication device 1400 may further include a storage unit 1401 for storing program codes and data of the communication device 1400.
  • the processing unit 1402 may be a processor or a controller, for example, a general-purpose central processing unit (central processing unit, CPU), a general-purpose processor, a digital signal processing (digital signal processing, DSP), and an application specific integrated circuit (application specific integrated circuit). circuits, ASIC), field programmable gate array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It can implement or execute various exemplary logical blocks, modules and circuits described in conjunction with the disclosure of this application.
  • the processor may also be a combination for realizing computing functions, for example, including a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the storage unit 1401 may be a memory.
  • the communication unit 1403 is an interface circuit of the device for receiving signals from other devices.
  • the communication unit 1403 is an interface circuit for the chip to receive signals from other chips or devices, or an interface circuit for the chip to send signals to other chips or devices.
  • the communication device 1400 may be the terminal device in any of the foregoing embodiments, and may also be a chip for the terminal device.
  • the processing unit 1402 may be, for example, a processor
  • the communication unit 1403 may be, for example, a transceiver.
  • the transceiver may include a radio frequency circuit
  • the storage unit may be, for example, a memory.
  • the processing unit 1402 may be a processor, for example, and the communication unit 1403 may be an input/output interface, a pin or a circuit, for example.
  • the processing unit 1402 can execute computer-executable instructions stored in the storage unit.
  • the storage unit is a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit located outside the chip in the terminal device.
  • the storage unit such as read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), etc.
  • the communication device 1400 is a terminal device, and the receiving unit is configured to receive the updated registration area of the terminal device when the first slice is unavailable in the first position and available in the second position.
  • the pre-update registration area includes the information of the first location and the information of the second location, and the allowed access network slice set of the terminal device includes the information of the first slice; the processing unit is configured to update the registration area of the terminal device.
  • the receiving unit is also used to receive the updated set of network slices allowed to be accessed by the terminal device; the processing unit is also used to update the set of allowed access network slices of the terminal device.
  • the current location of the terminal device is the first location
  • the updated set of allowed access network slices of the terminal device does not include the information of the first slice
  • the updated registration area of the terminal device The information of the first location is included, and the information of the second location is not included.
  • the sending unit is used to send a request message, the request message is used to request to establish or activate the session associated with the first slice; the receiving unit is also used to receive a request rejection message, the request rejection message includes Reason value, the reason value is used to indicate that the first slice is not available.
  • the receiving unit is further configured to receive information of the rejected network slice, where the information of the rejected network slice includes identification information of the first slice.
  • the current location of the terminal device is the second location
  • the updated registration area of the terminal device includes the information of the second location and does not include the information of the first location.
  • the receiving unit is further configured to receive instruction information, and the instruction information is used to instruct the terminal device to initiate a re-registration process.
  • the communication device 1500 may exist in the form of software or hardware.
  • the communication device 1500 may include a processing unit 1502 and a communication unit 1503.
  • the communication unit 1503 may include a receiving unit and a sending unit.
  • the processing unit 1502 is used to control and manage the actions of the communication device 1500.
  • the communication unit 1503 is used to support communication between the communication device 1500 and other network entities.
  • the communication device 1500 may further include a storage unit 1501 for storing program codes and data of the communication device 1500.
  • the processing unit 1502 may be a processor or a controller, for example, a CPU, a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules and circuits described in conjunction with the disclosure of this application.
  • the processor may also be a combination for realizing computing functions, for example, including a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the storage unit 1501 may be a memory.
  • the communication unit 1503 is an interface circuit of the device for receiving signals from other devices. For example, when the device is implemented as a chip, the communication unit 1503 is an interface circuit used by the chip to receive signals from other chips or devices, or an interface circuit used by the chip to send signals to other chips or devices.
  • the communication device 1500 may be the mobility management network element in any of the foregoing embodiments, and may also be a chip for the mobility management network element.
  • the processing unit 1502 may be, for example, a processor
  • the communication unit 1503 may be, for example, a transceiver.
  • the transceiver may include a radio frequency circuit
  • the storage unit may be, for example, a memory.
  • the processing unit 1502 may be a processor, for example, and the communication unit 1503 may be an input/output interface, a pin or a circuit, for example.
  • the processing unit 1502 can execute computer execution instructions stored in the storage unit.
  • the storage unit is a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit located in the mobility management network element.
  • the storage unit outside the chip such as ROM or other types of static storage devices that can store static information and instructions, RAM, etc.
  • the communication device 1500 is a mobility management network element
  • the processing unit is configured to determine that the first slice is unavailable at the first location and available at the second location, and to update the registration area of the terminal device, where
  • the pre-updated registration area of the terminal device includes the information of the first location and the information of the second location, and the set of allowed access network slices of the terminal device includes the information of the first slice;
  • the sending unit is used to send the terminal to the terminal device.
  • the updated registration area of the device is used to send the terminal to the terminal device.
  • the processing unit is also used to update the set of allowed access network slices of the terminal device; the sending unit is also used to send the updated set of allowed access network slices of the terminal device to the terminal device .
  • the current location of the terminal device is the first location
  • the updated set of allowed access network slices of the terminal device does not include the information of the first slice
  • the updated registration area of the terminal device The information of the first location is included, and the information of the second location is not included.
  • the processing unit is also used to trigger the release of the session associated with the first slice.
  • the receiving unit is used to receive a request message from the terminal device, the request message is used to request the establishment or activation of a session associated with the first slice; the sending unit is also used to send a request to the terminal device A rejection message, the request rejection message includes a reason value, and the reason value is used to indicate that the first slice is not available.
  • the sending unit is further configured to send information of the rejected network slice to the terminal device, and the information of the rejected network slice includes identification information of the first slice.
  • the processing unit is further configured to store the information of the rejected network slice in the context of the terminal device, the information of the rejected network slice includes the information of the first slice, and the information of the rejected network slice is used To indicate that the first slice is not available in the updated registration area of the terminal device.
  • the current location of the terminal device is the second location
  • the updated registration area of the terminal device includes the information of the second location and does not include the information of the first location.
  • the communication device may be the above-mentioned mobility management network element or terminal equipment.
  • the communication device 1600 includes a processor 1602, a communication interface 1603, and a memory 1601.
  • the communication device 1600 may further include a communication line 1604.
  • the communication interface 1603, the processor 1602, and the memory 1601 may be connected to each other through a communication line 1604;
  • the communication line 1604 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (extended industry standard architecture). , Referred to as EISA) bus and so on.
  • the communication line 1604 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used in FIG. 16, but it does not mean that there is only one bus or one type of bus.
  • the processor 1602 may be a CPU, a microprocessor, an ASIC, or one or more integrated circuits used to control the execution of the program of the present application.
  • Communication interface 1603 using any device such as a transceiver to communicate with other equipment or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), Wired access network, etc.
  • RAN radio access network
  • WLAN wireless local area networks
  • Wired access network etc.
  • the memory 1601 may be ROM or other types of static storage devices that can store static information and instructions, RAM or other types of dynamic storage devices that can store information and instructions, or it can be an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory).
  • read-only memory EEPROM
  • compact disc read-only memory, CD-ROM
  • optical disc storage including compact discs, laser discs, optical discs, digital universal discs, Blu-ray discs, etc.
  • magnetic disks A storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the memory can exist independently and is connected to the processor through a communication line 1604. The memory can also be integrated with the processor.
  • the memory 1601 is used to store computer-executable instructions for executing the solution of the present application, and the processor 1602 controls the execution.
  • the processor 1602 is configured to execute computer-executable instructions stored in the memory 1601, so as to implement the communication method provided in the foregoing embodiment of the present application.
  • the computer-executable instructions in the embodiments of the present application may also be referred to as application program code, which is not specifically limited in the embodiments of the present application.
  • At least one (piece, species) of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or Multiple.
  • Multiple refers to two or more, and other measure words are similar.
  • "a device” means to one or more such devices.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center.
  • 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 or a data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)), etc.
  • the various illustrative logic units and circuits described in the embodiments of this application can be implemented by general-purpose processors, digital signal processors, application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, Discrete gates or transistor logic, discrete hardware components, or any combination of the above are designed to implement or operate the described functions.
  • the general-purpose processor may be a microprocessor, and optionally, the general-purpose processor may also be any traditional processor, controller, microcontroller, or state machine.
  • the processor can also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration achieve.
  • the steps of the method or algorithm described in the embodiments of the present application can be directly embedded in hardware, a software unit executed by a processor, or a combination of the two.
  • the software unit can be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or any other storage medium in the field.
  • the storage medium may be connected to the processor, so that the processor can read information from the storage medium, and can store and write information to the storage medium.
  • the storage medium may also be integrated into the processor.
  • the processor and the storage medium can be arranged in the ASIC.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.

Landscapes

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

Abstract

本申请提供一种通信方法及装置。该方法包括：当终端设备的允许接入的网络切片集合内的第一切片在终端设备的注册区域内的某个位置(即第一位置)的状态从"可用"状态更新为"不可用"状态后，则网络侧可以更新终端设备的注册区域并通知终端设备更新注册区域，有助于保证终端设备在更新的注册区域内任一位置都可以访问"可用"切片，实现终端设备与网络侧保持正确、有效地通信，或者，理解为，有助于避免由于终端设备没有及时更新注册区域而造成的终端设备在第一位置发起与第一切片关联的业务请求而引起与网络侧的通信失败的问题。

Description

一种通信方法及装置
相关申请的交叉引用
本申请要求在2019年02月18日提交中国专利局、申请号为201910123531.2、申请名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及移动通信技术领域，尤其涉及一种通信方法及装置。
背景技术
当终端设备携带请求的网络切片集合并成功注册到网络之后，终端设备从网络侧获取允许接入的网络切片集合和注册区域，那么终端设备在注册区域内的任一跟踪区域可以接入到允许接入的网络切片集合中任一网络切片标识所指示的网络切片，并使用该网络切片提供的服务。
运营商可以在任意时刻决定是否可以改变某个跟踪区域部署的网络切片的状态。那么，一旦终端设备的允许接入的网络切片集合中的某个网络切片标识所指示的网络切片的状态发生了改变，可能会导致终端设备的注册区域内某些跟踪区域对应的网络切片不再可用，若核心网不及时通知终端设备，可能会出现终端设备在注册区域内某个网络切片不可用的跟踪区域请求访问该网络切片而导致失败，影响终端设备的业务体验，因此核心网如何判断是否需要通知终端设备目前还没有相应的机制予以解决。
发明内容
本申请提供一种通信方法及装置，用以在网络切片的状态在某个跟踪区域发生了改变后，及时通知终端设备，进而实现终端设备与网络侧保持正确、有效地通信。
第一方面，本申请提供一种通信方法，包括：第一切片在第一位置为不可用、在第二位置可用，则终端设备接收终端设备的更新后的注册区域，终端设备的更新前的注册区域包括第一位置的信息和第二位置的信息，终端设备的允许接入的网络切片集合包括第一切片的信息；终端设备更新终端设备的注册区域。基于该方案，当终端设备的允许接入的网络切片集合内的第一切片在终端设备的注册区域内的某个位置(即第一位置)的状态从“可用”状态更新为“不可用”状态后，则网络侧可以更新终端设备的注册区域并通知终端设备更新注册区域，有助于保证终端设备在更新的注册区域内任一位置都可以访问“可用”切片，实现终端设备与网络侧保持正确、有效地通信，或者，理解为，有助于避免由于终端设备没有及时更新注册区域而造成的终端设备在第一位置发起与第一切片关联的业务请求而引起与网络侧的通信失败的问题。
在一种可能的实现方法中，终端设备接收终端设备的更新后的允许接入的网络切片集合；终端设备更新终端设备的允许接入的网络切片集合。
在一种可能的实现方法中，终端设备的当前位置为第一位置，则终端设备的更新后的允许接入的网络切片集合不包括第一切片的信息，终端设备的更新后的注册区域包括第一位置的信息、且不包括第二位置的信息。
在一种可能的实现方法中，终端设备发送请求消息，请求消息用于请求建立或激活与第一切片关联的会话；终端设备接收请求拒绝消息，请求拒绝消息包括原因值，原因值用于指示第一切片不可用。
在一种可能的实现方法中，终端设备接收拒绝的网络切片的信息，拒绝的网络切片的信息包括第一切片的标识信息。
在一种可能的实现方法中，终端设备的当前位置为第二位置，则终端设备的更新后的注册区域包括第二位置的信息、且不包括第一位置的信息。
在一种可能的实现方法中，终端设备接收指示信息，指示信息用于指示终端设备发起重注册流程。
第二方面，本申请提供一种通信方法，包括：移动性管理网元确定第一切片在第一位置为不可用、在第二位置可用，移动性管理网元更新终端设备的注册区域；其中，终端设备的更新前的注册区域包括第一位置的信息和第二位置的信息，终端设备的允许接入的网络切片集合包括第一切片的信息；移动性管理网元向终端设备发送终端设备的更新后的注册区域。基于该方案，当终端设备的允许接入的网络切片集合内的第一切片在终端设备的注册区域内的某个位置(即第一位置)的状态从“可用”状态更新为“不可用”状态后，则网络侧可以更新终端设备的注册区域并通知终端设备更新注册区域，有助于保证终端设备在更新的注册区域内任一位置都可以访问“可用”切片，实现终端设备与网络侧保持正确、有效地通信，或者，理解为，有助于避免由于终端设备没有及时更新注册区域而造成的终端设备在第一位置发起与第一切片关联的业务请求而引起与网络侧的通信失败的问题。
在一种可能的实现方法中，移动性管理网元更新终端设备的允许接入的网络切片集合；移动性管理网元向终端设备发送终端设备的更新后的允许接入的网络切片集合。
在一种可能的实现方法中，终端设备的当前位置为第一位置，则终端设备的更新后的允许接入的网络切片集合不包括第一切片的信息，终端设备的更新后的注册区域包括第一位置的信息、且不包括第二位置的信息。
在一种可能的实现方法中，移动性管理网元触发释放与第一切片关联的会话。
在一种可能的实现方法中，移动性管理网元接收来自终端设备的请求消息，请求消息用于请求建立或激活与第一切片关联的会话；移动性管理网元向终端设备发送请求拒绝消息，请求拒绝消息包括原因值，原因值用于指示第一切片不可用。
在一种可能的实现方法中，移动性管理网元向终端设备发送拒绝的网络切片的信息，拒绝的网络切片的信息包括第一切片的标识信息。
在一种可能的实现方法中，移动性管理网元在终端设备的上下文中存储拒绝的网络切片的信息，拒绝的网络切片的信息包括第一切片的信息，拒绝的网络切片的信息用于指示第一切片在终端设备的更新后的注册区域内不可用。
在一种可能的实现方法中，终端设备的当前位置为第二位置，则终端设备的更新后的注册区域包括第二位置的信息、且不包括第一位置的信息。
第三方面，本申请提供一种通信装置，该装置具有实现上述任意方面或任意方面中的 实现方法的通信方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第四方面，本申请提供一种通信装置，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行如上述任意方面或任意方面中的实现方法的通信方法。
第五方面，本申请提供一种通信装置，包括：包括用于执行以上任意方面各个步骤的单元或手段(means)。
第六方面，本申请提供一种通信装置，包括处理器和接口电路，所述处理器用于通过接口电路与其它装置通信，并执行以上任意方面提供的任意方法。该处理器包括一个或多个。
第七方面，本申请提供一种通信装置，包括处理器，用于与存储器相连，用于调用所述存储器中存储的程序，以执行上述任意方面的任意实现方式中的方法。该存储器可以位于该装置之内，也可以位于该装置之外。且该处理器包括一个或多个。
第八方面，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得处理器执行上述任意方面所述的方法。
第九方面，本申请还提供一种包括指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述任意方面所述的方法。
第十方面，本申请还提供一种芯片系统，包括：处理器，用于执行上述各方面所述的方法。
第十一方面，本申请还提供一种通信系统，包括用于执行上述第一方面或第一方面任一实现方法的终端设备，和，用于执行上述第二方面或第二方面任一实现方法的移动性管理网元。
附图说明
图1为5G网络架构示意图；
图2为本申请提供的一种切片的服务区域示意图；
图3为本申请提供的一种通信方法流程示意图；
图4为本申请提供的又一种通信方法流程示意图；
图5为本申请提供的又一种通信方法流程示意图；
图6为本申请提供的又一种通信方法流程示意图；
图7为本申请提供的又一种通信方法流程示意图；
图8为本申请提供的又一种通信方法流程示意图；
图9为本申请提供的又一种通信方法流程示意图；
图10为本申请提供的又一种通信方法流程示意图；
图11为本申请提供的又一种通信方法流程示意图；
图12为本申请提供的又一种通信方法流程示意图；
图13为本申请提供的又一种通信方法流程示意图；
图14为本申请提供的一种通信装置示意图；
图15为本申请提供的又一种通信装置示意图；
图16为本申请提供的又一种通信装置示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述。方法实施例中的具体操作方法也可以应用于装置实施例或系统实施例中。其中，在本申请的描述中，除非另有说明，“多个”的含义是两个或两个以上。
如图1所示，为第五代(the 5th generation，5G)网络架构示意图。图中示出了5G架构中的部分网元。其中，用户面功能(user plane function，UPF)网元，包括数据包路由和传输、包检测、业务用量上报、服务质量(Quality of Service,QoS)处理、合法监听、上行包检测、下行数据包存储等用户面相关的功能。
接入与移动性管理功能(access and mobility management function，AMF)网元，负责用户的移动性管理，包括移动状态管理，分配用户临时身份标识，认证和授权用户。
会话管理功能(session management function，SMF)网元，包括会话管理(如会话建立、修改和释放，包含UPF和AN之间的隧道维护)、UPF网元的选择和控制、业务和会话连续性(Service and Session Continuity，SSC)模式选择、漫游等会话相关的功能。
网络切片选择功能(Network Slice Selection Function，NSSF)网元，负责确定网络切片实例，选择AMF网元等。
本申请中的移动性管理网元可以是图1所示的AMF网元，也可以是未来通信系统中的具有上述AMF网元的功能的网元。本申请中的用户面网元可以是图1所示的UPF网元，也可以是未来通信系统中的具有上述UPF网元的功能的网元。本申请中的会话管理网元可以是图1所示的SMF网元，也可以是未来通信系统中的具有上述SMF网元的功能的网元。本申请中的切片选择网元可以是图1所示的NSSF网元，也可以是未来通信系统中的具有上述NSSF网元的功能的网元。
本申请中的接入网设备(也称为无线接入网(radio access network，RAN)设备)，是一种为终端提供无线通信功能的设备。接入网设备包括但不限于：5G中的下一代基站(g nodeB，gNB)、演进型节点B(evolved node B，eNB)、无线网络控制器(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)、传输点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心等。
本申请的终端设备(也可以称为用户设备(user equipment，UE))是一种具有无线收发功能的设备，可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。所述终端可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。
为方便说明，本申请后续，以移动性管理网元为AMF网元，切片选择网元为NSSF网元，会话管理网元为SMF网元，用户面网元为UPF网元为例进行说明。进一步地，将AMF网元简称为AMF，NSSF网元简称为NSSF，SMF网元简称为SMF，UPF网元简称 为UPF，终端设备简称为UE，接入网设备简称为RAN。即本申请后续所描述的AMF均可替换为移动性管理网元，NSSF均可替换为切片选择网元，SMF均可替换为会话管理网元，SMF均可替换为会话管理网元，UPF均可替换为用户面网元，RAN均可替换为接入网设备，UE均可替换为终端设备。
需要说明的是，本申请中，“网络切片”和“切片”指的是同一内容，在不同的地方使用其中一种描述，二者可以互换。
目前，多种多样的场景对第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)生态系统提出了不同的需求，如计费、策略、安全、移动性等需求。3GPP强调了网络切片之间不相互影响，例如突发的大量的抄表业务不应该影响正常的移动宽带业务。为了满足多样性需求和切片间的隔离，需要业务间相对独立的管理和运维，并提供量身定做的业务功能和分析能力。不同类型业务的实例部署在不同的网络切片上，相同业务类型的不同实例也可部署在不同的网络切片上。
当核心网部署了网络切片，用户初始附着(或称为注册)到网络时，会触发网络切片的选择过程。切片的选择过程取决于用户的签约数据，本地配置信息，漫游协议，运营商的策略等等。在网络切片的选择过程中，需要综合考虑以上参数，才能为UE选择最佳的切片类型。
当UE需要接入到某个网络切片时，UE可以提供请求的网络切片给核心网，用于核心网为UE选择网络切片实例。其中，UE请求的网络切片，可以用请求的网络切片集合来表示，或者也可以表示为请求的网络切片选择辅助信息(requested network slice selection assistance information，requested NSSAI)。requested NSSAI是由一个或多个单个网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)构成，每个S-NSSAI用于标识一个网络切片类型，也可以理解为，S-NSSAI用于标识网络切片，或者可以理解为S-NSSAI是网络切片的标识信息。
UE注册到网络之后，核心网网元(如AMF或NSSF)根据UE的签约数据、UE的requested NSSAI、漫游协议以及本地配置等信息综合判断，为UE选择允许接入的网络切片集合。其中，允许接入的网络切片集合可以用允许的(allowed)NSSAI来表示，allowed NSSAI包含的S-NSSAI均为当前网络有效的S-NSSAI。
一个AMF集合(AMF set)内的AMF可以向NSSF提供该AMF在某个跟踪区域(Tracking Area，TA)下支持的切片能力，而且后续如果该TA对应的切片发生了改变，还可以向NSSF更新该AMF网元在某个TA下支持的切片能力。NSSF可以根据运营商的策略或者在某种条件下(例如当网络切片发生拥塞时)，通知AMF set中的AMF：某个TA下部署的切片状态是否发生了改变。
例如，当网络切片拥塞时，NSSF可以通知AMF：某个TA下部署的切片禁止使用(也可以理解为该TA为该切片的受限制区域)，即该切片从“可用”状态更新为“不可用”状态，这样当位于该TA的UE请求接入该切片时，由于AMF从NSSF获知该切片在该TA下“不可用”，那么AMF会拒绝该UE接入该切片。
切片可用状态(available状态)指的是该切片可以访问或者可以接入；切片不可用状态(restriction状态)指的是该切片无法访问或者无法接入。其中，切片可以从“可用”状态更新为“不可用”状态，也可以从“不可用”状态更新为“可用”状态。
如图2所示，为本申请提供的一种切片的服务区域示意图。假设切片A(slice-A，用 S-NSSAI-A标识)和切片B(slice-B，用S-NSSAI-B标识)的服务区域均为：TA-1,TA-2，TA-3，……，TA-10(图中进示例性地仅画出了TA-1，TA-2和TA-3)，且在这10个TA内均为“可用”状态。某个时刻，由于拥塞等原因，运营商决定将切片A的服务区域TA-3从“可用”更新为“不可用”状态，那么在位置TA-3，不允许UE接入切片A使用切片A提供的服务。此时，切片A在TA-1,TA-2，TA-4，……，TA-10为“可用”状态，在TA-3为“不可用”状态。也可以理解为，TA-1,TA-2，TA-4，……，TA-10为切片A的可用区域，TA-3为切片A的不可用区域(或受限制区域)。针对上述切片B，其可用区域仍保持为：TA-1,TA-2，TA-3，……，TA-10，或者理解为，切片B在TA-1,TA-2，TA-3，……，TA-10保持为“可用”状态。
为解决背景技术提到的问题，本申请提供多种通信方法，基于该方法，当UE的allowed NSSAI中的某个S-NSSAI标识的切片的状态发生了改变，则核心网可以判断是否需要通知UE，以及定义了需要向UE通知哪些信息，以便于实现UE与核心网之间的正确、有效地通信。
本申请针对的应用场景是：UE的allowed NSSAI中的某个S-NSSAI标识的切片(本申请称为第一切片)在该UE的注册区域(Registration Area，RA)内的某一个或多个TA内的状态发生改变(可以是从“可用”状态更新为“不可用”状态，也可以是从“不可用”状态更新为“可用”状态)。
为方便说明，本申请将结合图2所示的具体示例进行说明，并且，假设UE的allowed NSSAI包括：S-NSSAI-A和S-NSSAI-B，其中，S-NSSAI-A为切片A的标识，S-NSSAI-B为切片B的标识；UE的注册区域包括TAI-1、TAI-2和TAI-3，其中，TAI指的是跟踪区标识(Tracking Area Identity)，TAI-1用于标识TA-1，TAI-2用于标识TA-2，TAI-3用于标识TA-3。
在第一种情形中，第一切片(以第一切片为切片A为例)在TA-3的状态从“可用”状态更新为“不可用”状态，且第一切片在TA-1和TA-2的状态保持为“可用”状态。
在第二种情形中，在上述第一种情形发生之后，第一切片(以第一切片为切片A为例)在TA-3的状态从“不可用”状态更新为“可用”状态，且第一切片在TA-1和TA-2的状态保持为“可用”状态。
需要说明的是，本申请仅以图2为例进行示例说明，但不限于图2所示的该具体示例。
基于图1所示的网络架构，如图3所示，本申请提供一种通信方法流程示意图，该方法用于当UE的allowed NSSAI的某一切片(称为第一切片)在UE的注册区域的某个TA的状态从“可用”状态更新为“不可用”状态。即该方法可用于前述的第一种情形。
该方法包括以下步骤：
步骤301，AMF确定第一切片在第一位置为不可用、在第二位置可用；其中，UE的注册区域包括第一位置的信息和第二位置的信息，UE的允许接入的网络切片集合包括第一切片的信息。
这里的第一位置、第二位置分别可以是UE的注册区域内的TA，以图2为例，则第一位置可以是TA-3，第二位置可以是TA-1和/或TA-2，第一位置的信息可以是TAI-3，第二位置的信息可以是TAI-1和/或TAI-2。
UE的允许接入的网络切片集合即为UE的allowed NSSAI，以图2为例，这里的第一切片例如可以是切片A。
其中，AMF确定第一切片在第一位置为不可用，指的是AMF确定第一切片在第一位置的状态为“不可用”；AMF确定第一切片在第二位置为可用，指的是AMF确定第一切片在第二位置的状态为“可用”。
本申请中，第二位置指的是UE的注册区域内的除第一位置之外的任一或任多个位置。
步骤302，AMF更新UE的注册区域。
比如，AMF可以根据UE的当前位置更新UE的注册区域。当然，AMF也可以根据UE的当前位置以及结合其他信息来更新UE的注册区域。这里的UE的其他信息例如包括UE的状态(连接态、空闲态等)。
步骤303，AMF向UE发送UE的更新后的注册区域。
步骤304，UE更新UE的注册区域。
即，UE将接收到的UE的更新后的注册区域，更新为UE的注册区域。
基于上述方案，当UE的allowed NSSAI内的第一切片在UE的注册区域内的某个TA(即第一位置)的状态从“可用”状态更新为“不可用”状态后，则网络侧(如AMF)可以更新UE的注册区域并通知UE更新注册区域，有助于保证UE在更新的注册区域内任一位置都可以访问“可用”切片，实现UE与网络侧保持正确、有效地通信，或者，理解为，有助于避免由于UE没有及时更新注册区域而造成的UE在第一位置发起与第一切片关联的业务请求而引起与网络侧的通信失败的问题。
可选的，在上述步骤303之前，AMF可以向UE发送指示信息，指示信息用于指示UE发起重注册流程，然后AMF在UE发起的重注册流程中，执行上述步骤303。
下面结合图2的示例，分两种情形，分别对图3的实施例进行进一步解释说明，其中：
UE的allowed NSSAI＝{S-NSSAI-A，S-NSSAI-B}；
UE的RA＝{TAI-1，TAI-2，TAI-3}；
第一切片：切片A；
第一位置：TA-3；
第二位置：TA-1和/或TA-2；
UE的当前位置：第一位置或第二位置；
第一切片在TA-3的状态由“可用”更新为“不可用”。
情形一、UE的当前位置为第一位置
该情形中，第一切片在UE在当前位置为不可用，则上述步骤302中，AMF更新UE的注册区域的具体方法，例如可以是：UE的更新后的注册区域包括第一位置的信息、且不包括第二位置的信息。以上述示例为例，则UE的更新后的注册区域(new RA)为：TAI-3。因此，上述步骤304中，UE更新UE的注册区域，具体为：UE将注册区域更新为：TAI-3。
在该情形一下，进一步的，还可以执行以下步骤305-步骤307。
步骤305，AMF更新UE的允许接入的网络切片集合。
比如，AMF可以根据UE的当前位置更新UE的允许接入的网络切片集合。当然，AMF也可以根据UE的当前位置以及结合其他信息来更新UE的允许接入的网络切片集合。这里的UE的其他信息例如包括UE的状态(连接态、空闲态等)。
步骤306，AMF向UE发送UE的更新后的允许接入的网络切片集合。
步骤307，UE更新UE的允许接入的网络切片集合。
其中，上述步骤305中，AMF更新UE的允许接入的网络切片集合的具体方法，例如 可以是：UE的更新后的允许接入的网络切片集合不包括第一切片的信息。以上述示例为例，则UE的更新后的允许接入的网络切片集合(new allowed NSSAI)为：S-NSSAI-B。因此，上述步骤307中，UE更新UE的允许接入的网络切片集合，具体为：UE将允许接入的网络切片集合更新为：S-NSSAI-B。
因此，该情形一中，针对上述示例，则：
UE的更新后的注册区域(new RA)为：TAI-3；
UE的更新后的允许接入的网络切片集合(new allowed NSSAI)为：S-NSSAI-B。
需要说明的是，上述步骤305-步骤307，与上述步骤302-步骤304之间没有严格的执行顺序。比如，可以先执行步骤302-步骤304，再执行步骤305-步骤307；再比如，可以先执行步骤305-步骤307，再执行步骤302-步骤304；再比如，可以先并行执行步骤302和步骤305，然后并行执行步骤303和步骤306，然后并行执行步骤304和步骤307，等等。
在一种实现方法中，若第一切片与某个或某些已经建立的会话关联，则AMF还可以触发释放与该第一切片关联的会话。
在一种实现方法中，若第一切片与某个或某些UE请求建立或激活的会话关联，则AMF还可以拒绝建立或激活与该第一切片关联的会话。比如，图3所示的方法可以在UE的会话建立流程中执行，则在该会话建立流程中，还可以执行以下步骤：
步骤A，AMF接收来自UE的请求消息，请求消息用于请求建立或激活与第一切片关联的会话。
步骤B，AMF向UE发送请求拒绝消息，请求拒绝消息包括原因值，原因值用于指示第一切片不可用。
可选的，该请求拒绝消息也可以不包括原因值，即仅通知UE拒绝建立或激活会话，而不通知拒绝的原因。
在一种实现方法中，AMF还可以向UE发送拒绝的网络切片的信息，拒绝的网络切片的信息包括第一切片的标识信息。即AMF将拒绝的网络切片的信息通知给UE，例如可以通过上述步骤303、或步骤306、或通过一个单独的步骤，向UE发送拒绝的网络切片的信息。
在一种实现方法中，AMF可以在UE的上下文中存储拒绝的网络切片的信息，拒绝的网络切片的信息包括第一切片的信息，拒绝的网络切片的信息用于指示第一切片在UE的更新后的注册区域内不可用。
情形二、UE的当前位置为第二位置
该情形中，第一切片在UE在当前位置为可用，则上述步骤302中，AMF更新UE的注册区域的具体方法，例如可以是：UE的更新后的注册区域包括第二位置的信息、且不包括第一位置的信息。以上述示例为例，则UE的更新后的注册区域为：TAI-1、TAI-2。因此，上述步骤304中，UE更新UE的注册区域，具体为：UE将注册区域更新为：TAI-1、TAI-2。
下面结合不同的具体应用场景，对图3所述的实施例的应用进行介绍说明。
应用场景1、UE发起会话建立流程或UE已经完成会话建立
应用场景1.1、UE请求建立会话，该会话与上述第一切片关联，该第一切片在第一位置不可用、在第二位置可用，且UE的当前位置为第一位置(即上述情形一)
如图4所示，为针对该应用场景1.1的一种通信方法流程示意图。该方法包括以下步 骤：
步骤400，AMF向NSSF发送TAI，以及该AMF在该TAI标识的TA下支持的切片类型(用S-NSSAI标识)。
比如，AMF可以调用NSSF的服务化操作Nnssf_NSSAIAvailability_Update，携带TAI，以及该AMF在该TAI标识的TA下支持的切片类型(用S-NSSAI标识)。
步骤401，UE发起注册流程，携带requested NSSAI，AMF接受该UE的注册请求，并给UE分配注册区域(RA)，AMF向UE返回allowed NSSAI和RA。
其中，RA包含由多个TAI构成的TA list，且allowed NSSAI包含的任一S-NSSAI在该RA内任一TA都可以访问，或者可以理解为，allowed NSSAI包含的任一S-NSSAI在该RA内任一TA都可以UE提供服务。
步骤402，某一时刻，NSSF决定改变第一切片在第一位置的状态(比如，由于第一切片的拥塞情况超过了阈值)，将第一切片从“可用”状态更新为“不可用”。
这里的第一切片、第一位置的含义，可参考前述实施例的描述，这里不再赘述。
步骤403，NSSF通知AMF：第一切片在第一位置更新为不可用。
例如，NSSF可以调用Nnssf_NSSAIAvailability_Notify服务化操作，通知AMF：第一切片在第一位置更新为不可用。
当然，若有多个切片分别在某个或某些位置的状态更新为不可用，则NSSF可以向AMF发送多个S-NSSAI及分别对应的不可用的位置列表。比如，S-NSSAI-A在TA-11，TA-12更新为不可用，S-NSSAI-B在TA-13，TA-14更新为不可用，则NSSF可以向AMF发送：(S-NSSAI-A，(TA-11，TA-12))、(S-NSSAI-B，(TA-13，TA-14))。
步骤404，UE的当前位置为第一位置，UE向AMF发送非接入层(non access stratum，NAS)消息，NAS消息中可以携带会话建立请求、会话标识(协议数据单元(protocol data unit，PDU)session ID)以及该会话对应的S-NSSAI和数据网名称(Data Network Name，DNN)。
这里，NAS消息中的S-NSSAI标识的切片包括上述第一切片。
步骤405，AMF收到该UE的会话建立请求之后，确定UE请求的S-NSSAI标识的第一切片在UE的当前位置不可用。
即AMF确定UE请求建立的会话关联的第一切片，在UE的当前位置(即第一位置)不可用。
步骤406，AMF拒绝该UE发送的NAS消息，携带原因值：UE请求的S-NSSAI在UE的当前位置不可用。
即，AMF拒绝了UE的会话建立请求。
步骤407，由于会话建立失败，AMF触发更新该UE的allowed NSSAI和RA。
步骤408，AMF向UE发送配置更新消息，携带new allowed NSSAI和new RA，其中:
new allowed NSSAI不包含不可用的S-NSSAI，new RA包括第一位置的信息。其中，new allowed NSSAI中的切片的标识对应的切片在new RA可用。
比如，基于图2示例，则old RA＝{TA-1，TA-2，TA-3}，new RA＝{TA-3}。old allowed NSSAI＝{S-NSSAI-A,S-NSSAI-B}，new allowed NSSAI＝{S-NSSAI-B}。具体更新的说明，可以参前述图3实施例的情形一中的相关描述，这里不再赘述。
可选地，配置更新消息中还可以携带在UE的当前注册区域中拒绝的网络切片(rejected  S-NSSAI in current RA)，用于通知UE：rejected S-NSSAI在new RA不可用，即rejected S-NSSAI包括步骤404中UE请求的会话对应的S-NSSAI。
可选地，作为一个可替代的实现方式，上述步骤408中的配置更新消息不携带new allowed NSSAI和new RA，而携带重注册指示信息(或称为指示信息)，用于指示UE发起注册流程。
步骤409，UE向AMF返回配置更新完成消息。
步骤410，若UE在步骤408收到重注册指示信息，则UE在步骤409之后发起注册流程，UE发送注册请求消息，AMF在向UE发送的注册接受消息中携带new allowed NSSAI和new RA。
其中，new allowed NSSAI不包含不可用的S-NSSAI，new RA包括第一位置的信息。其中，new allowed NSSAI中的切片的标识对应的切片在new RA可用。
比如，基于图2示例，则old RA＝{TA-1，TA-2，TA-3}，new RA＝{TA-3}。old allowed NSSAI＝{S-NSSAI-A,S-NSSAI-B}，new allowed NSSAI＝{S-NSSAI-B}。具体更新的说明，可以参前述图3实施例的情形一中的相关描述，这里不再赘述。
可选地，注册接受消息还可以携带在UE的当前注册区域中拒绝的网络切片(rejected S-NSSAI in current RA)，用于通知UE：rejected S-NSSAI在new RA不可用，即rejected S-NSSAI包括步骤404中UE请求的建立会话对应的S-NSSAI。
步骤411，AMF在UE的上下文中存储rejected S-NSSAI in current RA，用来记录曾经向哪些UE发送过rejected S-NSSAI。
该步骤411为可选步骤。
基于上述方案，当UE请求建立的会话关联的切片在UE的当前位置不可用时，则网络侧拒绝UE建立该会话，使得UE获知在当前位置下无法接入该切片，同时更新UE的注册区域，有助于保证UE在更新的注册区域内任一位置都可以访问“可用”切片，实现UE与网络侧保持正确、有效地通信。
应用场景1.2、UE请求建立会话，该会话与上述第一切片关联，该第一切片在第一位置不可用、在第二位置可用，且UE的当前位置为第二位置(即上述情形二)
如图5所示，为针对该应用场景1.2的一种通信方法流程示意图。该方法包括以下步骤：
步骤500-步骤503，同实施例4中的步骤400-步骤403，可参考前述描述，这里不再赘述。
步骤504，UE的当前位置为第二位置，UE向AMF发送NAS消息，NAS消息中可以携带会话建立请求、会话标识(PDU session ID)以及该会话对应的S-NSSAI和DNN。
这里，NAS消息中的S-NSSAI标识的切片为上述第一切片。
步骤505，AMF收到该UE的会话建立请求之后，确定UE请求的S-NSSAI标识的第一切片在UE的当前位置可用，但UE的注册区域包括了UE请求的S-NSSAI不可用的TA(即第一位置)。
即AMF确定UE请求建立的会话关联的第一切片，在UE的当前位置(即第二位置)可用。并且，第一切片在UE的注册区域的某个TAI标识的TA(即第一位置)内不可用。
步骤506，继续会话建立流程的其他步骤，比如包含AMF根据S-NSSAI和DNN选择SMF，SMF根据S-NSSAI和DNN选择UPF等等，直到该会话成功建立。
步骤507，由于UE的注册区域包含UE请求的S-NSSAI不可用的TA，则AMF决定触发更新该UE的注册区域，AMF向UE发送配置更新消息，携带new RA。
其中,new RA＝old RA删除切片状态改变的TA,即new RA不包括切片状态改变的TA，其中AMF在步骤503获取了状态改变的TA。比如，基于图2示例，则old RA＝{TA-1，TA-2，TA-3}，new RA＝{TA-1，TA-2}。
可选地，作为一个可替代的实现方式，上述步骤507中的配置更新消息不携带new RA，而携带重注册指示信息，用于指示UE发起注册流程。
步骤508，UE向AMF返回配置更新完成消息。
步骤509，若UE在步骤507收到重注册指示信息，则UE在步骤508之后发起注册流程，UE发送注册请求消息，AMF在向UE发送的注册接受消息中携带new RA。
其中，new RA＝old RA删除切片状态改变的TA,即new RA不包括切片状态改变的TA，其中AMF在步骤503获取了状态改变的TA。比如，基于图2示例，则old RA＝{TA-1，TA-2，TA-3}，new RA＝{TA-1，TA-2}。
基于上述方案，当UE请求建立的会话关联的切片在UE的当前位置可用时，则网络侧接受UE建立该会话，使得UE获知在当前位置下可以接入该切片，同时更新UE的注册区域，有助于保证UE在更新的注册区域内任一位置都可以访问“可用”切片，实现UE与网络侧保持正确、有效地通信。
应用场景1.3、UE请求建立的会话已经建立完成，该会话与上述第一切片关联，该第一切片在第一位置不可用
如图6所示，为针对该应用场景1.3的一种通信方法流程示意图。该方法包括以下步骤：
步骤600，同实施例4的步骤400，可参考前述描述。
步骤601a，UE发起注册流程，携带requested NSSAI，AMF接受该UE的注册请求，并给UE分配注册区域，AMF向UE返回allowed NSSAI和注册区域。
步骤601b，UE发起会话建立流程，请求建立与S-NSSAI对应的会话，该会话建立成功，AMF上保存会话标识(PDU session ID)、S-NSSAI和SMF ID的关联关系。
这里的S-NSSAI标识的切片为第一切片。
步骤602-步骤603，同实施例4的步骤402-步骤403，可参考前述描述。
步骤604，如果UE处于连接状态、UE的当前位置为第一位置，且AMF确定第一切片在UE的当前位置不可用。如果UE处于空闲状态，此时，AMF并不确定UE当前所在的具体位置，在这种情况下，AMF可以等待UE从空闲状态更新为连接状态之后(例如UE发起业务请求等信令)，AMF获取UE的当前位置(为第一位置)，且确定第一切片在UE的当前位置不可用。
步骤605，AMF决定触发释放在当前位置下，不可用的第一切片对应的会话，AMF根据上下文判断出该会话对应的SMF，然后向SMF发送会话释放请求，请求释放该会话。
比如，AMF可以调用Nsmf_PDUSession_UpdateSMContext，携带PDU session release request(包含原因值：该会话对应的S-NSSAI在UE的当前位置不可用)。
步骤606，由于UE当前位于第一切片不可用的区域，AMF触发更新该UE的allowed NSSAI和RA，AMF向UE发送配置更新消息，携带new allowed NSSAI和new RA，其中:
new allowed NSSAI不包含不可用的S-NSSAI；new RA包括第一位置的信息。其中，new  allowed NSSAI中的切片的标识对应的切片在new RA可用。
具体更新的说明，可以参前述图3实施例的情形一中的相关描述，这里不再赘述。
可选地，配置更新消息中还可以携带rejected S-NSSAI in current RA，用于通知UE：rejected S-NSSAI在new RA不可用，即rejected S-NSSAI包括步骤601b中UE请求建立会话对应的S-NSSAI。
可选地，作为一个可替代的实现方式，上述步骤606中的配置更新消息不携带new allowed NSSAI和new RA，而携带重注册指示信息，用于指示UE发起注册流程。
步骤607，UE向AMF返回配置更新完成消息。
步骤608，若UE在步骤606收到重注册指示信息，则UE在步骤607之后发起注册流程，UE发送注册请求消息，AMF在向UE发送的注册接受消息中携带new allowed NSSAI和new RA。
其中，new allowed NSSAI不包含不可用的S-NSSAI，new RA包括第一位置的信息。其中，new allowed NSSAI中的切片的标识对应的切片在new RA可用。
具体更新的说明，可以参前述图3实施例的情形一中的相关描述，这里不再赘述。
可选地，注册接受消息还可以携带在UE的当前注册区域中拒绝的网络切片(rejected S-NSSAI in current RA)，用于通知UE：rejected S-NSSAI在new RA不可用，即rejected S-NSSAI包括步骤601b中UE请求建立会话对应的S-NSSAI。
步骤609，AMF在UE的上下文中存储UE的当前注册区域中拒绝的网络切片(rejected S-NSSAI in current RA)，用来记录曾经向哪些UE发送过rejected S-NSSAI。
该步骤609为可选步骤。
基于上述方案，当UE请求建立完成的会话关联的切片在UE的当前位置不可用时，则网络侧可以释放该已经建立的会话，使得UE获知在当前位置下无法接入该切片，有助于保证UE在更新的注册区域内任一位置都可以访问“可用”切片，实现UE与网络侧保持正确、有效地通信。
应用场景2、UE的切换流程
以图2所示的示例为例，由于拥塞等原因，NSSF决定将切片A(即第一切片)的服务区域TA-3(即第一位置)从“可用”更新为“不可用”状态。
T1时刻，UE在第一切片可用的区域(如TA-2)发起建立第一切片对应的会话，即在第一切片中建立了PDU session。
T2时刻，处于连接态的UE从TA-2移动到TA-3(即第一位置)，UE通过切换流程，从源侧RAN(Source-RAN，S-RAN)切换到目标侧RAN(Target-RAN，T-RAN)，其中，源侧RAN位于第一切片可用的区域，目标侧RAN位于第一切片不可用的区域。
UE在切换至目标侧RAN前，UE建立的会话对应的第一切片在源侧RAN所在的TA可用，UE在切换至目标侧RAN后，由于第一切片在目标侧RAN所在的TA不可用，因此网络侧将会释放该会话。或者可以理解为，源侧RAN位于UE的注册区域的某个或某些TA内，且第一切片在源侧RAN可用，目标侧RAN位于UE的注册区域的某个或某些TA内，且第一切片在目标侧RAN不可用，即UE切换至目标侧RAN后，目标侧RAN所在的TA内不支持该第一切片。
如图7所示，为针对该应用场景2的一种通信方法流程示意图。该方法包括以下步骤：
步骤700-步骤703，同实施例4的步骤400-步骤403，可参考前述描述。
步骤704a，源侧RAN发起了Xn接口的切换，根据UE的测量报告确定目标侧RAN。
步骤704b，目标侧RAN向AMF发送路径切换请求(Path Switch Request)消息，携带要切换的会话列表(List of PDU Sessions To Be Switched)以及目标侧RAN所在的TA对应的TAI。
步骤705，AMF根据要切换的会话列表中包含的PDU session IDs，以及上下文中存储的每一个PDU session ID对应的S-NSSAI，确定会话列表中包含的PDU session关联的第一切片第一位置不可用。
比如，要切换的会话列表包含的信息为表1：
表1
List of PDU Sessions To Be Switched
PDU session ID-1
PDU session ID-2
AMF存储的每一个PDU session ID对应的S-NSSAI为表2：
表2
Figure PCTCN2019117588-appb-000001
以图2所示的示例为例，第一切片对应S-NSSAI-A，且S-NSSAI-A对应的第一切片在第一位置不可用。
这里的第一位置，指的是目标侧RAN所在的TA，且UE的注册区域包括该TA对应的TAI。比如，以图2所示的示例为例，目标侧RAN所在的TA为TA-3，UE的注册区域包括TA-3。
步骤706a，AMF决定触发释放在第一位置下，不可用的第一切片对应的会话。
以表2所示的示例为例，在第一位置下，不可用的第一切片对应的会话为PDU session ID-1。
步骤706b，AMF根据上下文判断出该会话对应的SMF，然后向SMF发送会话释放请求，请求释放该会话。
比如，AMF可以调用Nsmf_PDUSession_UpdateSMContext，携带PDU session release request(包含原因值：该会话对应的S-NSSAI在目标侧RAN不可用)。
步骤706c，AMF向目标侧RAN发送路径切换请求确认(Path Switch Request ACK)消息，携带new allowed NSSAI。
可选的，路径切换请求确认消息还携带切换失败的PDU session列表。
其中，new allowed NSSAI不包含在第一位置不可用的S-NSSAI，比如，基于图2所示的实施例，则new allowed NSSAI＝{S-NSSAI-B}。切换失败的PDU session列表包含切换失败的会话的标识。
步骤707，切换完成之后，如果UE发起移动性注册更新流程，携带requested NSSAI， AMF根据UE的requested NSSAI和UE的当前位置(即第一位置)，确定new allowed NSSAI和new RA，并向UE发送new allowed NSSAI和new RA。
具体的，new allowed NSSAI不包含第一切片的标识，new RA包括第一位置的信息。
具体更新的说明，可以参前述图3实施例的情形一中的相关描述，这里不再赘述。
基于该方案，在切换过程中，AMF判断第一切片在目标侧RAN所在的第一位置不可用，则通过删除在目标侧RAN不可用的第一切片对应的会话，分配新的allowed NSSAI或者RA，使得UE获知在当前位置(即第一位置)下无法接入该切片。
应用场景3、空闲态的UE发起激活流程
以图2所示的示例为例，由于拥塞等原因，NSSF决定将切片A(即第一切片)的服务区域TA-3(即第一位置)从“可用”更新为“不可用”状态。
T1时刻，UE在第一切片可用的区域(如TA-2)发起了第一切片对应的会话建立，即在第一切片中建立了PDU session。
T2时刻，UE处于空闲态，从TA-2移动到TA-3，即从第一切片可用的区域移动到第一切片不可用的区域。
应用场景3.1、空闲态的UE在第一切片不可用的区域(如TA-3)发起了业务请求，请求激活第一切片对应的会话(PDU session)用户面数据连接。
如图8所示，为针对该应用场景3.1的一种通信方法流程示意图。该方法包括以下步骤：
步骤800-步骤803，同图6所示的实施例的步骤600-步骤603，可参考前述描述，这里不再赘述。
步骤804a，空闲态的UE向(R)AN发起业务请求，携带要激活的会话列表(List of PDU Sessions To Be Activated)，该列表中包含PDU session ID。
比如，要激活的会话列表包含的信息为表3：
表3
List of PDU Sessions To Be Switched
PDU session ID-1
PDU session ID-2
步骤804b，(R)AN转发UE的业务请求，同时将UE的当前位置上报给AMF。
作为一种可替代的实现方法，在上述步骤804a的业务请求中可以携带UE的当前位置，则该步骤804b中，(R)AN向AMF发送该业务请求。
其中，UE的当前位置为第一位置。以图2所示的示例为例，UE的当前位置位于TA-3。
步骤805，AMF确定要激活的会话列表中的会话对应的第一切片在UE的当前位置不可用。
其中，AMF上存储有会话的标识(PDU session ID)和切片的标识(S-NSSAI)的对应关系。
比如，AMF存储的每一个PDU session ID对应的S-NSSAI为表4：
表4
每一个PDU session ID对应的S-NSSAI
PDU session ID-1 S-NSSAI-A
PDU session ID-2 S-NSSAI-B
以图2所示的示例为例，第一切片对应S-NSSAI-A，且S-NSSAI-A对应的第一切片在第一位置不可用。
步骤806a，AMF拒绝该UE的业务请求，并返回原因值：第一切片在UE的当前位置不可用。
步骤806b，AMF决定触发释放在当前位置下，不可用的第一切片对应的会话，AMF根据上下文判断出该会话对应的SMF，然后向SMF发送会话释放请求，请求释放该会话。
比如，AMF可以调用Nsmf_PDUSession_UpdateSMContext，携带PDU session release request(包含原因值：该会话对应的S-NSSAI在UE的当前位置不可用)。
以图2所示的示例为例，在当前位置下，不可用的第一切片对应的会话为PDU session ID-1。
步骤807，由于业务请求失败，AMF触发更新该UE的allowed NSSAI和RA，AMF向UE发送配置更新消息，携带new allowed NSSAI和new RA，其中:
new allowed NSSAI不包含不可用的S-NSSAI(即上述第一切片的标识)；new RA包括第一位置的信息。其中，new allowed NSSAI中的切片的标识对应的切片在new RA可用。
比如，基于图2示例，则old RA＝{TA-1，TA-2，TA-3}，new RA＝{TA-3}。old allowed NSSAI＝{S-NSSAI-A,S-NSSAI-B}，new allowed NSSAI＝{S-NSSAI-B}。具体更新的说明，可以参前述图3实施例的情形一中的相关描述，这里不再赘述。
可选地，配置更新消息中还可以携带rejected S-NSSAI in current RA，用于通知UE：rejected S-NSSAI在new RA不可用，即rejected S-NSSAI包括步骤804a中UE请求激活的会话对应的的S-NSSAI。
可选地，作为一个可替代的实现方式，上述步骤807中的配置更新消息不携带new allowed NSSAI和new RA，而携带重注册指示信息，用于指示UE发起注册流程。
步骤808，UE向AMF返回配置更新完成消息。
步骤809，若UE在步骤807收到重注册指示信息，则UE在步骤808之后发起注册流程，UE发送注册请求消息，AMF在向UE发送的注册接受消息中携带new allowed NSSAI和new RA。
其中，new allowed NSSAI不包含UE请求的S-NSSAI(即不包含不可用的S-NSSAI)，new RA包括第一位置的信息。
具体更新的说明，可以参前述图3实施例的情形一中的相关描述，这里不再赘述。
可选地，注册接受消息还可以携带在UE的当前注册区域中拒绝的网络切片(rejected S-NSSAI in current RA)，用于通知UE：rejected S-NSSAI在new RA不可用，即rejected S-NSSAI包括步骤804a中UE请求激活的会话对应的S-NSSAI。
步骤810，AMF在UE的上下文中存储UE的当前注册区域中拒绝的网络切片(rejected S-NSSAI in current RA)，用来记录曾经向哪些UE发送过rejected S-NSSAI。
该步骤810为可选步骤。
基于上述方案，AMF判断第一切片在UE的当前位置(第一位置)下的状态为“不可用”，则通过拒绝UE的业务请求，分配new allowed NSSAI或者RA，使得UE获知在当 前位置下无法接入该第一切片，有助于保证UE在更新的注册区域内任一位置都可以访问“可用”切片，实现UE与网络侧保持正确、有效地通信。
应用场景3.2、空闲态的UE在第一切片可用的区域(如TA-2)发起了业务请求，请求激活第一切片对应的会话(PDU session)用户面数据连接。
如图9所示，为针对该应用场景3.2的一种通信方法流程示意图。该方法包括以下步骤：
步骤900-步骤903，同图8所示的实施例的步骤800-步骤803，可参考前述描述，这里不再赘述。
步骤904a，空闲态的UE向(R)AN发起业务请求，携带要激活的会话列表(List of PDU Sessions To Be Activated)，该列表中包含PDU session ID。
比如，要激活的会话列表包含的信息为表5：
表5
List of PDU Sessions To Be Switched
PDU session ID-1
PDU session ID-2
步骤904b，(R)AN转发UE的业务请求，同时将UE的当前位置上报给AMF。
作为一种可替代的实现方法，在上述步骤904a的业务请求中可以携带UE的当前位置，则该步骤904b中，(R)AN向AMF发送该业务请求。
其中，UE的当前位置为第二位置。
以图2所示的示例为例，UE的当前位置位于TA-1或者TA-2。步骤905，AMF确定要激活的会话列表中的会话对应的第一切片在UE的当前位置(第二位置)可用。
其中，AMF上存储有会话的标识(PDU session ID)和切片的标识(S-NSSAI)的对应关系。
比如，AMF存储的每一个PDU session ID对应的S-NSSAI为表6：
表6
Figure PCTCN2019117588-appb-000002
以图2所示的示例为例，第一切片对应S-NSSAI-A，且S-NSSAI-A对应的第一切片在第二位置可用。
步骤906，继续业务请求的其他流程，直到该流程成功结束。
步骤907，由于UE的注册区域包含要激活的会话对应的S-NSSAI不可用的TA(即第一位置)，则AMF决定触发更新该UE的注册区域，AMF向UE发送配置更新消息，携带new RA。
其中,new RA＝old RA删除切片状态改变的TA,即new RA不包括切片状态改变的TA，其中AMF在步骤903获取了状态改变的TA。比如，基于图2示例，则old RA＝{TA-1，TA-2，TA-3}，new RA＝{TA-1，TA-2}。
可选地，作为一个可替代的实现方式，上述步骤907中的配置更新消息不携带new RA，而携带重注册指示信息，用于指示UE发起注册流程。
步骤908，UE向AMF返回配置更新完成消息。
步骤909，若UE在步骤907收到重注册指示信息，则UE在步骤908之后发起注册流程，UE携带注册请求消息，AMF在注册接受消息中携带new RA。
其中，new RA＝old RA删除切片状态改变的TA,即new RA不包括切片状态改变的TA，其中AMF在步骤903获取了状态改变的TA。new allowed NSSAI中的切片的标识对应的切片在new RA可用。
比如，基于图2示例，则old RA＝{TA-1，TA-2，TA-3}，new RA＝{TA-1，TA-2}。
基于上述方案，AMF判断第一切片在UE的当前位置(第二位置)下的状态为“可用”，则网络侧接受UE的业务请求，使得UE获知在当前位置下可以接入该切片，同时更新UE的注册区域，有助于保证UE在更新的注册区域内任一位置都可以访问“可用”切片，实现UE与网络侧保持正确、有效地通信。
应用场景4、网络侧发起UE的激活流程
该应用场景4与上述应用场景3的主要区别在于：应用场景3是由空闲态的UE主动发起的业务请求流程，应用场景4是由网络侧触发的业务请求流程。
以图2所示的示例为例，由于拥塞等原因，NSSF决定将切片A(即第一切片)的服务区域TA-3(即第一位置)从“可用”更新为“不可用”状态。
T1时刻，UE在第一切片可用的区域(如TA-2)发起了第一切片对应的会话建立，即在第一切片中建立了PDU session。
T2时刻，UE处于空闲态，从TA-2移动到TA-3，即从第一切片可用的区域移动到第一切片不可用的区域。
应用场景4.1、空闲态的UE在第一切片不可用的区域(如TA-3)发起了业务请求，请求激活第一切片对应的会话(PDU session)用户面数据连接。
如图10所示，为针对该应用场景4.1的一种通信方法流程示意图。该方法包括以下步骤：
步骤1000-步骤1003，同图8所示的实施例的步骤800-步骤803，可参考前述描述，这里不再赘述。
步骤1004a，UE处于空闲状态，下行数据到达UPF。
步骤1004b，UPF向SMF发送数据到达通知。
步骤1005，SMF向AMF发送会话标识(PDU session ID)和UE的永久标识。
例如，SMF调用AMF的Namf_Communication_N1N2MessageTransfer服务操作，携带会话标识(PDU session ID)和UE的永久标识。
步骤1006，AMF触发对UE的寻呼。
步骤1007a，UE收到寻呼消息之后，向(R)AN发送业务请求。
步骤1007b，(R)AN转发UE的业务请求，同时将UE的当前位置上报给AMF。
作为一种可替代的实现方法，在上述步骤1007a的业务请求中可以携带UE的当前位置，则该步骤1007b中，(R)AN向AMF发送该业务请求。
其中，UE的当前位置为第一位置。
步骤1008，AMF确定要激活的会话对应的第一切片在UE的当前位置不可用。
其中，AMF上存储有会话的标识(PDU session ID)和切片的标识(S-NSSAI)的对应关系。
步骤1009a，AMF拒绝该UE的业务请求，并返回原因值：第一切片在UE的当前位置不可用。
步骤1009b，AMF决定触发释放在当前位置下，不可用的第一切片对应的会话，AMF根据上下文判断出该会话对应的SMF，然后向SMF发送会话释放请求，请求释放该会话。
比如，AMF可以调用Nsmf_PDUSession_UpdateSMContext，携带PDU session release request(包含原因值：该会话对应的S-NSSAI在UE的当前位置不可用)。
步骤1010，由于业务请求失败，AMF触发更新该UE的allowed NSSAI和RA，AMF向UE发送配置更新消息，携带new allowed NSSAI和new RA，其中:
new allowed NSSAI不包含不可用的S-NSSAI(即上述第一切片的标识)；new RA包括第一位置的信息。其中，new allowed NSSAI中的切片的标识对应的切片在new RA可用。
比如，基于图2示例，则old RA＝{TA-1，TA-2，TA-3}，new RA＝{TA-3}。old allowed NSSAI＝{S-NSSAI-A,S-NSSAI-B}，new allowed NSSAI＝{S-NSSAI-B}。具体更新的说明，可以参前述图3实施例的情形一中的相关描述，这里不再赘述。
可选地，配置更新消息中还可以携带rejected S-NSSAI in current RA，用于通知UE：rejected S-NSSAI在new RA不可用，即rejected S-NSSAI包括步骤1001b中UE请求建立会话对应的S-NSSAI。
可选地，作为一个可替代的实现方式，上述步骤1010中的配置更新消息不携带new allowed NSSAI和new RA，而携带重注册指示信息，用于指示UE发起注册流程。步骤1011，UE向AMF返回配置更新完成消息。
步骤1012，若UE在步骤1010收到重注册指示信息，则UE在步骤1011之后发起注册流程，UE发送注册请求消息，AMF在向UE发送的注册接受消息中携带new allowed NSSAI和new RA。
其中:new allowed NSSAI不包含不可用的S-NSSAI(即上述第一切片的标识)；new RA包括第一位置的信息。其中，new allowed NSSAI中的切片的标识对应的切片在new RA可用。
比如，基于图2示例，则old RA＝{TA-1，TA-2，TA-3}，new RA＝{TA-3}。old allowed NSSAI＝{S-NSSAI-A,S-NSSAI-B}，new allowed NSSAI＝{S-NSSAI-B}。具体更新的说明，可以参前述图3实施例的情形一中的相关描述，这里不再赘述。
可选地，注册接受消息中还可以携带rejected S-NSSAI in current RA，用于通知UE：rejected S-NSSAI在new RA不可用，即rejected S-NSSAI包括步骤1001b中UE请求建立会话对应的S-NSSAI。
步骤1013，AMF在UE的上下文中存储UE的当前注册区域中拒绝的网络切片(rejected S-NSSAI in current RA)，用来记录曾经向哪些UE发送过rejected S-NSSAI。
该步骤1013为可选步骤。
基于上述方案，AMF判断第一切片在UE的当前位置(第一位置)下的状态为“不可用”，则通过拒绝UE的业务请求，分配new allowed NSSAI和RA，使得UE获知在当前位置下无法接入该第一切片，有助于保证UE在更新的注册区域内任一位置都可以访问“可用”切片，实现UE与网络侧保持正确、有效地通信。
应用场景4.2、空闲态的UE在第一切片可用的区域(如TA-2)发起了业务请求，请求激活第一切片对应的会话(PDU session)用户面数据连接。
如图11所示，为针对该应用场景4.2的一种通信方法流程示意图。该方法包括以下步骤：
步骤1100-步骤1106，同图10所示的实施例的步骤1000-步骤1006，可参考前述描述，这里不再赘述。
步骤1107a，UE收到寻呼消息之后，向(R)AN发送业务请求。
步骤1107b，(R)AN转发UE的业务请求，同时将UE的当前位置上报给AMF。
其中，UE的当前位置为第二位置。
步骤1108，AMF确定要激活的会话对应的第一切片在UE的当前位置可用。
其中，AMF上存储有会话的标识(PDU session ID)和切片的标识(S-NSSAI)的对应关系。
步骤1109，继续业务请求的其他流程，直到该流程成功结束。
步骤1110，由于UE的注册区域包含要激活的会话对应的S-NSSAI不可用的TA(即第一位置)，则AMF决定触发更新该UE的注册区域，AMF向UE发送配置更新消息，携带new RA。
其中,new RA＝old RA删除切片状态改变的TA,即new RA不包括切片状态改变的TA，其中AMF在步骤1103获取了状态改变的TA。比如，基于图2示例，则old RA＝{TA-1，TA-2，TA-3}，new RA＝{TA-1，TA-2}。
可选地，作为一个可替代的实现方式，上述步骤1110中的配置更新消息不携带new RA，而携带重注册指示信息，用于指示UE发起注册流程。
步骤1111，UE向AMF返回配置更新完成消息。
步骤1112，若UE在步骤1110收到重注册指示信息，则UE在步骤1111之后发起注册流程，UE发送注册请求消息，AMF在向UE发送的注册接受消息中携带new RA。
其中，new RA＝old RA删除切片状态改变的TA,即new RA不包括切片状态改变的TA，其中AMF在步骤1103获取了状态改变的TA。比如，基于图2示例，则old RA＝{TA-1，TA-2，TA-3}，new RA＝{TA-1，TA-2}。
基于上述方案，AMF判断第一切片在UE的当前位置(第二位置)下的状态为“可用”，则网络侧接受UE的业务请求，使得UE获知在当前位置下可以接入该切片，同时更新UE的注册区域，有助于保证UE在更新的注册区域内任一位置都可以访问“可用”切片，实现UE与网络侧保持正确、有效地通信。
以上应用场景1至应用场景4，针对在第一位置的状态发生改变的第一切片，是当UE或者网络进行业务时，在该第一切片对应的会话的建立、激活、切换的流程中，判断该第一切片在UE的当前位置是否可用，进而确定更新UE的RA或allowed NSSAI的方法。作为又一种应用场景，也可以无需在该会话的建立、激活、切换的流程中执行上述通信方法，而只需要根据UE的allowed NSSAI是否包含状态发生改变的第一切片以及UE的注册区域是否包含第一位置来判断是否需要更新UE的allowed NSSAI或者RA。下面给出一个具体示例。
如图12所示，为本申请提供的又一种通信方法流程示意图。该方法包括以下步骤：
步骤1200-步骤1203，同实施例4中的步骤400-步骤403，可参考前述描述，这里不 再赘述。
步骤1204，AMF根据UE的上下文中的allowed NSSAI，确定allowed NSSAI包含不可用的S-NSSAI(即第一切片的标识)，且UE的注册区域包含第一位置的信息，且该UE处于连接态。
步骤1205，AMF判断第一切片在UE的当前位置是否可用。
比如，若UE的当前位置为第一位置，则AMF确定第一切片在UE的当前位置不可用。
比如，若UE的当前位置为第二位置(第二位置与第一位置不同)，则AMF确定第一切片在UE的当前位置可用。
步骤1206，AMF向UE发送配置更新消息。
其中，若上述步骤1205中，AMF确定第一切片在UE的当前位置不可用，则AMF触发更新该UE的allowed NSSAI和RA，AMF向UE发送配置更新消息，携带new allowed NSSAI和new RA，其中，new allowed NSSAI不包含不可用的S-NSSAI；new RA包括第一位置的信息。其中，new allowed NSSAI中的切片的标识对应的切片在new RA可用。
比如，基于图2示例，则old RA＝{TA-1，TA-2，TA-3}，new RA＝{TA-3}。old allowed NSSAI＝{S-NSSAI-A,S-NSSAI-B}，new allowed NSSAI＝{S-NSSAI-B}。具体更新的说明，可以参前述图3实施例的情形一中的相关描述，这里不再赘述。
可选地，配置更新消息中还可以携带rejected S-NSSAI in current RA，用于通知UE：rejected S-NSSAI在new RA不可用，即rejected S-NSSAI包括步骤1203中通知的S-NSSAI(即第一切片的标识)。
若上述步骤1205中，AMF确定第一切片在UE的当前位置可用，AMF决定触发更新该UE的注册区域，AMF向UE发送配置更新消息，携带new RA。其中,new RA＝old RA删除切片状态改变的TA,即new RA不包括切片状态改变的TA，其中AMF在步骤1203获取了状态改变的TA。比如，基于图2示例，则old RA＝{TA-1，TA-2，TA-3}，new RA＝{TA-1，TA-2}。
可选地，作为一个可替代的实现方式，上述步骤1206的配置更新消息不携带new allowed NSSAI和/或new RA，而携带重注册指示信息，用于指示UE发起注册流程。
步骤1207，UE向AMF返回配置更新完成消息。
步骤1208，若UE在步骤1206收到重注册指示信息，则UE在步骤1207之后发起注册流程，UE发送注册请求消息。
其中，若上述步骤1205中，AMF确定第一切片在UE的当前位置不可用，则AMF触发更新该UE的allowed NSSAI和RA，AMF向UE发送注册接受消息，携带new allowed NSSAI和new RA，其中，new allowed NSSAI不包含不可用的S-NSSAI；new RA包括第一位置的信息。其中，new allowed NSSAI中的切片的标识对应的切片在new RA可用。
比如，基于图2示例，则old RA＝{TA-1，TA-2，TA-3}，new RA＝{TA-3}。old allowed NSSAI＝{S-NSSAI-A,S-NSSAI-B}，new allowed NSSAI＝{S-NSSAI-B}。具体更新的说明，可以参前述图3实施例的情形一中的相关描述，这里不再赘述。
可选地，注册接受消息中还可以携带rejected S-NSSAI in current RA，用于通知UE：rejected S-NSSAI在new RA不可用，即rejected S-NSSAI包括步骤1203中通知的S-NSSAI(即第一切片的标识)。
若上述步骤1205中，AMF确定第一切片在UE的当前位置可用，AMF决定触发更新 该UE的注册区域，AMF向UE发送注册接受消息，携带new RA。其中,new RA＝old RA删除切片状态改变的TA,即new RA不包括切片状态改变的TA，其中AMF在步骤1203获取了状态改变的TA。比如，基于图2示例，则old RA＝{TA-1，TA-2，TA-3}，new RA＝{TA-1，TA-2}。步骤1209，AMF在UE的上下文中存储UE的当前注册区域中拒绝的网络切片(rejected S-NSSAI in current RA)，用来记录曾经向哪些UE发送过rejected S-NSSAI。
该步骤1209为可选步骤，当上述步骤1205中，AMF确定第一切片在UE的当前位置不可用时，则AMF可以执行该步骤1209，也可以不执行该步骤1209。当上述步骤1205中，AMF确定第一切片在UE的当前位置可用时，则AMF不执行该步骤1209。
基于上述方案，当UE的allowed NSSAI内的第一切片在UE的注册区域内的某个TA(即第一位置)的状态从“可用”状态更新为“不可用”状态后，则网络侧(如AMF)可以更新UE的注册区域并通知UE更新注册区域，并且，AMF只根据UE的状态和当前位置来判断是否需要更新UE的allowed NSSAI或者RA,有助于保证UE在更新的注册区域内任一位置都可以访问“可用”切片，实现UE与网络侧保持正确、有效地通信，或者，理解为，有助于避免由于UE没有及时更新注册区域而造成的UE在第一位置发起与第一切片关联的业务请求而引起与网络侧的通信失败的问题。
以上图2至图12所示的实施例，是针对第一种情形的实现方式，即第一切片在第一位置从“可用”状态更新为“不可用”状态。下面给出一个实施例，其针对的是第二种情形的实现方式，即第一切片在第一位置从“不可用”状态更新为“可用”状态。
如图13所示，为本申请提供的又一种通信方法流程示意图。该方法包括以下步骤：
步骤1301，NSSF确定第一切片在第一位置的状态发生了改变：从不可用更新为可用。
例如，在上述图2至图12所示的实施例之后，某一时刻，NSSF决定改变第一切片在第一位置的状态(如，由于切片的拥塞情况低于阈值)，将第一切片从“不可用”状态更新为“可用”。
这里的第一切片、第一位置的含义，可参考前述实施例的描述，这里不再赘述。
步骤1302，NSSF通知AMF：第一切片在第一位置更新为可用。
例如，NSSF可以调用Nnssf_NSSAIAvailability_Notify服务化操作，通知AMF：第一切片在第一位置更新为可用。
当然，若有多个切片分别在某个或某些位置的状态更新为可用，则NSSF可以向AMF发送多个S-NSSAI及分别对应的可用的位置列表。比如，S-NSSAI-A在TA-11，TA-12更新为可用，S-NSSAI-B在TA-13，TA-14更新为可用，则NSSF可以向AMF发送：(S-NSSAI-A，(TA-11，TA-12))、(S-NSSAI-B，(TA-13，TA-14))。
步骤1303，AMF根据各个UE上下文中存储的拒绝的网络切片的信息(S-NSSAI rejected in RA)，判断曾经向哪些UE发送过S-NSSAI rejected in RA，且该UE的RA中包含第一位置的信息。
步骤1304，如果UE处于空闲状态，AMF寻呼UE。
该步骤为可选步骤，当UE处于空闲状态时，则执行该步骤，然后执行步骤1305。当UE处于连接态，则可跳过步骤1304直接执行步骤1305。
步骤1305，UE处于连接态，AMF向UE发送配置信息消息。
在一种实现方式中，该配置更新消息中携带new allowed NSSAI，该allowed NSSAI是在UE的当前allowed NSSAI中新增了该rejected S-NSSAI(即第一切片的标识)。
在又一种实现方式中，该配置更新消息携带拒绝的S-NSSAI可用(rejected S-NSSAI available)指示，触发UE自己构造new requested NSSAI尝试接入该切片(即第一切片)。UE在接收到rejected S-NSSAI available指示后，可以决定是否构造new requested NSSAI并尝试接入该切片。
步骤1306，UE向AMF返回配置更新完成消息。
步骤1307，AMF删除在UE的上下文中存储的UE的当前注册区域中拒绝的网络切片(rejected S-NSSAI in current RA)中的第一切片的标识。
基于上述方案，AMF判断第一切片在第一位置的切片状态更新为“可用”，则通过UE上下文存储的Rejected S-NSSAI in current RA，触发AMF通知UE，该第一切片在第一位置可用，使得UE获知在第一位置下可以接入该切片，有助于保证UE及时地访问“可用”切片，实现UE与网络侧保持正确、有效地通信。
上述主要从各个网元之间交互的角度对本申请提供的方案进行了介绍。可以理解的是，上述实现各网元为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
如图14所示，为本申请所涉及的通信装置的一种可能的示例性框图，该通信装置1400可以以软件或硬件的形式存在。通信装置1400可以包括：处理单元1402和通信单元1403。作为一种实现方式，该通信单元1403可以包括接收单元和发送单元。处理单元1402用于对通信装置1400的动作进行控制管理。通信单元1403用于支持通信装置1400与其他网络实体的通信。通信装置1400还可以包括存储单元1401，用于存储通信装置1400的程序代码和数据。
其中，处理单元1402可以是处理器或控制器，例如可以是通用中央处理器(central processing unit，CPU)，通用处理器，数字信号处理(digital signal processing，DSP)，专用集成电路(application specific integrated circuits，ASIC)，现场可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包括一个或多个微处理器组合，DSP和微处理器的组合等等。存储单元1401可以是存储器。通信单元1403是一种该装置的接口电路，用于从其它装置接收信号。例如，当该装置以芯片的方式实现时，该通信单元1403是该芯片用于从其它芯片或装置接收信号的接口电路，或者，是该芯片用于向其它芯片或装置发送信号的接口电路。
该通信装置1400可以为上述任一实施例中的终端设备，还可以为用于终端设备的芯片。例如，当通信装置1400为终端设备时，该处理单元1402例如可以是处理器，该通信单元1403例如可以是收发器。可选的，该收发器可以包括射频电路，该存储单元例如可以是存储器。例如，当通信装置1400为用于终端设备的芯片时，该处理单元1402例如可以是处理器，该通信单元1403例如可以是输入/输出接口、管脚或电路等。该处理单元1402可执行存储单元存储的计算机执行指令，可选地，该存储单元为该芯片内的存储单元，如 寄存器、缓存等，该存储单元还可以是该终端设备内的位于该芯片外部的存储单元，如只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)等。
在一个实施例中，该通信装置1400为终端设备，接收单元，用于第一切片在第一位置为不可用、在第二位置可用，则接收终端设备的更新后的注册区域，终端设备的更新前的注册区域包括第一位置的信息和第二位置的信息，终端设备的允许接入的网络切片集合包括第一切片的信息；处理单元，用于更新终端设备的注册区域。
在一种可能的实现方法中，接收单元，还用于接收终端设备的更新后的允许接入的网络切片集合；处理单元，还用于更新终端设备的允许接入的网络切片集合。
在一种可能的实现方法中，终端设备的当前位置为第一位置，则终端设备的更新后的允许接入的网络切片集合不包括第一切片的信息，终端设备的更新后的注册区域包括第一位置的信息、且不包括第二位置的信息。
在一种可能的实现方法中，发送单元，用于发送请求消息，请求消息用于请求建立或激活与第一切片关联的会话；接收单元，还用于接收请求拒绝消息，请求拒绝消息包括原因值，原因值用于指示第一切片不可用。
在一种可能的实现方法中，接收单元，还用于接收拒绝的网络切片的信息，拒绝的网络切片的信息包括第一切片的标识信息。
在一种可能的实现方法中，终端设备的当前位置为第二位置，则终端设备的更新后的注册区域包括第二位置的信息、且不包括第一位置的信息。
在一种可能的实现方法中，接收单元，还用于接收指示信息，指示信息用于指示终端设备发起重注册流程。
可以理解的是，该通信装置用于上述通信方法时的具体实现过程以及相应的有益效果，可以参考前述方法实施例中的相关描述，这里不再赘述。
如图15所示，为本申请所涉及的通信装置的一种可能的示例性框图，该通信装置1500可以以软件或硬件的形式存在。通信装置1500可以包括：处理单元1502和通信单元1503。作为一种实现方式，该通信单元1503可以包括接收单元和发送单元。处理单元1502用于对通信装置1500的动作进行控制管理。通信单元1503用于支持通信装置1500与其他网络实体的通信。通信装置1500还可以包括存储单元1501，用于存储通信装置1500的程序代码和数据。
其中，处理单元1502可以是处理器或控制器，例如可以是CPU，通用处理器，DSP，ASIC，FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包括一个或多个微处理器组合，DSP和微处理器的组合等等。存储单元1501可以是存储器。通信单元1503是一种该装置的接口电路，用于从其它装置接收信号。例如，当该装置以芯片的方式实现时，该通信单元1503是该芯片用于从其它芯片或装置接收信号的接口电路，或者，是该芯片用于向其它芯片或装置发送信号的接口电路。
该通信装置1500可以为上述任一实施例中的移动性管理网元，还可以为用于移动性管理网元的芯片。例如，当通信装置1500为移动性管理网元时，该处理单元1502例如可以是处理器，该通信单元1503例如可以是收发器。可选的，该收发器可以包括射频电路， 该存储单元例如可以是存储器。例如，当通信装置1500为用于移动性管理网元的芯片时，该处理单元1502例如可以是处理器，该通信单元1503例如可以是输入/输出接口、管脚或电路等。该处理单元1502可执行存储单元存储的计算机执行指令，可选地，该存储单元为该芯片内的存储单元，如寄存器、缓存等，该存储单元还可以是该移动性管理网元内的位于该芯片外部的存储单元，如ROM或可存储静态信息和指令的其他类型的静态存储设备，RAM等。
在一个实施例中，该通信装置1500为移动性管理网元，处理单元，用于确定第一切片在第一位置为不可用、在第二位置可用，以及更新终端设备的注册区域，其中，终端设备的更新前的注册区域包括第一位置的信息和第二位置的信息，终端设备的允许接入的网络切片集合包括第一切片的信息；发送单元，用于向终端设备发送终端设备的更新后的注册区域。
在一种可能的实现方法中，处理单元，还用于更新终端设备的允许接入的网络切片集合；发送单元，还用于向终端设备发送终端设备的更新后的允许接入的网络切片集合。
在一种可能的实现方法中，终端设备的当前位置为第一位置，则终端设备的更新后的允许接入的网络切片集合不包括第一切片的信息，终端设备的更新后的注册区域包括第一位置的信息、且不包括第二位置的信息。
在一种可能的实现方法中，处理单元，还用于触发释放与第一切片关联的会话。
在一种可能的实现方法中，接收单元，用于接收来自终端设备的请求消息，请求消息用于请求建立或激活与第一切片关联的会话；发送单元，还用于向终端设备发送请求拒绝消息，请求拒绝消息包括原因值，原因值用于指示第一切片不可用。
在一种可能的实现方法中，发送单元，还用于向终端设备发送拒绝的网络切片的信息，拒绝的网络切片的信息包括第一切片的标识信息。
在一种可能的实现方法中，处理单元，还用于在终端设备的上下文中存储拒绝的网络切片的信息，拒绝的网络切片的信息包括第一切片的信息，拒绝的网络切片的信息用于指示第一切片在终端设备的更新后的注册区域内不可用。
在一种可能的实现方法中，终端设备的当前位置为第二位置，则终端设备的更新后的注册区域包括第二位置的信息、且不包括第一位置的信息。
可以理解的是，该通信装置用于上述通信方法时的具体实现过程以及相应的有益效果，可以参考前述方法实施例中的相关描述，这里不再赘述。
参阅图16所示，为本申请提供的一种通信装置示意图，该通信装置可以是上述移动性管理网元、或终端设备。该通信装置1600包括：处理器1602、通信接口1603、存储器1601。可选的，通信装置1600还可以包括通信线路1604。其中，通信接口1603、处理器1602以及存储器1601可以通过通信线路1604相互连接；通信线路1604可以是外设部件互连标准(peripheral component interconnect，简称PCI)总线或扩展工业标准结构(extended industry standard architecture，简称EISA)总线等。所述通信线路1604可以分为地址总线、数据总线、控制总线等。为便于表示，图16中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
处理器1602可以是一个CPU，微处理器，ASIC，或一个或多个用于控制本申请方案程序执行的集成电路。
通信接口1603，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以 太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)，有线接入网等。
存储器1601可以是ROM或可存储静态信息和指令的其他类型的静态存储设备，RAM或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路1604与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器1601用于存储执行本申请方案的计算机执行指令，并由处理器1602来控制执行。处理器1602用于执行存储器1601中存储的计算机执行指令，从而实现本申请上述实施例提供的通信方法。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
本领域普通技术人员可以理解：本申请中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本申请实施例的范围，也表示先后顺序。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。“至少一个”是指一个或者多个。至少两个是指两个或者多个。“至少一个”、“任意一个”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a,b,或c中的至少一项(个、种)，可以表示：a,b,c,a-b,a-c,b-c,或a-b-c，其中a,b,c可以是单个，也可以是多个。“多个”是指两个或两个以上，其它量词与之类似。此外，对于单数形式“a”，“an”和“the”出现的元素(element)，除非上下文另有明确规定，否则其不意味着“一个或仅一个”，而是意味着“一个或多于一个”。例如，“a device”意味着对一个或多个这样的device。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包括一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
本申请实施例中所描述的各种说明性的逻辑单元和电路可以通过通用处理器，数字信号处理器，专用集成电路(ASIC)，现场可编程门阵列(FPGA)或其它可编程逻辑装置， 离散门或晶体管逻辑，离散硬件部件，或上述任何组合的设计来实现或操作所描述的功能。通用处理器可以为微处理器，可选地，该通用处理器也可以为任何传统的处理器、控制器、微控制器或状态机。处理器也可以通过计算装置的组合来实现，例如数字信号处理器和微处理器，多个微处理器，一个或多个微处理器联合一个数字信号处理器核，或任何其它类似的配置来实现。
本申请实施例中所描述的方法或算法的步骤可以直接嵌入硬件、处理器执行的软件单元、或者这两者的结合。软件单元可以存储于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、可移动磁盘、CD-ROM或本领域中其它任意形式的存储媒介中。示例性地，存储媒介可以与处理器连接，以使得处理器可以从存储媒介中读取信息，并可以向存储媒介存写信息。可选地，存储媒介还可以集成到处理器中。处理器和存储媒介可以设置于ASIC中。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包括这些改动和变型在内。

Claims (30)

  1. 一种通信方法，其特征在于，包括：
    第一切片在第一位置为不可用、在第二位置可用，则终端设备接收所述终端设备的更新后的注册区域，所述终端设备的更新前的注册区域包括所述第一位置的信息和第二位置的信息，所述终端设备的允许接入的网络切片集合包括所述第一切片的信息；
    所述终端设备更新所述终端设备的注册区域。
  2. 如权利要求1所述的方法，其特征在于，还包括：
    所述终端设备接收所述终端设备的更新后的允许接入的网络切片集合；
    所述终端设备更新所述终端设备的允许接入的网络切片集合。
  3. 如权利要求2所述的方法，其特征在于，所述终端设备的当前位置为所述第一位置，则所述终端设备的更新后的允许接入的网络切片集合不包括所述第一切片的信息，所述终端设备的更新后的注册区域包括所述第一位置的信息、且不包括所述第二位置的信息。
  4. 如权利要求3所述的方法，其特征在于，还包括：
    所述终端设备发送请求消息，所述请求消息用于请求建立或激活与所述第一切片关联的会话；
    所述终端设备接收请求拒绝消息，所述请求拒绝消息包括原因值，所述原因值用于指示所述第一切片不可用。
  5. 如权利要求3或4所述的方法，其特征在于，还包括：
    所述终端设备接收拒绝的网络切片的信息，所述拒绝的网络切片的信息包括所述第一切片的标识信息。
  6. 如权利要求1所述的方法，其特征在于，所述终端设备的当前位置为所述第二位置，则所述终端设备的更新后的注册区域包括所述第二位置的信息、且不包括所述第一位置的信息。
  7. 如权利要求1-6任一所述的方法，其特征在于，还包括：
    所述终端设备接收指示信息，所述指示信息用于指示所述终端设备发起重注册流程。
  8. 一种通信方法，其特征在于，包括：
    移动性管理网元确定第一切片在第一位置为不可用、在第二位置可用，所述移动性管理网元更新终端设备的注册区域，其中，所述终端设备的更新前的注册区域包括所述第一位置的信息和所述第二位置的信息，所述终端设备的允许接入的网络切片集合包括所述第一切片的信息；
    所述移动性管理网元向所述终端设备发送所述终端设备的更新后的注册区域。
  9. 如权利要求8所述的方法，其特征在于，还包括：
    所述移动性管理网元更新所述终端设备的允许接入的网络切片集合；
    所述移动性管理网元向所述终端设备发送所述终端设备的更新后的允许接入的网络切片集合。
  10. 如权利要求9所述的方法，其特征在于，所述终端设备的当前位置为所述第一位置，则所述终端设备的更新后的允许接入的网络切片集合不包括所述第一切片的信息，所述终端设备的更新后的注册区域包括所述第一位置的信息、且不包括所述第二位置的信息。
  11. 如权利要求10所述的方法，其特征在于，还包括：
    所述移动性管理网元触发释放与所述第一切片关联的会话。
  12. 如权利要求10所述的方法，其特征在于，还包括：
    所述移动性管理网元接收来自所述终端设备的请求消息，所述请求消息用于请求建立或激活与所述第一切片关联的会话；
    所述移动性管理网元向所述终端设备发送请求拒绝消息，所述请求拒绝消息包括原因值，所述原因值用于指示所述第一切片不可用。
  13. 如权利要求10-12任一所述的方法，其特征在于，还包括：
    所述移动性管理网元向所述终端设备发送拒绝的网络切片的信息，所述拒绝的网络切片的信息包括所述第一切片的标识信息。
  14. 如权利要求8-13任一所述的方法，其特征在于，还包括：
    所述移动性管理网元在所述终端设备的上下文中存储拒绝的网络切片的信息，所述拒绝的网络切片的信息包括所述第一切片的信息，所述拒绝的网络切片的信息用于指示所述第一切片在所述终端设备的更新后的注册区域内不可用。
  15. 如权利要求8所述的方法，其特征在于，所述终端设备的当前位置为所述第二位置，则所述终端设备的更新后的注册区域包括所述第二位置的信息、且不包括所述第一位置的信息。
  16. 一种通信装置，其特征在于，包括：
    接收单元，用于第一切片在第一位置为不可用、在第二位置可用，则接收终端设备的更新后的注册区域，所述终端设备的更新前的注册区域包括所述第一位置的信息和第二位置的信息，所述终端设备的允许接入的网络切片集合包括所述第一切片的信息；
    处理单元，用于更新所述终端设备的注册区域。
  17. 如权利要求16所述的装置，其特征在于，所述接收单元，还用于接收所述终端设备的更新后的允许接入的网络切片集合；
    所述处理单元，还用于更新所述终端设备的允许接入的网络切片集合。
  18. 如权利要求17所述的装置，其特征在于，所述终端设备的当前位置为所述第一位置，则所述终端设备的更新后的允许接入的网络切片集合不包括所述第一切片的信息，所述终端设备的更新后的注册区域包括所述第一位置的信息、且不包括所述第二位置的信息。
  19. 如权利要求18所述的装置，其特征在于，所述装置还包括发送单元，用于发送请求消息，所述请求消息用于请求建立或激活与所述第一切片关联的会话；
    所述接收单元，还用于接收请求拒绝消息，所述请求拒绝消息包括原因值，所述原因值用于指示所述第一切片不可用。
  20. 如权利要求18或19所述的装置，其特征在于，所述接收单元，还用于接收拒绝的网络切片的信息，所述拒绝的网络切片的信息包括所述第一切片的标识信息。
  21. 如权利要求16所述的装置，其特征在于，所述终端设备的当前位置为所述第二位置，则所述终端设备的更新后的注册区域包括所述第二位置的信息、且不包括所述第一位置的信息。
  22. 如权利要求16-21任一所述的装置，其特征在于，所述接收单元，还用于接收指示信息，所述指示信息用于指示所述终端设备发起重注册流程。
  23. 一种通信装置，其特征在于，包括：
    处理单元，用于确定第一切片在第一位置为不可用、在第二位置可用；以及，更新所述终端设备的注册区域，其中，终端设备的更新前的注册区域包括所述第一位置的信息和所述第二位置的信息，所述终端设备的允许接入的网络切片集合包括所述第一切片的信息；
    发送单元，用于向所述终端设备发送所述终端设备的更新后的注册区域。
  24. 如权利要求23所述的装置，其特征在于，所述处理单元，还用于更新所述终端设备的允许接入的网络切片集合；
    所述发送单元，还用于向所述终端设备发送所述终端设备的更新后的允许接入的网络切片集合。
  25. 如权利要求24所述的装置，其特征在于，所述终端设备的当前位置为所述第一位置，则所述终端设备的更新后的允许接入的网络切片集合不包括所述第一切片的信息，所述终端设备的更新后的注册区域包括所述第一位置的信息、且不包括所述第二位置的信息。
  26. 如权利要求25所述的装置，其特征在于，所述处理单元，还用于触发释放与所述第一切片关联的会话。
  27. 如权利要求25所述的装置，其特征在于，所述装置还包括接收单元，用于接收来自所述终端设备的请求消息，所述请求消息用于请求建立或激活与所述第一切片关联的会话；
    所述发送单元，还用于向所述终端设备发送请求拒绝消息，所述请求拒绝消息包括原因值，所述原因值用于指示所述第一切片不可用。
  28. 如权利要求25-27任一所述的装置，其特征在于，所述发送单元，还用于向所述终端设备发送拒绝的网络切片的信息，所述拒绝的网络切片的信息包括所述第一切片的标识信息。
  29. 如权利要求23-28任一所述的装置，其特征在于，所述处理单元，还用于在所述终端设备的上下文中存储拒绝的网络切片的信息，所述拒绝的网络切片的信息包括所述第一切片的信息，所述拒绝的网络切片的信息用于指示所述第一切片在所述终端设备的更新后的注册区域内不可用。
  30. 如权利要求23所述的装置，其特征在于，所述终端设备的当前位置为所述第二位置，则所述终端设备的更新后的注册区域包括所述第二位置的信息、且不包括所述第一位置的信息。
PCT/CN2019/117588 2019-02-18 2019-11-12 一种通信方法及装置 WO2020168753A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910123531.2A CN111586772B (zh) 2019-02-18 2019-02-18 一种通信方法及装置
CN201910123531.2 2019-02-18

Publications (1)

Publication Number Publication Date
WO2020168753A1 true WO2020168753A1 (zh) 2020-08-27

Family

ID=72125990

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/117588 WO2020168753A1 (zh) 2019-02-18 2019-11-12 一种通信方法及装置

Country Status (2)

Country Link
CN (1) CN111586772B (zh)
WO (1) WO2020168753A1 (zh)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109743213B (zh) * 2019-02-28 2021-08-13 腾讯科技（深圳）有限公司 一种网络切片处理方法和设备以及系统
CN114189844A (zh) * 2020-09-14 2022-03-15 中兴通讯股份有限公司 终端跨区域通信方法、网元设备及存储介质
CN114302492A (zh) * 2020-09-23 2022-04-08 维沃移动通信有限公司 切片请求方法、终端及网络侧设备
WO2022069126A1 (en) * 2020-10-01 2022-04-07 Nokia Technologies Oy Ran congestion management and service continuity with user consent option
WO2023000154A1 (zh) * 2021-07-20 2023-01-26 北京小米移动软件有限公司 跟踪区异常处理方法及装置、通信设备及存储介质
WO2023050317A1 (zh) * 2021-09-30 2023-04-06 北京小米移动软件有限公司 跟踪区处理方法及装置、通信设备及存储介质
WO2023123218A1 (zh) * 2021-12-30 2023-07-06 Oppo广东移动通信有限公司 网络切片的请求方法、设备、存储介质及程序产品
WO2023141877A1 (en) * 2022-01-27 2023-08-03 Zte Corporation Methods, devices, and systems for performing network slice replacement during mobility
CN117062189A (zh) * 2022-05-06 2023-11-14 华为技术有限公司 通信方法和装置
CN117615306A (zh) * 2022-08-22 2024-02-27 华为技术有限公司 注册方法及装置
CN115412434B (zh) * 2022-08-26 2024-02-09 哲库科技(北京)有限公司 一种切片请求方法和终端设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108347751A (zh) * 2017-01-25 2018-07-31 华为技术有限公司 通信方法和通信装置
WO2018175498A1 (en) * 2017-03-20 2018-09-27 Zte Corporation Network slicing serving function
WO2018199672A1 (en) * 2017-04-27 2018-11-01 Samsung Electronics Co., Ltd. Network slice-available area information acquisition method

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10862818B2 (en) * 2015-09-23 2020-12-08 Huawei Technologies Co., Ltd. Systems and methods for distributing network resources to network service providers
JP6725703B2 (ja) * 2016-02-16 2020-07-22 アイディーエーシー ホールディングス インコーポレイテッド ネットワークスライシング操作
EP3641424B1 (en) * 2017-06-17 2022-05-04 LG Electronics Inc. Method for registering a user equipment with a network slice in a wireless communication system and user equipment therefor
CN109219111B (zh) * 2017-06-29 2020-09-04 华为技术有限公司 切片选择方法和装置
CN109257769B (zh) * 2017-07-12 2020-09-01 维沃移动通信有限公司 一种处理网络切片拥塞的方法、相关设备和系统
CN109391648B (zh) * 2017-08-04 2020-12-22 华为技术有限公司 一种应用与网络切片的关联方法、装置和通信系统
CN109168180B (zh) * 2017-08-11 2020-03-10 华为技术有限公司 通信方法及源基站、目标基站、核心网设备、终端设备
US20200059989A1 (en) * 2017-08-16 2020-02-20 Lenovo (Singapore) Pte. Ltd. Indicating a packet data unit session as unavailable

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108347751A (zh) * 2017-01-25 2018-07-31 华为技术有限公司 通信方法和通信装置
WO2018175498A1 (en) * 2017-03-20 2018-09-27 Zte Corporation Network slicing serving function
WO2018199672A1 (en) * 2017-04-27 2018-11-01 Samsung Electronics Co., Ltd. Network slice-available area information acquisition method

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "Xn based mobility for inter-RA case", 3GPP DRAFT; R3-180471 XN BASED MOBILITY FOR INTER-RA CASE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), vol. RAN WG3, no. Sophia Antipolis, France; 20180122 - 20180126, 12 January 2018 (2018-01-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051387316 *

Also Published As

Publication number Publication date
CN111586772A (zh) 2020-08-25
CN111586772B (zh) 2021-06-22

Similar Documents

Publication Publication Date Title
WO2020168753A1 (zh) 一种通信方法及装置
CN109951877B (zh) 一种切片信息更新方法及装置
WO2021000609A1 (zh) 一种网络性能的上报方法及装置
CN113596744B (zh) 一种通信方法、装置及系统
EP3668178B1 (en) Session processing method and related device
US11812496B2 (en) User group session management method and apparatus
CN110012437B (zh) 一种组播报文的发送方法、装置及系统
WO2020169086A1 (zh) 一种用户面路径的选择方法及装置
RU2628316C2 (ru) Способы для обеспечения plmn-идентификатора шлюза сети пакетной передачи данных для узла ran
CN111010673A (zh) 一种通信方法及装置
WO2020169019A1 (zh) 一种通信方法及装置
BR112020016328A2 (pt) Método de comunicação, aparelho de comunicações, sistema de comunicações e um meio legível por computador
WO2021012736A1 (zh) 一种会话管理网元的选择方法、装置及系统
US20200196208A1 (en) Method and Apparatus for Selecting Radio Access Network Device
US20060252430A1 (en) Frequency layer dispersion
WO2020200254A1 (zh) 一种通信方法及装置
JP2021503865A (ja) 通信方法及び装置
US20210014720A1 (en) Relocation Method and Apparatus
CN111586892B (zh) 一种传输方法及装置
WO2019192445A1 (zh) 一种组播组创建、组播组加入方法及装置
WO2020088601A1 (zh) 控制终端与网络连接的方法及装置
WO2020103517A1 (zh) 终端的能力信息的获取方法、装置及系统
WO2016054962A1 (zh) 无线通信中切换接入点的方法、网络控制节点和用户设备
WO2019120109A1 (zh) 一种切片信息更新方法及装置
WO2022007484A1 (zh) 重定向方法、网络设备、终端设备及可读存储介质

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: 19916173

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19916173

Country of ref document: EP

Kind code of ref document: A1