WO2021244165A1 - 网络切片重选方法和装置、电子设备、存储介质 - Google Patents

网络切片重选方法和装置、电子设备、存储介质 Download PDF

Info

Publication number
WO2021244165A1
WO2021244165A1 PCT/CN2021/088339 CN2021088339W WO2021244165A1 WO 2021244165 A1 WO2021244165 A1 WO 2021244165A1 CN 2021088339 W CN2021088339 W CN 2021088339W WO 2021244165 A1 WO2021244165 A1 WO 2021244165A1
Authority
WO
WIPO (PCT)
Prior art keywords
network slice
user equipment
routing policy
policy rule
equipment routing
Prior art date
Application number
PCT/CN2021/088339
Other languages
English (en)
French (fr)
Inventor
杨海城
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP21818518.9A priority Critical patent/EP4132108A4/en
Priority to US17/922,616 priority patent/US20230224780A1/en
Priority to JP2022548024A priority patent/JP7410312B2/ja
Publication of WO2021244165A1 publication Critical patent/WO2021244165A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/38—Reselection control by fixed network equipment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • 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
    • 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

Definitions

  • the embodiments of the present disclosure relate to, but are not limited to, the field of wireless communication.
  • the 2G/3G/4G network only fulfills a single service requirement-telephone or Internet, and cannot meet the new service requirements brought about by the explosive growth of data services.
  • the 5G network is oriented to multiple connections and diversified services, and needs to be able to be deployed flexibly like building blocks, to facilitate the rapid on-line or off-line of new services, and to meet people’s growing demand for data services.
  • the industry generally believes that network slicing can realize 5G multi-scenarios and diversified services, and is of indispensable importance in many 5G technologies.
  • Network slicing technology essentially divides the operator’s physical network into multiple virtual networks. Each virtual network is divided according to different service requirements, such as delay, bandwidth, security, and reliability, to flexibly respond to different networks Application scenarios.
  • the embodiments of the present disclosure provide a network slice reselection method and device, electronic equipment, and computer-readable storage medium.
  • embodiments of the present disclosure provide a network slice reselection method, including: receiving a message sent by the network side for the currently selected network slice, and reselecting the network slice; wherein the reason carried in the message is insufficient resources.
  • an embodiment of the present disclosure provides an electronic device, including: at least one processor; a memory on which at least one program is stored.
  • the at least one One processor implements any network slice reselection method described in this article.
  • embodiments of the present disclosure provide a computer-readable storage medium having a computer program stored on the computer-readable storage medium, and when the computer program is executed by a processor, any network slice reselection described herein is implemented. method.
  • FIG. 1 is a flowchart of a network slice reselection method provided by an embodiment of the disclosure
  • FIG. 2 is a schematic diagram of the structure of a single network slice selection auxiliary information according to an embodiment of the disclosure
  • Example 3 is a flowchart of a network slice reselection method provided in Example 1 of an embodiment of the disclosure
  • Example 4 is a flowchart of a network slice reselection method provided in Example 2 of the embodiments of the disclosure.
  • FIG. 5 is a flowchart of a network slice reselection method provided in Example 3 of an embodiment of the disclosure
  • FIG. 6 is a flowchart of a network slice reselection method provided in Example 4 of an embodiment of the disclosure.
  • FIG. 7 is a block diagram of a network slice reselection device provided by an embodiment of the disclosure.
  • the embodiments of the present disclosure are based on the proposed processing method of network slicing congestion of the 5G network, the method of processing congestion in the embodiments of the present disclosure is also applicable to future communication networks (such as 6G, 7G, etc.), or any other use Communication network realized by network slicing technology.
  • FIG. 1 is a flowchart of a network slice reselection method provided by an embodiment of the disclosure.
  • an embodiment of the present disclosure provides a network slice reselection method, which is applied to a terminal (for example, executed by the terminal).
  • the method may include: Step 100: Receive a network slice for the current selection from the network side For the sent message, reselect the network slice; wherein, the reason carried in the message is insufficient resource.
  • the message sent by the network side for the currently selected network slice is not received; or, the message sent by the network side for the currently selected network slice is received, and the reason contained in the message is not insufficient resources. There is no network congestion in the currently selected network slice, and this process ends.
  • the network slice reselection method provided by the embodiments of the present disclosure, when a message sent by the network side for the currently selected network slice is received, it is considered that the currently selected network slice is network congested, and the network slice is reselected, which reduces the currently selected network slice. While the network is congested, it is ensured that the terminal continues to perform services through the newly selected network slice, thereby improving the user experience.
  • the message includes any one of the following: Protocol Data Unit (PDU, Protocol Data Unit) Session Establishment Reject (PDU Session Establishment Reject) message, PDU Session Modification Reject (PDU Session Modification Reject) message, PDU Session release (PDU Session Release) message.
  • PDU Protocol Data Unit
  • PDU Session Establishment Reject PDU Session Establishment Reject
  • PDU Session Modification Reject PDU Session Modification Reject
  • PDU Session release PDU Session Release
  • PDU Session Establishment Reject message PDU Session Modification Reject message
  • PDU Session Release message are the names of messages in the 5G network.
  • the above messages can have other names with the same name.
  • the function message may also be another message with the same function, and the specific name of the message is not limited in the embodiment of the present disclosure.
  • network slice selection is achieved by matching available URSP rules in a URSP (UE Route Selection Policy) rule list.
  • URSP UE Route Selection Policy
  • the URSP rule list includes: a URSP rule list preset by the terminal and a URSP rule list updated from the network side.
  • the priority of the URSP rule list updated from the network side is higher than the URSP rule list preset in the factory.
  • the available URSP rules can be matched in the URSP rule list according to the applied network slice parameters to obtain the S-NSSAI (Single Network Slice Selection Assistance Information) of the network slice.
  • S-NSSAI Single Network Slice Selection Assistance Information
  • the network slicing parameter includes but is not limited to at least one of the following: Data Network Name (DNN, Data Network Name), application identifier, and Fully Qualified Domain Name (FQDN, Fully Qualified Domain Name).
  • DNN Data Network Name
  • FQDN Fully Qualified Domain Name
  • the input parameter of the URSP rule is at least one of DNN, application ID, FQDN, etc.
  • the output parameter is S-NSSAI.
  • S-NSSAI identifies a network slice. As shown in Figure 2, S-NSSAI includes the following two parts: Slice/Service Type (SST) and Slice Differentiator (SD).
  • SST Slice/Service Type
  • SD Slice Differentiator
  • SST represents the expected network slicing behavior in terms of functions and services.
  • SST can be a standard value (e.g., Enhanced Mobile Broadband (eMBB), the ultra-reliable Low Latency Communication (uRLLC) ), Massive Internet of Things (MIoT, Massive Internet of Things)), it can also be a non-standard value.
  • eMBB Enhanced Mobile Broadband
  • uRLLC ultra-reliable Low Latency Communication
  • MIoT Massive Internet of Things
  • MIoT Massive Internet of Things
  • the length of SST is 1 byte
  • the value range of standard SST (the current protocol only uses three values, as shown in Table 1) is 0-127
  • the operator-defined value range is 128-255.
  • the operator-defined value is only valid under this network, and the standard value is common to the entire network.
  • SD is optional information, supplementing SST to distinguish multiple network slices of the same SST.
  • Case 1 The terminal is a single-card user. In this case, there is only one URSP rule list, that is, the following first URSP rule list.
  • the method further includes: converting the URSP rule corresponding to the currently selected network slice Identified as unavailable; correspondingly, the reselecting the network slice includes: matching a URSP rule that is not identified as unavailable or matching a URSP rule that is identified as available in the first URSP rule list, and reselecting the matched available URSP rule The network slice corresponding to the URSP rule.
  • any of the following methods may be adopted:
  • Manner 1 Mark the URSP rule corresponding to the currently selected network slice as unavailable within a preset time; remove the identification of the URSP rule after the preset time; or, after the preset time
  • the URSP rule is identified as available.
  • a timer can be set. When the timer starts, the URSP rule corresponding to the currently selected network slice is marked as unavailable; when the timer expires, the URSP rule is removed or the URSP rule is marked as available;
  • Method 2 Detect whether the network slice corresponding to the URSP rule identified as unavailable has network congestion; detect that the network slice corresponding to the URSP rule identified as unavailable does not have network congestion, and remove the identification of the URSP rule; or , The URSP rule is identified as available; network congestion is detected in the network slice corresponding to the URSP rule identified as unavailable, and the identification of the URSP rule is retained.
  • Case 2 The terminal is a dual-card or multi-card user.
  • each card of the terminal corresponds to a URSP rule list, for example, the following first URSP rule list and second URSP rule list.
  • the method further includes: converting the URSP rule corresponding to the currently selected network slice Be identified as unavailable; correspondingly, the reselecting the network slice includes: matching a URSP rule that is not identified as unavailable or a URSP rule that is identified as available in the first URSP rule list, and reselecting the matched available URSP rule The network slice corresponding to the rule.
  • the reselecting the network slice further includes: reselecting the available URSP rule corresponding to the second URSP rule list Network slicing; wherein, the first URSP rule list is a URSP rule list corresponding to a card that is currently undergoing service processing, and the second URSP rule list is a URSP rule list corresponding to a card that is not currently undergoing service processing.
  • the URSP rule that is not identified as unavailable or the URSP rule that is identified as available may be matched in the second URSP rule list, and the network slice corresponding to the matched available URSP rule can be reselected.
  • the terminal can traverse all URSP rule lists, and when none of the URSP rule lists match any available URSP rules, the process ends.
  • any of the following methods may be adopted:
  • Manner 1 Mark the URSP rule corresponding to the currently selected network slice as unavailable within a preset time; remove the identification of the URSP rule after the preset time; or, after the preset time
  • the URSP rule is identified as available.
  • a timer can be set. When the timer starts, the URSP rule corresponding to the currently selected network slice is marked as unavailable; when the timer expires, the URSP rule is removed or the URSP rule is marked as available;
  • Method 2 Detect whether the network slice corresponding to the URSP rule identified as unavailable has network congestion; detect that the network slice corresponding to the URSP rule identified as unavailable does not have network congestion, remove the identification of the URSP rule or change The URSP rule is identified as available; network congestion is detected in the network slice corresponding to the URSP rule that is identified as unavailable, and the URSP rule identification continues to be retained.
  • the network slice reselection method may include step 300 to step 305.
  • step 300 the application applies for network slice A.
  • step 301 it is judged whether the identity of the application is correct, if the identity of the application is correct, proceed to step 302; if the identity of the application is incorrect, the process ends.
  • step 302 the S-NSSAI is obtained by matching the available URSP rules in the URSP rule list.
  • the available URSP rules may be matched in the URSP rule list according to the applied network slicing parameters to obtain the S-NSSAI of the network slicing.
  • the network slice parameters include but are not limited to at least one of the following: DNN, application identifier, FQDN.
  • the input parameter of the URSP rule is at least one of DNN, application ID, FQDN, etc.
  • the output parameter is S-NSSAI.
  • a PDU session establishment request is sent to the network side.
  • the PDU session establishment request carries the S-NSSAI to indicate the network slice that it wishes to apply for.
  • step 304 monitor whether the PDU Session Establishment Reject message on the network side is received, and determine whether the reason carried in the message is an insufficient resource, if a PDU Session Establishment Reject message is received, and the reason carried in the message is insufficient resource, continue Go to step 305; if the PDU Session Establishment Reject message is not received; or the PDU Session Establishment Reject message is received, and the reason carried in the message is not sufficient resource, then this process is ended.
  • step 305 the URSP rule is marked as "unavailable", and step 302 is continued.
  • the network slice reselection method may include step 400 to step 404.
  • step 400 the application applies for network slice A, and the PDU session has been successfully created.
  • step 401 monitor whether the PDU Session Modification Reject or PDU Session Release message sent by the network side to the terminal is received, and determine whether the reason carried in the message is insufficient resource; if the PDU Session Modification Reject or PDU sent to the terminal by the network side is received PDU Session Release message, and the reason contained in the message is insufficient resource, then continue to step 402; if no PDU Session Modification Reject or PDU Session Release message is received; or, PDU Session Modification Reject or PDU Session Modification Reject sent from the network side to the terminal is received. PDU Session Release message, and the reason carried in the message is not sufficient resource, then this process ends.
  • step 402 the URSP rule corresponding to network slice A is marked as "unavailable”.
  • step 403 the S-NSSAI is obtained by matching the available URSP rules in the URSP rule list.
  • step 404 it is determined whether the PDU session corresponding to the network slice has been created. If the PDU session corresponding to the network slice has been created, the existing PDU session is used. If the PDU session has not been created, a PDU session establishment request is sent to the network side, PDU The session establishment request carries the S-NSSAI, indicating the network slice to be applied for.
  • This example describes the method of handling congestion in the dual-card scenario (two Subscriber Identity Module (SIM, Subscriber Identity Module) cards of different operators, assuming that the data service of SIM card 1 is currently used).
  • SIM Subscriber Identity Module
  • SIM Subscriber Identity Module
  • the method may include steps 500 to 505.
  • step 500 the application applies for the network slice A of the SIM card 1, and the PDU session has been successfully created.
  • step 501 monitor whether the PDU Session Modification Reject or PDU Session Release message sent by the network side to the terminal is received, and determine whether the reason carried in the message is an insufficient resource; if the PDU Session Modification Reject or PDU sent to the terminal by the network side is received PDU Session Release message, and the reason contained in the message is insufficient resource, continue to step 502; if no PDU Session Modification Reject or PDU Session Release message is received; or, PDU Session Modification Reject or PDU Session Modification Reject or sent from the network side to the terminal are received. PDU Session Release message, and the reason carried in the message is not sufficient resource, then this process ends.
  • step 502 the URSP rule corresponding to the network slice A of the SIM card 1 is marked as "unavailable”.
  • step 503 if the available URSP rule cannot be matched in the URSP rule list of SIM card 1, then the available URSP rule is matched in the URSP rule list of SIM card 2, for example, the network slice B corresponding to the available URSP rule is matched. Or network slice C, get the S-NSSAI of network slice B or network slice C.
  • step 504 the data service is switched from SIM card 1 to SIM card 2, and SIM card 2 is successfully registered on the 5G network.
  • a PDU session establishment request is sent to the network side.
  • the PDU session establishment request carries the S-NSSAI to indicate the network slice that it wishes to apply for.
  • This example describes the method of handling congestion in the dual-card scenario (two Subscriber Identity Module (SIM, Subscriber Identity Module) cards of different operators, assuming that the data service of SIM card 1 is currently used).
  • SIM Subscriber Identity Module
  • SIM card 1 of the terminal tries to register to the 5G network of SIM card 2, and it is created after SIM card 1 is successfully registered on the 5G network of SIM card 2.
  • Specify the PDU session of the network slice that is, the scenario where the SIM card 1 roams to the network of the SIM card 2).
  • the method may include steps 600 to 605.
  • step 600 the application applies for the network slice A of the SIM card 1, and the PDU session has been successfully created.
  • step 601 monitor whether the PDU Session Modification Reject or PDU Session Release message sent by the network side to the terminal is received, and determine whether the reason carried in the message is insufficient resource; if the PDU Session Modification Reject or PDU sent to the terminal by the network side is received PDU Session Release message, and the reason contained in the message is insufficient resource, proceed to step 602; if the PDU Session Modification Reject or PDU Session Release message is not received; or, the PDU Session Modification Reject or PDU Session Modification Reject sent from the network side to the terminal is received. PDU Session Release message, and the reason carried in the message is not sufficient resource, then this process ends.
  • step 602 the URSP rule corresponding to the network slice A of the SIM card 1 is identified as "unavailable”.
  • step 603 if the available URSP rule cannot be matched in the URSP rule list of SIM card 1, then the available URSP rule is matched in the URSP rule list of SIM card 2, for example, the network slice B corresponding to the available URSP rule is matched. Or network slice C, get the S-NSSAI of network slice B or network slice C.
  • step 604 the SIM card 1 attempts to register to the 5G network of the SIM card 2, and the SIM card 1 successfully registers on the 5G network of the SIM card 2.
  • a PDU session establishment request is sent to the network side.
  • the PDU session establishment request carries the S-NSSAI to indicate the network slice to be applied for.
  • an embodiment of the present disclosure provides an electronic device, including: at least one processor; a memory on which at least one program is stored.
  • the at least one processor implements any of the foregoing.
  • a network slice reselection method including: at least one processor; a memory on which at least one program is stored.
  • the processor is a device with data processing capabilities, which includes but is not limited to a central processing unit (CPU), etc.;
  • the memory is a device with data storage capabilities, which includes but is not limited to random access memory (RAM, more specifically such as SDRAM). , DDR, etc.), read-only memory (ROM), charged erasable programmable read-only memory (EEPROM), flash memory (FLASH).
  • RAM random access memory
  • ROM read-only memory
  • EEPROM charged erasable programmable read-only memory
  • FLASH flash memory
  • the processor and the memory are connected to each other through a bus, and further connected to other components of the computing device.
  • embodiments of the present disclosure provide a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, any one of the foregoing network slice reselection methods is implemented.
  • FIG. 7 is a block diagram of a network slice reselection device provided by an embodiment of the disclosure.
  • an embodiment of the present disclosure provides a network slice reselection device, including: a congestion detection module 701, configured to monitor whether a message sent by the network side for the currently selected network slice is received, and determine whether the message carries Whether the reason is insufficient resources; and the network slice selection module 702 is configured to receive the message sent by the network side for the currently selected network slice by the congestion detection module 701, and the reason carried in the message is insufficient resources, and reselect the network slice.
  • a congestion detection module 701 configured to monitor whether a message sent by the network side for the currently selected network slice is received, and determine whether the message carries Whether the reason is insufficient resources
  • the network slice selection module 702 is configured to receive the message sent by the network side for the currently selected network slice by the congestion detection module 701, and the reason carried in the message is insufficient resources, and reselect the network slice.
  • the message includes any one of the following: a protocol data unit session establishment rejection message, a protocol data unit session modification rejection message, and a protocol data unit session release message.
  • the network slice selection module 702 may be configured to: the congestion detection module 701 receives a message sent by the network side for the currently selected network slice, and the reason carried in the message is insufficient resources, and the current selection
  • the user equipment routing policy rule corresponding to the network slice is identified as unavailable; the user equipment routing policy rule that is not identified as unavailable is matched in the first user equipment routing policy rule list or the user equipment identified as available is matched
  • the routing policy rule is to reselect the network slice corresponding to the available user equipment routing policy rule that is matched.
  • the network slice selection module 702 may be configured to implement the identification of the user equipment routing policy rule corresponding to the currently selected network slice as unavailable in the following manner: The user equipment routing policy rule corresponding to the selected network slice is identified as unavailable; the identification of the user equipment routing policy rule is removed after the preset time; or the user equipment routing policy rule is identified after the preset time The device routing policy rule is identified as available.
  • the network slice selection module 702 is further configured to: detect whether the network slice corresponding to the user equipment routing policy rule identified as unavailable is network congested; and the user equipment route identified as unavailable is detected The network slice corresponding to the selection policy rule does not have network congestion, and the identification of the user equipment routing policy rule is removed; or, the user equipment routing policy rule is identified as available.
  • the network slice selection module 702 is further configured to: when the available user equipment routing policy rules cannot be matched in the first user equipment routing policy rule list, the second user equipment routing policy Reselect the network slice corresponding to the available user equipment routing policy rule in the rule list;
  • the first user equipment routing policy rule list is a user equipment routing policy rule list corresponding to a card currently undergoing service processing
  • the second user equipment routing policy rule list is a card that is not currently undergoing service processing The corresponding user equipment routing policy rule list.
  • the specific implementation process of the foregoing network slicing reselection device is the same as the specific implementation process of the network slicing reselection method in the foregoing embodiment, and will not be repeated here.
  • Such software may be distributed on a computer-readable medium, and the computer-readable medium may include a computer storage medium (or a non-transitory medium) and a communication medium (or a transitory medium).
  • the term computer storage medium includes volatile and non-volatile implementations in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Sexual, removable and non-removable media.
  • Computer storage media include but are not limited to RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, tapes, magnetic disk storage or other magnetic storage, or can be used Any other medium that can store desired information and can be accessed by a computer.
  • a communication medium usually contains computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery medium. .

