WO2021233148A1 - 切片接入方法、装置及系统 - Google Patents

切片接入方法、装置及系统 Download PDF

Info

Publication number
WO2021233148A1
WO2021233148A1 PCT/CN2021/092614 CN2021092614W WO2021233148A1 WO 2021233148 A1 WO2021233148 A1 WO 2021233148A1 CN 2021092614 W CN2021092614 W CN 2021092614W WO 2021233148 A1 WO2021233148 A1 WO 2021233148A1
Authority
WO
WIPO (PCT)
Prior art keywords
ursp
network
slice
information
rsd
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2021/092614
Other languages
English (en)
French (fr)
Inventor
丁辉
李卓明
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to JP2022570437A priority Critical patent/JP7485793B2/ja
Priority to EP21807768.3A priority patent/EP4142218A4/en
Priority to KR1020227042561A priority patent/KR20230007473A/ko
Publication of WO2021233148A1 publication Critical patent/WO2021233148A1/zh
Priority to US18/054,529 priority patent/US20230072956A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/13—Cell handover without a predetermined boundary, e.g. virtual cells

Definitions

  • This application relates to the field of communication technology, and in particular to a slice access method, device and system.
  • the 3rd generation partnership project (3GPP) proposes the technology of network slice (network slice).
  • a physical network is divided into multiple logical networks, and a network slice is a collective term for one or more logical networks.
  • the terminal can access the network slice and perform services with the help of the network slice (logical network).
  • the terminal mainly determines which slices are needed for the current service according to the matching result of the user equipment route selection policy (URSP). Specifically, the terminal determines the single network slice selection assistance information (single network slice selection assistance information, S-NSSAI) corresponding to the slice to be used by the service according to one or more URSPs, and determines whether the S-NSSAI is included in the current network. Within the network slice selection assistance information (allowed network slice selection assistance information, allowed NSSAI).
  • S-NSSAI single network slice selection assistance information
  • the terminal If the S-NSSAI indicated by the current URSP does not appear in allowed NSSAI, or the session establishment request initiated by the terminal device according to the S-NSSAI is rejected by the network side, and the rejection reason value shows that the UE is not supported to access the S-NSSAI, the terminal The URSP matching will continue to be performed according to the URSP priority until it is determined that the S-NSSAI (referred to as the target S-NSSAI) indicated by a certain URSP applicable to the service appears in the allowed NSSAI and is accepted by the network side.
  • the target S-NSSAI referred to as the target S-NSSAI
  • the terminal determines the requirement through the S-NSSAI indicated by the wildcarded URSP and allowed NSSAI. Which slice to use.
  • the terminal can determine which slice to use, since the slice that the UE actually needs to access may not be deployed in the current area of the current access network, the final target S-NSSAI or wildcard URSP is indicated. S-NSSAI may not be able to meet the business needs of the terminal.
  • the embodiments of the present application provide a slice access method, device, and system, which can reduce the probability of a terminal service failure caused by matching a slice that is not suitable for the current service to be initiated.
  • an embodiment of the present application provides a slice access method, which is executed by a terminal device.
  • a terminal device can refer to a terminal device, or a component (such as a chip system) in the terminal device.
  • the method includes:
  • One or more user routing policy rules URSP rules are received from the network device, and URSP matching is performed according to the one or more URSP rules.
  • at least one URSP rule in the URSP rule includes indication information; the indication information is used to indicate to match one or more preset URSP rules or match one or more preset routing description RSDs.
  • the indication information is used to indicate that one or more preset URSP rules are matched, which means that only one or more preset URSP rules are matched, and other URSP rules except the preset URSP rules are not matched.
  • the indication information is used to indicate that one or more preset RSDs are matched, which means that only one or more preset RSDs are matched, and other RSDs other than the preset RSDs are not matched.
  • the terminal can receive indication information from the network device, so that when a service needs to be initiated, URSP matching is triggered, and only the preset URSP indicated by the indication information is matched, or it may not match the preset indicated by the indication information URSP. In this way, the number of URSPs that need to be matched can be reduced, and the matching slice information that has been matched with the URSP is not suitable for service requirements, and the PDU session established accordingly cannot support the service to be initiated, resulting in the probability of terminal service failure.
  • URSP matching is performed according to one or more URSP rules, including:
  • the URSP rule includes one or more RSDs, and the RSD includes S-NSSAI.
  • S-NSSAI is not supported by the first network, which means that S-NSSAI is not in the Allowed NSSAI of the first network. Or, although the S-NSSAI is in the Allowed NSSAI, the Allowed NSSAI received by the terminal device may not be updated. Or, after the terminal device initiates a PDU session establishment request, it receives a rejection reason value from the network side, and the reason value indicates that the S-NSSAI does not support access temporarily. Or other situations that are not supported by the first network.
  • the first network refers to the current access network of the terminal.
  • the method further includes: accessing the second network through a mobility change process, and requesting at least one of the one or more S-NSSAIs in the second network.
  • the second network is a network that supports at least one of one or more S-NSSAIs.
  • the terminal device switches from the first network to the second network through the mobility change process, or registers to the second network.
  • the terminal device after the terminal device accesses the second network, it can also request access to one or more S-NSSAIs (ie, S-NSSAI) in the second network through the following registration process. At least one of the services required to access). In order to access at least one required slice.
  • S-NSSAI S-NSSAI
  • the terminal device first performs the switching, and after switching from the first network to the second network, triggers the registration process to the second network. Or, if the above-mentioned registration method is adopted, the terminal device directly registers with the second network from the first network through the registration process. In the registration process to the second network, the terminal device may send a registration request to the second network, and the registration request message includes Requested NSSAI.
  • Requested NSSAI includes at least one of the above-mentioned one or more S-NSSAIs, that is, includes at least one required S-NSSAI.
  • the terminal device only matches S-NSSAI-1 to S-NSSAI-3 in URSP1, and these three S-NSSAIs are not in the Allowed NSSAI of the first network, and the Requested NSSAI sent by the terminal device to the second network includes At least one of S-NSSAI-1 to S-NSSAI-3.
  • the registration distance can also be used to update the UE context and other information in the second network.
  • the terminal device when selecting session parameters for the PDU session, in addition to the URSP rules and the Allowed NSSAI information, it also refers to the information about whether the surrounding network at the current location of the UE supports the required slice. And, it can determine whether to trigger the mobility change process to the neighboring network. In this way, the terminal device can access the required slice (that is, at least one of the slices respectively corresponding to S-NSSAI-1 to S-NSSAI-3) through the second network, and establish a PDU session in the required slice. Because the required slice information (including S-NSSAI, DNN, etc.) is determined according to the service information in the URSP matching process, the PDU session established according to the required slice information can meet the service requirements of the terminal device. The probability of service failure due to the terminal device matching the slice information that is not suitable for the service is reduced.
  • the method further includes: obtaining network selection auxiliary information, and the network selection auxiliary information includes one or more of the following information:
  • the target slice set is one or more slices corresponding to the target NSSAI; the target NSSAI includes one or more of the following: the NSSAI corresponding to the network slice requested by the terminal device, the NSSAI corresponding to the network slice that denies the terminal device to access, and the terminal device is allowed to access The NSSAI corresponding to the incoming network slice.
  • the terminal device executes the mobility change process based on one or more of the following information: local configuration, monitored broadcast information, and network selection auxiliary information.
  • an embodiment of the present application provides a slice access method, which is executed by a network device.
  • a network device can refer to a network device or a component (such as a chip system) in the network device.
  • the method includes:
  • the indication information is used to indicate to match one or more preset URSP rules or match one or more preset routing description RSDs.
  • the network device determining the indication information includes determining the indication information according to one or more of the following information: user subscription information, the location of the terminal device, and pre-configuration information.
  • sending the instruction information to the terminal device includes: sending one or more URSP rules to the terminal device, and at least one of the one or more URSP rules includes the instruction information.
  • the method further includes:
  • the network selection auxiliary information includes one or more of the following information: information about one or more networks that support one or more slices in the target slice set, the priority of one or more networks, and one or more networks separately support Network slice information.
  • the target slice set is one or more slices corresponding to the target NSSAI; the target NSSAI includes one or more of the following: the NSSAI corresponding to the network slice requested by the terminal device, the NSSAI corresponding to the network slice that denies the terminal device to access, and the terminal device is allowed to access The NSSAI corresponding to the incoming network slice.
  • an embodiment of the present application provides a slice access device, which is the aforementioned terminal device.
  • a terminal device can refer to a terminal device, or a component (such as a chip system) in the terminal device.
  • the device includes a communication interface and a processor.
  • the communication interface is used to receive one or more user routing policy rules URSP rule from the network device, and at least one URSP rule in the URSP rule includes indication information; the indication information is used to indicate matching of one or more preset URSP rules or matching One or more preset routing options describe RSD.
  • the processor is used to perform URSP matching according to one or more URSP rules.
  • the processor is used to perform URSP matching according to one or more URSP rules, including:
  • the processor is further configured to access the second network through the mobility change process, and request at least one of the one or more S-NSSAIs in the second network.
  • the second network is a network that supports at least one of one or more S-NSSAIs.
  • the processor is also used to obtain network selection auxiliary information, and the network selection auxiliary information includes one or more of the following information:
  • the target slice set is one or more slices corresponding to the target NSSAI; the target NSSAI includes one or more of the following: the NSSAI corresponding to the network slice requested by the terminal device, the NSSAI corresponding to the network slice that denies the terminal device to access, and the terminal device is allowed to access The NSSAI corresponding to the incoming network slice.
  • the processor is configured to access the second network through the mobility change process, including: being configured to execute the mobility change process according to the network selection auxiliary information to access the second network.
  • an embodiment of the present application provides a slice access device, which is the aforementioned network device.
  • the device includes a communication interface and a processor.
  • the processor is used to determine indication information, and the indication information is used to indicate matching one or more preset URSP rules or matching one or more preset routing description RSDs.
  • the communication interface is used to send instruction information to the terminal device.
  • the processor is used to determine the indication information, including: used to determine the indication information according to one or more of the following information: user subscription information, location of the terminal device, and pre-configuration information.
  • the communication interface is used to send instruction information to the terminal device, including: it is used to send one or more URSP rules to the terminal device, and at least one of the one or more URSP rules includes the instruction information.
  • the processor is also used for:
  • the network selection auxiliary information includes one or more of the following information: information about one or more networks that support one or more slices in the target slice set, the priority of one or more networks, and the networks supported by one or more networks respectively Slice information.
  • the target slice set is one or more slices corresponding to the target NSSAI; the target NSSAI includes one or more of the following: the NSSAI corresponding to the network slice requested by the terminal device, the NSSAI corresponding to the network slice that denies the terminal device to access, and the terminal device is allowed to access The NSSAI corresponding to the incoming network slice.
  • the preset URSP includes: non-wildcard URSP rules; or, the preset URSP rules include the first URSP rule and one or more second URSP rules; or, the preset URSP rules include the first URSP rule;
  • the first URSP rule is the URSP rule where the indication information is located;
  • the second URSP rule is the URSP rule with a higher priority than the first URSP rule;
  • the preset RSD includes the first RSD and one or more second RSDs; or, the preset RSD includes the first RSD;
  • the first RSD is the RSD where the indication information is located; the second RSD is the RSD with a higher priority than the first RSD.
  • the present application provides a slice access device, which is used to implement the function of the terminal device in any of the foregoing aspects, or is used to implement the function of the network device in any of the foregoing aspects.
  • the present application provides a slice access device, which has the function of implementing the slice access method of any one of the foregoing aspects.
  • 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.
  • a slice access device including: a processor and a memory; the memory is used to store computer execution instructions, and when the slice access device is running, the processor executes the computer execution instructions stored in the memory, So that the slice access apparatus executes the slice access method according to any one of the above aspects.
  • a slice access device including: a processor; the processor is configured to couple with a memory, and after reading an instruction in the memory, execute the slice access method according to any one of the above aspects according to the instruction .
  • an embodiment of the present application provides a slice access device.
  • the device may be a chip system.
  • the chip system includes a processor and a memory for implementing the function of the method described in any of the above aspects.
  • the chip system can be composed of chips, or it can include chips and other discrete devices.
  • a slice access device in a tenth aspect, the device may be a circuit system, the circuit system includes a processing circuit, and the processing circuit is configured to execute the slice access method according to any one of the foregoing aspects.
  • an embodiment of the present application also provides a computer-readable storage medium, including instructions, which when run on a computer, cause the computer to execute the method of any one of the foregoing aspects.
  • the embodiments of the present application also provide a computer program product, including instructions, which when run on a computer, cause the computer to execute the method of any one of the foregoing aspects.
  • an embodiment of the present application provides a system.
  • the system includes a terminal device that executes the slice access method of any one of the first aspect and the first aspect, and a terminal device that executes the second aspect and any one of the second aspect The slice access method of the network device.
  • the system further includes a mobility management network element (for example, it may be the AMF shown in FIG. 1).
  • the mobility management network element is used to send a message from the terminal to a policy network element (that is, the network device of the fourth aspect described above), or to send a message from the policy network element to the terminal.
  • the mobility management network element is used to transparently transmit messages between the terminal and the policy network element.
  • FIG. 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the application
  • FIG. 2 is a schematic diagram of the architecture of a communication system provided by an embodiment of the application.
  • FIG. 3 is a schematic diagram of the architecture of a slice access system provided by an embodiment of the application.
  • FIG. 4 is a schematic diagram of the principle of the URSP matching process provided by an embodiment of the application.
  • FIG. 8 and FIG. 9 are schematic diagrams of the structure of the slice access device provided by the embodiment of the application.
  • first and second in the description of the application and the drawings are used to distinguish different objects, or to distinguish different processing of the same object, rather than describing a specific order of the objects.
  • At least one means one or more
  • Multiple means two or more.
  • A/B can indicate A or B.
  • Types and characteristic attributes of network slices As above, a physical network can be abstractly divided into multiple network slices, and each network slice can form an end-to-end logical network. Network slices are logically isolated from each other and do not affect each other. Generally, in order to meet different communication requirements, network slicing is divided into multiple types. For example, but not limited to enhanced mobile broadband (eMBB) type, massive machine type connection (mMTC), ultra-reliability and low latency connection (uRLLC) type . Among them, the network characteristics of different types of network slices are different.
  • eMBB enhanced mobile broadband
  • mMTC massive machine type connection
  • uRLLC ultra-reliability and low latency connection
  • the network slicing of eMBB requires the characteristics of supporting large bandwidth and low-latency services
  • the network slicing of mMTC requires the characteristics of supporting massive access and small bandwidth
  • the slicing of uRLLC requires the characteristics of high reliability and low latency. It can be seen that the types of supported application services, end-to-end delay, and the maximum rate of a single terminal, etc., all belong to the characteristic attributes of the network slice, and these characteristic attributes depend on the design of the slice.
  • a single slice access assistance information (Single network slice selection assistance information, S-NSSAI) is used to uniquely indicate a network slice.
  • Network slice selection assistance information (network slice selection assistance information, NSSAI):
  • NSSAI refers to a collection of one or more S-NSSAIs.
  • NSSAI can be used to represent one or more network slices.
  • PDU session a session service that realizes PDU connectivity between the UE and a data network (DN), which is identified by the PDU Session ID.
  • URSP Generally, when operators create required network slices for customers on the physical infrastructure of communication networks based on customer orders, they often sign service level agreements (SLAs) with customers based on business needs. ). In a PLMN of an operator, the entire network may not support the same network slice set (network slice set). Operators can divide different slice sets according to areas, or even single-point base stations. In this way, different regional networks may correspond to different slices. Therefore, in a non-roaming scenario, the user may only be able to access the required slice through a part of the home network, or in a roaming scenario, the user may only be able to access the required slice through a part of the visited network.
  • SLAs service level agreements
  • URSP is defined in the standard for user routing issues. It is mainly used to determine PDU session parameters required by different applications (applications, APPs) or services, such as network slices, data network names (DNN), session service continuity mode (session service continuity mode, SSC mode), etc.
  • applications applications, APPs
  • services such as network slices, data network names (DNN), session service continuity mode (session service continuity mode, SSC mode), etc.
  • the terminal can determine the corresponding PDU session parameters according to the network requirements of the APP or the service, and establish a PDU session based on the parameters. After that, the data of the APP or service is transmitted through the established session.
  • the URSP mainly includes traffic descriptors (Traffic descriptors) and one or more Route Selection Descriptors (RSDs) (shown in bold) in Table 1 above.
  • Traffic descriptor is used to match with service information (application ID or flow ID or service ID, etc.).
  • service information application ID or flow ID or service ID, etc.
  • a terminal modem matches the application identifier (APP ID) provided by the application layer with the traffic descriptors in each URSP rule according to the priority of one or more URSP rules from high to low.
  • Traffic descriptors such as Application descriptors in Table 1 above (such as operating system identifier (OSId) + application identifier (OSAppId), for example, WeChat under the Android operating system can be expressed as android+com.wechat), IP descriptors (For example, the destination IP address corresponding to the initiated service).
  • OSId operating system identifier
  • OSAppId application identifier
  • WeChat under the Android operating system can be expressed as android+com.wechat
  • IP descriptors For example, the destination IP address corresponding to the initiated service).
  • RSD includes DNN, S-NSSAI, SSC mode and other information.
  • URSP1 includes Traffic descriptor and 3 RSDs.
  • Traffic descriptor distinguishes different services through application identifiers or other types of identifiers.
  • RSD1 includes S-NSSAI-1
  • RSD2 includes S-NSSAI-2
  • RSD3 includes S-NSSAI-3.
  • URSP matching When the UE determines that a specific service/application needs to be initiated, it first matches the service/application to be initiated with the TrafficDescriptor in the URSP rule according to the priority order of the URSP rule.
  • the UE also needs to determine according to the current RSD of the URSP rule
  • the slice S-NSSAI required for the service and determine whether the slice S-NSSAI belongs to the Allowed NSSAI of the current network.
  • the terminal needs to determine whether the slice S-NSSAI belongs to the current Allowed NSSAI of the visited network.
  • the terminal needs to determine whether the slice S-NSSAI is within the current Allowed NSSAI of the home network.
  • the UE will continue to match the subsequent URSP rules or subsequent RSDs according to the URSP priority/RSD priority until it is determined that the slice S-NSSAI allowed for the service appears in the Allowed NSSAI and the The slice S-NSSAI is accepted by the network side. For example, when the UE determines that the URSP rule corresponding to the application ID of the initiating service is unavailable, it can continue to match the URSP rule with the lowest priority according to the priority, that is, the TrafficDescriptor shown in Figure 4(a) is a match-all URSP. rule. The URSP rule that the UE finally matches is called the target URSP rule. The RSD that the UE finally matches is called the target RSD.
  • the UE determines whether there is an existing PDU session that meets the target RSD definition.
  • the UE can choose to initiate a PDU based on the existing PDU session
  • a session modification request (PDU Session Modification Request) is used to establish a new quality of service flow (QoS flow) on an existing PDU session, and to carry services through the newly created QoS flow.
  • the PDU session modification request message can be carried by the N1 SM Container.
  • the PDU session modification request includes (or carries) the PDU Session ID, packet filters, and requested QoS parameters (Requested QoS).
  • the PDU Session ID is used to associate the AMF with a specific session context, and the N1 SM Container of the terminal is transparently transmitted from the AMF to the SMF.
  • the UE will initiate a PDU session establishment request for the service/application, and carry the newly allocated PDU Session ID in the session establishment request message, which is in the RSD DNN, S-NSSAI, N1 SM Container (SSC mode, PDU Session Type) and other parameters.
  • the newly allocated PDU Session ID is used to identify the PDU session corresponding to the PDU session establishment request
  • DNN+S-NSSAI is used as a parameter for AMF to select the SMF entity for the PDU session establishment request
  • N1 SM Container is transparently transmitted by AMF To the selected SMF.
  • the V2X service needs to access URLLC-type slices.
  • the URSP1 rule provided by the home network for the terminal includes three RSDs, which are three slice information corresponding to V2X, and these three slices are all URLLC type slices.
  • the visited network currently accessed by the UE may not deploy URLLC-type slices, that is, the Allowed NSSAI received by the UE does not include the URLLC slices it needs to access.
  • the slices corresponding to S-NSSAI-4 and S-NSSAI-5 supported by the first network are not of URLLC type.
  • the UE When it is determined that the V2X service needs to be initiated, the UE first matches the TrafficDescriptor, and the UE uses the service information to be initiated, such as the V2X service identifier and the TrafficDescriptor in one or more URSP rules stored locally Perform matching and determine that the Traffic Descriptor in URSP1 is consistent with the service to be initiated, and the UE continues to match the RSD in URSP1.
  • the UE first matches the S-NSSAI-1 according to the priority order, and finds that the S-NSSAI-1 does not belong to the Allowed NSSAI.
  • the UE continues to match the subsequent S-NSSAI-2, and finds that the S-NSSAI-2 does not belong to Allowed NSSAI, and so on, until all the RSDs in the URSP1 are matched, the UE finds None of the S-NSSAI indicated by the URSP1 is supported by the current network, that is, none of them are in the Allowed NSSAI of the current network.
  • the UE will continue to match subsequent URSP rules according to the priority of the URSP rule until it matches the default URSP rule with the lowest priority (also called a wildcard URSP rule).
  • the slice information included in the default URSP rule is eMBB type slice information.
  • the UE will establish a PDU session according to the eMBB type slice information, and the established PDU session may not meet the V2X service requirements.
  • an embodiment of the present application provides a slice access method.
  • the slice access method in the embodiment of the present application will be described in detail as follows.
  • the slice access method provided in the embodiments of the present application is applied to a communication system that uses network slices for communication.
  • a communication system For example, 5G system, or subsequent evolution system or other systems.
  • the communication system includes: network exposure function (NEF), policy control function (PCF), application function (AF), unified data management (UDM), user database ( User data repository, UDR), access and mobility management function (core access and mobility management function, AMF), session management function (session management function, SMF), access network (access network, AN) network elements.
  • AN includes network elements or equipment such as wired access network and radio access network (RAN), user plane function (UPF), DN network element, and terminal UE.
  • the terminal accesses the AN in a wireless or wired manner.
  • the wireless method can be, for example, access via wireless-fidelity (WiFi), or access to the AN via a cellular network (e.g., E-UTRA, NR, etc.).
  • WiFi wireless-fidelity
  • a cellular network e.g., E-UTRA, NR, etc.
  • the terminal communicates with AMF through N1; AN communicates with UPF through N3, AN communicates with AMF through N2; UPF communicates with SMF through N4, UPF communicates with DN network element through N6; AMF communicates with UDM through N8; SMF communicates with AMF through N11 , SMF communicates with UDM through N10, SMF communicates with PCF through N7; AMF communicates with AUSF through N12 (not shown in Figure 1), and AUSF communicates with UDM through N13 (not shown in Figure 1). AF communicates with PCF through N5.
  • UDM communicates with UDR through N35.
  • UDM communicates with AF/NEF through N52.
  • UDR communicates with PCF through N36.
  • AMF communicates with PCF through N15.
  • AF/NEF refers to the interaction between the AF and the core network element via the NEF.
  • AF It mainly conveys the requirements of the application side on the network side, for example, QoS requirements or user status event subscriptions.
  • AF can be a third-party functional entity, or an application service deployed by an operator, such as an IMS voice call service.
  • application function entities of third-party applications when interacting with the core network, they can also be authorized by NEF.
  • a third-party AF sends a request message to NEF, and NEF determines whether the AF is allowed to send the request message. If the verification passes , The request message will be forwarded to the corresponding PCF or UDM.
  • UDM Mainly responsible for the management of contract data, user access authorization and other functions.
  • UDR Mainly responsible for the access function of contract data, strategy data, application data and other types of data.
  • UDR can also add the corresponding S-NSSAI to the user's Subscribed NSSAI, and at the same time increase the bandwidth, QoS guarantee and other subscription values allowed by the user under the S-NSSAI.
  • PCF It is mainly responsible for policy control functions such as charging for session and service flow level, quality of service (QoS) bandwidth guarantee and mobility management, UE policy decision-making.
  • AMF Access and mobility control
  • SM PCF PCF for session management
  • AM PCF and SM PCF may not be the same PCF entity.
  • SMF Mainly perform functions such as session management, execution of PCF issuing control policies, selection of UPF, and UE Internet Protocol (IP) address allocation.
  • IP Internet Protocol
  • AMF Mainly perform functions such as mobility management and access authentication/authorization. In addition, it is also responsible for transferring user policies between UE and PCF.
  • UPF As the interface UPF with the data network, it completes the functions of user plane data forwarding, session/stream-based billing statistics, and bandwidth limitation.
  • AN Corresponding to different access networks, such as wired access, wireless base station access and other methods.
  • N7 The interface between PCF and SMF, used to issue PDU session granularity and service data flow granularity control strategy.
  • N15 The interface between PCF and AMF, used to issue UE policies and access control related policies.
  • N5 The interface between AF and PCF, used for application service request issuance and network event reporting.
  • N4 The interface between SMF and UPF, used to transfer information between the control plane and the user plane, including controlling the issuance of user-oriented forwarding rules, QoS control rules, traffic statistics rules, etc., and user-plane information reporting .
  • N11 The interface between SMF and AMF, used to transfer PDU session tunnel information between AN and UPF, transfer control messages sent to UE, transfer radio resource control information sent to AN, etc.
  • N2 The interface between AMF and RAN, used to transfer radio bearer control information from the core network side to the AN.
  • N1 The interface between the AMF and the UE, which has nothing to do with access, and is used to deliver QoS control rules to the UE.
  • N8 The interface between AMF and UDM, used for AMF to obtain access and mobility management related subscription data and authentication data from UDM, and AMF to register UE current mobility management related information with UDM, etc.
  • N9 Used for user plane data forwarding between UPF and UPF.
  • N10 The interface between SMF and UDM, used for SMF to obtain session management related subscription data from UDM, and SMF to register UE current session related information with UDM, etc.
  • N35 The interface between UDM and UDR, used for UDM to obtain user subscription data information from UDR.
  • N36 Interface between PCF and UDR, used for PCF to obtain policy-related contract data and application data-related information from UDR.
  • the terminals involved in the embodiments of this application may include various handheld devices with communication functions, wearable devices, computing devices, or other processing devices connected to a modem; and may also include personal digital assistants (personal digital assistants). , PDA) computers, tablet computers, laptop computers, machine type communication (MTC) terminals, user equipment (UE), etc.
  • PDA personal digital assistant
  • MTC machine type communication
  • UE user equipment
  • a terminal it can also refer to a chip system such as a UE.
  • the embodiment of the present application does not limit the implementation form of the terminal.
  • the above-mentioned network elements can communicate in a certain way (for example, the terminal communicates with AMF through N1).
  • the terminal communicates with AMF through N1.
  • the above only lists some of the ways of communication between network elements. In order to simplify the description, In the embodiment of the present application, the communication mode between other network elements will not be described in detail.
  • the names of the various network elements and the names of the interfaces between the various network elements in Figure 1 are just an example.
  • the names of the various network elements or the interfaces between the various network elements may be other names or network elements. It can also be called an entity, which is not specifically limited in the embodiments of the present application. All or some of the network elements in Figure 1 may be physical physical network elements, or virtualized network elements, which are not limited here.
  • the architecture may also include other network elements, such as operation management (OAM) network elements, network slice selection function (NSSF), network repository function (NRF) ), authentication server function (authentication server function, AUSF), etc.
  • OAM operation management
  • NSSF network slice selection function
  • NRF network repository function
  • authentication server function authentication server function, AUSF
  • the 5G communication system shown in FIG. 1 includes a system in a non-roaming scenario and a system in a roaming scenario.
  • the system of each scenario may be a system based on a service-oriented interface, or a system based on a reference point.
  • the specific description based on the service-oriented interface and the reference point can refer to the prior art, which will not be repeated here.
  • the embodiment of this application mainly introduces the roaming architecture.
  • the technical solution of this application is also applicable to the non-roaming architecture.
  • the non-roaming architecture please refer to the prior art, which will not be repeated here.
  • the 3GPP standard defines two roaming modes for users to access in visited places, namely, home-routed roaming and local breakout roaming.
  • the functions of some network elements, the interfaces between the network elements, and other information can refer to the related description of the architecture shown in Figure 1, which will not be repeated here.
  • certain network elements are divided into two parts. Some are located in the home public land mobile network (HPLMN), and some are located in the visited public land mobile network (VPLMN).
  • HPLMN home public land mobile network
  • VPN visited public land mobile network
  • the network elements respectively deployed in the visited and home locations can be used to obtain corresponding network services.
  • PCF is divided into V-PCF (that is, PCF in the visited place) and H-PCF (that is, PCF in the home place).
  • SMF is divided into V-SMF and H-SMF.
  • FIG. 2(a) for the roaming architecture of home access roaming.
  • AMF and H-SMF are located in the visited place and the home place, respectively, and the session management function is performed by the home place H-SMF that supports interaction with UDM/H-PCF.
  • the H-PCF connected to the V-PCF and the H-PCF connected to the H-SMF may not be the same PCF entity in actual scenarios.
  • FIG. 2(b) shows the roaming architecture of local access roaming.
  • both AMF and SMF are located in the visited place.
  • the session management function is performed by the SMF of the visited place.
  • the V-PCF connected to the AMF and the V-PCF connected to the SMF may not be the same PCF entity in actual scenarios.
  • (b) of FIG. 2 includes a short message function (short messaging service function, SMSF). SMSF communicates with UDM through N21, and communicates with AMF through N20.
  • SMSF short messaging service function
  • a certain network element obtains information from another network element (for example: B network element), which may mean that A network element directly receives information from B network element, or It means that A network element receives information from B network element via other network elements (for example: C network element).
  • B network element may mean that A network element directly receives information from B network element, or It means that A network element receives information from B network element via other network elements (for example: C network element).
  • C network element can transparently transmit the information, or process the information, for example: carry the information in different messages for transmission or filter the information , Only send the filtered information to A network element.
  • network element A when network element A sends information to network element B, it can mean that network element A sends information directly to network element B, or it can mean that network element A sends information to network element B via other network elements (for example, network element C). Yuan) to send information to the B network element.
  • the system 300 includes: a terminal 301 and a policy network element 302.
  • the Policy network element 302 used to send URSP to the terminal.
  • This URSP is different from the prior art URSP.
  • the URSP includes indication information, and the indication information is used to indicate to match one or more preset URSP rules, or to indicate to match one or more preset RSDs.
  • the preset URSP rule and the preset RSD can refer to the following embodiments for details.
  • Terminal 301 used to perform URSP matching according to the URSP from the policy network element 302.
  • S-NSSAIs corresponding to one or more preset URSPs are not supported by the first network, or one or more S-NSSAIs corresponding to one or more preset RSDs are not supported Not supported by the first network, stop URSP matching. In this way, it is possible to reduce the probability that the subsequent matching to a slice that is not suitable for the service will cause the terminal service to fail.
  • the slice access system further includes: a mobility management network element 304 and a data network element 303.
  • Mobility management network element 304 used to send a message from the terminal 301 to the policy network element 302, or to send a message from the policy network element 302 to the terminal 301.
  • the mobility management network element 304 is used to transparently transmit a message between the terminal 301 and the policy network element 302.
  • Data network element 303 used to store some data, which can be used for policy network elements to formulate URSP, or for other network elements to obtain user-related information.
  • the data network element in Figure 3 can be the UDM in Figure 1 or Figure 2 or other network elements with similar functions, and can also be UDR or other network elements with similar functions.
  • the mobility management network element can be as shown in Figure 1.
  • the AMF in Fig. 2 or other network elements with similar functions and the strategic network element may be the PCF in Fig. 1 or the H-PCF in Fig. 2 or other network elements with similar functions.
  • the connection relationship between the network elements shown in FIG. 3 may refer to the connection relationship between the corresponding network elements in FIG. 1 or FIG. 2. I won't repeat it here.
  • the slice access method provided in the embodiment of the present application includes the following steps:
  • the H-PCF determines one or more URSP rules, and at least one of the one or more URSP rules includes indication information.
  • the indication information is used to indicate to match one or more preset URSP rules, or to indicate to match one or more preset routing description RSDs.
  • the indication information may be used as the RSD granularity, located in the RSD, that is, included in the foregoing Table 2.
  • the indication information can also be used as the URSP granularity and located in the URSP Rule, that is, it is included in the foregoing Table 1.
  • the indication information is used to indicate to match one or more preset URSP rules, which means that only one or more preset URSP rules are matched, and no other URSP rules except the preset URSP rules are matched.
  • the indication information is used to indicate that one or more preset RSDs are matched, which means that only one or more preset RSDs are matched, and other RSDs other than the preset RSDs are not matched.
  • the H-PCF encapsulates the URSP rules that need to be matched into indication information, that is, all URSP rules that need to be matched include the indication information.
  • the preset URSP rule may include the URSP rule where the indication information is located (referred to as the first URSP rule in the embodiment of this application).
  • the H-PCF decision obtains URSP1, URSP2, URSP3, and the default URSP rule.
  • URSP1, URSP2, and URSP3 all include indication information
  • the preset URSP rules are URSP1, URSP2, and URSP3. Subsequently, the terminal device only matches URSP1, URSP2, and URSP3.
  • the specific content of the indication information may be changed.
  • the last URSP rule that needs to be matched can contain indications that can be the same as the indications included in the previous URSP rule (that is, the URSP rule with a higher priority than the last URSP rule). different.
  • the last URSP rule to be matched is URSP3.
  • URSP1 and URSP2 include the same indication information, and the indication information included in URSP3 may be different from the indication information included in URSP1.
  • URSP3 includes indication information with a value of 0, URSP1 includes indication information with a value of 1, and URSP2 also includes indication information with a value of 1.
  • the indication information included in the last URSP rule to be matched may be consistent with the indication information included in the previous URSP rule (that is, the URSP rule with a higher priority than the last URSP rule).
  • URSP3 includes indication information with a value of 1, and both URSP1 and URSP2 include indication information with a value of 1.
  • the H-PCF encapsulates the last URSP rule among the URSP rules to be matched into the indication information.
  • the preset URSP rule may include the first URSP rule (the first URSP rule is the URSP rule where the indication information is located) and one or more second URSP rules (the second URSP rule is higher in priority than the first URSP rule). Rules of URSP rules).
  • URSP1 high priority
  • URSP2 medium priority
  • URSP3 low priority
  • the first URSP rule is URSP2
  • the second URSP rule is URSP1.
  • the first URSP rule is URSP3, the second URSP rule with higher priority than URSP3, namely URSP1 and URSP2.
  • the first RSD mentioned in the embodiment of this application refers to the RSD where the indication information is located.
  • the second RSD it usually refers to an RSD with a higher priority than the first RSD.
  • the second RSD that is, the RSD with a higher priority than the first RSD, includes the RSD in the current URSP rule with a higher priority than the first RSD, and the RSD in other URSP rules with a higher priority than the current URSP rule.
  • the first RSD is RSD5 where the indication information is located
  • the second RSD is RSD4 with priority higher than RSD5 in the current URSP rule (that is, URSP2 where RSD5 is located), and the priority is higher than
  • the URSP1 of the URSP2 includes RSD1 to RSD3.
  • the preset URSP rule may include the first URSP rule (that is, the URSP rule where the indication information is located) and one or more second URSP rules (that is, the URSP rule with a higher priority than the first URSP rule).
  • the H-PCF decision to obtain URSP1, URSP2, and the default URSP rule referring to (c) of FIG. 4, the H-PCF decision to obtain URSP1, URSP2, and the default URSP rule.
  • only URSP2 includes the indication information
  • the preset URSP rule includes the URSP rule where the indication information is located (that is, URSP2) and URSP1 with a higher priority than URSP2.
  • the terminal device only matches the preset URSP rule, that is, only matches URSP1 and URSP2.
  • the indication information may be located in the RSD.
  • the preset RSD may refer to the first RSD (that is, the RSD where the indication information is located) and one or more second RSDs (RSDs with a higher priority than the first RSD).
  • the H-PCF decision obtains URSP1, URSP2, URSP3, and the default URSP rule.
  • only RSD5 of URSP2 includes the indication information
  • the preset RSD includes the RSD where the indication information is located (ie, RSD5) and RSD1 to RSD4 with a priority higher than RSD5.
  • the terminal device only matches the preset RSD, that is, only matches RSD1 to RSD5.
  • the preset URSP rule includes the first RSD, that is, includes the RSD where the indication information is located.
  • RSD1, RSD2, RSD3, RSD8, and RSD9 all include indication information
  • the preset RSD includes RSD1, RSD2, RSD3, RSD8, and RSD9 where the indication information is located.
  • the terminal device only matches the preset RSD, that is, only matches RSD1, RSD2, RSD3, RSD8, and RSD9.
  • the preset URSP rule includes a non-wildcard URSP rule, that is, a non-default URSP rule. That is, the terminal device only matches the non-default URSP rule, and does not match the default URSP rule.
  • the H-PCF decision to obtain at least 3 URSP rules namely, URSP1, URSP2, and default URSP rules.
  • the preset URSP rules are non-default URSP1, URSP2, and other non-default URSP rules.
  • the terminal device only matches the non-default URSP rule shown in (a) of FIG. 4 in the URSP matching process.
  • the instruction information can be encapsulated in a non-default URSP rule that needs to be matched, for example, see Figure 4(f).
  • the instruction information can also be encapsulated in the default URSP rule that does not need to be matched.
  • the instructions can also have other packaging methods.
  • the H-PCF executes the URSP rule decision based on one or more of user subscription information, the current location of the terminal device, and local pre-configuration.
  • the H-PCF sends one or more URSP rules to the terminal device.
  • the terminal device receives one or more URSP rules from the network device.
  • the H-PCF determines whether the URSP rule of the terminal device needs to be updated or added according to the URSP policy section ID (PSI) reported by the terminal device.
  • the H-PCF sends one or more URSP rules to the terminal device.
  • at least one URSP rule in the one or more URSP rules includes the foregoing indication information.
  • the H-PCF first sends the one or more URSP rules to the AMF, and the AMF then sends the one or more URSP rules to the terminal device through the (R)AN.
  • H-PCF sends the one or more URSP rules to AMF by calling the Namf_Communication_N1N2MessageTransfer service provided by AMF.
  • the AMF determines that the UE is currently in an idle state, the AMF initiates a network-triggered service request process (network triggered service request) to trigger the terminal device to recover from the idle state to the connected state.
  • the AMF sends the above-mentioned one or more URSP rules to the terminal device in the connected state through the RAN.
  • the slice access method of the embodiment of the present application may further include the following steps:
  • the terminal device sends a first confirmation message to the AMF.
  • the AMF receives the first confirmation message from the terminal device.
  • the terminal device After receiving the URSP rule from the H-PCF, the terminal device sends a first confirmation message to the AMF.
  • the first confirmation message is used to indicate that the terminal device has received the one or more URSP rules.
  • the terminal device sends the first confirmation message to the AMF through the (R)AN.
  • This S503 is an optional step.
  • the AMF sends a first confirmation message to the H-PCF.
  • the H-PCF receives the first confirmation message from the AMF.
  • the AMF returns the Namf_Communication_N1MessageNotify service response to send the first confirmation message to the H-PCF.
  • This S504 is an optional step.
  • S505 Perform URSP matching according to one or more URSP rules.
  • the terminal device performs URSP matching.
  • the terminal device needs to match the service information, that is, the terminal device needs to determine the URSP rule for the current service to be initiated matching or the RSD for the current service to be initiated matching.
  • the terminal modem compares the application ID provided by the application layer with the above-mentioned URSP rules according to the priority of one or more URSP rules from high to low. Match the traffic descriptors in respectively. Among them, the matched URSP rule is called the URSP rule matched by the current service to be initiated.
  • the RSD included in the URSP rule matching the current service to be initiated is called the RSD matching the current service to be initiated.
  • the one or more URSP rules received by the terminal device from the H-PCF include URSP1, URSP2, URSP3, default URSP rules, and the like.
  • the terminal device initiates a V2X service, and the URSP rules matching the current service to be initiated among the one or more preset URSPs determined by the terminal device are URSP1 and URSP2.
  • the terminal device initiates a V2X service, and the RSDs matching the current service to be initiated among one or more preset RSDs are RSD1 to RSD3.
  • the terminal may also use other methods when performing URSP matching based on service information, such as based on the domain name information corresponding to the service to be initiated, the destination server IP address information, etc., or the modem layer directly performs the above matching actions without application layer participation.
  • service information such as based on the domain name information corresponding to the service to be initiated, the destination server IP address information, etc., or the modem layer directly performs the above matching actions without application layer participation.
  • the embodiments of this application do not limit this.
  • S-NSSAI is not supported by the first network, which means that S-NSSAI is not in the Allowed NSSAI of the first network. Or, although the S-NSSAI is in the Allowed NSSAI, the Allowed NSSAI received by the terminal device may not be updated. Or, after the terminal device initiates a PDU session establishment request, it receives a rejection reason value from the network side, and the reason value indicates that the S-NSSAI does not support access temporarily. Or other situations that are not supported by the first network.
  • the first network refers to the current network of the terminal.
  • the preset URSP rules are URSP1, URSP2, and URSP3. Then the terminal device only matches URSP1, URSP2, and URSP3 when executing the URSP matching process. Wherein, when the terminal device matches the URSP3, according to the traffic descriptor (ie wechat) in the URSP3, it is determined that the URSP3 is not the URSP rule matching the V2X service currently to be initiated. When the terminal device matches UPSR1 and URSP2, it is found that S-NSSAI-1 to S-NSSAI-7 corresponding to URSP1 and URSP2 are not in the Allowed NSSAI of the first network. In this case, the terminal device stops the URSP matching and does not continue to match.
  • follow-up URSP rules In this case, the terminal device can try to access at least one required slice.
  • the indication information included in the last URSP rule (that is, URSP3) to be matched may be the same or different from the indication information included in the high-priority URSP rule.
  • URSP3 includes indication information with a value of 1
  • both URSP1 and URSP2 include indication information with a value of 1.
  • the terminal device may not be able to know whether the URSP3 is the last URSP rule to be matched when the URSP3 is matched, and it needs to unblock the next URSP rule. If the terminal device determines that the next URSP rule does not include the indication information, it means that the next URSP rule is not a preset URSP rule, and the terminal device does not need to match the URSP rule.
  • URSP3 includes indication information with a value of 0, and both URSP1 and URSP2 include indication information with a value of 1.
  • the terminal device since the indication information included in the last URSP rule (i.e. URSP3) is different from the previous URSP rules (URSP1 and URSP2), the terminal device can know that the URSP3 is the last one to be matched when it matches the URSP3. URSP rules. In this way, the terminal device does not need to unblock the next URSP rule, which reduces the operations that the terminal device needs to perform, and the implementation process is simpler.
  • the preset RSD (that is, the RSD where the indication information is located) is RSD1, RSD2, RSD3, RSD8, and RSD9. Then the terminal device only matches RSD1, RSD2, RSD3, RSD8, and RSD9 when performing the URSP matching process. Specifically, when the terminal device is matched to RSD8 and RSD9, it is found that the RSD8 and RSD9 are not the RSD that is currently matched by the service to be initiated.
  • the terminal device matches RSD1, RSD2, RSD3, it is determined that the S-NSSAI-1, S-NSSAI-2, and S-NSSAI corresponding to RSD1, RSD2, and RSD3 are not in the Allowed NSSAI of the first network, and the terminal device stops URSP Match, no longer continue to match the subsequent RSD.
  • the terminal can receive indication information from the network device, so as to trigger URSP matching when it needs to initiate a service, and only match the preset URSP indicated by the indication information, or may not match the indication information.
  • the indicated preset URSP In this way, the number of URSPs that need to be matched can be reduced, and the matching slice information that has been matched with the URSP is not suitable for service requirements, and the PDU session established accordingly cannot support the service to be initiated, resulting in the probability of terminal service failure.
  • S506 The terminal device executes the mobility change process.
  • the terminal device may perform the mobility change process.
  • the terminal device is switched from the first network to the second network, or registered to the second network.
  • the terminal device can also request access to at least one of the above-mentioned one or more S-NSSAIs (that is, service required access) in the second network through the following registration process one.
  • the second network is a network that supports at least one of one or more S-NSSAIs.
  • the terminal device executes the mobility change process according to one or more of the following information: local configuration, monitored broadcast information, and network selection auxiliary information.
  • the network selection auxiliary information includes one or more of the following information:
  • the target slice set is one or more slices corresponding to the target NSSAI;
  • the target NSSAI includes one or more of the following: the NSSAI (ie Requested NSSAI) corresponding to the network slice requested by the terminal device, and the network slice corresponding to the terminal device's access denied
  • the NSSAI ie Rejected NSSAI
  • the NSSAI ie Allowed NSSAI
  • the network selection assistance information in the embodiment of the present application can be divided into two types.
  • the target slice is Requested NSSAI
  • the network selection auxiliary information is called the first network selection auxiliary information.
  • the network selection auxiliary information is called the second network selection auxiliary information.
  • the first network selection auxiliary information and the second network selection auxiliary information please refer to the embodiments corresponding to FIG. 6 and FIG. 7 below.
  • the general term of network selection auxiliary information is still used here.
  • the network selection assistance information may be in the form of a list of PLMN IDs (S-NSSAI: Preferred PLMN ID List) preferred by the S-NSSAI.
  • the network selection assistance information may be in the form of an S-NSSAI list (Precedence, PLMN ID, Supported S-NSSAI list).
  • Precedence refers to the priority of each PLMN
  • the PLMN ID is the identification of one or more PLMNs that support one or more slices in the target slice set
  • the Supported S-NSSAI list is the S-NSSAI list supported by the corresponding PLMN.
  • the target slice set is one or more slices identified by Requested NSSAI, such as slice 1 to slice 3 (respectively corresponding to S-NSSAI-1 to S-NSSAI-3).
  • the PLMN-identified list represents network selection assistance information
  • the list can be (S-NSSAI-1: PLMN1, PLMN 2; S-NSSAI-2: PLMN 1, PLMN 3; S-NSSAI-3: PLMN 4, PLMN 2, PLMN3).
  • the list may also include the priority of the one or more PLMNs.
  • the list can be (S-NSSAI-1: PLMN 1 (high priority), PLMN 2 (low priority); S-NSSAI-2: PLMN 1 (high priority), PLMN 3 (low priority) ; S-NSSAI-3: PLMN 4 (high priority), PLMN 2 (medium priority), PLMN 3 (low priority)).
  • the priority can also be indicated in other ways, such as a numerical value. The smaller the numerical value, the higher the priority. The higher the value, the higher the priority. The embodiments of this application do not make limitations.
  • the list also includes S-NSSAIs respectively supported by the one or more PLMNs.
  • the list can be (high priority, PLMN 1, S-NSSAI-1, S-NSSAI-2; high priority, PLMN 2, S-NSSAI-1, S-NSSAI-4; low priority, PLMN 3, S-NSSAI-3, S-NSSAI-2).
  • the monitored broadcast information of the surrounding network includes slice information supported by the surrounding network.
  • the broadcast information includes supported slice information broadcast by neighboring cells.
  • the terminal device can determine whether the surrounding network supports the access of the slice required by it, and when a certain network (such as the second network) is determined Supporting the slicing, the terminal device triggers the mobility change process to the second network (that is, accesses the second network through the handover/mobility registration process).
  • the terminal device may continue to request the S-NSSAI corresponding to the required slice in the second network, that is, request at least one of the above-mentioned one or more S-NSSAIs. Exemplarily, as shown in FIG.
  • the terminal device when the terminal device initiates a service and performs URSP matching, it reads the instruction information and learns that only the URSP1 and URSP2 are matched, and there is no need to match subsequent URSP rules. After matching URSP1 and URSP2, the terminal device learns that all S-NSSAI-1 to S-NSSAI-7 required by the service are not in the Allowed NSSAI of the first network. In this case, in order to access the required at least one slice, the terminal device may perform a mobility change process, register or switch to a second network that supports the required at least one slice. As shown in (b) of Figure 4, the terminal device can register or switch to a second network that supports S-NSSAI-1 and S-NSSAI-2.
  • the terminal device may send a registration request message to the second network. Specifically, if the switching method described above is adopted, the terminal device first performs the switching, and after switching from the first network to the second network, triggers the registration process to the second network. Or, if the above-mentioned registration method is adopted, the terminal device directly registers with the second network from the first network through the registration process.
  • the terminal device may send a registration request to the second network, and the registration request message includes Requested NSSAI.
  • Requested NSSAI includes at least one of the above-mentioned one or more S-NSSAIs, that is, includes at least one required S-NSSAI.
  • the terminal device only matches S-NSSAI-1 to S-NSSAI-3 in URSP1, and these three S-NSSAIs are not in the Allowed NSSAI of the first network, and the Requested NSSAI sent by the terminal device to the second network includes At least one of S-NSSAI-1 to S-NSSAI-3.
  • the registration distance can also be used to update the UE context and other information in the second network.
  • the order of execution of one or more of the above steps is not limited, for example, the order of execution of S505 and S506, for example, the order of execution between S504 and S505.
  • the terminal device when selecting session parameters for the PDU session, in addition to the URSP rules and the Allowed NSSAI information, it also refers to the information about whether the surrounding network at the current location of the UE supports the required slice. And, it can determine whether to trigger the mobility change process to the neighboring network. In this way, the terminal device can access the required slice (that is, at least one of the slices respectively corresponding to S-NSSAI-1 to S-NSSAI-3) through the second network, and establish a PDU session in the required slice. Because the required slice information (including S-NSSAI, DNN, etc.) is determined according to the service information in the URSP matching process, the PDU session established according to the required slice information can meet the service requirements of the terminal device. The probability of service failure due to the terminal device matching the slice information that is not suitable for the service is reduced.
  • the terminal device uses the aforementioned network selection assistance information, it can also refer to the support status of the S-NSSAI corresponding to the currently established PDU session in the second network, so as to avoid the impact on the currently ongoing service.
  • the slice to be accessed by the UE is S-NSSAI 3
  • the current existing session is PDU Session 1 (corresponding to parameter S-NSSAI 1)
  • PDU Session 2 corresponding to parameter S-NSSAI 2
  • the terminal device may not perform the above-mentioned S505, that is, not trigger the mobility change process to the second network, but abandon the above-mentioned service to be initiated. After receiving the updated Allowed NSSAI that contains the required S-NSSAI, the terminal device initiates the corresponding service again.
  • a method for determining the first network selection auxiliary information includes:
  • the terminal device initiates a registration request to the AMF.
  • the AMF receives the registration request from the terminal device.
  • the registration request may be an initial registration request, or a mobility registration request, or other possible registration requests.
  • the registration request includes Requested NSSAI.
  • the Requested NSSAI is determined based on one or more of the following information: Configured NSSAI configured by the home network, Allowed NSSAI in the last registration process of the terminal device, and other configuration information.
  • the registration request is used to request access to one or more slices indicated by the Requested NSSAI from the network side.
  • the AMF sends a first policy creation/update request to the H-PCF.
  • the H-PCF receives the first policy creation/update request from the AMF.
  • the AMF calls the Npcf_UEPolicyControl_Create/Update Request service of the H-PCF to send the first policy creation/update request to the H-PCF.
  • the first policy creation/update request carries the Requested NSSAI from the terminal device (that is, the above-mentioned target NSSAI), and user location information (ULI) from the (R)AN.
  • the ULI is, for example, but not limited to, a cell ID (Cell ID) and a tracking area identity (TAI).
  • AMF interacts with H-PCF through V-PCF, that is, AMF first sends a first policy creation/update request to V-PCF, and then V-PCF transfers the first policy The creation/update request is forwarded to H-PCF. If the process is initiated in a non-roaming scenario, the AMF directly interacts with the H-PCF, that is, directly sends the first policy creation/update request to the H-PCF.
  • the H-PCF determines the first network selection auxiliary information.
  • H-PCF determines the first network selection auxiliary information based on one or more of the following information: user policy subscription data obtained from UDR, the above-mentioned first policy creation/update request from AMF (including the target NSSAI, namely Requested NSSAI), local configuration information.
  • the first network selection assistance information includes information about one or more networks that support one or more S-NSSAIs in the Requested NSSAI.
  • the first network selection auxiliary information further includes the priority of the one or more networks, and/or the network slice information supported by the one or more networks respectively.
  • the H-PCF sends the first network selection auxiliary information to the AMF.
  • the AMF receives the first network selection auxiliary information from the H-PCF.
  • the H-PCF returns the Npcf_UEPolicyControl_Create/Update Response service response to send the first network selection assistance information to the AMF.
  • the H-PCF sends the first network selection assistance information to the AMF via the V-PCF. If this step occurs in a non-roaming scenario, the H-PCF directly sends the first network selection assistance information to the AMF.
  • the AMF sends the first network selection auxiliary information to the terminal device.
  • the terminal device receives the first network selection auxiliary information from the AMF.
  • the AMF sends a registration response message to the terminal device, where the registration response message includes the aforementioned first network selection assistance information.
  • the terminal device may store the first network selection auxiliary information. So that when the current network does not support the required slice, a new network supporting at least one slice is determined according to the first network selection auxiliary information, and the new network is switched or registered to the new network through the mobility change process. In this way, the terminal device can access the required at least one slice through the new network.
  • another method for determining the auxiliary information for the second network selection includes the following steps:
  • the UDM sends a subscription data update notification to the AMF.
  • the AMF receives the subscription data update notification from the UDM, and the subscription data update notification may carry the updated network slice selection assistance information (Subscribed NSSAI) of the user subscription.
  • Subscribe NSSAI Network Slice Selection assistance information
  • UDM sends a subscription data update notification to AMF through the Nudm_SDM_Notify service.
  • the terminal device sends a registration request to the AMF.
  • the AMF receives the registration request from the terminal device,
  • the registration request is the same as the registration request in Figure 6.
  • the registration request may carry the Requested NSSAI that the terminal device requests to access.
  • the order of execution of S701 and S702 is not limited. That is, S701 can be executed first, or S702 can be executed first. In addition, S701 and S702 can be executed at the same time, or only S701 or S702 can be executed.
  • the AMF determines the slice list Allowed NSSAI for which the terminal device is allowed to access and the slice list Rejected NSSAI for which the terminal device is denied access.
  • the AMF determines Allowed NSSAI and Rejected NSSAI according to one or more of the following information: local configuration, NSSF notification, the aforementioned Subscribed NSSAI, and slice information supported by the current tracking area (TA).
  • TA current tracking area
  • AMF can also update the previously determined Allowed NSSAI and Rejected NSSAI information. For example, AMF judges that some or all slices are congested or unavailable according to local configuration/NSSF notification messages and/or other information. AMF needs to guide terminal devices to access through other slices, and update the Allowed NSSAI and Rejected NSSAI information of the terminal device .
  • the AMF initiates a second policy creation/update request to the H-PCF.
  • the H-PCF receives the second policy creation/update request from the AMF.
  • the AMF invokes the Npcf_UEPolicyControl_Create/Update Request service of the H-PCF to send the second policy creation/update request to the H-PCF.
  • the second policy creation/update request may carry one or more of the following information: Allowed NSSAI, Rejected NSSAI, ULI obtained by AMF decision.
  • the AMF interacts with the H-PCF via the V-PCF. If it is a non-roaming scenario, the AMF directly interacts with the H-PCF.
  • the H-PCF determines the second network selection auxiliary information according to the second policy creation/update request.
  • the H-PCF executes a policy decision based on one or more of the following information, and determines the second network selection auxiliary information: Allowed NSSAI, Rejected NSSAI, ULI, UDR policy signing information and local configuration.
  • the second network selection assistance information is decided according to Rejected NSSAI, and the second network selection assistance information includes one or more network information supporting one or more S-NSSAIs in Rejected NSSAI; and/or the second network is decided according to Allowed NSSAI Selection assistance information, where the second network selection assistance information includes one or more network information supporting one or more S-NSSAIs in the Allowed NSSAI.
  • the second network selection assistance information includes one or more network information supporting one or more S-NSSAIs in Rejected NSSAI, and/or one or more network information supporting one or more S-NSSAIs in Allowed NSSAI.
  • the second network selection auxiliary information further includes the priority of the one or more networks, and/or slice information supported by each network.
  • the H-PCF sends the second network selection auxiliary information to the AMF.
  • the AMF receives the second network selection auxiliary information from the H-PCF.
  • the H-PCF returns the Npcf_UEPolicyControl_Create/Update Response service response to send the second network selection assistance information to the AMF. If it is a roaming scenario, the AMF forwards the second network selection assistance information to the H-PCF via the V-PCF. If it is a non-roaming scenario, the AMF directly sends the second network selection assistance information to the H-PCF.
  • the AMF sends the second network selection auxiliary information to the terminal device.
  • the terminal device receives the second network selection assistance information from the AMF.
  • the AMF sends the second network selection assistance information to the terminal device through a user configuration update request (configuration update request) or a registration response message.
  • the terminal device sends a second confirmation message (ACK) to the AMF.
  • ACK second confirmation message
  • the terminal device receives the second confirmation message from the AMF.
  • this step is optional.
  • the terminal device After receiving the second network selection assistance information, the terminal device sends a second confirmation message to the AMF to indicate that the second network selection assistance information is received.
  • each device in the foregoing method embodiments may also be implemented by a chip that can be used in the device.
  • each device includes a hardware structure and/or software module corresponding to each function.
  • the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Those skilled in the art 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 technical solutions of the embodiments of the present application.
  • the embodiments of the present application can divide functional units of terminal devices, policy network elements, etc. according to the above-mentioned method examples.
  • each functional unit can be divided corresponding to each function, or two or more functions can be integrated into one processing unit. middle.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit. It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 8 shows a schematic block diagram of a slice access apparatus provided in an embodiment of the present application.
  • the apparatus 1200 may exist in the form of software or hardware, for example, it may be a chip that can be used in a hardware device.
  • the device 1200 includes: a processing unit 1202 and a communication unit 1203.
  • the processing unit 1202 may be used to support the device 1200 to execute S505 and S506 shown in FIG. 5, and/or other processes used in the solution described herein.
  • the communication unit 1203 is used to support the communication between the device 1200 and other network elements (for example, the strategic network element H-PCF), for example, to perform S502 and S503 shown in FIG. 5, S601 and S605 shown in FIG. 6, as shown in FIG. S702, S707, S708 shown, and/or other steps of the solution described herein.
  • the processing unit 1202 may be used to support the device 1200 to perform S705 shown in FIG. 7 and/or other processes used in the solution described herein.
  • the communication unit 1203 is used to support communication between the apparatus 1200 and other network elements (such as terminals), for example, to perform S704 and S706 shown in FIG. 7 and/or other steps of the solution described herein.
  • the device 1200 may further include a storage unit 1201 for storing program codes and data of the device 1200.
  • the data may include but not limited to raw data or intermediate data.
  • the processing unit 1202 may be a processor or a controller, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processing (Digital Signal Processing, DSP), application-specific integration Circuit (Application Specific Integrated Circuit, 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 of computing functions, for example, a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the communication unit 1203 may be a transceiver, a transceiving circuit, a communication interface, or the like.
  • the storage unit 1201 may be a memory.
  • the processing unit 1202 is a processor
  • the communication unit 1203 is a communication interface
  • the storage unit 1201 is a memory
  • the structure of the slice access device involved in the embodiment of the present application may be as shown in FIG. 9.
  • FIG. 9 shows a simplified schematic diagram of a possible design structure of the slice access device involved in an embodiment of the present application.
  • the slice access device 1500 includes a processor 1502, a communication interface 1503, and a memory 1501.
  • the slice access apparatus 1500 may further include a bus 1504.
  • the communication interface 1503, the processor 1502, and the memory 1501 may be connected to each other through a bus 1504.
  • the bus 1504 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus or the like.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus 1504 can be divided into an address bus, a data bus, a control bus, and so on. For ease of representation, only one line is used in FIG. 9, but it does not mean that there is only one bus or one type of bus.
  • a person of ordinary skill in the art can understand that: in the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application are generated in whole or in part.
  • the computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • Computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • computer instructions can be transmitted from a website, computer, server, or data center through a cable (such as Coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) transmission to another 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. Available media can be magnetic media (for example, floppy disks, hard drives, tapes), optical media (for example, Digital Video Disc (DVD)), or semiconductor media (for example, Solid State Disk (SSD)), etc. .
  • the disclosed system, device, and method can be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or integrated. To another system, or some features can be ignored, or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical or other forms.
  • the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network devices (such as terminals) superior. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each functional unit may exist independently, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit may be implemented in the form of hardware, or may be implemented in the form of hardware plus software functional units.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提供一种切片接入方法、装置及系统，涉及通信技术领域，能够降低匹配到不适合当前待发起业务的切片，导致终端业务失败的概率。该切片接入方法包括：从网络装置接收一个或多个用户路由选择策略规则 URSP rule，并根据一个或多个 URSP 规则执行 URSP 匹配。URSP 规则中至少一个 URSP 规则包括指示信息; 指示信息用于指示匹配一个或多个预设 URSP 规则或匹配一个或多个预设路由选择描述 RSD。该方法应用于接入网络切片的流程中。

Description

切片接入方法、装置及系统
本申请要求于2020年05月21日提交国家知识产权局、申请号为202010437050.1、发明名称为“切片接入方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及切片接入方法、装置及系统。
背景技术
为了满足第五代(5th generation，5G)移动通信系统中的网络差异化需求，第三代合作伙伴项目(3rd generation partnership project，3GPP)提出网络切片(network slice)这一技术。将一张物理网络划分为多个逻辑网络，网络切片就是其中一个或多个逻辑网络的合称。终端可以接入网络切片，并借助网络切片(逻辑网络)执行业务。
目前，终端主要根据用户路由选择策略(user equipment route selection policy，URSP)的匹配结果确定当前业务需使用哪些切片。具体的，终端根据一个或多个URSP确定业务所需使用切片对应的单个网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)，并判断该S-NSSAI是否包含在当前网络所允许的网络切片选择辅助信息(allowed network slice selection assistance information，allowed NSSAI)之内。若当前URSP指示的S-NSSAI未出现在allowed NSSAI中，或终端设备根据该S-NSSAI所发起的会话建立请求被网络侧拒绝，且拒绝原因值显示不支持UE接入该S-NSSAI，终端将根据URSP优先级继续执行URSP匹配，直至确定适用于该业务的某一URSP指示的S-NSSAI(称为目标S-NSSAI)出现在allowed NSSAI中且被网络侧所接受。或者，当与该当前待发起业务匹配的全部非通配URSP所指示的S-NSSAI均不在allowed NSSAI中或未被网络侧接受，则终端通过通配URSP指示的S-NSSAI及allowed NSSAI确定需使用哪个切片。
上述情况下，虽然终端能够确定需使用哪个切片，但由于UE实际需要接入的切片可能并未在当前接入网络的当前区域部署，因此最终所确定的目标S-NSSAI或者通配URSP指示的S-NSSAI很可能无法满足终端的业务需求。
发明内容
本申请实施例提供切片接入方法、装置及系统，能够降低匹配到不适合当前待发起业务的切片，导致终端业务失败的概率。
为达到上述目的，本申请实施例采用如下技术方案：
第一方面，本申请实施例提供一种切片接入方法，该方法由终端装置执行。终端装置可以指终端设备，也可以指终端设备中的组件(比如芯片系统)。该方法包括：
从网络装置接收一个或多个用户路由选择策略规则URSP rule，并根据一个或多个URSP规则执行URSP匹配。其中，URSP规则中至少一个URSP规则包括指示信息；指示信息用于指示匹配一个或多个预设URSP规则或匹配一个或多个预设路由选择描述RSD。
其中，指示信息用于指示匹配一个或多个预设URSP规则，指的是，仅匹配一个或多个预设URSP规则，不匹配除预设URSP规则之外的其他URSP规则。类似的，指示信息用于指示匹配一个或多个预设RSD，指的是，仅匹配一个或多个预设RSD，不匹配除预设RSD之外的其他RSD。
采用上述切片接入方法，终端可以从网络装置接收指示信息，从而在需要发起业务时，触发URSP匹配，并仅匹配指示信息所指示的预设URSP，或者可以不匹配指示信息所指示的预设URSP。如此，能够降低所需匹配URSP的数量，并且，降低一直匹配URSP导致匹配到的切片信息不适合业务所需，据此建立的PDU会话无法支持所需发起的业务，以致终端业务失败的概率。
在一种可能的设计中，根据一个或多个URSP规则执行URSP匹配，包括：
若一个或多个预设URSP规则中与当前待发起业务匹配的URSP规则对应的一个或多个单个网络切片选择辅助信息S-NSSAI均不被第一网络支持，停止URSP匹配。或者，若一个或多个预设RSD中与当前待发起业务匹配的RSD对应的一个或多个S-NSSAI均不被第一网络支持，停止URSP匹配。
其中，URSP规则包括一个或多个RSD，RSD包括S-NSSAI。
S-NSSAI不被第一网络支持，指的是S-NSSAI不在第一网络的Allowed NSSAI中。或，S-NSSAI虽然在Allowed NSSAI中，但终端装置接收的该Allowed NSSAI可能是未更新的。或者，终端装置发起PDU会话建立请求后，接收到网络侧拒绝原因值，且该原因值指示该S-NSSAI暂不支持接入。或其他不被第一网络支持的情况。第一网络指的是终端的当前接入网络。
在一种可能的设计中，方法还包括：通过移动性变更流程接入第二网络，并在第二网络中请求一个或多个S-NSSAI中的至少一个。
其中，第二网络为支持一个或多个S-NSSAI中至少一个的网络。
具体的，终端装置通过移动性变更流程，终端装置由第一网络切换到第二网络，或者，注册到第二网络。
此外，与常规移动性管理流程不同，本申请实施例中，终端装置在接入第二网络之后，还可以通过如下注册流程在第二网络中请求接入上述一个或多个S-NSSAI(即业务所需接入)中至少一个。以便于接入至少一个所需切片。
具体的，若采用上述切换方式，则终端装置先执行切换，由第一网络切换至第二网络之后，触发向第二网络的注册流程。或者，若采用上述注册方式，则终端装置直接通过注册流程，由第一网络注册到第二网络。在向第二网络中的注册流程中，终端装置可以向第二网络发送注册请求，注册请求消息包括Requested NSSAI。Requested NSSAI包括上述一个或多个S-NSSAI中的至少一个，即至少包括一个所需S-NSSAI。示例性的，终端装置仅匹配URSP1中的S-NSSAI-1至S-NSSAI-3，且这三个S-NSSAI均不在第一网络的Allowed NSSAI，终端装置向第二网络发送的Requested NSSAI包括S-NSSAI-1至S-NSSAI-3中的至少一个。可选的，该注册路程还可以用于更新第二网络中的UE上下文等信息。
采用上述移动性变更方法，在为PDU会话选择会话参数时，除根据URSP规则、Allowed NSSAI信息外，还参考了UE当前位置周边网络是否支持所需切片这一信息。 并且，能够判断是否触发向相邻网络的移动性变更流程。如此，终端装置可以通过第二网络接入所需切片(即S-NSSAI-1至S-NSSAI-3分别对应的切片中的至少一个)，并在所需切片内建立PDU会话。因为所需切片信息(包括S-NSSAI、DNN等信息)是在URSP匹配流程中根据业务信息确定的，所以，根据所需切片信息建立的PDU会话能够满足终端装置的业务需求。降低了终端装置因匹配到不适合业务的切片信息，导致业务失败的概率。
在一种可能的设计中，方法还包括：获取网络选择辅助信息，网络选择辅助信息包括如下一项或多项信息：
支持目标切片集内一个或多个切片的一个或多个网络的信息、一个或多个网络的优先级、一个或多个网络分别支持的网络切片信息。
目标切片集为目标NSSAI对应的一个或多个切片；目标NSSAI包括如下一种或多种：终端装置所请求网络切片对应的NSSAI、拒绝终端装置接入的网络切片对应的NSSAI、允许终端装置接入的网络切片对应的NSSAI。
在一种可能的设计中，终端装置根据如下一项或多项信息，执行移动性变更流程：本地配置、监听到的广播信息、网络选择辅助信息。
第二方面，本申请实施例提供一种切片接入方法，该方法由网络装置执行。网络装置可以指网络设备，也可以指网络设备中的组件(比如芯片系统)。该方法包括：
确定指示信息，并向终端装置发送指示信息。其中，指示信息用于指示匹配一个或多个预设URSP规则或匹配一个或多个预设路由选择描述RSD。
在一种可能的设计中，网络装置确定指示信息，包括根据如下一项或多项信息确定指示信息：用户签约信息、终端装置的位置、预配置信息。
在一种可能的设计中，向终端装置发送指示信息，包括：向终端装置发送一个或多个URSP规则，一个或多个URSP规则中的至少一个包括指示信息。
在一种可能的设计中，其特征在于，方法还包括：
获取目标NSSAI；根据目标NSSAI确定网络选择辅助信息，并向终端装置发送网络选择辅助信息。
其中，网络选择辅助信息包括如下一项或多项信息：支持目标切片集内一个或多个切片的一个或多个网络的信息、一个或多个网络的优先级、一个或多个网络分别支持的网络切片信息。
目标切片集为目标NSSAI对应的一个或多个切片；目标NSSAI包括如下一种或多种：终端装置所请求网络切片对应的NSSAI、拒绝终端装置接入的网络切片对应的NSSAI、允许终端装置接入的网络切片对应的NSSAI。
第三方面，本申请实施例提供一种切片接入装置，该装置为上述终端装置。终端装置可以指终端设备，也可以指终端设备中的组件(比如芯片系统)。该装置包括通信接口和处理器。其中，通信接口，用于从网络装置接收一个或多个用户路由选择策略规则URSP rule，URSP规则中至少一个URSP规则包括指示信息；指示信息用于指示匹配一个或多个预设URSP规则或匹配一个或多个预设路由选择描述RSD。处理器，用于根据一个或多个URSP规则执行URSP匹配。
在一种可能的设计中，处理器，用于根据一个或多个URSP规则执行URSP匹配， 包括：
用于若一个或多个预设URSP规则中与当前待发起业务匹配的URSP规则对应的一个或多个单个网络切片选择辅助信息S-NSSAI均不被第一网络支持，停止URSP匹配。
或者，用于若一个或多个预设RSD中与当前待发起业务匹配的RSD对应的一个或多个S-NSSAI均不被第一网络支持，停止URSP匹配。
在一种可能的设计中，处理器，还用于通过移动性变更流程接入第二网络，并在第二网络中请求一个或多个S-NSSAI中的至少一个。
其中，第二网络为支持一个或多个S-NSSAI中至少一个的网络。
在一种可能的设计中，处理器，还用于获取网络选择辅助信息，网络选择辅助信息包括如下一项或多项信息：
支持目标切片集内一个或多个切片的一个或多个网络的信息、一个或多个网络的优先级、一个或多个网络分别支持的网络切片信息。
目标切片集为目标NSSAI对应的一个或多个切片；目标NSSAI包括如下一种或多种：终端装置所请求网络切片对应的NSSAI、拒绝终端装置接入的网络切片对应的NSSAI、允许终端装置接入的网络切片对应的NSSAI。
在一种可能的设计中，处理器，用于通过移动性变更流程接入第二网络，包括：用于根据网络选择辅助信息执行移动性变更流程，以接入第二网络。
第四方面，本申请实施例提供一种切片接入装置，该装置为上述网络装置。该装置包括通信接口和处理器。其中，处理器，用于确定指示信息，指示信息用于指示匹配一个或多个预设URSP规则或匹配一个或多个预设路由选择描述RSD。通信接口，用于向终端装置发送指示信息。
在一种可能的设计中，处理器，用于确定指示信息，包括：用于根据如下一项或多项信息确定指示信息：用户签约信息、终端装置的位置、预配置信息。
在一种可能的设计中，通信接口，用于向终端装置发送指示信息，包括：用于向终端装置发送一个或多个URSP规则，一个或多个URSP规则中的至少一个包括指示信息。
在一种可能的设计中，处理器，还用于：
获取目标NSSAI；根据目标NSSAI确定网络选择辅助信息；向终端装置发送网络选择辅助信息。
网络选择辅助信息包括如下一项或多项信息：支持目标切片集内一个或多个切片的一个或多个网络的信息、一个或多个网络的优先级、一个或多个网络分别支持的网络切片信息。
目标切片集为目标NSSAI对应的一个或多个切片；目标NSSAI包括如下一种或多种：终端装置所请求网络切片对应的NSSAI、拒绝终端装置接入的网络切片对应的NSSAI、允许终端装置接入的网络切片对应的NSSAI。
在上述任一方面的任一种可能的设计中，预设URSP包括：非通配URSP规则；或者，预设URSP规则包括第一URSP规则以及一个或多个第二URSP规则；或者，预设URSP规则包括第一URSP规则；
其中，第一URSP规则为指示信息所在的URSP规则；第二URSP规则为优先级高于第一URSP规则的URSP规则；
预设RSD包括第一RSD以及一个或多个第二RSD；或者，预设RSD包括第一RSD；
其中，第一RSD为指示信息所在的RSD；第二RSD为优先级高于第一RSD的RSD。
第五方面，本申请提供一种切片接入装置，用于实现上述任一方面中终端装置的功能，或者，用于实现上述任一方面中网络装置的功能。
第六方面，本申请提供一种切片接入装置，该装置具有实现上述任一方面中任一项的切片接入方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第七方面，提供一种切片接入装置，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该切片接入装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该切片接入装置执行如上述任一方面中任一项的切片接入方法。
第八方面，提供一种切片接入装置，包括：处理器；处理器用于与存储器耦合，并读取存储器中的指令之后，根据指令执行如上述任一方面中任一项的切片接入方法。
第九方面，本申请实施例提供了一种切片接入装置，该装置可以为芯片系统，该芯片系统包括处理器，还可以包括存储器，用于实现上述任一方面所描述方法的功能。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
第十方面，提供一种切片接入装置，该装置可以为电路系统，电路系统包括处理电路，处理电路被配置为执行如上述任一方面中任一项的切片接入方法。
第十一方面，本申请实施例中还提供一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行上述任一方面的方法。
第十二方面，本申请实施例中还提供一种计算机程序产品，包括指令，当其在计算机上运行时，使得计算机执行上述任一方面的方法。
第十三方面，本申请实施例提供了一种系统，系统包括执行第一方面以及第一方面的任一项的切片接入方法的终端装置和执行第二方面以及第二方面的任一项的切片接入方法的网络装置。可选的，该系统还包括移动性管理网元(比如可以为图1所示AMF)。移动性管理网元用于将来自终端的消息发给策略网元(即上述第四方面的网络装置)，或者，将来自策略网元的消息发送给终端。示例性的，移动性管理网元用于将终端和策略网元之间的消息进行透传。
附图说明
图1为本申请实施例提供的通信系统的架构示意图；
图2为本申请实施例提供的通信系统的架构示意图；
图3为本申请实施例提供的切片接入系统的架构示意图；
图4为本申请实施例提供的URSP匹配流程的原理示意图；
图5-图7为本申请实施例提供的切片接入方法的流程示意图；
图8和图9为本申请实施例提供的切片接入装置的结构示意图。
具体实施方式
本申请的说明书以及附图中的术语“第一”和“第二”等是用于区别不同的对象，或者用于区别对同一对象的不同处理，而不是用于描述对象的特定顺序。
“至少一个”是指一个或者多个，
“多个”是指两个或两个以上。
“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。
字符“/”一般表示前后关联对象是一种“或”的关系，例如，A/B可以表示A或B。
此外，本申请的描述中所提到的术语“包括”和“具有”以及它们的任何变形，意图在于覆盖不排他的包含。例如包含了一系列步骤或单元的过程、方法、系统、产品或设备没有限定于已列出的步骤或单元，而是可选地还包括其他没有列出的步骤或单元，或可选地还包括对于这些过程、方法、产品或设备固有的其它步骤或单元。
需要说明的是，本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
本申请的说明书以及附图中“的(英文：of)”，相应的“(英文corresponding，relevant)”和“对应的(英文：corresponding)”有时可以混用，应当指出的是，在不强调其区别时，其所要表达的含义是一致的。
首先，对本申请实施例设计的技术术语进行介绍：
1、网络切片的类型与特征属性：如上文，一张物理网络可以被抽象划分成多个网络切片，每个网络切片可以构成一个端到端的逻辑网络。网络切片彼此之间在逻辑上是隔离的，互不影响。通常情况下，为了满足不同的通信需求，网络切片被划分为多种类型。比如但不限于增强移动宽带(enhanced mobile broad band，eMBB)类型、海量机器类型连接(massive machine type connection，mMTC)、超高可靠性超低时延连接(ultra reliability and low latency connection，uRLLC)类型。其中，不同类型网络切片的网络特征不相同。如eMBB的网络切片要求具备支持大带宽、低时延业务的特征；mMTC的网络切片要求具备支持海量接入，带宽小的特征；uRLLC的切片要求具备高可靠性、低时延的特征。可见，支持的应用业务种类、端到端时延、单终端最大速率等，这些都属于网络切片的特征属性，这些特征属性依赖于切片的设计。
2、单个切片接入辅助信息(Single network slice selection assistance information，S-NSSAI)，用于唯一表示一个网络切片。
3、网络切片选择辅助信息(network slice selection assistance information，NSSAI)：
NSSAI指的是一个或多个S-NSSAI的集合。相应的，NSSAI可以用于表示一个或多个网络切片。
4、PDU会话(Session)：UE与数据网(data network，DN)间实现PDU连通性的会话服务，由PDU Session ID标识。
5、URSP：通常，运营商根据客户订单，在通信网络的物理基础设施上为客户创 建所需网络切片时，往往会根据业务需求，与客户签署网络切片的服务等级协议(service level agreement，SLA)。在运营商的一个PLMN内，不一定整张网络都支持相同的网络切片集合(network slice set)。运营商可以根据区域，甚至单点基站，划分不同的切片集合。如此，不同区域网络可能对应不同切片。因此，在非漫游场景下，用户可能仅可通过归属网络中的部分区域接入所需切片，或者，在漫游场景下，仅可通过部分拜访网络中的部分区域接入所需切片。
目前，针对用户的路由问题，标准中定义了URSP。主要用于确定不同应用程序(application，APP)或业务所需的PDU会话参数，如网络切片、数据网络名称(DNN)、会话服务连续性模式(session service continuity mode，SSC mode)等。通过URSP，终端可以根据APP或者业务的网络需求，确定对应的PDU会话参数，并基于参数建立PDU会话。之后，通过建立的会话传输该APP或者业务的数据。
URSP的结构如下表1所示：
表1
Figure PCTCN2021092614-appb-000001
Figure PCTCN2021092614-appb-000002
URSP主要包括上述表1中的流量描述符(Traffic descriptor)和一个或多个路由选择描述符(Route Selection Descriptors，RSD)(已加粗显示)。其中，Traffic descriptor用于与业务信息(应用标识或流标识或业务标识等)进行匹配。比如，终端调制解调器(modem)按照上述一个或多个URSP规则的优先级从高到低，将应用层提供的应用标识(APP ID)与各个URSP规则中的流量描述符分别进行匹配。Traffic descriptor有多种类型，比如上述表1中的Application descriptors(比如操作系统标识(OSId)+应用标识(OSAppId)，比如，安卓操作系统下的微信可以表示为android+com.wechat)、IP descriptors(比如发起业务对应的目的IP地址)。
其中，RSD的结构如下表2所示：
表2
Figure PCTCN2021092614-appb-000003
Figure PCTCN2021092614-appb-000004
RSD包括DNN、S-NSSAI、SSC mode等信息。
示例性的，如图4的(a)所示，URSP1包括Traffic descriptor、3个RSD。其中，Traffic descriptor通过应用标识或其他类型标识区分不同业务。RSD1包括S-NSSAI-1，RSD2包括S-NSSAI-2，RSD3包括S-NSSAI-3。
6、URSP匹配：当UE判断需发起特定业务/应用时，先按URSP规则的优先级顺序对待发起业务/应用与URSP规则中的Traffic Descriptor进行匹配。
若匹配到具体的URSP规则(该URSP规则也可能是默认URSP规则(也可称为通配URSP规则)，如Traffic Descriptor为match-all形式)，则UE还需根据该URSP规则的当前RSD确定该业务所需采用的切片S-NSSAI，并判断该切片S-NSSAI是否属于当前网络的Allowed NSSAI。具体的，在漫游场景中，终端需判断该切片S-NSSAI是否属于拜访网络当前的Allowed NSSAI，在非漫游场景中，终端需判断该切片S-NSSAI是否在归属网络当前的Allowed NSSAI之内。若该S-NSSAI不在Allowed NSSAI中，则UE将继续根据URSP优先级/RSD优先级对后续URSP规则或后续RSD进行匹配，直至确定该业务允许使用的切片S-NSSAI出现在Allowed NSSAI中且该切片S-NSSAI被网络侧接受。例如，UE在判断发起业务的应用ID所对应的URSP规则不可用时，可根据优先级继续匹配至优先级最低的URSP规则，即图4的(a)所示Traffic Descriptor为match-all形式的URSP规则。UE最终匹配的URSP规则称为目标URSP规则。UE最终匹配的RSD称为目标RSD。
接下来，UE判断是否存在符合目标RSD定义的已有PDU会话。
若已有PDU会话对应的DNN，S-NSSAI，SSC mode等信息与目标RSD包括的信息均一致，说明已有PDU会话和当前业务需求一致，则UE可选择在已有PDU会话基础上发起PDU会话修改请求(PDU Session Modification Request)，以便在已有PDU会话上建立新的服务质量流(quality of service，QoS flow)，通过新建的QoS flow来 承载业务。
该PDU会话修改请求消息可以通过N1 SM Container承载。该PDU会话修改请求包括(或称携带)PDU Session ID，包过滤器(packet filters)，请求QoS参数(Requested QoS)等。其中，PDU Session ID用于AMF关联至具体会话上下文，终端的N1 SM Container则由AMF透传至SMF。
若已有PDU Session(s)均无法与该URSP的RSD信息匹配，则UE将为该业务/应用发起PDU会话建立请求，并在该会话建立请求消息中携带新分配的PDU Session ID，RSD中的DNN，S-NSSAI，N1 SM Container(SSC mode，PDU Session Type)等参数。其中，新分配的PDU Session ID用于标识该PDU会话建立请求所对应的PDU会话，DNN+S-NSSAI则作为AMF为该PDU会话建立请求选择SMF实体的参数，N1 SM Container则由AMF透传至所选择的SMF。
以UE需访问V2X业务为例，根据归属网络提供的URSP规则，V2X业务需接入URLLC类型的切片。如图4的(a)所示，归属网络为终端提供的URSP1规则包括3个RSD，分别为V2X对应的3个切片信息，这3个切片均为URLLC类型切片。在一种可能的部署场景中，UE当前所接入的拜访网络可能并未部署URLLC类型的切片，即UE所收到的Allowed NSSAI中并未包含其所需接入的URLLC切片。如图4的(a)所示，第一网络支持的S-NSSAI-4、S-NSSAI-5对应的切片均不是URLLC类型。以图4的(a)为例，当判断需发起V2X业务时，UE先匹配Traffic Descriptor，UE使用待发起业务信息，比如V2X业务标识与本地所保存的一个或多个URSP规则中的Traffic Descriptor进行匹配，确定URSP1中的Traffic Descriptor与待发起业务一致，则UE继续匹配该URSP1中的RSD。UE按照优先级顺序先匹配S-NSSAI-1，发现该S-NSSAI-1不属于Allowed NSSAI。此种情况下，根据现有技术，UE继续匹配后续的S-NSSAI-2，发现该S-NSSAI-2也不属于Allowed NSSAI，以此类推，直至匹配完该URSP1中的全部RSD，UE发现该URSP1指示的S-NSSAI均不被当前网络支持，即均不在当前网络的Allowed NSSAI中。此种情况下，UE将继续根据URSP规则的优先级匹配后续的URSP规则，直至匹配至优先级最低的默认URSP规则(也可称为通配URSP规则)。如图4的(a)所示，默认URSP规则包含的切片信息是eMBB类型切片信息。此时，UE会根据该eMBB类型切片信息建立PDU会话，导致建立的PDU会话很可能无法满足V2X业务需求。
为了解决上述技术问题，本申请实施例提供一种切片接入方法。如下将详细介绍本申请实施例的切片接入方法。
本申请实施例提供的切片接入方法应用于使用网络切片进行通信的通信系统中。比如，5G系统，或后续演进系统或其他系统。参见图1，为本申请实施例所适用的一种通信系统的示例性架构。该通信系统包括：网络开放功能(network exposure function，NEF)、策略控制功能(policy control function，PCF)、应用功能(application function，AF)、统一数据管理(unified data management，UDM)、用户数据库(user data repository，UDR)、接入和移动性管理功能(core access and mobility management function，AMF)、会话管理功能(session management function，SMF)、接入网(access network，AN)网元。其中，AN包括有线接入网和无线接入网(radio access network，RAN)、用户 面功能(user plane function，UPF)、DN网元等网元或设备以及终端UE。
其中，终端通过无线或有线方式接入AN，无线方式例如可以为通过无线保真(wireless-fidelity，WiFi)接入，还可以通过蜂窝网(例如E-UTRA、NR等)接入AN。终端通过N1与AMF通信；AN通过N3与UPF通信，AN通过N2与AMF通信；UPF通过N4与SMF通信，UPF通过N6与DN网元通信；AMF通过N8与UDM通信；SMF通过N11与AMF通信，SMF通过N10与UDM通信，SMF通过N7与PCF通信；AMF通过N12(图1中并未示出)与AUSF通信，AUSF通过N13(图1中并未示出)与UDM通信。AF通过N5与PCF通信。UDM通过N35与UDR通信。UDM通过N52与AF/NEF通信。UDR通过N36与PCF通信。AMF通过N15与PCF通信。
其中，图1所示系统中，AF/NEF指的是AF经由NEF与核心网网元进行交互。
图1所示系统中，部分网元的功能如下：
AF：主要传递应用侧对网络侧的需求，例如，QoS需求或用户状态事件订阅等。AF可以是第三方功能实体，也可以是运营商部署的应用服务，如IMS语音呼叫业务。对于第三方应用的应用功能实体，其与核心网进行交互时，还可经由NEF进行授权处理，例如第三方AF向NEF发送请求消息，NEF判断该AF是否被允许发送该请求消息，若验证通过，则将转发该请求消息至对应PCF或UDM。
UDM：主要负责管理签约数据、用户接入授权等功能。
UDR：主要负责签约数据、策略数据、应用数据等类型数据的存取功能。
此外，UDR还可以在用户的Subscribed NSSAI中增加相应S-NSSAI，同时增加该S-NSSAI下用户所允许使用的带宽、QoS保障等签约值。
PCF：主要负责针对会话、业务流级别进行计费、服务质量(quality of service，QoS)带宽保障及移动性管理、UE策略决策等策略控制功能。该架构中，AMF与SMF所连接的PCF分别对应AM PCF(即PCF for access and mobility control)和SM PCF(即PCF for session management)，在实际部署场景中，AM PCF和SM PCF可能不是同一个PCF实体。
SMF：主要进行会话管理、PCF下发控制策略的执行、UPF的选择、UE网际互连协议(internet protocol，IP)地址分配等功能。
AMF：主要进行移动性管理、接入鉴权/授权等功能。此外，还负责在UE与PCF间传递用户策略。
UPF：作为和数据网络的接口UPF，完成用户面数据转发、基于会话/流级的计费统计，带宽限制等功能。
AN：对应不同接入网，如有线接入、无线基站接入等多种方式。
其中，图1所示架构中，部分接口功能描述如下：
1、N7：PCF与SMF之间的接口，用于下发PDU会话粒度以及业务数据流粒度控制策略。
2、N15：PCF与AMF之间的接口，用于下发UE策略及接入控制相关策略。
3、N5：AF与PCF之间的接口，用于应用业务请求下发以及网络事件上报。
4、N4：SMF与UPF之间的接口，用于控制面与用户面之间传递信息，包括控制面向用户面的转发规则、QoS控制规则、流量统计规则等的下发以及用户面的信息上 报。
5、N11：SMF与AMF之间的接口，用于传递AN和UPF之间的PDU会话隧道信息、传递发送给UE的控制消息、传递发送给AN的无线资源控制信息等。
6、N2：AMF与RAN之间的接口，用于传递核心网侧至AN的无线承载控制信息等。
7、N1：AMF与UE之间的接口，接入无关，用于向UE传递QoS控制规则等。
8、N8：AMF与UDM间的接口，用于AMF向UDM获取接入与移动性管理相关签约数据与鉴权数据，以及AMF向UDM注册UE当前移动性管理相关信息等。
9、N9：用于UPF与UPF之间的用户面数据转发。
10、N10：SMF与UDM间的接口，用于SMF向UDM获取会话管理相关签约数据，以及SMF向UDM注册UE当前会话相关信息等。
11、N35：UDM与UDR间的接口，用于UDM从UDR中获取用户签约数据信息。
12、N36：PCF与UDR间的接口，用于PCF从UDR中获取策略相关签约数据以及应用数据相关信息。
可选的，本申请实施例中所涉及到的终端可以包括各种具有通信功能的手持设备、可穿戴设备、计算设备或连接到调制解调器的其它处理设备；还可以包括个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、膝上型电脑(laptop computer)、机器类型通信(machine type communication，MTC)终端、用户设备(user equipment，UE)等。当然，提及终端时，也可以指诸如UE中的芯片系统。本申请实施例对终端的实现形式不做限定。
可以理解的是，根据5G系统部署的需求，上述网元之间可采用一定方式通信(例如，终端通过N1与AMF通信)，上述仅列举了部分网元之间通信的方式，为简化描述，本申请实施例不再对其他网元之间的通信方式进行赘述。
可选的，图1中的各个网元的名字以及各个网元之间的接口名字只是一个示例，具体实现中各个网元或者各个网元之间的接口的名字可能为其他名字，或者网元也可以称之为实体，本申请实施例对此不作具体限定。图1中的全部或者部分网元可以是物理上的实体网元，也可以是虚拟化的网元，在此不做限定。
可选的，该架构中，还可以包括其他网元，比如运营管理(operation administration management，OAM)网元、网络切片选择功能(network slice selection function，NSSF)、网络仓库功能(network repository function，NRF)、鉴权服务器功能(authentication server function，AUSF)等。本申请实施例对此不进行限制。
进一步的，图1所示5G通信系统包括非漫游场景下的系统和漫游场景下的系统。可选的，每一种场景的系统可以为基于服务化接口的系统，也可以为基于参考点的系统。这里，基于服务化接口和基于参考点的具体描述可参见现有技术，此处不再赘述。
本申请实施例主要介绍以漫游架构，本申请的技术方案同样适用非漫游架构，非漫游架构可参见现有技术，这里不再赘述。具体的，3GPP标准中定义了用户在拜访地接入的两种漫游方式，即归属地接入漫游(home-routed roaming)与本地接入漫游(local breakout roaming)两种方式。
其中，在漫游架构中，部分网元的功能，网元之间的接口等信息可参见图1所示 架构的相关描述，这里不再赘述。在漫游架构中，某些网元被划分为两部分。一部分位于归属地公共陆地移动网络(home public land mobile network，HPLMN)，一部分位于拜访地公共陆地移动网络(visited public land mobile network，VPLMN)。当终端处于漫游场景，可利用分别部署在拜访地和归属地的网元获取相应网络服务。比如，图2的(a)中，PCF被划分为V-PCF(即拜访地的PCF)和H-PCF(即归属地的PCF)。类似的，SMF被划分为V-SMF和H-SMF。
参见图2的(a)为归属地接入漫游的漫游架构。该图2的(a)所示漫游架构中，AMF与H-SMF分别位于拜访地和归属地，会话管理功能由支持与UDM/H-PCF交互的归属地H-SMF执行。此外，V-PCF所连接的H-PCF与H-SMF所连接的H-PCF，在实际场景中可能不是同一个PCF实体。
图2的(b)，为本地接入漫游的漫游架构。该漫游架构中，AMF、SMF均位于拜访地。会话管理功能由拜访地的SMF执行。此外，AMF所连接的V-PCF与SMF所连接的V-PCF，在实际场景中可能不是同一个PCF实体。其中，图2的(b)包括短消息功能(short messaging service function，SMSF)。SMSF与UDM通过N21通信，与AMF通过N20通信。
在本申请的实施例中，某一网元(例如：A网元)获取来自另一网元(例如：B网元)的信息，可以指A网元直接从B网元接收信息，也可以指A网元经其他网元(例如：C网元)从B网元接收信息。当A网元经C网元从B网元接收信息时，C网元可以对信息进行透传，也可以将信息进行处理，例如：将信息携带在不同的消息中进行传输或者对信息进行筛选，只发送筛选后的信息给A网元。类似的，在本申请的各实施例中，A网元向B网元发送信息，可以指A网元直接向B网元发送信息，也可以指A网元经其他网元(例如：C网元)向B网元发送信息。
此外，本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本申请实施例提供一种切片接入系统。参见图3，该系统300包括：终端301以及策略网元302。
策略网元302：用于向终端发送URSP。该URSP与现有技术的URSP不同。具体的，该URSP包括指示信息，指示信息用于指示匹配一个或多个预设URSP规则，或者用于指示匹配一个或多个预设RSD。其中，预设URSP规则和预设RSD，具体可参见下述实施例。
终端301：用于根据来自策略网元302的URSP，执行URSP匹配。当一个或多个预设URSP对应的一个或多个单个网络切片选择辅助信息S-NSSAI均不被第一网络支持，或，一个或多个预设RSD对应的一个或多个S-NSSAI均不被第一网络支持，停止URSP匹配。如此，能够降低后续匹配到不适合业务的切片，导致终端业务失败的概率。
作为一种可能的实现方式，切片接入系统还包括：移动性管理网元304以及数据网元303。
移动性管理网元304：用于将来自终端301的消息发给策略网元302，或者，将来自策略网元302的消息发送给终端301。示例性的，移动性管理网元304用于将终端301和策略网元302之间的消息进行透传。
数据网元303：用于存储一些数据，这些数据可以用于策略网元制定URSP，或者，用于其他网元获知用户相关信息。
其中，图3中的数据网元可以为图1或图2中的UDM或具有类似功能的其他网元，还可以为UDR或具有类似功能的其他网元，移动性管理网元可以为图1或图2中的AMF或具有类似功能的其他网元，策略网元可以为图1中的PCF或图2中的H-PCF或具有类似功能的其他网元。并且，图3所示网元之间的连接关系可以参见图1或图2中相应网元之间的连接关系。这里不再赘述。
本申请实施例的技术方案可以应用于图2所示的漫游场景或非漫游场景(参见现有技术)。
以网络装置为图1所示的PCF或图2所示的H-PCF为例，参见图5，本申请实施例提供的切片接入方法包括如下步骤：
S501、H-PCF确定一个或多个URSP rule，该一个或多个URSP rule中的至少一个URSP rule包括指示信息。
其中，指示信息用于指示匹配一个或多个预设URSP规则，或者，用于指示匹配一个或多个预设路由选择描述RSD。
可选的，该指示信息可以作为RSD粒度，位于RSD中，即包括在上述表2中。
可选的，指示信息也可以作为URSP粒度，位于URSP Rule中，即包括在上述表1中。
指示信息用于指示匹配一个或多个预设URSP规则，指的是，仅匹配一个或多个预设URSP规则，不匹配除预设URSP规则之外的其他URSP规则。类似的，指示信息用于指示匹配一个或多个预设RSD，指的是，仅匹配一个或多个预设RSD，不匹配除预设RSD之外的其他RSD。
本申请实施例中，作为一种可能的实现方式，H-PCF将需匹配的URSP规则封装进指示信息，即需匹配的URSP规则均包括指示信息。这种情况下，预设URSP规则可以包括指示信息所在URSP规则(本申请实施例中称为第一URSP规则)。示例性的，参见图4的(b)，H-PCF决策得到URSP1、URSP2、URSP3，以及默认URSP规则。其中，URSP1、URSP2、URSP3均包括指示信息，则预设URSP规则为URSP1、URSP2和URSP3。后续，终端装置仅匹配URSP1、URSP2以及URSP3。
需要说明的是，本申请实施例中，指示信息的具体内容可以发生变化。比如，当存在两个及以上指示信息时，需匹配的最后一个URSP规则，其包括的指示信息，可以与之前URSP规则(即优先级高于该最后一个URSP规则的URSP规则)包括的指示信息不同。比如，图4的(b)中，需匹配的最后一个URSP规则即URSP3，URSP1和URSP2包括的指示信息相同，URSP3包括的指示信息可以与URSP1包括的指示信息不同。假设指示信息为1比特(0或1)，URSP3包括数值为0的指示信息，URSP1包括数值为1的指示信息，URSP2也包括数值为1的指示信息。当然，需匹配的最后一个URSP规则，其包括的指示信息，可以与之前URSP规则(即优先级高于该最后 一个URSP规则的URSP规则)包括的指示信息一致。比如，URSP3包括数值为1的指示信息，URSP1和URSP2均包括数值为1的指示信息。
作为一种可能的实现方式，H-PCF将需匹配的URSP规则中最后一个URSP规则封装进指示信息。这种情况下，预设URSP规则可以包括第一URSP规则(第一URSP规则即指示信息所在URSP规则)以及一个或多个第二URSP规则(第二URSP规则即优先级高于该第一URSP规则的URSP规则)。
比如，存在URSP1(高优先级)、URSP2(中优先级)、URSP3(低优先级)。那么，若第一URSP规则为URSP2，则第二URSP规则为URSP1。若第一URSP规则为URSP3，则优先级高于URSP3的第二URSP规则即URSP1和URSP2。
类似的，本申请实施例中提及的第一RSD，指的是指示信息所在的RSD。当提到第二RSD，通常指的是优先级高于该第一RSD的RSD。第二RSD，即优先级高于第一RSD的RSD包括当前URSP规则中优先级高于该第一RSD的RSD，以及优先级高于该当前URSP规则的其他URSP规则中的RSD。示例性的，参见图4的(d)，第一RSD为指示信息所在的RSD5，第二RSD为当前URSP规则(即RSD5所在的URSP2)中优先级高于RSD5的RSD4，以及优先级高于该URSP2的URSP1所包括的RSD1至RSD3。
因此，这种情况下，预设URSP规则可以包括第一URSP规则(即指示信息所在URSP规则)以及一个或多个第二URSP规则(即优先级高于该第一URSP规则的URSP规则)。示例性的，参见图4的(c)，H-PCF决策得到URSP1、URSP2，以及默认URSP规则。其中，仅URSP2均包括指示信息，则预设URSP规则包括指示信息所在URSP规则(即URSP2)以及优先级高于URSP2的URSP1。后续，终端装置仅匹配该预设URSP规则，即仅匹配URSP1和URSP2。
作为另一种可能的实现方式，指示信息可能位于RSD中。预设RSD，可以指第一RSD(即指示信息所在RSD)以及一个或多个第二RSD(优先级高于第一RSD的RSD)。示例性的，参见图4的(d)，H-PCF决策得到URSP1、URSP2、URSP3，以及默认URSP规则。其中，仅URSP2的RSD5包括指示信息，则预设RSD包括指示信息所在RSD(即RSD5)以及优先级高于RSD5的RSD1至RSD4。后续，终端装置仅匹配该预设RSD，即仅匹配RSD1至RSD5。
或者，作为另一种可能的实现方式，预设URSP规则包括第一RSD，即包括指示信息所在RSD。示例性的，参见图4的(e)，H-PCF决策得到URSP1、URSP4，以及默认URSP规则。其中，RSD1、RSD2、RSD3、RSD8和RSD9均包括指示信息，则预设RSD包括指示信息所在的RSD1、RSD2、RSD3、RSD8和RSD9。后续，终端装置仅匹配该预设RSD，即仅匹配RSD1、RSD2、RSD3、RSD8和RSD9。
可选的，作为另一种可能的实现方式，预设URSP规则包括非通配URSP规则，即非默认URSP规则。即终端装置仅匹配非默认URSP规则，不匹配默认URSP规则。示例性的，参见图4的(a)，H-PCF决策得到至少3个URSP规则，即URSP1、URSP2、默认URSP规则。这里，预设URSP规则即非默认的URSP1、URSP2以及其他非默认URSP规则。终端装置在URSP匹配流程中仅匹配图4的(a)所示的非默认URSP规则。其中，指示信息可封装在需匹配的非默认URSP规则中，比如，参见图4的(f)。 指示信息也可封装在不需匹配的默认URSP规则中。或者，指示还可以有其他的封装方式。
具体的，H-PCF根据用户签约信息、终端装置的当前位置、本地预配置中的一种或多种信息，执行URSP规则决策。
S502、H-PCF向终端装置发送一个或多个URSP rule。
相应的，终端装置从网络装置接收一个或多个URSP rule。
这里，H-PCF根据终端装置上报的URSP策略区块标识(policy section ID，PSI)，判断是否需更新或新增终端装置的URSP规则。当确定需更新或新增终端装置的URSP规则，H-PCF向终端装置发送一个或多个URSP规则。其中，一个或多个URSP rule中至少一个URSP rule包括上述指示信息。
具体的，H-PCF先向AMF发送该一个或多个URSP规则，AMF再通过(R)AN向终端装置发送该一个或多个URSP规则。作为一种可能的实现方式，H-PCF通过调用AMF提供的Namf_Communication_N1N2MessageTransfer服务，向AMF发送该一个或多个URSP规则。可选的，若AMF判断UE当前处于空闲(idle)态，则AMF发起网络侧触发的服务请求流程(network triggered service request)，以触发终端装置从空闲态恢复至连接(connected)态。当终端装置处于连接态，AMF通过RAN向连接态的终端装置发送上述一个或多个URSP规则。
可选的，本申请实施例的切片接入方法，还可以包括如下步骤：
S503、终端装置向AMF发送第一确认消息。
相应的，AMF从终端装置接收第一确认消息。
可以理解，终端装置在收到来自H-PCF的URSP规则后，向AMF发送第一确认消息，该第一确认消息用以指示该终端装置已收到上述一个或多个URSP规则。
具体的，终端装置通过(R)AN向AMF发送第一确认消息。
该S503为可选步骤。
S504、AMF向H-PCF发送第一确认消息。
相应的，H-PCF从AMF接收第一确认消息。
作为一种可能的实现方式，AMF返回Namf_Communication_N1MessageNotify服务响应向H-PCF发送第一确认消息。
该S504为可选步骤。
S505、根据一个或多个URSP规则执行URSP匹配。
具体的，与现有技术不同，本申请实施例中，若一个或多个预设URSP规则中与当前待发起业务匹配的URSP规则对应的一个或多个S-NSSAI均不被第一网络支持，或，一个或多个预设RSD中与当前待发起业务匹配的RSD对应的一个或多个S-NSSAI均不被第一网络支持，停止URSP匹配。
终端装置执行URSP匹配，首先终端装置需匹配业务信息，即终端装置需先确定当前待发起业务匹配的URSP规则或当前待发起业务匹配的RSD。作为一种可能的实现方式，当发起业务时，终端modem按照上述一个或多个URSP规则的优先级从高到低，将应用层提供的发起业务的应用标识(APP ID)与上述各个URSP规则中的流量描述符分别进行匹配。其中，匹配一致的URSP规则称为当前待发起业务匹配的URSP 规则。当前待发起业务匹配的URSP规则所包括的RSD，称为当前待发起业务匹配的RSD。示例性的，如图4的(b)，终端装置从H-PCF接收的一个或多个URSP规则包括URSP1、URSP2、URSP3、默认URSP规则等。当前，终端装置发起V2X业务，则终端装置所确定的一个或多个预设URSP中与当前待发起业务匹配的URSP规则为URSP1和URSP2。又比如，图4的(e)中，终端装置发起V2X业务，且一个或多个预设RSD中与当前待发起业务匹配的RSD为RSD1至RSD3。具体地，终端在根据业务信息执行URSP匹配时还可能采用其他方式，如根据待发起业务对应的域名信息、目的服务器IP地址信息等，或是直接由modem层执行上述匹配动作而无需应用层参与，本申请实施例对此不做限定。
S-NSSAI不被第一网络支持，指的是S-NSSAI不在第一网络的Allowed NSSAI中。或，S-NSSAI虽然在Allowed NSSAI中，但终端装置接收的该Allowed NSSAI可能是未更新的。或者，终端装置发起PDU会话建立请求后，接收到网络侧拒绝原因值，且该原因值指示该S-NSSAI暂不支持接入。或其他不被第一网络支持的情况。第一网络指的是终端的当前网络。
示例性的，参见图4的(b)，预设URSP规则为URSP1、URSP2以及URSP3。则终端装置在执行URSP匹配流程时仅匹配URSP1、URSP2和URSP3。其中，终端装置匹配URSP3时，根据URSP3中的流量描述符(即wechat)，确定该URSP3并非当前待发起V2X业务匹配的URSP规则。终端装置匹配UPSR1和URSP2时，发现URSP1和URSP2对应的S-NSSAI-1至S-NSSAI-7均不在第一网络的Allowed NSSAI中，此种情况下，终端装置停止URSP匹配，不再继续匹配后续URSP规则。此种情况下，终端装置可尝试接入至少一个所需切片。
其中，如上文描述，需匹配的最后一个URSP规则(即URSP3)包括的指示信息，与高优先级URSP规则包括的指示信息可能相同或不同。比如，URSP3包括数值为1的指示信息，URSP1和URSP2均包括数值为1的指示信息。这种情况下，终端装置在匹配完URSP3的同时，可能无法获知该URSP3是否为最后一个需匹配的URSP规则，其还需解封下一个URSP规则。若终端装置确定下一个URSP规则不包括指示信息，说明该下一个URSP规则不是预设URSP规则，终端装置无需匹配该URSP规则。
又比如，URSP3包括数值为0的指示信息，URSP1和URSP2均包括数值为1的指示信息。这种情况下，由于最后一个URSP规则(即URSP3)包括的指示信息与之前的URSP规则(URSP1和URSP2)均不同，终端装置在匹配完URSP3的同时，可获知该URSP3是最后一个需匹配的URSP规则。如此，终端装置无需再解封下一个URSP规则，减少终端装置需执行的操作，实现流程更为简单。
又比如，参见图4的(e)，预设RSD(即指示信息所在的RSD)为RSD1、RSD2、RSD3、RSD8和RSD9。则终端装置在执行URSP匹配流程时仅匹配RSD1、RSD2、RSD3、RSD8和RSD9。具体的，当终端装置匹配至RSD8和RSD9时，发现该RSD8和RSD9并非当前待发起业务匹配的RSD。当终端装置匹配至RSD1、RSD2、RSD3时，确定RSD1、RSD2和RSD3分别对应的S-NSSAI-1、S-NSSAI-2和S-NSSAI均不在第一网络的Allowed NSSAI中，终端装置停止URSP匹配，不再继续匹配后续RSD。
本申请实施例提供的切片接入方法，终端可以从网络装置接收指示信息，从而在 需要发起业务时，触发URSP匹配，并仅匹配指示信息所指示的预设URSP，或者可以不匹配指示信息所指示的预设URSP。如此，能够降低所需匹配URSP的数量，并且，降低一直匹配URSP导致匹配到的切片信息不适合业务所需，据此建立的PDU会话无法支持所需发起的业务，以致终端业务失败的概率。
S506、终端装置执行移动性变更流程。
可选的，当终端装置执行业务所需接入的切片不被第一网络支持，终端装置可以执行移动性变更流程。通过移动性变更流程，终端装置由第一网络切换到第二网络，或者，注册到第二网络。
此外，与常规移动性管理流程不同，本申请实施例中，终端装置还可以通过如下注册流程在第二网络中请求接入上述一个或多个S-NSSAI(即业务所需接入)中至少一个。以便于接入至少一个所需切片。其中，第二网络为支持一个或多个S-NSSAI中至少一个的网络。
切换或注册的具体流程可参见现有技术，这里不再赘述。
作为一种可能的实现方式，终端装置根据如下一项或多项信息，执行移动性变更流程：本地配置、监听到的广播信息、网络选择辅助信息。
网络选择辅助信息包括如下一项或多项信息：
支持目标切片集内一个或多个切片的一个或多个网络的信息、支持一个或多个网络的优先级、该一个或多个网络分别支持的网络切片信息。
其中，目标切片集为目标NSSAI对应的一个或多个切片；目标NSSAI包括如下一种或多种：终端装置所请求网络切片对应的NSSAI(即Requested NSSAI)、拒绝终端装置接入的网络切片对应的NSSAI(即Rejected NSSAI)、允许终端装置接入的网络切片对应的NSSAI(即Allowed NSSAI)。
根据目标切片的不同，本申请实施例的网络选择辅助信息可以分为两种。目标切片为Requested NSSAI，网络选择辅助信息称为第一网络选择辅助信息。当目标切片为Rejected NSSAI和/或Allowed NSSAI，网络选择辅助信息称为第二网络选择辅助信息。第一网络选择辅助信息和第二网络选择辅助信息的具体介绍可参见下述图6、图7对应的实施例。此处仍沿用网络选择辅助信息这一统称。
网络选择辅助信息可以为S-NSSAI所偏好PLMN标识的列表(S-NSSAI：Preferred PLMN ID List)形式。或，网络选择辅助信息可以为S-NSSAI列表(Precedence，PLMN ID，Supported S-NSSAI list)形式。其中，Precedence指各个PLMN的优先级，PLMN ID是支持目标切片集内一个或多个切片的一个或多个PLMN的标识，Supported S-NSSAI list是相应PLMN支持的S-NSSAI列表。
示例性的，目标NSSAI为Requested NSSAI，则目标切片集为Requested NSSAI标识的一个或多个切片，比如切片1至切片3(分别对应S-NSSAI-1至S-NSSAI-3)。若以PLMN标识的列表表示网络选择辅助信息，则该列表可以为(S-NSSAI-1：PLMN1，PLMN 2；S-NSSAI-2：PLMN 1，PLMN 3；S-NSSAI-3：PLMN 4，PLMN 2，PLMN3)。可选的，该列表还可包括该一个或多个PLMN的优先级。比如，该列表可以为(S-NSSAI-1：PLMN 1(高优先级)，PLMN 2(低优先级)；S-NSSAI-2：PLMN 1(高优先级)，PLMN 3(低优先级)；S-NSSAI-3：PLMN 4(高优先级)，PLMN 2 (中优先级)，PLMN 3(低优先级))。这里，优先级也可以用其他方式指示，比如以数值指示，数值越小，优先级越高。也可以数值越大，优先级越高。本申请实施例不做限制。可选的，该列表还包括该一个或多个PLMN分别支持的S-NSSAI。若以S-NSSAI列表形式表示网络选择辅助信息，该列表可以为(高优先级，PLMN 1，S-NSSAI-1，S-NSSAI-2；高优先级，PLMN 2，S-NSSAI-1，S-NSSAI-4；低优先级，PLMN 3，S-NSSAI-3，S-NSSAI-2)。
监听的周边网络的广播信息包括该周边网络支持的切片信息。比如，广播信息包括邻小区广播的所支持切片信息。
可以理解，在终端装置执行业务所需切片不被当前的第一网络支持的情况下，终端装置可以判断周边网络是否支持其所需切片的接入，当确定某一网络(比如第二网络)支持该切片，终端装置触发向该第二网络的移动性变更流程(即通过切换/移动性注册流程接入该第二网络)。并且，终端装置可以在该第二网络中继续请求所需切片对应的S-NSSAI，即请求上述一个或多个S-NSSAI中的至少一个。示例性的，如图4的(b)所示，当终端装置发起业务，执行URSP匹配时，读取指示信息，获知仅匹配该URSP1和URSP2，无需匹配后续URSP规则。经过匹配URSP1和URSP2，终端装置获知业务所需S-NSSAI-1至S-NSSAI-7均不在第一网络的Allowed NSSAI中。此种情况下，为了接入所需至少一个切片，终端装置可执行移动性变更流程，注册或切换至支持所需至少一个切片的第二网络中。如图4的(b)所示，终端装置可以注册或切换至支持S-NSSAI-1和S-NSSAI-2的第二网络中。
在移动性变更流程中，终端装置可以向第二网络发送注册请求消息。具体的，若采用上述切换方式，则终端装置先执行切换，由第一网络切换至第二网络之后，触发向第二网络的注册流程。或者，若采用上述注册方式，则终端装置直接通过注册流程，由第一网络注册到第二网络。
在向第二网络中的注册流程中，终端装置可以向第二网络发送注册请求，注册请求消息包括Requested NSSAI。Requested NSSAI包括上述一个或多个S-NSSAI中的至少一个，即至少包括一个所需S-NSSAI。示例性的，终端装置仅匹配URSP1中的S-NSSAI-1至S-NSSAI-3，且这三个S-NSSAI均不在第一网络的Allowed NSSAI，终端装置向第二网络发送的Requested NSSAI包括S-NSSAI-1至S-NSSAI-3中的至少一个。可选的，该注册路程还可以用于更新第二网络中的UE上下文等信息。
需要说明的是，本申请实施例中，不限制上述一个或多个步骤之间的执行顺序先后，比如，S505和S506的执行顺序先后，再比如，S504与S505之间的先后顺序。
本申请实施例中，在为PDU会话选择会话参数时，除根据URSP规则、Allowed NSSAI信息外，还参考了UE当前位置周边网络是否支持所需切片这一信息。并且，能够判断是否触发向相邻网络的移动性变更流程。如此，终端装置可以通过第二网络接入所需切片(即S-NSSAI-1至S-NSSAI-3分别对应的切片中的至少一个)，并在所需切片内建立PDU会话。因为所需切片信息(包括S-NSSAI、DNN等信息)是在URSP匹配流程中根据业务信息确定的，所以，根据所需切片信息建立的PDU会话能够满足终端装置的业务需求。降低了终端装置因匹配到不适合业务的切片信息，导致业务失败的概率。
此外，终端装置在使用上述网络选择辅助信息时，还可参考当前已建立PDU会话对应的S-NSSAI在第二网络的支持情况，从而避免对当前正在进行的业务的影响。例如，UE待接入的切片为S-NSSAI 3，当前已存在会话为PDU Session 1(对应参数S-NSSAI 1)，PDU Session 2(对应参数S-NSSAI 2)，则UE在执行移动性变更流程时，除考虑第二网络对S-NSSAI 3的支持情况外，还需考虑第二网络应该尽可能支持S-NSSAI 1与S-NSSAI 2。
当然，当终端装置执行业务所需接入的切片不被第一网络支持，终端装置可以不执行上述S505，即不触发向第二网络的移动性变更流程，而是放弃上述待发起的业务，待后续收到更新的Allowed NSSAI中包含所需S-NSSAI，终端装置再发起对应业务。
在另一些实施例中，还提供第一网络选择辅助信息的确定方法。参见图6，该方法包括：
S601、终端装置向AMF发起注册请求。
相应的，AMF从终端装置接收注册请求。
其中，该注册请求可以是初始注册请求，或是移动性注册请求，或是其他可能的注册请求。该注册请求包括Requested NSSAI。该Requested NSSAI是根据如下一项或多项信息确定的：归属网络配置的Configured NSSAI，终端装置上一次注册流程中的Allowed NSSAI，其他配置信息。该注册请求用以向网络侧请求接入Requested NSSAI指示的一个或多个切片。
S602、AMF向H-PCF发送第一策略创建/更新请求。
相应的，H-PCF从AMF接收第一策略创建/更新请求。
具体的，AMF调用H-PCF的Npcf_UEPolicyControl_Create/Update Request服务向H-PCF发送第一策略创建/更新请求。该第一策略创建/更新请求携带来自终端装置的Requested NSSAI(即上述的目标NSSAI)，及来自(R)AN的用户位置信息(user location information，ULI)。ULI比如但不限于是小区标识(Cell ID)、跟踪区标识(tracking area identity，TAI)。
需要说明的是，若该流程发生在漫游场景，则AMF通过V-PCF与H-PCF交互，即AMF先向V-PCF发送第一策略创建/更新请求，再由V-PCF将第一策略创建/更新请求转发至H-PCF。若该流程在非漫游场景发起，则AMF直接与H-PCF交互，即直接向H-PCF发送第一策略创建/更新请求。
S603、H-PCF确定第一网络选择辅助信息。
具体的，H-PCF根据如下一项或多项信息确定第一网络选择辅助信息：从UDR获取的用户策略签约数据、来自AMF的上述第一策略创建/更新请求(其中包括目标NSSAI，即Requested NSSAI)、本地配置信息。
具体的，该第一网络选择辅助信息包括支持Requested NSSAI内一个或多个S-NSSAI的一个或多个网络的信息。可选的，该第一网络选择辅助信息还包括该一个或多个网络的优先级，和/或该一个或多个网络分别支持的网络切片信息。
S604、H-PCF向AMF发送第一网络选择辅助信息。
相应的，AMF从H-PCF接收第一网络选择辅助信息。
具体的，H-PCF返回Npcf_UEPolicyControl_Create/Update Response服务响应向 AMF发送第一网络选择辅助信息。
可以理解，若该步骤发生在漫游场景，则H-PCF经由V-PCF向AMF发送第一网络选择辅助信息。若该步骤发生在非漫游场景，则H-PCF直接向AMF发送第一网络选择辅助信息。
S605、AMF向终端装置发送第一网络选择辅助信息。
相应的，终端装置从AMF接收第一网络选择辅助信息。
可选的，AMF向终端装置发送注册响应消息，该注册响应消息包括上述第一网络选择辅助信息。
可以理解，终端装置在收到上述第一网络选择辅助信息后，可以存储该第一网络选择辅助信息。以便在当前网络不支持所需切片时，根据该第一网络选择辅助信息确定支持所需至少一个切片的新网络，并通过移动性变更流程切换或注册到该新网络。如此，终端装置可以通过新网络接入所需至少一个切片。
在另一些实施例中，还提供第二网络选择辅助信息的另一种确定方法。参见图7，该方法包括如下步骤：
S701、UDM向AMF发送签约数据更新通知。
相应的，AMF接收来自UDM的签约数据更新通知，该签约数据更新通知可携带更新后的用户签约的网络切片选择辅助信息(Subscribed NSSAI)。
作为一种可能的实现方式，UDM通过Nudm_SDM_Notify服务向AMF发送签约数据更新通知。
S702、终端装置向AMF发送注册请求。
相应的，AMF接收来自终端装置的注册请求，
该注册请求同图6中的注册请求。该注册请求可携带终端装置请求接入的Requested NSSAI。
本申请实施例中，不限制S701、S702的执行顺序先后。即可以先执行S701，也可以先执行S702。此外，S701与S702可以同时执行，也可以仅执行S701或S702。
S703、AMF确定允许终端装置接入的切片列表Allowed NSSAI及拒绝终端装置接入的切片列表Rejected NSSAI。
可选地，AMF根据如下一项或多项信息，确定Allowed NSSAI以及Rejected NSSAI：本地配置、NSSF通知、上述Subscribed NSSAI、当前跟踪区(TA)所支持的切片信息。
AMF也可以更新此前确定的Allowed NSSAI，Rejected NSSAI信息。例如，AMF根据本地配置/NSSF通知消息和/或其他信息，判断部分或全部切片发生拥塞或切片不可用，AMF需引导终端装置通过其他切片接入，并更新终端装置的Allowed NSSAI，Rejected NSSAI信息。
S704、AMF向H-PCF发起第二策略创建/更新请求。
相应的，H-PCF从AMF接收第二策略创建/更新请求。
可选的，AMF调用H-PCF的Npcf_UEPolicyControl_Create/Update Request服务，向H-PCF发送第二策略创建/更新请求。该第二策略创建/更新请求可携带如下一项或多项信息：AMF决策得到的Allowed NSSAI、Rejected NSSAI、ULI。
可以理解，若该场景为漫游场景，则AMF经由V-PCF与H-PCF交互。若为非漫游场景，则AMF直接与H-PCF交互。
S705、H-PCF根据第二策略创建/更新请求，确定第二网络选择辅助信息。
具体的，H-PCF根据如下一项或多项信息，执行策略决策，确定第二网络选择辅助信息：Allowed NSSAI、Rejected NSSAI、ULI、UDR中的策略签约信息、本地配置。例如，根据Rejected NSSAI决策第二网络选择辅助信息，该第二网络选择辅助信息包括支持Rejected NSSAI中一个或多个S-NSSAI的一个或多个网络信息；和/或根据Allowed NSSAI决策第二网络选择辅助信息，该第二网络选择辅助信息包括支持Allowed NSSAI中一个或多个S-NSSAI的一个或多个网络信息。第二网络选择辅助信息包括支持Rejected NSSAI中一个或多个S-NSSAI的一个或多个网络信息，和/或，支持Allowed NSSAI中一个或多个S-NSSAI的一个或多个网络信息。可选的，该第二网络选择辅助信息还包括上述一个或多个网络的优先级，和/或每一网络支持的切片信息。
该第二网络选择辅助信息的具体形式可参考上述实施例，这里不再赘述。
S706、H-PCF向AMF发送第二网络选择辅助信息。
相应的，AMF从H-PCF接收第二网络选择辅助信息。
作为一种可能的实现方式，H-PCF返回Npcf_UEPolicyControl_Create/Update Response服务响应向AMF发送第二网络选择辅助信息。若为漫游场景，AMF经由V-PCF向H-PCF转发第二网络选择辅助信息。若为非漫游场景，AMF直接向H-PCF发送第二网络选择辅助信息。
S707、AMF向终端装置发送第二网络选择辅助信息。
相应的，终端装置从AMF接收第二网络选择辅助信息。
可选的，AMF通过用户配置更新流程(configuration update request)或注册响应消息将第二网络选择辅助信息发送至终端装置。
S708、终端装置向AMF发送第二确认消息(ACK)。
相应的，终端装置从AMF接收第二确认消息。
其中，该步骤为可选步骤。终端装置收到上述第二网络选择辅助信息后，向AMF发送第二确认消息，以指示收到第二网络选择辅助信息。
可以理解的是，上述各个方法实施例中由各个设备实现的方法和功能也可以通过可用于设备的芯片实现。
上述主要从不同网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，各个设备为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。结合本申请中所公开的实施例描述的各示例的单元及算法步骤，本申请实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。本领域技术人员可以对每个特定的应用来使用不同的方法来实现所描述的功能，但是这种实现不应认为超出本申请实施例的技术方案的范围。
本申请实施例可以根据上述方法示例对终端装置、策略网元等进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集 成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
图8示出了本申请实施例中提供的切片接入装置的一种示意性框图。该装置1200可以以软件的形式存在，也可以为硬件，比如可以为可用于硬件设备中的芯片。装置1200包括：处理单元1202和通信单元1203。
若装置1200为上述终端装置，处理单元1202可以用于支持装置1200执行图5所示S505、S506，和/或用于本文所描述的方案的其它过程。通信单元1203用于支持装置1200和其他网元(例如策略网元H-PCF)之间的通信，比如，执行图5所示的S502、S503，图6所示的S601、S605，图7所示的S702、S707、S708，和/或，本文所描述方案的其他步骤。
若装置1200为策略网元(即上述提及的网络装置)，处理单元1202可以用于支持装置1200执行图7所示S705，和/或用于本文所描述的方案的其它过程。通信单元1203用于支持装置1200和其他网元(例如终端)之间的通信，比如，执行图7所示的S704、S706，和/或，本文所描述方案的其他步骤。
可选的，装置1200还可以包括存储单元1201，用于存储装置1200的程序代码和数据，数据可以包括不限于原始数据或者中间数据等。
一种可能的方式中，处理单元1202可以是处理器或控制器，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理(Digital Signal Processing，DSP)，应用专用集成电路(Application Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field－Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信单元1203可以是收发器、收发电路或通信接口等。存储单元1201可以是存储器。
一种可能的方式中，当处理单元1202为处理器，通信单元1203为通信接口，存储单元1201为存储器时，本申请实施例所涉及的切片接入装置的结构可以为图9所示。
图9示出了本申请实施例中所涉及的切片接入装置的一种可能的设计结构的简化示意图。切片接入装置1500包括：处理器1502、通信接口1503、存储器1501。可选的，切片接入装置1500还可以包括总线1504。其中，通信接口1503、处理器1502以及存储器1501可以通过总线1504相互连接。总线1504可以是外设部件互连标准(Peripheral Component Interconnect，简称PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，简称EISA)总线等。总线1504可以分为地址总线、数据总线、控制总线等。为便于表示，图9中仅用一条线表示，但并不表示仅有一根总线或一种类型的总线。
本领域普通技术人员可以理解：在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例的流程或功能。计算 机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包括一个或多个可用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，数字视频光盘(Digital Video Disc，DVD))、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络设备(例如终端)上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个功能单元独立存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本申请可借助软件加必需的通用硬件的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在可读取的存储介质中，如计算机的软盘，硬盘或光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述的方法。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (24)

  1. 一种切片接入方法，其特征在于，包括：
    从网络装置接收一个或多个用户路由选择策略规则URSP rule，所述URSP规则中至少一个URSP规则包括指示信息；所述指示信息用于指示匹配一个或多个预设URSP规则或匹配一个或多个预设路由选择描述RSD；
    根据所述一个或多个URSP规则执行URSP匹配。
  2. 根据权利要求1所述的切片接入方法，其特征在于，所述预设URSP包括：非通配URSP规则；或者，所述预设URSP规则包括第一URSP规则以及一个或多个第二URSP规则；或者，所述预设URSP规则包括所述第一URSP规则；
    其中，所述第一URSP规则为指示信息所在的URSP规则；所述第二URSP规则为优先级高于所述第一URSP规则的URSP规则；
    所述预设RSD包括第一RSD以及一个或多个第二RSD；或者，所述预设RSD包括所述第一RSD；
    其中，所述第一RSD为指示信息所在的RSD；所述第二RSD为优先级高于所述第一RSD的RSD。
  3. 根据权利要求1或2所述的切片接入方法，其特征在于，根据所述一个或多个URSP规则执行URSP匹配，包括：
    若所述一个或多个预设URSP规则中与当前待发起业务匹配的URSP规则对应的一个或多个单个网络切片选择辅助信息S-NSSAI均不被第一网络支持，停止URSP匹配；
    或者，若所述一个或多个预设RSD中与所述当前待发起业务匹配的RSD对应的一个或多个S-NSSAI均不被第一网络支持，停止URSP匹配。
  4. 根据权利要求3所述的切片接入方法，其特征在于，所述方法还包括：
    通过移动性变更流程接入第二网络，并在所述第二网络中请求所述一个或多个S-NSSAI中的至少一个；
    其中，所述第二网络为支持所述一个或多个S-NSSAI中至少一个的网络。
  5. 根据权利要求1至4中任一项所述的切片接入方法，其特征在于，所述方法还包括：获取网络选择辅助信息，所述网络选择辅助信息包括如下一项或多项信息：
    支持目标切片集内一个或多个切片的一个或多个网络的信息、所述一个或多个网络的优先级、所述一个或多个网络分别支持的网络切片信息；
    所述目标切片集为目标NSSAI对应的一个或多个切片；所述目标NSSAI包括如下一种或多种：终端装置所请求网络切片对应的NSSAI、拒绝终端装置接入的网络切片对应的NSSAI、允许终端装置接入的网络切片对应的NSSAI。
  6. 根据权利要求5所述的切片接入方法，其特征在于，所述通过移动性变更流程接入第二网络，包括：根据所述网络选择辅助信息执行移动性变更流程，以接入第二网络。
  7. 一种切片接入方法，其特征在于，包括：
    网络装置确定指示信息，所述指示信息用于指示匹配一个或多个预设URSP规则或匹配一个或多个预设路由选择描述RSD；
    向终端装置发送所述指示信息。
  8. 根据权利要求7所述的切片接入方法，其特征在于，所述预设URSP规则，包括非通配URSP规则；或者，所述预设URSP包括：非通配URSP规则；或者，所述预设URSP规则包括第一URSP规则以及一个或多个第二URSP规则；或者，所述预设URSP规则包括所述第一URSP规则；
    其中，所述第一URSP规则为指示信息所在的URSP规则；所述第二URSP规则为优先级高于所述第一URSP规则的URSP规则；
    所述预设RSD包括第一RSD以及一个或多个第二RSD；或者，所述预设RSD包括所述第一RSD；
    其中，所述第一RSD为指示信息所在的RSD；所述第二RSD为优先级高于所述第一RSD的RSD。
  9. 根据权利要求7或8所述的切片接入方法，其特征在于，网络装置确定指示信息，包括根据如下一项或多项信息确定所述指示信息：用户签约信息、终端装置的位置、预配置信息。
  10. 根据权利要求7至9中任一项所述的切片接入方法，其特征在于，向终端装置发送所述指示信息，包括：向所述终端装置发送一个或多个URSP规则，所述一个或多个URSP规则中的至少一个包括所述指示信息。
  11. 根据权利要求7至10中任一项所述的切片接入方法，其特征在于，所述方法还包括：
    获取目标NSSAI；
    根据所述目标NSSAI确定网络选择辅助信息；
    向所述终端装置发送所述网络选择辅助信息；
    所述网络选择辅助信息包括如下一项或多项信息：支持目标切片集内一个或多个切片的一个或多个网络的信息、所述一个或多个网络的优先级、所述一个或多个网络分别支持的网络切片信息；
    所述目标切片集为目标NSSAI对应的一个或多个切片；所述目标NSSAI包括如下一种或多种：终端装置所请求网络切片对应的NSSAI、拒绝终端装置接入的网络切片对应的NSSAI、允许终端装置接入的网络切片对应的NSSAI。
  12. 一种切片接入装置，其特征在于，包括：
    通信接口，用于从网络装置接收一个或多个用户路由选择策略规则URSP rule，所述URSP规则中至少一个URSP规则包括指示信息；所述指示信息用于指示匹配一个或多个预设URSP规则或匹配一个或多个预设路由选择描述RSD；
    处理器，用于根据所述一个或多个URSP规则执行URSP匹配。
  13. 根据权利要求12所述的切片接入装置，其特征在于，所述预设URSP包括：非通配URSP规则；或者，所述预设URSP规则包括第一URSP规则以及一个或多个第二URSP规则；或者，所述预设URSP规则包括所述第一URSP规则；
    其中，所述第一URSP规则为指示信息所在的URSP规则；所述第二URSP规则为优先级高于所述第一URSP规则的URSP规则；
    所述预设RSD包括第一RSD以及一个或多个第二RSD；或者，所述预设RSD包 括所述第一RSD；
    其中，所述第一RSD为指示信息所在的RSD；所述第二RSD为优先级高于所述第一RSD的RSD。
  14. 根据权利要求12或13所述的切片接入装置，其特征在于，所述处理器，用于根据所述一个或多个URSP规则执行URSP匹配，包括：
    用于若所述一个或多个预设URSP规则中与当前待发起业务匹配的URSP规则对应的一个或多个单个网络切片选择辅助信息S-NSSAI均不被第一网络支持，停止URSP匹配；
    或者，若所述一个或多个预设RSD中与所述当前待发起业务匹配的RSD对应的一个或多个S-NSSAI均不被第一网络支持，停止URSP匹配。
  15. 根据权利要求14所述的切片接入装置，其特征在于，所述处理器，还用于通过移动性变更流程接入第二网络，并在所述第二网络中请求所述一个或多个S-NSSAI中的至少一个；
    其中，所述第二网络为支持所述一个或多个S-NSSAI中至少一个的网络。
  16. 根据权利要求12至15中任一项所述的切片接入装置，其特征在于，所述处理器，还用于获取网络选择辅助信息，所述网络选择辅助信息包括如下一项或多项信息：
    支持目标切片集内一个或多个切片的一个或多个网络的信息、所述一个或多个网络的优先级、所述一个或多个网络分别支持的网络切片信息；
    所述目标切片集为目标NSSAI对应的一个或多个切片；所述目标NSSAI包括如下一种或多种：终端装置所请求网络切片对应的NSSAI、拒绝终端装置接入的网络切片对应的NSSAI、允许终端装置接入的网络切片对应的NSSAI。
  17. 根据权利要求16所述的切片接入装置，其特征在于，所述处理器，用于通过移动性变更流程接入第二网络，包括：用于根据所述网络选择辅助信息执行移动性变更流程，以接入第二网络。
  18. 一种切片接入装置，其特征在于，包括：
    处理器，用于确定指示信息，所述指示信息用于指示匹配一个或多个预设URSP规则或匹配一个或多个预设路由选择描述RSD；
    通信接口，用于向终端装置发送所述指示信息。
  19. 根据权利要求18所述的切片接入装置，其特征在于，所述预设URSP规则，包括非通配URSP规则；或者，所述预设URSP包括：非通配URSP规则；或者，所述预设URSP规则包括第一URSP规则以及一个或多个第二URSP规则；或者，所述预设URSP规则包括所述第一URSP规则；
    其中，所述第一URSP规则为指示信息所在的URSP规则；所述第二URSP规则为优先级高于所述第一URSP规则的URSP规则；
    所述预设RSD包括第一RSD以及一个或多个第二RSD；或者，所述预设RSD包括所述第一RSD；
    其中，所述第一RSD为指示信息所在的RSD；所述第二RSD为优先级高于所述第一RSD的RSD。
  20. 根据权利要求18或19所述的切片接入装置，其特征在于，所述处理器，用于确定指示信息，包括：用于根据如下一项或多项信息确定所述指示信息：用户签约信息、终端装置的位置、预配置信息。
  21. 根据权利要求18至20中任一项所述的切片接入装置，其特征在于，所述通信接口，用于向终端装置发送所述指示信息，包括：用于向所述终端装置发送一个或多个URSP规则，所述一个或多个URSP规则中的至少一个包括所述指示信息。
  22. 根据权利要求18至21中任一项所述的切片接入装置，其特征在于，所述处理器，还用于：
    获取目标NSSAI；
    根据所述目标NSSAI确定网络选择辅助信息；
    向所述终端装置发送所述网络选择辅助信息；
    所述网络选择辅助信息包括如下一项或多项信息：支持目标切片集内一个或多个切片的一个或多个网络的信息、所述一个或多个网络的优先级、所述一个或多个网络分别支持的网络切片信息；
    所述目标切片集为目标NSSAI对应的一个或多个切片；所述目标NSSAI包括如下一种或多种：终端装置所请求网络切片对应的NSSAI、拒绝终端装置接入的网络切片对应的NSSAI、允许终端装置接入的网络切片对应的NSSAI。
  23. 一种计算机可读存储介质，其特征在于，包括程序或指令，当所述程序或指令被执行时，如权利要求1-6中任一项所述的切片接入方法被实现，或者，如权利要求7-11中任一项所述的切片接入方法被实现。
  24. 一种切片接入系统，其特征在于，包括如权利要求12-17中任一项所述的切片接入装置，以及权利要求18-22中任一项所述的切片接入装置。
