Slice access optimization methods and related products

Abstract

This application discloses a slice access optimization method and related products. After obtaining slice access policy information, a first network device sends the information to a terminal, which then accesses the network slice according to the policy. This allows the network to indicate the slice access policy to the user equipment, optimizing user equipment behavior and mitigating the impact of insufficient network slice resources on the user equipment.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to a slice access optimization method and related products. Background Technology

[0002] With the emergence of various new services, the existing 4G mobile communication network can no longer meet the ever-increasing demands of these services, thus network slicing has received considerable attention. Network slicing is an on-demand networking method that divides the physical network into multiple independent logical meshes based on the different service applications' requirements for the number of users, Quality of Service (QoS), and bandwidth. This allows operators to separate multiple virtual end-to-end networks on a unified infrastructure. Each network slice is logically isolated from the radio access network to the core network to adapt to various types of applications. However, network slicing resources are limited. When these resources are insufficient, user equipment's sliced ​​services will be affected, such as slower access speeds or even inability to access the desired network slice services, thereby impacting the user experience. Summary of the Invention

[0003] This application provides a slice access optimization method and related products, aiming to indicate slice access strategies to user equipment through the network, optimize user equipment behavior, and mitigate the impact of insufficient network slice resources on user equipment.

[0004] In a first aspect, embodiments of this application provide a slice access optimization method, the method comprising:

[0005] The first network device obtains slice access policy information;

[0006] The first network device sends the slice access policy information to the terminal.

[0007] Secondly, embodiments of this application provide a slice access optimization method, the method comprising:

[0008] The terminal obtains slice access policy information from the first network device;

[0009] The terminal accesses the first network slice according to the slice access policy information.

[0010] Thirdly, embodiments of this application provide a slice access optimization method, the method comprising:

[0011] The second network device obtains slice access policy request information from the first network device;

[0012] The second network device sends an access policy request response message to the first network device.

[0013] Fourthly, embodiments of this application provide a slice access optimization device, comprising: an acquisition unit for a first electronic device to acquire slice access policy information; and a sending unit for the first electronic device to send the slice access policy information to a terminal.

[0014] Fifthly, embodiments of this application provide a slice access optimization device, comprising: an acquisition unit for a terminal to acquire slice access policy information from a first network device; and an access unit for the terminal to access a first network slice according to the slice access policy information.

[0015] In a sixth aspect, embodiments of this application provide a slice access optimization apparatus, comprising: an acquisition unit for a second network device to acquire slice access policy request information from a first network device; and a sending unit for the second network device to send information related to the slice access policy request information to the first network device.

[0016] In a seventh aspect, embodiments of this application provide a network device including a processor, a memory, a communication interface, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the processor, and the programs include instructions for performing steps in any method of the first aspect of embodiments of this application.

[0017] Eighthly, embodiments of this application provide a terminal including a processor, a memory, a communication interface, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the processor, and the programs include instructions for performing steps in any method of the second aspect of embodiments of this application.

[0018] Ninthly, embodiments of this application provide a network device including a processor, a memory, a communication interface, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the processor, and the programs include instructions for performing steps in any method of the third aspect of this application.

[0019] In a tenth aspect, embodiments of this application provide a chip, including: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform some or all of the steps described in any of the methods of the first, second, or third aspects of embodiments of this application.

[0020] In one aspect, embodiments of this application provide a chip module, including the chip described in the tenth aspect of embodiments of this application.

[0021] In a twelfth aspect, embodiments of this application provide a computer-readable storage medium storing a computer program for electronic data interchange, wherein the computer program causes a computer to perform some or all of the steps described in any of the methods of the first, second, or third aspects of embodiments of this application.

[0022] As can be seen from this embodiment, after the first network device obtains the slice access policy information, it sends the slice access policy information to the terminal, and the terminal then accesses the network slice according to the slice access policy information. This allows the network to indicate the slice access policy to the user equipment, optimizing user equipment behavior and mitigating the impact of insufficient network slice resources on the user equipment. Attached Figure Description

[0023] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0024] Figure 1a This is a system architecture diagram of an example communication system provided in an embodiment of this application;

[0025] Figure 1b This is a schematic diagram of the structure of a first network device provided in an embodiment of this application;

[0026] Figure 1c This is a schematic diagram of the structure of a terminal provided in an embodiment of this application;

[0027] Figure 1d This is a schematic diagram of the structure of a second network device provided in an embodiment of this application;

[0028] Figure 2a This is a flowchart illustrating a slice access optimization method provided in an embodiment of this application;

[0029] Figure 2b This is a flowchart illustrating another slice access optimization method provided in an embodiment of this application;

[0030] Figure 3 This is a functional unit block diagram of a slice access optimization device provided in an embodiment of this application;

[0031] Figure 4 This is a functional unit block diagram of another slice access optimization device provided in this application embodiment;

[0032] Figure 5This is a functional unit block diagram of another slice access optimization device provided in this application embodiment;

[0033] Figure 6 This is a functional unit block diagram of another slice access optimization device provided in this application embodiment;

[0034] Figure 7 This is a functional unit block diagram of another slice access optimization device provided in this application embodiment;

[0035] Figure 8 This is a functional unit block diagram of another slice access optimization device provided in this application embodiment. Detailed Implementation

[0036] To enable those skilled in the art to better understand the present application, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0037] The terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0038] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0039] To better understand the technical solutions of the embodiments of this application, the technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings.

[0040] like Figure 1aAs shown, the example communication system 100 may be, for example, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) system, a General Packet Radio Service (GPRS) system, a Long Term Evolution (LTE) system, an Advanced Long Term Evolution (LTE-A) system, a New Radio (NR) system, an evolution of the NR system, an LTE-based access to unlicensed spectrum (LTE-U) system, an NR-based access to unlicensed spectrum (NR-U) system, a Universal Mobile Telecommunication System (UMTS), a next-generation communication system, or other communication systems.

[0041] Traditional communication systems typically support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication but also, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and vehicle-to-vehicle (V2V) communication. The embodiments of this application can also be applied to these communication systems. Optionally, the communication system in the embodiments of this application can be applied to carrier aggregation (CA) scenarios, dual connectivity (DC) scenarios, and standalone (SA) network deployment scenarios.

[0042] The embodiments of this application do not limit the spectrum to which the application is applied. For example, the embodiments of this application can be applied to licensed spectrum or unlicensed spectrum.

[0043] In this application embodiment, the first network device 110 and the second network device 130 can be an evolved NodeB (eNB or eNodeB) in an LTE system, a radio controller or network element in a cloud radio access network (CRAN) scenario, or a relay device, access point, vehicle-mounted device, wearable device, or network device in a future 5G network or a future evolved PLMN network. They can also be one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or network nodes constituting a gNB or transmission point, such as a baseband unit (BBU) or a distributed unit (DU), etc. This application embodiment is not limited to these. Figure 1b As shown, the first network device 110 in this embodiment may include one or more of the following components: a processor 210, a memory 220, and a communication interface 230. The processor 210 is communicatively connected to the memory 220 and the communication interface 230, respectively. The memory 220 also includes one or more programs 221. Similarly... Figure 1d The second network device 130 may also include one or more of the following components: processor 410, memory 420 and communication interface 430, wherein processor 410 is communicatively connected to memory 420 and communication interface 430 respectively, and memory 420 also includes one or more programs 421.

[0044] In some deployments, a gNB may include a centralized unit (CU) and a distribution unit (DU). A gNB may also include an active antenna unit (AAU). The CU implements some of the gNB's functions, and the DU implements others. For example, the CU handles non-real-time protocols and services, implementing radio resource control (RRC) and packet data convergence protocol (PDCP) layer functions. The DU handles physical layer protocols and real-time services, implementing radio link control (RLC), media access control (MAC), and physical (PHY) layer functions. The AAU implements some physical layer processing functions, radio frequency processing, and active antenna-related functions. Since RRC layer information ultimately becomes PHY layer information, or is derived from PHY layer information, in this architecture, higher-layer signaling, such as RRC layer signaling, can be considered to be sent by the DU, or by the DU+AAU. It is understood that network devices can be devices that include one or more of the following: CU nodes, DU nodes, and AAU nodes. In addition, the CU can be classified as a network device in the radio access network (RAN) or as a network device in the core network (CN), and this application does not limit this.