Landscapes

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

Abstract

本申请提供了一种网络切片重选方法，该方法包括：接收到网络侧针对当前选择的网络切片发送的消息，重新选择网络切片；其中，所述消息携带的理由为资源不足。本申请还提供了一种网络切片重选装置、电子设备、计算机可读存储介质。

Description

网络切片重选方法和装置、电子设备、存储介质 技术领域
本公开实施例涉及但不限于无线通信领域。
背景技术
2G/3G/4G网络仅实现了单一的业务需求——电话或上网，无法满足数据业务爆炸式增长所带来的新业务需求。
5G网络面向多连接和多样化业务，需要能够像积木一样灵活部署，方便进行新业务的快速上线或下线，满足人们日益增长的数据业务需求。业界普遍认为，网络切片可实现5G多场景、多样化业务，在5G诸多技术中具有不可或缺的重要性。
网络切片技术本质上是将运营商的物理网络划分为多个虚拟网络，每一个虚拟网络根据不同的服务需求，如时延、带宽、安全性和可靠性等来划分，以灵活应对不同的网络应用场景。
然而，在人员密集区域，网络切片拥塞仍不可避免。
发明内容
本公开实施例提供一种网络切片重选方法和装置、电子设备、计算机可读存储介质。
第一方面，本公开实施例提供一种网络切片重选方法，包括：接收到网络侧针对当前选择的网络切片发送的消息，重新选择网络切片；其中，所述消息携带的理由为资源不足。
第二方面，本公开实施例提供一种电子设备，包括：至少一个处理器；存储器，其上存储有至少一个程序，当所述至少一个程序被所述至少一个处理器执行，使得所述至少一个处理器实现本文所述任意一种网络切片重选方法。
第三方面，本公开实施例提供一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现本文所述任意一种网络切片重选方法。
附图说明
图1为本公开实施例提供的一种网络切片重选方法的流程图；
图2为本公开实施例的单个网络切片选择辅助信息的结构示意图；
图3为本公开实施例的示例1提供的一种网络切片重选方法的流程图；
图4为本公开实施例的示例2提供的一种网络切片重选方法的流程图；
图5为本公开实施例的示例3提供的一种网络切片重选方法的流程图；
图6为本公开实施例的示例4提供的一种网络切片重选方法的流程图；
图7为本公开实施例提供的一种网络切片重选装置的组成框图。
具体实施方式
为使本领域的技术人员更好地理解本公开的技术方案，下面结合附图对本公开提供的网络切片重选方法和装置、电子设备、计算机可读存储介质进行详细描述。
在下文中将参考附图更充分地描述示例实施例，但是所述示例实施例可以以不同形式来体现且不应当被解释为限于本文阐述的实施例。反之，提供这些实施例的目的在于使本公开透彻和完整，并将使本领域技术人员充分理解本公开的范围。
在不冲突的情况下，本公开各实施例及实施例中的各特征可相互组合。
如本文所使用的，术语“和/或”包括至少一个相关列举条目的任何和所有组合。
本文所使用的术语仅用于描述特定实施例，且不意欲限制本公开。如本文所使用的，单数形式“一个”和“该”也意欲包括复数形式，除非上下文另外清楚指出。还将理解的是，当本说明书中使用术 语“包括”和/或“由……制成”时，指定存在所述特征、整体、步骤、操作、元件和/或组件，但不排除存在或添加至少一个其它特征、整体、步骤、操作、元件、组件和/或其群组。
除非另外限定，否则本文所用的所有术语(包括技术和科学术语)的含义与本领域普通技术人员通常理解的含义相同。还将理解，诸如那些在常用字典中限定的那些术语应当被解释为具有与其在相关技术以及本公开的背景下的含义一致的含义，且将不解释为具有理想化或过度形式上的含义，除非本文明确如此限定。
本公开实施例虽然是基于5G网络的网络切片的拥塞所提出的处理方法，但是本公开实施例的处理拥塞的方法同样适用于未来的通信网络(如6G、7G等)，或者，其他任何采用网络切片技术实现的通信网络。
图1为本公开实施例提供的一种网络切片重选方法的流程图。
第一方面，参照图1，本公开实施例提供一种网络切片重选方法，应用于终端(例如，由终端执行)，该方法可以包括：步骤100、接收到网络侧针对当前选择的网络切片发送的消息，重新选择网络切片；其中，所述消息携带的理由为资源不足(insufficient resource)。
在一些示例性实施例中，没有接收到网络侧针对当前选择的网络切片发送的消息；或者，接收到网络侧针对当前选择的网络切片发送的消息，且消息中携带的理由不是资源不足，认为当前选择的网络切片没有发生网络拥塞，结束本流程。
本公开实施例提供的网络切片重选方法，在接收到网络侧针对当前选择的网络切片发送的消息时，认为当前选择的网络切片发生网络拥塞，重新选择网络切片，减轻了当前选择的网络切片的网络拥塞的同时，保证终端通过重新选择的网络切片继续进行业务，从而提高了用户体验。
在一些示例性实施例中，所述消息包括以下任意一个：协议数据单元(PDU，Protocol Data Unit)会话建立拒绝(PDU Session Establishment Reject)消息、PDU会话修改拒绝(PDU Session Modification Reject)消息、PDU会话释放(PDU Session Release) 消息。
需要说明的是PDU Session Establishment Reject消息、PDU Session Modification Reject消息、PDU Session Release消息是5G网络中的消息名称，随着网络技术的发展，未来的通信系统中，上述消息可以是其他名称的具有相同功能的消息，也可以是其他具有相同功能的消息，本公开实施例对消息的具体名称不作限定。
在一些示例性实施例中，通过在URSP(用户设备路由选择策略,UE Route Selection Policy)规则列表中匹配可用的URSP规则的方式来实现网络切片的选择。
在一些示例性实施例中，URSP规则列表包括：终端出厂预先设置的URSP规则列表，以及从网络侧更新的URSP规则列表。从网络侧更新的URSP规则列表的优先级高于终端出厂预先设置的URSP规则列表。
在一些示例性实施例中，可以根据应用的网络切片参数在URSP规则列表中匹配可用的URSP规则，得到网络切片的S-NSSAI(单个网络切片选择辅助信息，Single Network Slice Selection Assistance Information)。
在一些示例性实施例中，网络切片参数包括但不限于以下至少之一：数据网络名称(DNN，Data Network Name)、应用标识、全限定域名(FQDN，Fully Qualified Domain Name)。
简单的说，URSP规则的输入参数是DNN、应用标识、FQDN等中的至少之一，输出参数是S-NSSAI。
在一些示例性实施例中，S-NSSAI标识了一个网络切片。如图2所示，S-NSSAI包括以下两部分：切片/服务类型(SST，Slice/Service Type)和切片差分器(SD，Slice Differentiator)。
其中，SST表示在功能和服务方面的预期网络切片行为，SST可以是一个标准值(如增强型移动宽带(eMBB，Enhanced Mobile Broadband)、超可靠低延时通信(uRLLC，the ultra Reliable Low Latency Communication)、大规模物联网(MIoT，Massive Internet of Thing))，也可以是一个非标准值。
SST的长度为1字节，标准SST的取值范围(当前协议只用了三个值，如表1所示)为0-127，运营商自定义取值范围为128-255。运营商自定义的值只在本网下有效，对于标准值全网通用。
其中，SD是可选信息，补充SST以区分相同SST的多个网络切片。
SST SST的值 特征
eMBB 1 适用于5G eMBB的网络切片
URLLC 2 适用于URLLC的网络切片
MIoT 3 适用于MIoT的网络切片
表1
下面分两种情况分别描述网络切片的重选。
情况一、终端为单卡用户，这种情况下，只有一个URSP规则列表，即下述第一URSP规则列表。
在一些示例性实施例中，所述接收到网络侧针对当前选择的网络切片发送的消息之后，所述重新选择网络切片之前，该方法还包括：将所述当前选择的网络切片对应的URSP规则标识为不可用；相应的，所述重新选择网络切片包括：在第一URSP规则列表中匹配没有被标识为不可用的URSP规则或者匹配被标识为可用的URSP规则，重新选择匹配到的可用的URSP规则对应的网络切片。
在一些示例性实施例中，为了保证被标识为不可用的URSP规则后续可重新供终端选择使用，可以采用以下任一种方式实现：
方式一、在预设时间内将所述当前选择的网络切片对应的URSP规则标识为不可用；在所述预设时间后去除对所述URSP规则的标识；或者，在所述预设时间后将所述URSP规则标识为可用。例如，可以设置一个定时器，当定时器启动时，将当前选择的网络切片对应的URSP规则标识为不可用；当定时器超时时，去除对URSP规则的标识或将URSP规则标识为可用；
方式二、检测被标识为不可用的URSP规则对应的网络切片是否发生网络拥塞；检测到被标识为不可用的URSP规则对应的网络切片没有发生网络拥塞，去除对所述URSP规则的标识；或者，将URSP 规则标识为可用；检测到被标识为不可用的URSP规则对应的网络切片发生网络拥塞，继续保留对URSP规则的标识。
情况二、终端为双卡或多卡用户，这种情况下，终端的每一个卡对应一个URSP规则列表，例如，下述第一URSP规则列表和第二URSP规则列表。
在一些示例性实施例中，所述接收到网络侧针对当前选择的网络切片发送的消息之后，所述重新选择网络切片之前，该方法还包括：将所述当前选择的网络切片对应的URSP规则标识为不可用；相应的，所述重新选择网络切片包括：在第一URSP规则列表中匹配没有被标识为不可用的URSP规则或被标识为可用的URSP规则，重新选择匹配到的可用的URSP规则对应的网络切片。
在另一些示例性实施例中，当在第一URSP规则列表中匹配不到可用的URSP规则时，所述重新选择网络切片还包括：在第二URSP规则列表中重新选择可用的URSP规则对应的网络切片；其中，所述第一URSP规则列表为当前正在进行业务处理的卡对应的URSP规则列表，所述第二URSP规则列表为当前未进行业务处理的卡对应的URSP规则列表。
具体的，可以在第二URSP规则列表中匹配没有被标识为不可用的URSP规则或被标识为可用的URSP规则，重新选择匹配到的可用的URSP规则对应的网络切片。
也就是说，终端可以遍历所有URSP规则列表，当所有URSP规则列表均匹配不到可用的URSP规则时，结束本流程。
在一些示例性实施例中，为了保证被标识为不可用的URSP规则后续可重新供终端选择使用，可以采用以下任一种方式实现：
方式一、在预设时间内将所述当前选择的网络切片对应的URSP规则标识为不可用；在所述预设时间后去除对所述URSP规则的标识；或者，在所述预设时间后将所述URSP规则标识为可用。例如，可以设置一个定时器，当定时器启动时，将当前选择的网络切片对应的URSP规则标识为不可用；当定时器超时时，去除对URSP规则的标识或将URSP规则标识为可用；
方式二、检测被标识为不可用的URSP规则对应的网络切片是否发生网络拥塞；检测到被标识为不可用的URSP规则对应的网络切片没有发生网络拥塞，去除对所述URSP规则的标识或将URSP规则标识为可用；检测到被标识为不可用的URSP规则对应的网络切片发生网络拥塞，继续保留对URSP规则的标识。
下面通过具体示例详细说明上述实施例的具体实现过程，所列举的示例仅仅是为了说明方便，不用于限定本公开实施例的保护范围。
示例1
如图3所示，该网络切片重选方法可以包括步骤300至步骤305。
在步骤300，应用申请网络切片A。
在步骤301，判断应用的身份是否正确，如果应用的身份正确，则继续执行步骤302；如果应用的身份不正确，则结束本流程。
在一些示例性实施例中，可以根据应用标识、应用包名、应用签名中的至少之一判断应用的身份是否正确。
在步骤302，在URSP规则列表中匹配可用的URSP规则得到S-NSSAI。
在一些示例性实施例中，可以根据应用的网络切片参数在URSP规则列表中匹配可用的URSP规则，得到网络切片的S-NSSAI。
在一些示例性实施例中，网络切片参数包括但不限于以下至少之一：DNN、应用标识、FQDN。
简单的说，URSP规则的输入参数是DNN、应用标识、FQDN等中的至少之一，输出参数是S-NSSAI。
在步骤303，向网络侧发送PDU会话建立请求，PDU会话建立请求中携带S-NSSAI，表明希望申请的网络切片。
在步骤304，监听是否接收到网络侧的PDU Session Establishment Reject消息，且判断消息中携带的理由是否为insufficient resource，如果接收到PDU Session Establishment Reject消息，且消息中携带的理由为insufficient resource，则继续执行步骤305；如果没有接收到PDU Session Establishment Reject消息；或接收到PDU Session Establishment Reject消息，且消息中携带的理由不 是insufficient resource，则结束本流程。
在步骤305，将该条URSP规则标识为“不可用”，继续执行步骤302。
示例2
如图4所示，该网络切片重选方法可以包括步骤400至步骤404。
在步骤400，应用申请网络切片A，且已成功创建PDU会话。
在步骤401，监听是否接收到网络侧给终端发送的PDU Session Modification Reject或PDU Session Release消息，且判断消息中携带的理由是否为insufficient resource；如果接收到网络侧给终端发送的PDU Session Modification Reject或PDU Session Release消息，且消息中携带的理由为insufficient resource，则继续执行步骤402；如果没有接收到PDU Session Modification Reject或PDU Session Release消息；或者，接收到网络侧给终端发送的PDU Session Modification Reject或PDU Session Release消息，且消息中携带的理由不是insufficient resource，则结束本流程。
在步骤402，将网络切片A对应的URSP规则标识为“不可用”。
在步骤403，在URSP规则列表中匹配可用的URSP规则得到S-NSSAI。
在步骤404，判断网络切片对应的PDU会话是否已创建，如果网络切片对应的PDU会话已创建，则使用已有的PDU会话，如果PDU会话未创建，则向网络侧发送PDU会话建立请求，PDU会话建立请求中携带S-NSSAI，表明希望申请的网络切片。
示例3
本示例描述该双卡场景(不同运营商的两张用户识别模块(SIM，Subscriber Identity Module)卡，假设当前使用的是SIM卡1的数据业务)下的处理拥塞的方法，在进行网络切片重选时，发现SIM卡2所在的5G网络下有可用的网络切片，则终端切换数据业务到SIM卡2，并在成功注册上5G网络后创建指定网络切片的PDU会话。
如图5所示，该方法可以包括步骤500至505。
在步骤500，应用申请SIM卡1的网络切片A，且已成功创建 PDU会话。
在步骤501，监听是否接收到网络侧给终端发送的PDU Session Modification Reject或PDU Session Release消息，且判断消息中携带的理由是否为insufficient resource；如果接收到网络侧给终端发送的PDU Session Modification Reject或PDU Session Release消息，且消息中携带的理由为insufficient resource，则继续执行步骤502；如果没有接收到PDU Session Modification Reject或PDU Session Release消息；或者，接收到网络侧给终端发送的PDU Session Modification Reject或PDU Session Release消息，且消息中携带的理由不是insufficient resource，则结束本流程。
在步骤502，将SIM卡1的网络切片A对应的URSP规则标识为“不可用”。
在步骤503，如果在SIM卡1的URSP规则列表中匹配不到可用的URSP规则，则在SIM卡2的URSP规则列表中匹配可用的URSP规则，如匹配到可用的URSP规则对应的网络切片B或网络切片C，得到网络切片B或网络切片C的S-NSSAI。
在步骤504，将数据业务由SIM卡1切换到SIM卡2，SIM卡2成功注册上5G网络。
在步骤505，向网络侧发送PDU会话建立请求，PDU会话建立请求中携带S-NSSAI，表明希望申请的网络切片。
示例4
本示例描述该双卡场景(不同运营商的两张用户识别模块(SIM，Subscriber Identity Module)卡，假设当前使用的是SIM卡1的数据业务)下的处理拥塞的方法，在进行网络切片重选时，发现SIM卡2所在的5G网络下有可用的网络切片，则终端的SIM卡1尝试注册到SIM卡2的5G网络，并在SIM卡1成功注册上SIM卡2的5G网络后创建指定网络切片的PDU会话(也就是SIM卡1漫游到SIM卡2的网络的场景)。
如图6所示，该方法可以包括步骤600至605。
在步骤600，应用申请SIM卡1的网络切片A，且已成功创建 PDU会话。
在步骤601，监听是否接收到网络侧给终端发送的PDU Session Modification Reject或PDU Session Release消息，且判断消息中携带的理由是否为insufficient resource；如果接收到网络侧给终端发送的PDU Session Modification Reject或PDU Session Release消息，且消息中携带的理由为insufficient resource，则继续执行步骤602；如果没有接收到PDU Session Modification Reject或PDU Session Release消息；或者，接收到网络侧给终端发送的PDU Session Modification Reject或PDU Session Release消息，且消息中携带的理由不是insufficient resource，则结束本流程。
在步骤602，将SIM卡1的网络切片A对应的URSP规则标识为“不可用”。
在步骤603，如果在SIM卡1的URSP规则列表中匹配不到可用的URSP规则，则在SIM卡2的URSP规则列表中匹配可用的URSP规则，如匹配到可用的URSP规则对应的网络切片B或网络切片C，得到网络切片B或网络切片C的S-NSSAI。
在步骤604，SIM卡1尝试注册到SIM卡2的5G网络，SIM卡1成功注册上SIM卡2的5G网络。
在步骤605，向网络侧发送PDU会话建立请求，PDU会话建立请求中携带S-NSSAI，表明希望申请的网络切片。
第二方面，本公开实施例提供一种电子设备，包括：至少一个处理器；存储器，其上存储有至少一个程序，当至少一个程序被至少一个处理器执行，使得至少一个处理器实现上述任意一种网络切片重选方法。
其中，处理器为具有数据处理能力的器件，其包括但不限于中央处理器(CPU)等；存储器为具有数据存储能力的器件，其包括但不限于随机存取存储器(RAM，更具体如SDRAM、DDR等)、只读存储器(ROM)、带电可擦可编程只读存储器(EEPROM)、闪存(FLASH)。
在一些实施例中，处理器、存储器通过总线相互连接，进而与 计算设备的其它组件连接。
第三方面，本公开实施例提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，计算机程序被处理器执行时实现上述任意一种网络切片重选方法。
图7为本公开实施例提供的一种网络切片重选装置的组成框图。
第四方面，参照图7，本公开实施例提供一种网络切片重选装置，包括：拥塞检测模块701，配置为监听是否接收到网络侧针对当前选择的网络切片发送的消息，判断消息中携带的理由是否为资源不足；以及网络切片选择模块702，配置为拥塞检测模块701接收到网络侧针对当前选择的网络切片发送的消息，且消息中携带的理由为资源不足，重新选择网络切片。
在一些示例性实施例中，所述消息包括以下任意一个：协议数据单元会话建立拒绝消息、协议数据单元会话修改拒绝消息、协议数据单元会话释放消息。
在一些示例性实施例中，网络切片选择模块702可以配置为：拥塞检测模块701接收到网络侧针对当前选择的网络切片发送的消息，且消息中携带的理由为资源不足，将所述当前选择的网络切片对应的用户设备路由选择策略规则标识为不可用；在第一用户设备路由选择策略规则列表中匹配没有被标识为不可用的用户设备路由选择策略规则或者匹配被标识为可用的用户设备路由选择策略规则，重新选择匹配到的可用的用户设备路由选择策略规则对应的网络切片。
在一些示例性实施例中，网络切片选择模块702可以配置为采用以下方式实现所述将当前选择的网络切片对应的用户设备路由选择策略规则标识为不可用：在预设时间内将所述当前选择的网络切片对应的用户设备路由选择策略规则标识为不可用；在所述预设时间后去除对所述用户设备路由选择策略规则的标识；或者，在所述预设时间后将所述用户设备路由选择策略规则标识为可用。
在一些示例性实施例中，网络切片选择模块702还配置为：检测被标识为不可用的用户设备路由选择策略规则对应的网络切片是否发生网络拥塞；检测到被标识为不可用的用户设备路由选择策略规 则对应的网络切片没有发生网络拥塞，去除对所述用户设备路由选择策略规则的标识；或者，将用户设备路由选择策略规则标识为可用。
在一些示例性实施例中，网络切片选择模块702还配置为：当在第一用户设备路由选择策略规则列表中匹配不到可用的用户设备路由选择策略规则时，在第二用户设备路由选择策略规则列表中重新选择可用的用户设备路由选择策略规则对应的网络切片；
其中，所述第一用户设备路由选择策略规则列表为当前正在进行业务处理的卡对应的用户设备路由选择策略规则列表，所述第二用户设备路由选择策略规则列表为当前未进行业务处理的卡对应的用户设备路由选择策略规则列表。
上述网络切片重选装置的具体实现过程与前述实施例网络切片重选方法的具体实现过程相同，这里不再赘述。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其它数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其它存储器技术、CD-ROM、数字多功能盘(DVD)或其它光盘存储、磁盒、磁带、磁盘存储或其它磁存储器、或者可以用于存储期望的信息并且可以被计算机访问的任何其它的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载 波或其它传输机制之类的调制数据信号中的其它数据，并且可包括任何信息递送介质。
本文已经公开了示例实施例，并且虽然采用了具体术语，但它们仅用于并仅应当被解释为一般说明性含义，并且不用于限制的目的。在一些实例中，对本领域技术人员显而易见的是，除非另外明确指出，否则可单独使用与特定实施例相结合描述的特征、特性和/或元素，或可与其它实施例相结合描述的特征、特性和/或元件组合使用。因此，本领域技术人员将理解，在不脱离由所附的权利要求阐明的本公开的范围的情况下，可进行各种形式和细节上的改变。