PCT/CN2021/092614 2020-05-21 2021-05-10 切片接入方法、装置及系统 Ceased WO2021233148A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2022570437A JP7485793B2 (ja) 2020-05-21 2021-05-10 スライスアクセス方法、装置、及びシステム
EP21807768.3A EP4142218A4 (en) 2020-05-21 2021-05-10 Slice access method, device and system
KR1020227042561A KR20230007473A (ko) 2020-05-21 2021-05-10 슬라이스 액세스 방법, 디바이스 및 시스템
US18/054,529 US20230072956A1 (en) 2020-05-21 2022-11-10 Slice access method, apparatus, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010437050.1 2020-05-21
CN202010437050.1A CN113708947B (zh) 2020-05-21 2020-05-21 切片接入方法、装置及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/054,529 Continuation US20230072956A1 (en) 2020-05-21 2022-11-10 Slice access method, apparatus, and system

Publications (1)

Publication Number Publication Date
WO2021233148A1 true WO2021233148A1 (zh) 2021-11-25

Family

ID=78645860

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/092614 Ceased WO2021233148A1 (zh) 2020-05-21 2021-05-10 切片接入方法、装置及系统

Country Status (6)

Country Link
US (1) US20230072956A1 (zh)
EP (1) EP4142218A4 (zh)
JP (1) JP7485793B2 (zh)
KR (1) KR20230007473A (zh)
CN (1) CN113708947B (zh)
WO (1) WO2021233148A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114928871A (zh) * 2022-05-13 2022-08-19 中国电信股份有限公司 中继流量的方法、网络接入方法及终端、介质及设备
CN116419310A (zh) * 2021-12-29 2023-07-11 中国移动通信有限公司研究院 一种切片接入控制方法及装置、网络设备
WO2023163571A1 (ko) * 2022-02-28 2023-08-31 주식회사 넷큐브 네트워크 슬라이스 지원 장치 및 그 지원 방법
WO2023246620A1 (zh) * 2022-06-20 2023-12-28 华为技术有限公司 通信方法、装置和系统
JP2025508813A (ja) * 2022-02-25 2025-04-10 レノボ・シンガポール・プライベート・リミテッド ルート選択ポリシー規則のための訪問先ネットワーク案内

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115868207B (zh) * 2020-05-28 2025-03-14 高通股份有限公司 建立协议数据单元会话的方法
CN120111715A (zh) * 2021-01-26 2025-06-06 华为技术有限公司 通信方法及装置
CN116471218A (zh) * 2022-01-11 2023-07-21 腾讯科技（深圳）有限公司 终端路由选择策略ursp检测方法及相关设备
CN116827845A (zh) * 2022-03-21 2023-09-29 中国电信股份有限公司 路由选择策略配置方法、装置、设备及存储介质
CN114666863B (zh) * 2022-03-25 2024-11-05 Oppo广东移动通信有限公司 数据路由方法及装置
CN116867020A (zh) * 2022-03-28 2023-10-10 维沃移动通信有限公司 终端路由选择策略ursp确定方法、终端及网络侧设备
CN114679725B (zh) * 2022-04-29 2024-11-29 中国电信股份有限公司 网络连接建立方法、终端、网络侧设备以及存储介质
US12408104B2 (en) * 2022-06-07 2025-09-02 Dish Wireless L.L.C. Network slicing group
CN118102479A (zh) * 2022-11-25 2024-05-28 荣耀终端有限公司 一种网络切片匹配方法和装置
CN116321102B (zh) * 2022-12-23 2025-08-29 广东树米科技有限公司 一种基于5g切片服务进行实名制业务开通的处理方法
WO2024083362A1 (en) * 2023-03-28 2024-04-25 Lenovo (Singapore) Pte. Ltd. Method and apparatus for providing user equipment policy sections in an evolved packet system
CN116723587B (zh) * 2023-08-07 2023-11-21 荣耀终端有限公司 一种会话管理方法及电子设备
WO2025174150A1 (ko) * 2024-02-18 2025-08-21 엘지전자 주식회사 네트워크 슬라이스

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109286567A (zh) * 2018-11-23 2019-01-29 腾讯科技（深圳）有限公司 路由选择策略的获取方法、装置及设备
CN110430590A (zh) * 2019-08-15 2019-11-08 广东工业大学 网络切片匹配方法及装置
CN110474840A (zh) * 2018-05-09 2019-11-19 华为技术有限公司 数据传输方法、装置和可读存储介质
WO2019222901A1 (en) * 2018-05-22 2019-11-28 Nokia Shanghai Bell Co., Ltd. Method, apparatus and computer readable media for enforcing a rule related to traffic routing

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110149670B (zh) * 2018-02-13 2024-05-14 华为技术有限公司 一种数据路由选择的方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110474840A (zh) * 2018-05-09 2019-11-19 华为技术有限公司 数据传输方法、装置和可读存储介质
WO2019222901A1 (en) * 2018-05-22 2019-11-28 Nokia Shanghai Bell Co., Ltd. Method, apparatus and computer readable media for enforcing a rule related to traffic routing
CN109286567A (zh) * 2018-11-23 2019-01-29 腾讯科技（深圳）有限公司 路由选择策略的获取方法、装置及设备
CN110430590A (zh) * 2019-08-15 2019-11-08 广东工业大学 网络切片匹配方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4142218A4

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116419310A (zh) * 2021-12-29 2023-07-11 中国移动通信有限公司研究院 一种切片接入控制方法及装置、网络设备
JP2025508813A (ja) * 2022-02-25 2025-04-10 レノボ・シンガポール・プライベート・リミテッド ルート選択ポリシー規則のための訪問先ネットワーク案内
WO2023163571A1 (ko) * 2022-02-28 2023-08-31 주식회사 넷큐브 네트워크 슬라이스 지원 장치 및 그 지원 방법
CN114928871A (zh) * 2022-05-13 2022-08-19 中国电信股份有限公司 中继流量的方法、网络接入方法及终端、介质及设备
CN114928871B (zh) * 2022-05-13 2024-02-06 中国电信股份有限公司 中继流量的方法、网络接入方法及终端、介质及设备
WO2023246620A1 (zh) * 2022-06-20 2023-12-28 华为技术有限公司 通信方法、装置和系统