[0045] In this application embodiment, terminal 120 can refer to user equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. Terminal can also be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, relay device, vehicle-mounted device, wearable device, terminal in a future 5G network, or terminal in a future evolved public land mobile network (PLMN), etc. This application embodiment does not limit this. Figure 1cAs shown, the terminal 120 in the terminal of this application embodiment may include one or more of the following components: processor 310, memory 320 and communication interface 330. The processor 310 is communicatively connected to the memory 320 and the communication interface 330 respectively. The memory 320 also includes one or more programs 321.

[0046] In this embodiment, terminal 120 or first network device 110 and second network device 130 include a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, such as Linux, Unix, Android, iOS, or Windows. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. Furthermore, this embodiment does not specifically limit the structure of the execution subject of the method provided in this embodiment, as long as it can communicate according to the method provided in this embodiment by running a program that records the code of the method provided in this embodiment. For example, the execution subject of the method provided in this embodiment can be a terminal, or a functional module in the terminal that can call and execute a program.

[0047] The concepts and terms involved in this application are defined or explained as follows.

[0048] Network slicing: To adapt to the varying network performance requirements of different services, future networks need to have on-demand configuration capabilities. This means being able to flexibly configure network slices, dividing the physical network into multiple virtual network slices. Each virtual network slice is designed for different application scenarios, and its final resource form is a virtual network with a specific topology, consisting of multiple interconnected virtual machines (VMs). Network slice mapping is the process of allocating the resources required by the data center (DC) resources (composed of hosts in the Network Functions Virtualization Infrastructure, NFVI) to the network slices.

[0049] URSP rules: In 5G, User Equipment (UE) related policy information, namely URSP rules, is introduced. The terminal equipment acts as the executor of these policies, selecting Packet Data Unit (PDU) sessions that conform to the URSP rules for uplink service flows. Specifically, certain services have specific requirements for the Data Network Name (DNN), Single Network Slice Selection Assistance Information (S-NSSAI), and Session and Service Continuity (SSC) mode of the PDU sessions used. In essence, URSP rules specify which applications a PDU session's attributes should correspond to. For example, a PDU session may have multiple attributes, and different PDU sessions may have different attributes. URSP defines the applications that each attribute of a PDU session should correspond to. For instance, if the first PDU session has a first attribute, the URSP can determine the applications corresponding to that first attribute, and these applications are the ones allowed for use by the first PDU session.

[0050] Currently, network slicing resources are limited. When these resources are insufficient, user devices' slicing services will be affected, such as slower access speeds or even inability to access the desired network slicing service, thus impacting the user experience. Furthermore, if the network side performs related operations, such as slice remapping, when a user device initiates network slicing access, the user device is unaware of these operations. Therefore, when the user device initiates network slicing access again, the network side needs to perform this operation again, further affecting the network slicing access speed.

[0051] To address the aforementioned issues, this application provides a slice access optimization method and related products, which will be described in detail below with reference to the accompanying drawings.

[0052] Please see Figure 2a , Figure 2a This is a flowchart illustrating a slice access optimization method provided in an embodiment of this application. As shown in the figure, the method includes the following steps:

[0053] Step 201: The first network device obtains slice access policy information.

[0054] The slice access policy information can be information previously acquired and stored locally by the first network device, or it can be access policy information generated by the first network device itself, or it can be information acquired by the first network device from other network devices, or it can be information generated by the first network device based on information acquired from other network devices.

[0055] In specific implementation, before the first network device obtains the slice access policy information, the first network device determines that the current slice resources are limited. Limited slice resources include limited slice resources on the Radio Access Network (RAN) side and limited slice resources on the Core Network (CN) side. Limited RAN-side resources include: the RAN side does not configure the corresponding network slice resources, i.e., it does not support the corresponding network slice; or the RAN side has configured the corresponding network slice resources, but the network slice resource utilization / load is too high, resulting in the inability to serve the corresponding network slice services for more user devices. Limited CN-side slice resources include: the CN side does not configure the corresponding network slice resources; or the CN side has configured the corresponding network slice resources, but the Generic Slice Template (GST) has limitations. The GST includes various attributes that may limit network slice access, such as the maximum number of supported user devices and the maximum number of supported Protocol Data Unit (PDU) sessions.

[0056] Step 202: The first network device sends the slice access policy information to the terminal;

[0057] Step 203: The terminal accesses the first network slice according to the slice access strategy information.

[0058] The slice access method corresponding to the slice access strategy information is different from the slice access method in the current terminal. This difference in slice access method may be due to different slice mapping rules used by the terminal, or different URSP information used by the terminal.

[0059] As can be seen from this embodiment, after the first network device obtains the slice access policy information, it sends the slice access policy information to the terminal, and the terminal then accesses the network slice according to the slice access policy information. This allows the network to indicate the slice access policy to the terminal, optimizing terminal behavior and mitigating the impact of insufficient network slice resources on the terminal. Furthermore, the terminal receiving the slice access policy information facilitates subsequent direct network slice access based on that policy, improving the network slice access speed.

[0060] In one possible instance, the slice access policy information includes first policy information related to slice remapping, or second policy information related to the terminal routing policy URSP.

[0061] The first policy information may include slice remapping rules and a first constraint condition for those rules, while the second policy information may include URSP information and a second constraint condition for that URSP information. The terminal can re-determine connectable network slices based on the slice remapping rules and obtain the network slice identifier corresponding to the currently determined network slice found based on the URSP information.

[0062] The network slice identifier can be: Single Network Slice Selection Assistance Information (S-NSSAI), or other identifiers that can identify network slices, such as sequence numbers.

[0063] As can be seen in this example, when slice resources are limited, the network side can enable the terminal to connect to the network slice by issuing slice remapping rules or re-determining the terminal's URSP information, which can ensure the user's network slice service experience.

[0064] In one possible instance, the slice access policy information includes the first policy information, and sending the slice access policy information to the terminal includes: sending a slice remapping rule to the terminal via a first message, and / or a first restriction condition of the slice remapping rule.

[0065] The first constraint may include the effective area and effective time of the slice remapping rule. The effective area may be geographic location information (such as latitude and longitude information), cell identifier (such as physical cell identifier), TA (Tracking Area), or TA list, etc. The effective time may be absolute or relative.

[0066] As can be seen, in this example, the terminal receiving the slice access policy information is beneficial for the terminal to directly access the network slice according to the slice access policy information in the future, thereby improving the access speed of the network slice.

[0067] In one possible instance, the method further includes sending a first stop policy of the slice remapping rule to the terminal via a second message.

[0068] The first stopping policy can be generated by the first network device itself, obtained from the second network device and stored locally, obtained by the first network device from the second network device, or generated by the first network device based on information sent by the second network device. The first message and the second message can be the same message, that is, the first network device can send the slice remapping rule, the first restriction condition, and the first stopping policy to the terminal through the same type of message.

[0069] As can be seen, in this example, the first network device also sends a stop policy to the terminal, causing the terminal to switch back to using the normal slice access method, providing the terminal with network slice services with performance guarantees.

[0070] In one possible instance, before sending the first stop policy of the slice remapping rule to the terminal via the second message, the method further includes: sending a first stop policy request message to a second network device; receiving a first stop policy response message from the second network device; and obtaining the first stop policy based on the first stop policy response message.

[0071] In this process, after receiving the first stop policy, the second network device sends a first stop policy response message to the first network device. The first stop policy request message may include the first stop policy, and the second network device's response message may include information determining whether to use the first stop policy. The first stop policy response message may include the first stop policy, or it may contain information related to the first stop policy; in this case, the first network device generates the first stop policy based on the relevant information.

[0072] As can be seen, in this example, the first network device generates a stop policy based on the information from the second network device, which can provide network slicing services with performance guarantees for the terminal.

[0073] In one possible instance, the first stopping policy includes instructing the terminal to discard the slice remapping rule.

[0074] As can be seen, the first network device instructs the terminal to discard the slice remapping rule, that is, the terminal stops using the slice remapping rule and switches back to the normal slice selection method, providing the terminal with network slice services with guaranteed performance.

[0075] In one possible instance, the first stopping policy includes instructing the terminal to suspend the use of the slice remapping rule for a first preset time period.