Claims (9)

  1. 一种网络切片重选方法，包括：
    接收到网络侧针对当前选择的网络切片发送的消息，重新选择网络切片；其中，所述消息携带的理由为资源不足。
  2. 根据权利要求1所述的方法，所述接收到网络侧针对当前选择的网络切片发送的消息之后，所述重新选择网络切片之前，该方法还包括：将所述当前选择的网络切片对应的用户设备路由选择策略规则标识为不可用。
  3. 根据权利要求2所述的方法，其中，所述重新选择网络切片包括：在第一用户设备路由选择策略规则列表中匹配没有被标识为不可用的用户设备路由选择策略规则或者匹配被标识为可用的用户设备路由选择策略规则，重新选择匹配到的可用的用户设备路由选择策略规则对应的网络切片。
  4. 根据权利要求2所述的方法，其中，所述将当前选择的网络切片对应的用户设备路由选择策略规则标识为不可用包括：
    在预设时间内将所述当前选择的网络切片对应的用户设备路由选择策略规则标识为不可用；
    在所述预设时间后去除对所述用户设备路由选择策略规则的标识；或者，在所述预设时间后将所述用户设备路由选择策略规则标识为可用。
  5. 根据权利要求2所述的方法，所述重新选择匹配到的可用的用户设备路由选择策略规则对应的网络切片后，该方法还包括：
    检测被标识为不可用的用户设备路由选择策略规则对应的网络切片是否发生网络拥塞；
    检测到被标识为不可用的用户设备路由选择策略规则对应的网络切片没有发生网络拥塞时，去除对所述用户设备路由选择策略规则的标识；或者，将所述用户设备路由选择策略规则标识为可用。
  6. 根据权利要求2所述的方法，当在第一用户设备路由选择策略规则列表中匹配不到可用的用户设备路由选择策略规则时，所述重新 选择网络切片还包括：
    在第二用户设备路由选择策略规则列表中重新选择可用的用户设备路由选择策略规则对应的网络切片；
    其中，所述第一用户设备路由选择策略规则列表为当前正在进行业务处理的卡对应的用户设备路由选择策略规则列表，所述第二用户设备路由选择策略规则列表为当前未进行业务处理的卡对应的用户设备路由选择策略规则列表。
  7. 根据权利要求1-6任一项所述的方法，其中，所述消息包括以下任意一个：
    协议数据单元会话建立拒绝消息、协议数据单元会话修改拒绝消息、协议数据单元会话释放消息。
  8. 一种电子设备，包括：
    至少一个处理器；
    存储器，其上存储有至少一个程序，当所述至少一个程序被所述至少一个处理器执行，使得所述至少一个处理器实现根据权利要求1-7任意一项所述的网络切片重选方法。
  9. 一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现根据权利要求1-7任意一项所述的网络切片重选方法。