Also Published As

Publication number Publication date
JP7485793B2 (ja) 2024-05-16
US20230072956A1 (en) 2023-03-09
EP4142218A1 (en) 2023-03-01
KR20230007473A (ko) 2023-01-12
CN113708947A (zh) 2021-11-26
EP4142218A4 (en) 2023-07-19
JP2023526415A (ja) 2023-06-21
CN113708947B (zh) 2023-02-28

Similar Documents

Publication Publication Date Title
CN113708947B (zh) 切片接入方法、装置及系统
US12550206B2 (en) User plane function selection for isolated network slice
EP3695653B1 (en) Ue configuration and update with network slice selection policy
US12317122B2 (en) Method of authorization for network slicing
US20260107339A1 (en) Enhanced multi-access protocol data unit (pdu) session
US20230422142A1 (en) Collaboration Between Mobile Network Operators for Mobile Edge Computing Applications
US11991660B2 (en) Apparatus, methods, and computer programs
WO2020248828A1 (zh) 通信方法、装置及系统
WO2020108002A1 (zh) 一种传输策略确定方法、策略控制方法及装置
CN115734282B (zh) 一种服务质量的处理方法、装置和通信系统
WO2023035925A1 (zh) 一种业务处理方法、装置和系统
WO2021046803A1 (en) Method, device, computer-readable storage and carrier for policy control
WO2020073899A1 (zh) 数据传输方法及装置
CN113746649B (zh) 一种网络切片控制方法及通信装置
US20240349165A1 (en) Method for slice resource release
CN118055519A (zh) 信息传输方法、会话建立方法、装置及存储介质
CN119032608A (zh) 无线通信的方法、用户设备及网络设备
CN117135610A (zh) 策略控制的方法与装置
WO2023280000A1 (zh) 一种通信方法、系统和装置
CN114270931B (zh) 用于网络切片的授权方法
CN118556427A (zh) Nsac信息的动态检索
CN120814299A (zh) 网络切片
WO2025098105A1 (zh) 一种边缘应用服务器发现方法及装置
CN118785275A (zh) 一种通信方法及通信装置
CN117044179A (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: 21807768

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022570437

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 202217066709

Country of ref document: IN

ENP Entry into the national phase

Ref document number: 2021807768

Country of ref document: EP

Effective date: 20221122

ENP Entry into the national phase

Ref document number: 20227042561

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

WWW Wipo information: withdrawn in national office

Ref document number: 2021807768

Country of ref document: EP