[0076] The first preset time period is the duration during which the terminal suspends the use of the slice remapping rule. This first preset time period can be a relative duration or an absolute duration. During this period, the slice remapping rule can be temporarily stored in the terminal's local storage medium.

[0077] As can be seen, in this example, the first network device instructs the terminal to suspend the use of the slice remapping rule and switch back to the normal slice selection method within a certain period of time, so as to provide the terminal with network slice services with guaranteed performance.

[0078] In one possible instance, the slice access policy information includes the first policy information. After obtaining the slice access policy information from the first network device, the method further includes: obtaining a first constraint condition for the slice remapping rule based on the first policy information; and discarding the slice remapping rule if the first constraint condition is not met.

[0079] The terminal can first determine the first constraint of the current slice remapping rule. If the first constraint is not met, the terminal can actively discard the slice remapping rule and use the normal slice selection method. The first constraint may include the usage area and / or usage time. For example, when the validity period of the slice remapping rule expires, the terminal directly discards the slice remapping rule. When there are multiple first constraints, the terminal can discard the slice remapping rule after a specific constraint is not met, after any one of the first constraints is not met, or after multiple or all of the first constraints are not met simultaneously.

[0080] In a specific implementation, after the terminal obtains the slice access policy information from the first network device, the method further includes: obtaining a first stop policy from the first network device; and discarding the slice remapping rule according to the first stop policy.

[0081] As can be seen, in this example, the terminal actively discards the slice remapping rule after the first restriction condition is not met, and switches back to using the normal slice selection method to ensure the performance of the network slice service used by the terminal.

[0082] In one possible instance, after obtaining slice access policy information from the first network device, the method further includes: obtaining a first constraint condition for the slice remapping rule based on the first policy information; and suspending the use of the slice remapping rule for a third preset time period if the first constraint condition is not met.

[0083] The first preset time period is the duration during which the terminal suspends the use of the slice remapping rule. The third preset time period can be a relative duration or an absolute duration. The first preset time period and the third preset time period can be the same.

[0084] In a specific implementation, after obtaining the slice access policy information from the first network device, the method further includes: obtaining a first stop policy from the first network device; and suspending the use of the slice remapping rule for a first preset time period according to the first stop policy.

[0085] As can be seen, in this example, after the terminal fails to meet the first restriction condition, it actively suspends the use of the slice remapping rule within the third preset time period and switches back to the normal slice selection method to ensure the performance of the network slice service used by the terminal.

[0086] In one possible instance, after sending the first stop policy of the slice remapping rule to the terminal via a second message, the method further includes sending the slice remapping rule enable information to the terminal.

[0087] In this implementation, the first network device can proactively send activation information to the terminal, or it can receive the terminal's request for activation information first and then send the activation information to the terminal. Alternatively, the second network device can send activation information to the first network device first, which then sends it to the terminal. In a specific implementation, the terminal can also directly activate the slice remapping rule after meeting the first constraint. For example, if the first constraint is that the slice remapping rule applies within region A, then because the terminal previously left region A, the first constraint is not met, and the slice remapping rule is suspended. When the terminal returns to region A, the first constraint is met, and the terminal can directly activate the slice remapping rule.

[0088] As can be seen, in this example, the first network device can instruct the terminal to enable the slice remapping rule, which can both ensure the performance of the network slice service used by the terminal and avoid sending slice access policy information again.

[0089] In one possible instance, the first message includes a System Message Block (SIB) message, a Radio Resource Control (RRC) message, or a Non-Access Stratum (NAS) message.

[0090] The first network device broadcasts slice remapping rules via SIB messages. These rules may also include limitations on the effective area and / or effective time. The effective area can be geographic location information (e.g., latitude and longitude), cell identifiers (e.g., physical cell identifiers), TA (Tracking Area), or TA list. The first network device can also instruct the terminal on slice remapping rules via dedicated RRC messages (e.g., adding slice remapping rule information within RRCReconfiguration / RRCReleasse, or a new RRC message). The first network device can also instruct the terminal on slice remapping rules via NAS messages (e.g., adding slice remapping information within PDU Session Establishment Accept / PDU sessionEstablishment Reject, or a new NAS message). Specifically, when the first message is an SIB message or an RRC message, the first network device can be a 5G base station (gNB); when the first message is a NAS message, the first network device can be an Access and Mobility Management Function (AMF) device.

[0091] As can be seen, in this example, the first network device can send the first policy information to the terminal through various messages, ensuring that the user can obtain the slice remapping rules, which is beneficial for the terminal to select the appropriate network slice to initiate access.

[0092] In one possible instance, the slice access policy information includes the second policy information, and sending the slice access policy information to the terminal includes: sending the first URSP information to the terminal via a third message, and / or the second limiting condition of the first URSP information.

[0093] The third message can be a configuration update message. The first network device can initiate a configuration update process to the terminal to update the terminal's current URSP information to the first URSP information. This first URSP information can be the updated URSP information based on the current URSP information, or it can be new URSP information obtained by the first network device; in this case, the first URSP information can be temporary. The second constraint can include the valid area and valid time of the first URSP information. The valid area can be geographical location information (such as latitude and longitude), cell identifiers (such as physical cell identifiers), TA (Tracking Area), or TA list, etc. The valid time can be absolute or relative.

[0094] As can be seen, in this example, the terminal receiving the slice access policy information is beneficial for the terminal to directly access the network slice according to the slice access policy information in the future, thereby improving the access speed of the network slice.

[0095] In one possible instance, the method further includes: a second stop strategy that sends the first URSP information to the terminal via a fourth message.

[0096] The third and fourth messages can be of the same type, i.e., both are configuration update messages, or they can be of different types, i.e., the fourth message can be an SIB message, an RRC message, or a NAS message. The second stop policy can be generated by the first network device itself, or it can be obtained from the second network device and stored locally, or it can be obtained by the first network device from the second network device, or it can be generated by the first network device based on information sent by the second network device.

[0097] In a specific implementation, before sending the first stop policy of the first URSP information to the terminal via the second message, the method further includes: sending a second stop policy request message to a second network device; receiving a second stop policy reply message from the second network device; and obtaining the second stop policy based on the second stop policy reply message.

[0098] In this process, after receiving the second stop policy, the second network device sends a response message to the first network device. This response message may include information determining whether to apply the second stop policy. The response message may include the second stop policy itself, or information related to it. In this case, the first network device generates the second stop policy based on this related information. This method of generating a stop policy based on the information from the second network device allows the first network device to provide network slicing services with performance guarantees for the terminal.

[0099] As can be seen, in this example, the first network device also sends a stop policy to the terminal, causing the terminal to switch back to using normal URSP information and providing the terminal with network slicing services with performance guarantees.

[0100] In one possible instance, the second stopping policy includes: indicating that the second URSP information is the current URSP information, the second URSP information is the URSP information updated according to preset URSP information, or the second URSP information is the URSP information regenerated by the first network device.

[0101] The first network device can initiate the terminal configuration update process again through the fourth message, actively updating the URSP information stored on the terminal side, that is, updating the first URSP information currently used on the terminal side to the second URSP information. The preset URSP information can be the first URSP information, that is, the second URSP information is updated based on the first URSP information. The preset URSP information can also be the original URSP information stored by the terminal before using the first URSP information. In this case, the second stop policy can include the second URSP information.

[0102] In a specific implementation, after the terminal obtains the slice access policy information from the first network device, the method further includes: obtaining a second stop policy from the first network device; determining the second URSP information as the current URSP information according to the second stop policy, wherein the second URSP information is URSP information updated according to preset URSP information, or the second URSP information is URSP information regenerated by the first network device.

[0103] As can be seen, in this example, the first network device actively updates the terminal's URSP information to provide the terminal with network slicing services that guarantee performance.

[0104] In one possible instance, the second stopping policy includes: instructing the terminal to discard the first URSP information and determining the third URSP information as the current URSP information.

[0105] The third URSP information can be the URSP information originally used by the terminal, or it can be a specific URSP information.

[0106] As can be seen, in this example, the first network device instructs the terminal to discard the first URSP information and switch back to using the third URSP information to provide the terminal with network slicing services with performance guarantees.