PCT/CN2021/088339 2020-06-01 2021-04-20 网络切片重选方法和装置、电子设备、存储介质 WO2021244165A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP21818518.9A EP4132108A4 (en) 2020-06-01 2021-04-20 NETWORK SLICE RESELECTION METHOD AND APPARATUS, ELECTRONIC DEVICE AND STORAGE MEDIUM
US17/922,616 US20230224780A1 (en) 2020-06-01 2021-04-20 Network slice reselection method and device, electronic device and storage medium
JP2022548024A JP7410312B2 (ja) 2020-06-01 2021-04-20 ネットワークスライス再選択方法及び装置、電子機器、記憶媒体

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010487424.0 2020-06-01
CN202010487424.0A CN113766592A (zh) 2020-06-01 2020-06-01 网络切片重选方法和装置、电子设备、存储介质

Publications (1)

Publication Number Publication Date
WO2021244165A1 true WO2021244165A1 (zh) 2021-12-09

Family

ID=78782288

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/088339 WO2021244165A1 (zh) 2020-06-01 2021-04-20 网络切片重选方法和装置、电子设备、存储介质

Country Status (5)

Country Link
US (1) US20230224780A1 (zh)
EP (1) EP4132108A4 (zh)
JP (1) JP7410312B2 (zh)
CN (1) CN113766592A (zh)
WO (1) WO2021244165A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108029062A (zh) * 2015-09-18 2018-05-11 华为技术有限公司 用于网络切片重选的系统和方法
CN109565746A (zh) * 2016-08-16 2019-04-02 Idac控股公司 网络切片重选
CN110062407A (zh) * 2018-01-19 2019-07-26 华为技术有限公司 网络切片性能管理的方法和装置
CN110167064A (zh) * 2018-02-12 2019-08-23 中兴通讯股份有限公司 一种控制终端接入的方法、网元、终端及系统

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018008927A1 (ko) 2016-07-05 2018-01-11 엘지전자 주식회사 차세대 이동통신 네트워크에서 액세스 제어를 수행하는 방법 및 사용자 장치
US10582432B2 (en) 2017-05-04 2020-03-03 Comcast Cable Communications, Llc Communications for network slicing using resource status information
KR20200056407A (ko) * 2017-10-13 2020-05-22 삼성전자주식회사 무선 통신 시스템 내 네트워크 슬라이스 혼잡을 관리하기 위한 사용자 장치(ue) 및 코어 네트워크
US11457403B2 (en) * 2018-05-08 2022-09-27 Lg Electronics Inc. Method and user equipment for performing access control in 5GS
US11039369B2 (en) * 2018-08-10 2021-06-15 Mediatek Inc. Handling 5G QoS rules on QoS operation errors
US20200162919A1 (en) 2018-11-16 2020-05-21 Lenovo (Singapore) Pte. Ltd. Accessing a denied network resource
US10602422B1 (en) * 2018-12-10 2020-03-24 Verizon Patent And Licensing Inc. Application-based user equipment route selection policy mapping

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108029062A (zh) * 2015-09-18 2018-05-11 华为技术有限公司 用于网络切片重选的系统和方法
CN109565746A (zh) * 2016-08-16 2019-04-02 Idac控股公司 网络切片重选
CN110062407A (zh) * 2018-01-19 2019-07-26 华为技术有限公司 网络切片性能管理的方法和装置
CN110167064A (zh) * 2018-02-12 2019-08-23 中兴通讯股份有限公司 一种控制终端接入的方法、网元、终端及系统

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI; HISILICON: "Slice Availability for Cell Reselection", 3GPP DRAFT; R2-1802261-SLICE AVAILABILITY, vol. RAN WG2, 16 February 2018 (2018-02-16), Athens, Greece, pages 1 - 3, XP051400106 *
See also references of EP4132108A4 *
SPREADTRUM COMMUNICATIONS: "Cell Reselection Based on Slice Information", 3GPP DRAFT; R2-1707978_CELL RESELECTION BASED ON SLICE INFORMATION, vol. RAN WG2, 20 August 2017 (2017-08-20), Berlin, Germany, pages 1 - 3, XP051317892 *