[0107] In one possible instance, the second stopping policy includes: instructing the terminal to suspend the use of the first URSP information for a second preset time period, and determining the third URSP information as the current URSP information.

[0108] The second preset time period is the duration during which the terminal suspends the use of the first URSP information. This first preset time period can be a relative duration or an absolute duration. During this period, the first URSP information can be temporarily stored in the terminal's local storage medium.

[0109] As can be seen, in this example, the first network device instructs the terminal to discard the first URSP information and switch back to using the third URSP information to provide the terminal with network slicing services with performance guarantees.

[0110] In one possible instance, the slice access policy information includes the second policy information. After the terminal obtains the slice access policy information from the first network device, the method further includes: obtaining a second constraint condition for the first URSP information based on the second policy information; if the second constraint condition is not met, discarding the first URSP information and determining the third URSP information as the current URSP information.

[0111] The terminal can first determine the second restriction condition of the first URSP information. If the second restriction condition is not met, the terminal can actively discard the first URSP information and use the existing third URSP information. The second restriction condition may include the usage area and / or usage time. For example, when the validity period of the first URSP information expires, the terminal directly discards the first URSP information. When there are multiple second restrictions, the terminal can discard the first URSP information after a specific restriction condition is not met, after any one of the second restrictions is not met, or after multiple or all of the second restrictions are not met simultaneously.

[0112] In a specific implementation, after the terminal obtains the slice access policy information from the first network device, the method further includes: obtaining a second stop policy from the first network device; discarding the first URSP information according to the second stop policy, and determining the third URSP information as the current URSP information.

[0113] As can be seen, in this example, the terminal actively discards the first URSP information and switches back to using the original third URSP information after the second restriction condition is not met, thus ensuring the performance of the network slicing service used by the terminal.

[0114] In one possible instance, after obtaining the slice access policy information from the first network device, the method further includes: obtaining a second constraint condition for the first URSP information based on the second policy information; if the second constraint condition is not met, suspending the use of the first URSP information for a fourth preset time period, and determining the third URSP information as the current URSP information.

[0115] The fourth preset time period is the duration during which the terminal suspends the use of the slice remapping rule. The third preset time period can be a relative duration or an absolute duration. The fourth preset time period and the third preset time period can be the same.

[0116] In a specific implementation, after the terminal obtains the slice access policy information from the first network device, the method further includes: obtaining a second stop policy from the first network device; suspending the use of the first URSP information for a second preset time period according to the second stop policy, and determining the third URSP information as the current URSP information.

[0117] As can be seen, in this example, after the terminal fails to meet the second restriction condition, it suspends the use of the first URSP information during the second preset time period and switches back to using the original third URSP information, thus ensuring the performance of the network slicing service used by the terminal.

[0118] In one possible instance, after the second stop policy of sending the first URSP information to the terminal via a fourth message, the method further includes: sending the first URSP information enable message to the terminal, wherein the first URSP information enable message is used to indicate that the first URSP information is the current URSP information.

[0119] In this implementation, the first network device can proactively send activation information to the terminal, or it can receive the terminal's request for activation information first and then send the activation information to the terminal. Alternatively, the second network device can send activation information to the first network device first, and then the first network device sends it to the terminal. In a specific implementation, the terminal can also directly activate the first URSP information as the current URSP information after meeting the second constraint. For example, if the second constraint is that the first URSP information is applicable within area B, then because the terminal previously left area B, the second constraint is not met, and the first URSP information is suspended. When the terminal returns to area B, the second constraint is met, and the terminal can directly activate the first URSP information as the current URSP information.

[0120] As can be seen, in this example, the first network device can instruct the terminal to enable the first URSP information, which can ensure the performance of the network slicing service used by the terminal without having to send the slice access policy information again.

[0121] In one possible example, please refer to Figure 2b , Figure 2b This is a flowchart illustrating another slice access optimization method provided in this application embodiment. As shown in the figure, obtaining slice access strategy information includes the following steps:

[0122] Step 301: The first network device sends a slice access policy request message to the second network device;

[0123] Step 302: The second network device sends an access policy request to the first network device;

[0124] Step 303: The first network device receives slice access policy response information from the second network device;

[0125] Step 304: The first network device obtains the slice access policy information based on the slice access policy response information.

[0126] The slice access policy response information may include slice access policy information or information related to the slice access policy information. In this case, the first network device can generate slice access policy information based on the related information. For example, the first network device can predict the network slice congestion time through the slice access policy response information sent by the second network device, thereby determining the first or second constraint condition.

[0127] As can be seen, in this example, the first network device generates slice access policy information based on the information of the second network device, which can provide network slice services with performance guarantees for the terminal.

[0128] In one possible instance, the slice access policy request information includes preset slice access policy information.

[0129] The slice access policy request information may include slice access policy information. The response information from the second network device may include a determination of whether to use the slice access policy information. The second network device determines whether the preset slice access policy information is available and informs the first network device through its response information. If available, it informs the first network device to use the preset slice access policy; if unavailable, it includes the final slice access policy information in its response information, and the first network device uses the final slice access policy information.

[0130] As can be seen, in this example, the first network device generates slice access policy information based on the information of the second network device, which can provide network slice services with performance guarantees for the terminal.

[0131] In one possible instance, the slice access policy request information includes: requesting to obtain slice remapping rules and / or a first constraint condition of the slice remapping rules.

[0132] The first network device can determine slice remapping rules based on pre-configured information and send a slice access policy request to the second network device, requesting to obtain the first constraint condition of the slice remapping rules. Alternatively, the first network device can send a slice access policy request to the second network device, requesting to obtain the slice remapping rules and the first constraint condition. Or, the first network device can first send a slice access policy request to the second network device, requesting to obtain the slice remapping rules, and then send another slice access policy request to the second network device, requesting to obtain the second constraint condition. Specifically, the first and second network devices can be various types of network devices, and their device types can also be different. After obtaining the slice access policy request information, the second network device can also interact and communicate with other network devices, thereby sending the slice remapping rules and / or the first constraint condition to the first network device. For example, when the first network device is an AMF (Application Data Function), the second network device can be a Network Data Analytics Function (NWDAF) device. When the first network device is a gNB, the second network device can be an AI entity on the RAN side. That is, the rules for slice remapping may not only be pre-configured, but also ad-hoc decisions / dynamically generated. They will be generated by the NWDAF or the RAN-side AI entity based on requirements such as slice resource load, slice QoS, or Service Level Agreement (SLA).

[0133] As can be seen, in this example, obtaining information related to slice remapping through two network devices helps the terminal select a suitable network slice to initiate access, adjusts the network slice resource load, and ensures the user's network slice service experience.

[0134] In one possible instance, the slice access policy request information includes: requesting to obtain first URSP information and / or second limiting conditions for the first URSP information.

[0135] The first network device can obtain first URSP information based on pre-configured information and send slice access policy request information to the second network device, requesting the acquisition of second restrictions on the first URSP information. Specifically, the first and second network devices can be of various types, and their device types can also be different. After obtaining the slice access policy request information, the second network device can also interact and communicate with other network devices to send the first URSP information and / or the second restrictions to the first network device. For example, if the first network device is an AMF device and the second network device is a Policy Control Function (PCF) device, the second network device can interact and communicate with other network devices, such as NWDAF, to send the first URSP information and other content to the first network device.

[0136] As can be seen, in this example, obtaining URSP information through two network devices helps the terminal select a suitable network slice to initiate access, adjusts the network slice resource load, and ensures the user's network slice service experience.

[0137] In one possible instance, the slice access policy information includes the first policy information, and accessing the first network slice according to the slice access policy information includes: determining a first network slice identifier according to third URSP information; obtaining a second network slice identifier according to the first network slice identifier and the first policy information; and accessing the first network slice according to the second network slice identifier.

[0138] The third URSP information is the user's existing URSP information.

[0139] As can be seen, this example standardizes the behavior of terminals using slice remapping rules, ensuring that terminals can correctly initiate access requests for remapped network slice services.

[0140] In one possible instance, before accessing the first network slice based on the second network slice identifier, the method further includes: determining a second network slice based on the first network slice identifier; determining that the second network slice is prohibited in the serving cell, and that the second network slice identifier satisfies a third restriction condition corresponding to the slice remapping rule.

[0141] The terminal first determines a first network slice identifier based on existing URSP information. If the first network slice identifier is prohibited in the serving cell, a second network slice identifier can be determined based on the first policy information, i.e., the slice remapping rule. If the second network slice identifier meets a third restriction condition, the terminal performs network slice access based on the second network slice identifier. The third restriction condition can be the same as the first restriction condition, or it can be a preset default restriction condition. If the first network device does not send the second restriction condition to the terminal, it can default to meeting the second restriction condition.

[0142] As can be seen, this example standardizes the behavior of terminals using slice remapping rules, ensuring that terminals can correctly initiate access requests for remapped network slice services.

[0143] In one possible instance, the slice access policy information includes the second policy information, and accessing the first network slice according to the slice access policy information includes: obtaining first URSP information and a second constraint condition of the first URSP information; if the second constraint condition is met, determining a third network slice identifier according to the first URSP information; and accessing the first network slice according to the third network slice identifier.

[0144] As can be seen, this example standardizes the behavior of the terminal in using URSP information, ensuring that the terminal can correctly initiate access requests for the remapped network slice services.

[0145] In one possible instance, accessing a network slice according to the slice access policy information includes: determining a first network slice identifier based on third URSP information if the second restriction condition is not met; and accessing the network slice according to the first network slice identifier.

[0146] The third URSP information is the original URSP information of the terminal.

[0147] As can be seen, this example standardizes the behavior of the terminal in using URSP information, ensuring that the terminal can correctly initiate access requests for the remapped network slice services.

[0148] In one possible instance, the method further includes sending a configuration update request if the second constraint is not met.

[0149] The configuration update request information is used by the first network device to initiate a configuration update process to the terminal in order to update the terminal's current URSP information.

[0150] In a specific implementation, the method further includes: a first network device obtaining a configuration update request message from the terminal; and initiating a configuration update based on the configuration update request message.

[0151] As can be seen, this example standardizes the behavior of the terminal in using URSP information, ensuring that the terminal can correctly initiate access requests for the remapped network slice services.

[0152] In one possible instance, after obtaining the slice access policy information from the first network device, the method further includes: in the case of cell selection or / and reselection, obtaining a third network slice based on the current URSP information; and determining the first cell to be camped on based on the third network slice and the first policy information.

[0153] In this process, the user can obtain the network slice identifier of the third network slice based on the current URSP information, then determine the relationship between the third network slice corresponding to the network slice identifier and the neighboring cells, and then determine the first cell to be camped on based on the first policy information.

[0154] As can be seen, in this example, by selecting / reselecting cells, the establishment of network slice services and basic service experience expected by user equipment are guaranteed.

[0155] In one possible instance, determining the first cell to be camped on based on the third network slice and the first policy information includes: determining at least one fourth network slice based on the first policy information and the third network slice when neighboring cells do not support the third network slice; and determining a cell from the cells corresponding to the at least one fourth network slice as the first cell to be camped on.

[0156] If a neighboring cell does not support the third network slice, the terminal can find a fourth network slice that can be mapped or replaced by the corresponding third network slice using the slice remapping rules. When performing cell reselection or selection, the terminal will consider cells that support the fourth network slice.

[0157] As can be seen, in this example, by considering the candidate cell's support for the remapped network slice during cell selection / reselection, the terminal can select / reselect a cell that supports the remapped network slice, thereby ensuring the establishment of the terminal's desired network slice services and the basic service experience.

[0158] In one possible instance, determining the first cell to be camped based on the third network slice and the first policy information includes: if there is at least one cell supporting the third network slice, determining at least one fourth network slice based on the first policy information and the third network slice; and determining a cell from the third cell corresponding to the third network slice and / or the cell corresponding to the at least one fourth network slice as the first cell to be camped.

[0159] If there are multiple cells that support the third network slice, under the same conditions (such as the same RSRP / RSRQ measurement), the terminal can additionally consider cells that support the fourth network slice when selecting / reselecting cells.

[0160] As can be seen, in this example, by taking into account the support of candidate cells for the remapped network slices during cell selection / reselection, the impact of changes in the target cell slice resource load on the terminal can be reduced, the reliability of slice service establishment can be improved, and the terminal slice service experience can be guaranteed.

[0161] In one possible instance, after obtaining the slice access policy information from the first network device, the method further includes: determining the current URSP information based on the second policy information; and performing cell selection or / reselection based on the current URSP information.

[0162] In the process of cell selection or reselection, if the first network device updates the URSP information to the terminal, the updated URSP information can be used to determine the network slice identifier, and then the target network slice can be determined based on the network slice identifier, and the terminal can camp on a cell that supports the target network slice.

[0163] As can be seen, in this example, by determining the network slice identifier based on the updated URSP information during cell selection / reselection, the reliability of slice service establishment can be improved, and the service experience of terminal slice services can be guaranteed.

[0164] This application provides a slice access optimization device, which is used to execute the steps performed by the first electronic device in the slice access optimization method described above. The slice access optimization device provided in this application may include units corresponding to the response steps.

[0165] This application embodiment can divide the slice access optimization device into functional units according to the above method example. For example, each function can be divided into a separate functional unit, or two or more functions can be integrated into one processing unit. The integrated unit can be implemented in hardware or as a software functional unit. The unit division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0166] When dividing each functional unit according to its corresponding function. Figure 3 This diagram illustrates a possible structure of the slice access optimization device involved in the above embodiments, as shown below. Figure 3 As shown, the slice access optimization device 3 includes: an acquisition unit 31, used by a first electronic device to acquire slice access strategy information; and a sending unit 32, used by the first electronic device to send the slice access strategy information to a terminal.

[0167] In one possible example, the slice access policy information includes first policy information related to slice remapping, or second policy information related to User Equipment Routing Policy (URSP).

[0168] In one possible example, the slice access policy information includes the first policy information. In terms of sending the slice access policy information to the terminal, the sending unit 32 is specifically used to: send a slice remapping rule and / or a first restriction condition of the slice remapping rule to the terminal via a first message.

[0169] In one possible example, the device 3 is also used to: send a first stop policy of the slice remapping rule to the terminal via a second message.

[0170] In one possible example, before sending the first stop policy of the slice remapping rule to the terminal via the second message, the device 3 is further configured to: send a first stop policy request message to the second network device; receive a first stop policy reply message from the second network device; and obtain the first stop policy based on the first stop policy reply message.

[0171] In one possible example, the first stopping policy includes instructing the terminal to discard the slice remapping rule.

[0172] In one possible example, the first stopping policy includes instructing the terminal to suspend the use of the slice remapping rule for a first preset time period.

[0173] In one possible example, after sending the first stop policy of the slice remapping rule to the terminal via the second message, the device 3 is further configured to: send the slice remapping rule enable information to the terminal.

[0174] In one possible example, the first message includes a System Message Block (SIB) message, a Radio Resource Control (RRC) message, or a Non-Access Stratum (NAS) message.

[0175] In one possible example, the slice access policy information includes the second policy information, and in terms of sending the slice access policy information to the terminal, the sending unit 32 is specifically used to: send the first URSP information to the terminal via a third message, and / or the second limiting condition of the first URSP information.

[0176] In one possible example, the device 3 is also used to: send a second stop strategy of the first URSP information to the terminal via a fourth message.

[0177] In one possible example, the second stopping strategy includes:

[0178] The second URSP information is indicated to be the current URSP information, the second URSP information is the URSP information updated according to the preset URSP information, or the second URSP information is the URSP information regenerated by the first network device.

[0179] In one possible example, the second stopping policy includes: instructing the terminal to discard the first URSP information and determining the third URSP information as the current URSP information.

[0180] In one possible example, the second stopping strategy includes: instructing the terminal to suspend the use of the first URSP information for a second preset time period, and determining the third URSP information as the current URSP information.

[0181] In one possible example, after the second stop policy of sending the first URSP information to the terminal via a fourth message, the device 3 is further configured to: send the first URSP information enable message to the terminal, wherein the first URSP information enable message is used to indicate that the first URSP information is the current URSP information.

[0182] In one possible example, regarding the acquisition of slice access policy information, the acquisition unit 31 is specifically configured to: send a slice access policy request message to the second network device; receive slice access policy response information from the second network device; and acquire the slice access policy information based on the slice access policy response information.