Also Published As

Publication number Publication date
US20230224780A1 (en) 2023-07-13
EP4132108A4 (en) 2023-09-27
CN113766592A (zh) 2021-12-07
JP7410312B2 (ja) 2024-01-09
JP2023513530A (ja) 2023-03-31
EP4132108A1 (en) 2023-02-08

Similar Documents

Publication Publication Date Title
US10542454B2 (en) Control and management of reflective QoS
CN109314917B (zh) 网络切片选择策略更新方法、及装置
CN110536375B (zh) 网络接入方法、装置、网络设备和计算机可读存储介质
KR101910477B1 (ko) 액세스 포인트 조종
WO2018157439A1 (zh) 业务处理的方法和设备
CN117793952A (zh) 一种通信方法及装置
US10425955B2 (en) Bearer setup method and apparatus
CN111034260B (zh) 漫游时的状态性应用标识
CN110177382B (zh) 拥塞通知方法、相关设备和系统
US20170006522A1 (en) Restriction control apparatus, restriction control system, and restriction control method
US20140269499A1 (en) Wireless client association and traffic context cookie
WO2018018795A1 (zh) 识别伪基站的方法、装置、系统及存储介质
WO2021233564A1 (en) Improving classification accuracy in user plane function re-selection scenarios
US20240023005A1 (en) Sim card selection method and apparatus, and terminal and storage medium
CN111147468A (zh) 用户接入方法、装置、电子设备及存储介质
CN113839882A (zh) 一种报文流分流方法及装置
US10251119B2 (en) Method and apparatus for handling reject
WO2021244165A1 (zh) 网络切片重选方法和装置、电子设备、存储介质
US20170310561A1 (en) Network Control Method and Apparatus
US10785165B2 (en) Method for controlling service data flow and network device
EP4005166A1 (en) Traffic monitoring in a network node
CN115334490A (zh) 网络分片准入控制(nsac)发现和漫游增强
WO2023151537A1 (zh) 小区切换方法、电子设备、计算机可读存储介质
WO2024055815A1 (zh) 管理边缘psa的方法、电子设备、计算机可读介质
WO2024093448A1 (en) Smart policy rule update

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022548024

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2021818518

Country of ref document: EP

Effective date: 20221103

NENP Non-entry into the national phase

Ref country code: DE