[0183] In one possible example, the slice access policy request information includes preset slice access policy information.

[0184] In one possible example, the slice access policy request information includes: requesting to obtain slice remapping rules and / or a first constraint condition of the slice remapping rules.

[0185] In one possible example, the slice access policy request information includes: requesting to obtain first URSP information and / or second constraints on the first URSP information.

[0186] In one possible example, the device 3 is further configured to: acquire a configuration update request message from the terminal; and initiate a configuration update based on the configuration update request message.

[0187] All relevant content regarding each step in the above method embodiments can be referenced from the functional descriptions of the corresponding functional units, and will not be repeated here. Of course, the slice access optimization device provided in this application embodiment includes, but is not limited to, the above-mentioned units. For example, the slice access optimization device may also include a storage unit. The storage unit can be used to store the program code and data of the slice access optimization device.

[0188] When using integrated modules, the structural schematic diagram of the slice access optimization device provided in this application embodiment is as follows: Figure 4 As shown. In Figure 4 In this document, the slice access optimization device 4 includes a processing module 40 and a communication module 41. The processing module 40 controls and manages the operations of the slice access optimization device, for example, the steps performed by the acquisition unit 31 and the transmission unit 32, and / or other processes for performing the techniques described herein. The communication module 41 is used for interaction between the slice access optimization device and other devices. Figure 4 As shown, the slice access optimization device 4 may also include a storage module 42, which is used to store the program code and data of the slice access optimization processing device 3, such as the contents stored in the aforementioned storage unit.

[0189] The processing module 40 can be a processor or controller, such as a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an ASIC, an FPGA, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc. The communication module 41 can be a transceiver, RF circuitry, or a communication interface, etc. The storage module 42 can be a memory.

[0190] All relevant content in each scenario involved in the above method embodiments can be referenced from the functional descriptions of the corresponding functional modules, and will not be repeated here. Both the slice access optimization device 3 and the slice access optimization device 4 described above can execute the above... Figure 2a The steps performed by the first electronic device in the slice access optimization method shown.

[0191] This application also provides a slice access optimization device, which is used to execute the steps performed by the terminal in the above-described slice access optimization method. The slice access optimization device provided in this application may include units corresponding to the response steps.

[0192] This application embodiment can divide the slice access optimization device into functional units according to the above method example. For example, each function can be divided into a separate functional unit, or two or more functions can be integrated into one processing unit. The integrated unit can be implemented in hardware or as a software functional unit. The unit division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0193] When dividing each functional unit according to its corresponding function. Figure 5 This diagram illustrates a possible structure of the slice access optimization device involved in the above embodiments, as shown below. Figure 5 As shown, the slice access optimization device 5 includes: an acquisition unit 51, used for the terminal to acquire slice access policy information from the first network device; and an access unit 52, used for the terminal to access the first network slice according to the slice access policy information.

[0194] In one possible example, the slice access policy information includes first policy information related to slice remapping, or second policy information related to User Equipment Routing Policy (URSP).

[0195] In one possible example, the slice access policy information includes the first policy information. After obtaining the slice access policy information from the first network device, the obtaining unit 51 is specifically used to: obtain a first constraint condition for the slice remapping rule according to the first policy information; and discard the slice remapping rule if the first constraint condition is not met.

[0196] In one possible example, after obtaining the slice access policy information from the first network device, the device 5 is further configured to: obtain a first constraint condition for the slice remapping rule based on the first policy information; and suspend the use of the slice remapping rule for a third preset time period if the first constraint condition is not met.

[0197] In one possible example, after obtaining the slice access policy information from the first network device, the device 5 is further configured to: obtain a first stop policy from the first network device; and discard the slice remapping rule according to the first stop policy.

[0198] In one possible example, after obtaining the slice access policy information from the first network device, the device 5 is further configured to: obtain a first stop policy from the first network device; and suspend the use of the slice remapping rule for a first preset time period according to the first stop policy.

[0199] In one possible example, the slice access policy information includes the second policy information. After obtaining the slice access policy information from the first network device, the device 5 is further configured to: obtain a second constraint condition for the first URSP information based on the second policy information; if the second constraint condition is not met, discard the first URSP information and determine the third URSP information as the current URSP information.

[0200] In one possible example, after obtaining the slice access policy information from the first network device, the device 5 is further configured to: obtain a second constraint condition for the first URSP information according to the second policy information; if the second constraint condition is not met, suspend the use of the first URSP information for a fourth preset time period, and determine the third URSP information as the current URSP information.

[0201] In one possible example, after obtaining the slice access policy information from the first network device, the device 6 is further configured to: obtain a second stop policy from the first network device; determine the second URSP information as the current URSP information according to the second stop policy, wherein the second URSP information is URSP information updated according to preset URSP information, or the second URSP information is URSP information regenerated by the first network device.

[0202] In one possible example, after obtaining the slice access policy information from the first network device, the device is further configured to: obtain a second stop policy from the first network device; discard the first URSP information according to the second stop policy, and determine the third URSP information as the current URSP information.

[0203] In one possible example, after obtaining the slice access policy information from the first network device, the device 5 is further configured to: obtain a second stop policy from the first network device; suspend the use of the first URSP information for a second preset time period according to the second stop policy, and determine the third URSP information as the current URSP information.

[0204] In one possible example, the slice access policy information includes the first policy information. In terms of accessing the first network slice according to the slice access policy information, the access unit 52 is specifically configured to: determine the first network slice identifier according to the third URSP information; obtain the second network slice identifier according to the first network slice identifier and the first policy information; and access the first network slice according to the second network slice identifier.

[0205] In one possible example, before accessing the first network slice according to the second network slice identifier, the device 5 is further configured to: determine the second network slice according to the first network slice identifier; determine that the second network slice is prohibited in the serving cell, and that the second network slice identifier satisfies a third restriction condition corresponding to the slice remapping rule.

[0206] In one possible example, the slice access policy information includes the second policy information, and in terms of accessing the first network slice according to the slice access policy information, the access unit 52 is specifically used for:

[0207] In one possible example, the specific purpose is to: obtain first URSP information and a second constraint condition of the first URSP information; if the second constraint condition is satisfied, determine a third network slice identifier based on the first URSP information; and access the first network slice based on the third network slice identifier.

[0208] In one possible example, regarding accessing a network slice according to the slice access policy information, the access unit 52 is specifically configured to: determine a first network slice identifier based on third URSP information if the second restriction condition is not met; and access the network slice based on the first network slice identifier.

[0209] In one possible example, the device 5 is also used to: send configuration update request information if the second limiting condition is not met.

[0210] In one possible example, after obtaining the slice access policy information from the first network device, the device 5 is further configured to: obtain a third network slice based on the current URSP information in the case of cell selection or / and reselection; and determine the first cell to be camped on based on the third network slice and the first policy information.

[0211] In one possible example, in determining the first cell to be camped based on the third network slice and the first policy information, the apparatus 5 is further configured to: determine at least one fourth network slice based on the first policy information and the third network slice if neighboring cells do not support the third network slice; and determine a cell from the cells corresponding to the at least one fourth network slice as the first cell to be camped.

[0212] In one possible example, in determining the first cell to be camped based on the third network slice and the first policy information, the apparatus 5 is further configured to: determine at least one fourth network slice based on the first policy information and the third network slice if at least one cell supporting the third network slice exists; and determine a cell from the third cell corresponding to the third network slice and / or the cell corresponding to the at least one fourth network slice as the first cell to be camped.

[0213] In one possible example, after obtaining the slice access policy information from the first network device, the device 5 is further configured to: determine the current URSP information based on the second policy information; and perform cell selection or / reselection based on the current URSP information.

[0214] All relevant content regarding each step in the above method embodiments can be referenced from the functional descriptions of the corresponding functional units, and will not be repeated here. Of course, the slice access optimization device provided in this application embodiment includes, but is not limited to, the above-mentioned units. For example, the slice access optimization device may also include a storage unit. The storage unit can be used to store the program code and data of the slice access optimization device.

[0215] When using integrated modules, the structural schematic diagram of the slice access optimization device provided in this application embodiment is as follows: Figure 6 As shown. In Figure 6 In this document, the slice access optimization device 6 includes a processing module 60 and a communication module 61. The processing module 60 controls and manages the operation of the slice access optimization device, for example, acquiring the steps performed by the acquisition unit 51 and the access unit 52, and / or other processes for performing the techniques described herein. The communication module 61 is used for interaction between the slice access optimization processing device and other devices. Figure 6 As shown, the slice access optimization device 6 may also include a storage module 62, which is used to store the program code and data of the slice access optimization processing device 5, such as the contents stored in the aforementioned storage unit.

[0216] The processing module 60 can be a processor or controller, such as a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an ASIC, an FPGA, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc. The communication module 61 can be a transceiver, RF circuitry, or a communication interface, etc. The storage module 62 can be a memory.

[0217] All relevant content in each scenario involved in the above method embodiments can be referenced from the functional descriptions of the corresponding functional modules, and will not be repeated here. Both the slice access optimization device 5 and the slice access optimization device 6 described above can execute the above... Figure 2a The steps performed by the terminal in the slice access optimization method shown are illustrated.

[0218] This application also provides a slice access optimization device, which is used to execute the steps performed by the second electronic device in the above-described slice access optimization method. The slice access optimization device provided in this application may include units corresponding to the response steps.

[0219] This application embodiment can divide the slice access optimization device into functional units according to the above method example. For example, each function can be divided into a separate functional unit, or two or more functions can be integrated into one processing unit. The integrated unit can be implemented in hardware or as a software functional unit. The unit division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0220] When dividing each functional unit according to its corresponding function. Figure 7 This diagram illustrates a possible structure of the slice access optimization device involved in the above embodiments, as shown below. Figure 7 As shown, the slice access optimization device 7 includes: an acquisition unit 71, used for the second network device to acquire slice access policy request information from the first network device; and a sending unit 72, used for the second network device to send information related to the slice access policy request information to the first network device.

[0221] All relevant content regarding each step in the above method embodiments can be referenced from the functional descriptions of the corresponding functional units, and will not be repeated here. Of course, the slice access optimization device provided in this application embodiment includes, but is not limited to, the above-mentioned units. For example, the slice access optimization device may also include a storage unit. The storage unit can be used to store the program code and data of the slice access optimization device.

[0222] When using integrated modules, the structural schematic diagram of the slice access optimization device provided in this application embodiment is as follows: Figure 8 As shown. In Figure 8 In this document, the slice access optimization device 8 includes a processing module 80 and a communication module 81. The processing module 80 controls and manages the operation of the slice access optimization device, for example, the steps performed by the acquisition unit 71 and the transmission unit 72, and / or other processes for performing the techniques described herein. The communication module 81 is used for interaction between the slice access optimization processing device and other devices. Figure 8 As shown, the slice access optimization device 8 may further include a storage module 82, which is used to store the program code and data of the slice access optimization processing device 7, such as the contents stored in the aforementioned storage unit.

[0223] The processing module 80 can be a processor or controller, such as a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an ASIC, an FPGA, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc. The communication module 81 can be a transceiver, RF circuitry, or a communication interface, etc. The storage module 82 can be a memory.

[0224] All relevant content in each scenario involved in the above method embodiments can be referenced from the functional descriptions of the corresponding functional modules, and will not be repeated here. Both the slice access optimization device 7 and the slice access optimization device 8 described above can execute the above... Figure 2a , Figure 2b The steps performed by the terminal in the slice access optimization method shown are illustrated.

[0225] This application also provides a computer-readable storage medium storing a computer program for electronic data interchange, wherein the computer program causes a computer to perform some or all of the steps described in the network-side device of the above method embodiments.

[0226] This application provides a chip for a first network device to obtain slice access policy information and for sending the slice access policy information to a terminal.

[0227] This application provides a chip module, including a transceiver component and a chip. The chip is used for a first network device to obtain slice access policy information and for sending the slice access policy information to a terminal.

[0228] This application provides a chip for a terminal to obtain slice access policy information from a first network device and for the terminal to access a first network slice according to the slice access policy information.

[0229] This application provides a chip module, including a transceiver component and a chip. The chip is used for a terminal to obtain slice access policy information from a first network device and for the terminal to access a first network slice according to the slice access policy information.

[0230] This application provides a chip for a second network device to obtain slice access policy request information from a first network device; and for the second network device to send information related to the slice access policy request information to the first network device.

[0231] This application provides a chip module, including a transceiver component and a chip. The chip is used for a second network device to obtain slice access policy request information from a first network device; and for the second network device to send information related to the slice access policy request information to the first network device.

[0232] The steps of the methods or algorithms described in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, portable hard disks, read-only optical discs (CD-ROMs), or any other form of storage medium well known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Furthermore, the ASIC can reside in an access network device, a target network device, or a core network device. Alternatively, the processor and storage medium can exist as discrete components in the access network device, the target network device, or the core network device.

[0233] Those skilled in the art will recognize that, in one or more of the examples above, the functions described in the embodiments of this application can be implemented, in whole or in part, by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs (DVDs)), or semiconductor media (e.g., solid-state drives (SSDs)).

[0234] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the embodiments of this application. It should be understood that the above descriptions are merely specific embodiments of the embodiments of this application and are not intended to limit the protection scope of the embodiments of this application. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solutions of the embodiments of this application should be included within the protection scope of the embodiments of this application.

Claims

1. A slice access optimization method, characterized in that, The method includes: The first network device obtains slice access policy information; the slice access policy information includes first policy information related to slice remapping, or second policy information related to User Equipment Routing Policy (URSP); the first policy information includes slice remapping rules, and / or first limiting conditions of the slice remapping rules; The first network device sends the slice access policy information to the terminal, so that the terminal accesses the first network slice according to the second network slice identifier. The first network slice is associated with the first network slice identifier. The first network slice identifier is determined according to the third URSP information. The third URSP information is the URSP information that the terminal already has. The second network slice identifier is obtained according to the first network slice identifier and the first policy information. When the slice access policy information includes the second policy information, sending the slice access policy information to the terminal includes: sending the first URSP information to the terminal via a third message, and / or the second restriction condition of the first URSP information; sending the second stop policy of the first URSP information to the terminal via a fourth message; The first network device sends a first stop policy for the slice remapping rule to the terminal; the first stop policy includes: instructing the terminal to discard the slice remapping rule, or instructing the terminal to suspend the use of the slice remapping rule for a first preset time period.

2. The method according to claim 1, characterized in that, The slice access policy information includes the first policy information, and sending the slice access policy information to the terminal includes: The first message sends a slice remapping rule and / or a first constraint condition of the slice remapping rule to the terminal.

3. The method according to claim 2, characterized in that, The first stop policy for sending the slice remapping rule to the terminal includes: The first stop policy of the slice remapping rule is sent to the terminal via a second message.

4. The method according to claim 3, characterized in that, Before sending the first stop policy of the slice remapping rule to the terminal via the second message, the method further includes: Send a first stop policy request message to the second network device; Receive the first stop policy response information from the second network device; The first stop policy is obtained based on the response information of the first stop policy.

5. The method according to claim 3, characterized in that, After sending the first stop policy of the slice remapping rule to the terminal via the second message, the method further includes: Send the slice remapping rule activation information to the terminal.

6. The method according to claim 2, characterized in that, The first message includes a System Message Block (SIB) message, a Radio Resource Control (RRC) message, or a Non-Access Stratum (NAS) message.

7. The method according to claim 1, characterized in that, The second stopping strategy includes: The second URSP information is indicated to be the current URSP information, the second URSP information is the URSP information updated according to the preset URSP information, or the second URSP information is the URSP information regenerated by the first network device.

8. The method according to claim 1, characterized in that, The second stopping strategy includes: instructing the terminal to discard the first URSP information and determining the third URSP information as the current URSP information.

9. The method according to claim 1, characterized in that, The second stopping strategy includes: instructing the terminal to suspend the use of the first URSP information during a second preset time period, and determining the third URSP information as the current URSP information.

10. The method according to claim 9, characterized in that, After the second stop policy of sending the first URSP information to the terminal via the fourth message, the method further includes: Send the first URSP information enable message to the terminal. The first URSP information enable message is used to indicate that the first URSP information is the current URSP information.

11. The method according to claim 1, characterized in that, The acquisition of slice access strategy information includes: Send a slice access policy request message to the second network device; Receive slice access policy response information from the second network device; The slice access policy information is obtained based on the slice access policy response information.

12. The method according to claim 11, characterized in that, The slice access policy request information includes preset slice access policy information.

13. The method according to claim 11, characterized in that, The slice access policy request information includes: requesting to obtain slice remapping rules and / or the first limiting conditions of the slice remapping rules.

14. The method according to claim 11, characterized in that, The slice access policy request information includes: requesting to obtain first URSP information and / or second limiting conditions for the first URSP information.

15. The method according to claim 1, characterized in that, The method further includes: Obtain a configuration update request message from the terminal; Initiate a configuration update based on the configuration update request message.

16. A slice access optimization method, characterized in that, The method includes: The terminal obtains slice access policy information from the first network device; the slice access policy information includes first policy information related to slice remapping, or second policy information related to User Equipment Routing Policy (URSP); the first policy information includes slice remapping rules, and / or first limiting conditions of the slice remapping rules; The first network slice identifier is determined based on the third URSP information, wherein the third URSP information is the URSP information already existing in the terminal; Obtain the second network slice identifier based on the first network slice identifier and the first policy information; Access to the first network slice is based on the second network slice identifier, and the first network slice is associated with the first network slice identifier; When the slice access policy information includes the second policy information, after obtaining the slice access policy information from the first network device, the second restriction condition for obtaining the first URSP information is obtained according to the second policy information. If the second restriction condition is not met, the first URSP information is discarded and the third URSP information is determined as the current URSP information; or, the first URSP information is suspended for a fourth preset time period and the third URSP information is determined as the current URSP information. After obtaining the slice access policy information from the first network device, the method further includes: Obtain the first stop policy from the first network device; The slice remapping rule may be discarded according to the first stopping policy, or the slice remapping rule may be suspended for a first preset time period according to the first stopping policy.

17. The method according to claim 16, characterized in that, The slice access policy information includes the first policy information. After obtaining the slice access policy information from the first network device, the method further includes: The first constraint condition of the slice remapping rule is obtained based on the first strategy information; If the first restriction condition is not met, the slice remapping rule is discarded.

18. The method according to claim 16, characterized in that, After obtaining the slice access policy information from the first network device, the method further includes: The first constraint condition of the slice remapping rule is obtained based on the first strategy information; If the first restriction condition is not met, the slice remapping rule will be suspended for a third preset time period.

19. The method according to claim 16, characterized in that, After obtaining the slice access policy information from the first network device, the method further includes: Obtain the second stop policy from the first network device; The second URSP information is determined to be the current URSP information according to the second stopping policy. The second URSP information is either the URSP information updated according to the preset URSP information, or the second URSP information is the URSP information regenerated by the first network device.

20. The method according to claim 16, characterized in that, After obtaining the slice access policy information from the first network device, the method further includes: Obtain the second stop policy from the first network device; The first URSP information is discarded according to the second stopping policy, and the third URSP information is determined as the current URSP information.

21. The method according to claim 16, characterized in that, After obtaining the slice access policy information from the first network device, the method further includes: Obtain the second stop policy from the first network device; According to the second stopping strategy, the use of the first URSP information is suspended during the second preset time period, and the third URSP information is determined to be the current URSP information.

22. The method according to claim 16, characterized in that, Before accessing the first network slice according to the second network slice identifier, the method further includes: The second network slice is determined based on the first network slice identifier; It is determined that the second network slice is prohibited in the serving cell, and the second network slice identifier satisfies the third restriction condition corresponding to the slice remapping rule.

23. The method according to claim 16, characterized in that, The slice access policy information includes the second policy information, and the step of accessing the first network slice according to the slice access policy information includes: The second constraint condition for obtaining the first URSP information; If the second restriction condition is met, a third network slice identifier is determined based on the first URSP information; Access the first network slice according to the third network slice identifier.

24. The method according to claim 23, characterized in that, Accessing the network slice according to the slice access policy information includes: If the second restriction condition is not met, the first network slice identifier is determined based on the third URSP information; Access the network slice based on the first network slice identifier.

25. The method according to claim 23, characterized in that, The method further includes: If the second restriction condition is not met, a configuration update request is sent.

26. The method according to claim 16, characterized in that, After obtaining the slice access policy information from the first network device, the method further includes: In the case of cell selection or / reselection, the third network slice is obtained based on the current URSP information; The first cell to be stationed is determined based on the third network slice and the first policy information.

27. The method according to claim 26, characterized in that, The step of determining the first cell to be camped on based on the third network slice and the first policy information includes: If the neighboring cell does not support the third network slice, at least one fourth network slice is determined based on the first policy information and the third network slice. One cell is selected from the cells corresponding to the at least one fourth network slice as the first cell to be stationed.

28. The method according to claim 26, characterized in that, The step of determining the first cell to be camped on based on the third network slice and the first policy information includes: If at least one cell supports the third network slice, at least one fourth network slice is determined based on the first policy information and the third network slice; One cell is determined from the third cell corresponding to the third network slice and / or the cell corresponding to at least one fourth network slice as the first cell to be camped.

29. The method according to claim 16, characterized in that, After obtaining the slice access policy information from the first network device, the method further includes: Determine the current URSP information based on the second strategy information; Cell selection or / reselection is performed based on the current URSP information.

30. A slice access optimization device, characterized in that, include: An acquisition unit is used by a first electronic device to acquire slice access policy information; the slice access policy information includes first policy information related to slice remapping, or second policy information related to User Equipment Routing Policy (URSP); the first policy information includes slice remapping rules, and / or first limiting conditions of the slice remapping rules; The sending unit is configured to send the slice access policy information from the first electronic device to the terminal, so that the terminal accesses the first network slice according to the second network slice identifier. The first network slice is associated with the first network slice identifier. The first network slice identifier is determined according to the third URSP information. The third URSP information is the URSP information that the terminal already has. The second network slice identifier is obtained according to the first network slice identifier and the first policy information. When the slice access policy information includes the second policy information, in terms of sending the slice access policy information to the terminal, the sending unit is used to send the first URSP information and / or the second restriction condition of the first URSP information to the terminal via a third message; the device is used to send the second stop policy of the first URSP information to the terminal via a fourth message. The sending unit is further configured to send the first stop policy of the slice remapping rule to the terminal; The first stopping strategy includes: instructing the terminal to discard the slice remapping rule, or instructing the terminal to suspend the use of the slice remapping rule for a first preset time period.

31. A slice access optimization device, characterized in that, include: The acquisition unit is used for the terminal to acquire slice access policy information from the first network device; The slice access policy information includes first policy information related to slice remapping, or second policy information related to User Equipment Routing Policy (URSP); the first policy information includes slice remapping rules, and / or first limiting conditions of the slice remapping rules. The access unit is configured to determine a first network slice identifier based on third URSP information, wherein the third URSP information is existing URSP information of the terminal; and to obtain a second network slice identifier based on the first network slice identifier and the first policy information. Access to the first network slice is based on the second network slice identifier, and the first network slice is associated with the first network slice identifier; When the slice access policy information includes the second policy information, after obtaining the slice access policy information from the first network device, the device is used to obtain the second restriction condition of the first URSP information according to the second policy information. If the second restriction condition is not met, the first URSP information is discarded and the third URSP information is determined as the current URSP information, or the first URSP information is suspended for a fourth preset time period and the third URSP information is determined as the current URSP information. The acquisition unit is further configured to acquire a first stop policy from the first network device after the terminal acquires slice access policy information from the first network device; discard the slice remapping rule according to the first stop policy, or suspend the use of the slice remapping rule for a first preset time period according to the first stop policy.

32. A network device, characterized in that, The method includes a processor, a memory, and one or more programs stored in the memory and configured to be executed by the processor, the programs including instructions for performing the steps of the method as described in any one of claims 1-15.

33. A terminal, characterized in that, The method includes a processor, a memory, and one or more programs stored in the memory and configured to be executed by the processor, the programs including instructions for performing the steps of the method as described in any one of claims 16-29.

34. A computer-readable storage medium, characterized in that, A computer program for storing electronic data interchange, wherein the computer program causes a computer to perform the method as described in any one of claims 1-15 or any one of claims 16-29.

Images