Configuring Routing Policies
Through the computing device receiving and processing the routing policy request of the user equipment, and configuring network slicing based on the traffic type and user type, solving the problem that user equipment cannot automatically adjust network slicing in the prior art, realizing automatic optimization of application or service performance and Improved user experience.
Patent Information
- Application Number
- CN201880098976.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2018-08-24
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2038-08-24
AI Technical Summary
The prior art is difficult to effectively configure and manage routing strategies between user equipment and network slicing, resulting in poor user experience, especially when the application or service performance does not meet thresholds.
Receive routing policy requests from user equipment through computing devices, determine appropriate network slices based on traffic type and user type, and configure routing policies in the core network, including policy control functions and access and mobility management functions to ensure traffic routing to a network slice that meets performance requirements.
It realizes automatic adjustment of network slices according to the performance needs of the application or service, improves user experience, ensures that traffic is routed to network slices that meet performance thresholds, and improves network resource utilization efficiency and user equipment performance performance.
Smart Images

Figure CN112913283B_ABST
Abstract
Description
Background Art
[0001] One or more network slices may be created on top of the network infrastructure, and data may be transmitted via the network slices. Different parameters for each network slice may be used to meet different requirements for network slices. A user device may select a network slice to route traffic generated by a specific application or service running on the user device. Summary of the invention
[0002] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the various embodiments, nor is it intended to be used to limit the scope of the claims.
[0003] Systems, apparatus, and methods for configuring a routing policy are described. A computing device may receive a routing policy request from a user device and via a network. The routing policy request may indicate an application or service. The computing device may receive a message from a second computing device indicating one or more types of traffic associated with the application or service. The computing device may determine a routing policy associated with the application or service based on the one or more types of traffic. The routing policy may indicate one or more of a protocol data unit session for the application or service or a network slice for the application or service. The computing device may send the routing policy to the user device.
[0004] In some examples, the computing device may select a network slice suitable for routing one or more types of traffic from a plurality of network slices. In some examples, the computing device may determine a user type associated with a user device. Determining a routing policy may be further based on the user type. In some examples, the computing device may determine a charging rate for an application or service based on one or more types of traffic and the user type. The routing policy may further indicate a charging rate. In some examples, the computing device may include a policy control function (PCF), and wherein receiving a routing policy request includes receiving a routing policy request via an access and mobility management function (AMF).
[0005] In some examples, the computing device may receive a negotiation request from a user device and based on the routing policy, the negotiation request indicating a second routing policy associated with the application or service. The computing device may determine a scope associated with the routing policy. Based on determining whether the second routing policy is within the scope associated with the routing policy, the computing device may determine whether to accept the second routing policy. In some examples, based on determining to accept the second routing policy, the computing device may send a message to the user device to apply the second routing policy.
[0006] In some examples, determining the scope associated with the routing policy can be based on one or more of a user type associated with the user device or a current condition of the network. In some examples, the computing device can determine whether to allow the user device to negotiate based on one or more of a user type associated with the user device or a current condition of the network. Based on determining that the user device is not allowed to negotiate, the computing device can send a message to the user device rejecting the negotiation request.
[0007] In some examples, the computing device may determine a number of negotiation requests associated with an application or service received from a user device. Based on determining that the number of negotiation requests meets a threshold number, the computing device may send a message to the user device rejecting the negotiation request. In some examples, the computing device may determine whether the routing policy request is valid based on a validation parameter associated with the routing policy request. Determining the routing policy may be based on determining that the routing policy request is valid.
[0008] In some examples, based on determining that the routing policy request does not indicate the verification parameter, the computing device may send a challenge request for the verification parameter to the user device. The computing device may receive a message indicating the verification parameter from the user device. The computing device may send a second message indicating the verification parameter to the second computing device. The computing device may receive a message indicating that the routing policy request is valid from the second computing device.
[0009] In some examples, the computing device may determine whether the routing policy is stored in a database of the computing device based on an identification of the application or service. Determining the routing policy may be based on determining that the routing policy is not stored in a database of the computing device. In some examples, receiving the routing policy request may be based on one or more of: attachment of a user device to a network, movement of a user device, a network switch of a user device, a message indicating a policy update from the computing device, or installation of an application or service on a user device.
[0010] In some examples, the computing device may include means for receiving a routing policy request from a user device and via a network. The routing policy request may indicate an application or service. The computing device may include means for receiving a message indicating one or more types of traffic associated with the application or service from a second computing device. The computing device may include means for determining a routing policy associated with the application or service based on one or more types of traffic. The routing policy may indicate one or more of a protocol data unit session for the application or service or a network slice for the application or service. The computing device may include means for sending the routing policy to the user device. Additional examples are discussed further below. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] Some example embodiments are illustrated by way of example and not limitation in the accompanying drawings, in which like reference numerals indicate like elements, and in which:
[0012] Figure 1 is a schematic diagram illustrating an example communication network in which the features described herein may be implemented.
[0013] Figure 2 is a schematic diagram showing an example system that uses network slicing for communication.
[0014] Figure 3 is a schematic diagram illustrating an example system for using and configuring user equipment routing policy rules.
[0015] Figure 4 is a sequence of events illustrating an example method for configuring user equipment routing policy rules.
[0016] Figure 5 is a flow chart illustrating an example method for configuring user equipment routing policy rules.
[0017] Figure 6 An example apparatus is shown that may be used in the network environment described herein or to implement one or more aspects described herein.
[0018] Figure 7 An example system is shown that can be used in the network environment described herein or to implement one or more aspects described herein. DETAILED DESCRIPTION
[0019] In the following description of various illustrative embodiments, reference is made to the accompanying drawings, which form a part of this specification and in which are shown by way of illustration various embodiments in which the present disclosure may be practiced. It will be understood that other embodiments may be utilized and structural and functional modifications may be made without departing from the scope of the present disclosure.
[0020] Figure 1 1 is a schematic diagram illustrating an example communication network 100 in which the features described herein may be implemented. The communication network 100 may include one or more user equipment (e.g., user equipment 101), one or more radio access networks (e.g., radio access network 103), one or more core networks (e.g., core network 105), one or more data networks (e.g., data network 107), and one or more data network service servers (e.g., data network service servers 109A, 109B). The communication network 100 may be configured to implement various communication protocols, such as communication protocols specified by the Third Generation Partnership Project (3GPP).
[0021] The user device 101 may include, for example, a smartphone, a personal computer, a tablet computer, a desktop computer, a laptop computer, a gaming device, a virtual reality headset, or any other mobile device or other fixed device having a wireless interface configured to communicate with a radio access network. The data network service servers 109A, 109B may be computing devices configured to provide any desired application or service.
[0022] The data network 107 may be a single network or a collection of multiple connected networks. The data network 107 may include one or more of any of various types of information distribution networks, such as satellite networks, telephone networks, cellular networks, Wi-Fi networks, Ethernet networks, fiber optic networks, coaxial cable networks, hybrid fiber coaxial networks, etc., without limitation. The data network 107 may include a local area network (LAN), a wide area network (WAN), a backbone network, etc. The data network 107 may include an Internet Protocol (IP)-based network (e.g., the Internet). The data network 107 may include multiple interconnected communication links (e.g., to connect data network service servers 109A, 109B and / or other devices).
[0023] The radio access network 103 may include any type of equipment for implementing a radio access technology, such as a third generation wireless system (3G), a fourth generation wireless system (4G), a long term evolution (LTE), and a fifth generation wireless system (5G). For example, the radio access network 103 may include a universal terrestrial radio access network (UTRAN), an evolved Node B (eNodeB), a gNodeB (gNB), or other types of radio access networks. The radio access network 103 may be configured to implement a radio protocol stack. The radio access network 103 may additionally or alternatively include a cloud radio access network (e.g., including a central unit and a distributed unit that together implement a radio protocol stack).
[0024] The core network 105 may include processes implemented on one or more computing devices. The core network 105 may be configured to manage connectivity between the user equipment 101 via the radio access network 103 and the data network 107 (e.g., the Internet). The core network 105 may include, for example, an evolved packet core (EPC), a 5G core network, or other types of core networks. The core network 105 may communicate with the radio access network 103 and / or the data network 107 via any type of communication link, such as an IP-based communication link. The radio access network 103 and the core network 105 may be configured to provide wireless communication between the user equipment 101 and the data network 107 (e.g., the Internet).
[0025] exist Figure 11 shows example components of a core network 105 (e.g., a 5G core network). The core network 105 may include one or more network functions, such as AMF 151 (core access and mobility management function), UPF 152 (user plane function), SMF 153 (session management function), AUSF 154 (authentication server function), NSSF 155 (network slice selection function), NEF 156 (network exposure function), NRF 157 (network repository function), PCF 158 (policy control function), UDM 159 (unified data management), AF 160 (application function), and / or other networks. The network functions 151-160 may include processes implemented on one or more computing devices. The network functions 151-160 may communicate with each other via any type of communication link, such as an IP-based communication link, a virtual network link, a logical connection, etc. The network functions 151-160 described herein may have similar meanings to those specified by 3GPP (e.g., in 3GPP Technical Specification 23.501 Version 15.2.0 Release 15). The core network 105 may include additional or alternative network functions, for example, to provide wireless communication between the user equipment 101 and a data network 107 (e.g., the Internet).
[0026] A network (e.g., communication network 100) or a portion thereof may be partitioned into multiple virtual networks that may run on the same physical infrastructure of the network (e.g., underlying physical 5G infrastructure). A network slice (e.g., a virtual network in the multiple virtual networks) may include, for example, a radio access network, network functions of a core network, etc. Resources (e.g., computing, storage, and network resources) of the physical infrastructure may be allocated to the network slice to implement, for example, a radio access network and / or network functions of a core network using network function virtualization (NFV). The network slice may be configured to provide specific network capabilities and network characteristics, and / or the network slice may be customized for (one or more) users in the network slice.
[0027] Various types of network slices can be established for different purposes. For example, an enhanced mobile broadband (eMBB) type of network slice may be suitable for handling 5G enhanced mobile broadband traffic, such as augmented reality (AR) or virtual reality (VR) application or service traffic. A massive Internet of Things (MIoT) type of network slice may be suitable for handling IoT traffic. An ultra-reliable low-latency communication (URLLC) type of network slice may be suitable for handling ultra-reliable low-latency communications, such as vehicle-to-everything (V2X) communications. Additionally or alternatively, network slices may be associated with different performance parameters, such as quality of service (QOS) and / or quality of experience (QOE), bandwidth, transmission latency, traffic security, etc.
[0028] Figure 2 is a schematic diagram illustrating an example system for communicating using network slicing. The system may include network slices 201A, 201B. The network slices in the network slices 201A, 201B may be identified by an identifier, such as single network slice selection assistance information (S-NSSAI). The network slice 201A may include a radio access network 103A, a UPF 152A, and a data network 107A. The network slice 201B may include a radio access network 103B, a UPF 152B, and a data network 107B. The network slices 201A, 201B may include additional or alternative components, such as other network functions of the core network 105. The network slices 201A, 201B may be implemented on the same physical infrastructure.
[0029] The network slices 201A, 201B may have different characteristics. Different resources may be allocated to the network slices 201A, 201B to implement their network functions (e.g., using network function virtualization). As an example, different amounts of computing resources may be used to implement the UPF 152A and the UPF 152B. As another example, different amounts of computing resources may be used to implement a portion of the RAN 103A and a portion of the RAN 103B (e.g., if they are cloud radio access networks, then to implement the central unit of the RAN 103A, 103B). Additionally, messages sent via the network slices 201A, 201B may be treated differently by the physical infrastructure. As an example, messages sent via the network slices 201A, 201B may be treated differently by the data network 107, which may prioritize messages sent via one of the network slices as if the network slices 201A, 201B were associated with two different data networks 107A, 107B.
[0030] The user equipment 101 can communicate with the data network service servers 109A, 109B via the network slice 201A, the network slice 201B and / or other network slices. The user equipment 101 can determine the network slice via which to send specific traffic generated by the user equipment 101 based on the user equipment (UE) routing selection policy (URSP) rule. Figure 3 1 is a schematic diagram showing an example system for using and configuring URSP rules. The system may include a user device 101, an AMF 151, a PCF 158, network slices 201A, 201B, and one or more data network service servers (e.g., data network service servers 109A-109C).
[0031] In order to communicate via the network slice, the user equipment 101 may establish one or more packet data unit (PDU) sessions to the data network in the network slice. The PDU session may include an association between the user equipment and the data network providing connectivity services. The user equipment 101 may indicate the S-NSSAI of the network slice to the AMF 151 and / or the SMF 153 during the PDU session establishment process to create the PDU session in the network slice. As an example, the user equipment may establish a PDU session 325A in the network slice 201A, and may establish PDU sessions 325B, 325C in the network slice 201B. The PDU sessions 325A, 325B, 325C may be associated with different performance parameters (such as quality of service (QOS)), and / or may be connected to different types of data networks (e.g., IP networks, non-IP networks, Ethernet, etc.).
[0032] The user device 101 may run and / or have installed various applications and / or services (e.g., applications and / or services 321A-321C). Applications and / or services 321A-321C may be, for example, augmented reality applications or services, vehicle-to-everything applications or services, and / or other types of applications and / or services running on a computing device. Applications and / or services 321A-321C may be connected to, for example, a data network service server, other computing devices, a software defined network (SDN) or network function virtualization (NFV) network, and / or any other sub-application / data network (e.g., a voice over IP (VoIP) network). Applications and / or services 321A-321C may transmit different types of traffic. For example, an application or service may be an augmented reality application or service or a virtual reality application or service, and may generate enhanced mobile broadband traffic. Another application or service may be a thermostat application or service, and may generate Internet of Things traffic. Another application or service may be a vehicle-to-everything application or service, and may generate ultra-reliable low-latency traffic. The user device 101 (e.g., via the mapping engine 323) can use the URSP rules to direct different types of traffic from applications and / or services 321A-321C to appropriate network slices and / or PDU sessions. For example, based on the URSP rules, the user device 101 can route traffic from a virtual reality application or service to an eMBB type network slice.
[0033] The URSP rule may indicate an application or service and a corresponding network slice (and / or PDU session) that may be used to transmit traffic associated with the application or service. In some cases, the user device 101 may not store URSP rules for a particular application or service, and traffic associated with the application or service may be transmitted according to a default URSP rule that may direct the traffic to a default network slice. As new applications and / or services emerge to provide new applications and / or services to users, traffic associated with the new applications and / or services may be routed via a default network slice that may not be suitable for routing traffic. The user experience may be negatively affected.
[0034] A negotiable URSP management function (NUMF) 301 in PCF 158 may be used to mitigate the challenge. NUMF 301 may be configured to generate URSP rules for new applications and / or services, for example, based on information obtained from a data network service server, UDM 159, and / or other computing devices. For example, if a new application or service is installed and / or updated on a user device, the user device may be configured to query NUMF 301 for URSP rules. In this way, applications and / or services running on the user device may be routed via the appropriate network slice based on the URSP rules specific to the application and / or service.
[0035] NUMF 301 may include a management component 303 and a verification component 305. Management component 303 may be configured to generate URSP rules and update user equipment with the URSP rules. Verification component 305 may be configured to determine whether a request for obtaining URSP rules is effectively generated and / or transmitted (e.g., to prevent malicious requests). Figure 4-5 Discusses more details about updating URSP rules on user equipment.
[0036] Figure 4 is a sequence of events illustrating an example method for configuring URSP rules. Although the steps of the sequence of events are described in a particular order, the order of the steps may be changed without departing from the scope of the disclosure provided herein. Although the sequence of events is described as being performed by a particular arrangement of computing systems, devices, and / or networks (e.g., user device 101, computing devices, and data network service servers), the process may be performed by a greater or lesser number of computing systems, devices, and / or networks and / or by any type of computing systems, devices, and / or networks.
[0037] In step 401, the user device 101 may send a routing policy request to a computing device (e.g., NUMF 301). The routing policy request may be sent via the AMF 151 and may be sent in an early data transmission (e.g., a random access channel (RACH) message), a radio resource control (RRC) message, and / or any other type of message. The routing policy request may indicate one or more applications and / or services (e.g., via one or more application and / or service identifiers). The user device 101 may send a routing policy request in various situations. For example, when the user device 101 is attached to the core network 105 (e.g., registering with the core network 105 to receive connectivity services), the user device 101 may send a routing policy request. During or after the attachment process, the user device 101 may determine which (which) applications and / or services installed on the user device 101 may not have corresponding (one or more) URSP rules. The routing policy request may seek to obtain (one or more) URSP rules for those applications and / or services.
[0038] If a new application or service is installed on the user device 101, and the user device 101 does not store URSP rules for the new application or service, the user device 101 may additionally or alternatively send a routing policy request. The routing policy request may seek to obtain URSP rules for the new application or service. Additionally or alternatively, the user device 101 may determine whether the user device 101 stores URSP rules for the application(s) and / or service(s) installed on the user device 101, and / or send routing policy requests for URSP rules(s) not stored on the user device 101 at different times, such as when the user device 101 detects that it has moved from one location to another, when the user device 101 receives a message from the PCF 158 indicating a specific URSP rule(s), when the user device 101 receives a message from the PCF 158 indicating a policy update, when the user device 101 performs a handover based on a service change or a network change, and / or when other events occur. Additionally or alternatively, the user equipment 101 may periodically send a request for (one or more) URSP rules for applications and / or services stored on the user equipment 101. Additionally or alternatively, the core network 105 may configure the user equipment 101 to identify whether and / or when to send a routing policy request.
[0039] The user device 101 may monitor the performance of the application or service of the application and / or service installed on the user device 101, and may send a routing policy request if the performance of the application or service does not meet a performance threshold. For example, the user device 101 may monitor the performance of a virtual reality application or service, and may determine whether the quality of a video (and / or other type of data) received via a network slice (e.g., a default network slice) currently being used by the user device 101 meets (e.g., meets or exceeds) a quality threshold. If not, the user device 101 may send a routing policy request to obtain an updated network slice for the application or service.
[0040] In step 403, the computing device may receive a routing policy request and may verify the received routing policy request (e.g., to prevent malicious requests). The routing policy request may indicate information for verifying the request. For example, the routing policy request may indicate a verification parameter, and the computing device may verify the routing policy request based on the verification parameter. The verification parameter may be, for example, a token, a password, a random value, etc., which is generated by a data network service server associated with the application or service indicated in the routing policy request (e.g., generated by an entity that develops and / or publishes the application or service). For example, when the user device 101 downloads an application or service, the verification parameter may be distributed to the user device 101. The verification parameter may also be transmitted to the computing device. If the computing device determines that the verification parameter indicated in the routing policy request does not match the verification parameter received by the computing device from the data network service server, the computing device may not further process the routing policy request. In this way, the computing device can detect a routing policy request sent by a deceptive application and / or service.
[0041] The computing device may verify the routing policy request based on an identifier of the application or service indicated in the routing policy request. The computing device may store a blacklist and / or whitelist of applications and / or services, which may indicate whether to allow the generation of URSP rules for the application and / or service. For example, if the application or service is determined to be a malicious application or service, the computing device may blacklist the application or service. If the computing device determines that the generation of URSP rules for the application or service indicated in the routing policy request is not permitted, the computing device may not further process the routing policy request.
[0042] Additionally or alternatively, the routing policy request may indicate an identifier of the user device 101, and the computing device may verify the routing policy request based on the user device identifier. The computing device may store a blacklist and / or a whitelist of user devices, which may indicate whether the user device has permission to send routing policy requests. If the computing device determines that the user device frequently sends routing policy requests indicating that the authentication parameters do not match the authentication parameters received from the data network service server, the user device may not have permission. If the computing device determines that the user device 101 does not have permission to send the routing policy request, the computing device may not further process the routing policy request.
[0043] If the routing policy request does not indicate information used to verify the routing policy request, then in step 405, the computing device may send a challenge request to the user device 101. The challenge request may request the user device 101 to send information used to verify the routing policy request to the computing device. In step 407, the user device 101 may receive the challenge request and may send a challenge response to the computing device. The challenge response may indicate information used to verify the routing policy request. The computing device may use the information in the challenge response to verify the routing policy request in a manner similar to that discussed in step 403. If the computing device does not receive a challenge response from the user device 101 within a time threshold after sending the challenge request, the computing device may determine not to further process the routing policy request.
[0044] The computing device may additionally or alternatively use a data network service server associated with the application or service indicated in the routing policy request to verify the routing policy request (e.g., in the case where the data network service server does not distribute verification parameters to the computing device). In step 409, the computing device may send an authentication request to the data network service server, the authentication request indicating information used to verify the routing policy request (such as an identifier of the user device 101, an identifier of the application or service, and / or verification parameters). The data network service server may receive the authentication request and may verify the routing policy request based on the information. For example, the data network service server may determine whether the verification parameters indicated in the authentication request match the verification parameters generated and stored by the data network service server. In step 411, the data network service server may send an authentication response to the computing device indicating whether the routing policy request is valid.
[0045] If the routing policy request is verified, then in step 413, the computing device may determine the URSP rule(s) for the application(s) and / or service(s) indicated in the routing policy request. The computing device may obtain information related to the application(s) and / or service(s) from various sources, such as data network service servers associated with the application(s) and / or service(s) and / or UDM 159. For example, the computing device may receive threshold performance parameters (e.g., quality of service, bandwidth, transmission latency), and may select network slices and / or PDU sessions that meet the performance parameters. The computing device may include the selected network slices and / or PDU sessions in the URSP rules for the application or service of the user device 101. In combination Figure 5 Further details regarding determination of URSP rules by a computing device are discussed.
[0046] After determining the URSP rule(s) for the application(s) and / or service(s) indicated in the routing policy request, in step 415, the computing device may send a message indicating the determined URSP rule(s) to the user device 101. The user device 101 may receive the message and may extract the URSP rule(s) from the message. The user device 101 may determine whether to accept or reject the URSP rule(s) received from the computing device based on various criteria. If the user device 101 determines to reject the one or more URSP rules received from the computing device, then in step 417, the user device 101 may initiate a URSP rule negotiation with the computing device.
[0047] The user device 101 may determine whether to accept or reject the URSP rules for the application or service and received from the computing device. Whether to accept or reject the URSP rules may be based on expected performance parameters associated with the application or service stored on the user device 101. The expected performance parameters may indicate, for example, quality of service, bandwidth, transmission delay, data security, etc. In some examples, the expected performance parameters may indicate the quality of service, bandwidth, transmission delay, and / or data security level at which the application or service works in an optimal state.
[0048] The user device 101 can receive expected performance parameters from a data network service server associated with the application or service. The developer of the application or service may know the appropriate service quality, bandwidth, or transmission latency for the application or service, and can input this information to the data network service server. Additionally or alternatively, the data network service server can monitor various instances of the application or service running on the user device. Various instances of the application or service can use network slices and / or PDU sessions with different performance parameters. The data network service server can determine the expected performance parameters for the application or service to operate correctly (e.g., for a virtual reality application or service with a transmission video quality that exceeds a video quality threshold).
[0049] The user device 101 may determine whether the network slice and / or PDU session indicated in the URSP rule received from the computing device meets (e.g., meets or exceeds) the expected performance parameters associated with the application or service. If so, the user device 101 may accept the URSP rule, may indicate acceptance to the computing device, and may apply the URSP rule. Otherwise, the user device 101 may reject the URSP rule. Additionally or alternatively, the URSP rule received from the computing device may indicate a charging rate for using the indicated network slice and / or PDU session. The user device may determine whether the charging rate is lower than a threshold charging rate (e.g., one dollar per gigabyte of data) for the user device 101. If so, the user device 101 may accept the URSP rule. Otherwise, the user device 101 may reject the URSP rule. The threshold charging rate may be set, for example, by a user of the user device 101.
[0050] If the user equipment 101 determines to reject the URSP rule received from the computing device, the user equipment 101 may send a negotiation request in step 419. The core network 105 may configure the user equipment 101 whether to send a negotiation request. The negotiation request may indicate the expected performance parameters (and / or the threshold charging rate). Additionally or alternatively, the user equipment 101 may store identifiers of various network slices and / or PDU sessions. The user equipment 101 may select a network slice and / or PDU session that meets the expected performance parameters, and may include the selected network slice and / or PDU session in the negotiation request.
[0051] The computing device may receive a negotiation request from the user device 101, and may determine whether the expected performance parameter falls within the range of the threshold performance parameter used by the computing device in determining the URSP rule in step 413. The range may be set, for example, by an operator and / or administrator of the core network 105. Additionally or alternatively, the computing device may adjust the range based on the type of the user device 101. For example, if the user device 101 is associated with a prioritized user, the computing device may set the range to be larger. Additionally or alternatively, the computing device may adjust the range based on current network conditions (e.g., current conditions of the radio access network 103, the core network 105, and / or the data network 107). For example, if the network(s) are currently overloaded (e.g., if the communication delay via the network(s) exceeds the threshold delay), the computing device may set the range to be smaller.
[0052] If the expected performance parameter falls within the range of the threshold performance parameter used in the URSP rule determined by the computing device in step 413, the computing device may determine another network slice and / or PDU session that meets the expected performance parameter. In step 423, the computing device may send a message to the user device 101 applying the determined network slice and / or PDU session.
[0053] If the expected performance parameter does not fall within the range of the threshold performance parameter used in the URSP rule determined by the computing device in step 413, the computing device may send a negotiation response to the user device 101 in step 421. The negotiation response may indicate a set of performance parameters within the range of the threshold performance parameter used in the URSP rule determined by the computing device in step 413. The user device 101 may determine whether to accept or reject the set of performance parameters indicated in the negotiation response. The computing device may set a limit on the number of negotiation rounds that may occur between the user device 101 and the computing device. The limit may be adjusted based on the type of user device 101 and / or current network conditions. For example, if the user device 101 is associated with a prioritized user, and / or if the network(s) are not currently overloaded, the limit may be adjusted to a larger value. If a final agreement is made on the URSP rule after the negotiation, the user device 101 and the computing device may apply the URSP rule.
[0054] Additionally or alternatively, the computing device may establish criteria for negotiation between the computing device and the user device 101. For example, the computing device may determine whether to allow the user device 101 to negotiate (e.g., to obtain URSP rules that are different from the URSP rules originally assigned by the computing device) based on the type of the user device 101. As an example, if the user device 101 is associated with a prioritized user, the computing device may allow the user device 101 to negotiate. If the user device 101 is associated with a regular user, the computing device may not allow the user device 101 to negotiate. Additionally or alternatively, the computing device may determine whether to allow the user device 101 to negotiate based on current network conditions. For example, if (one or more) networks are currently overloaded, the computing device may not allow the user device 101 to negotiate (e.g., to obtain a higher performance network slice and / or PDU session).
[0055] If the computing device determines that user device 101 is not allowed to negotiate, and if user device 101 sends a negotiation request to the computing device, the computing device may send a negotiation response indicating a rejection of the negotiation request to user device 101. In such a situation, user device 101 may apply the URSP rule originally sent by the computing device (e.g., in step 415) or the default URSP rule of user device 101. Additionally or alternatively, if user device 101 is allowed to negotiate, and if the number of negotiation requests sent by user device 101 regarding a particular URSP rule originally assigned by the computing device (e.g., in step 415) exceeds a limit on the number of negotiation rounds that may occur between user device 101 and the computing device, the computing device may send a negotiation response indicating a rejection of the negotiation request to user device 101.
[0056] Figure 5 is a flow chart showing an example method for configuring URSP rules. The method may be, for example, Figure 3 For simplicity, the steps of the method may be described as being performed by specific components and / or computing devices, but the steps may be performed by any components and / or computing devices. Figure 4 The process associated with step 413 may be implemented using the process described below.
[0057] In step 501, a computing device (eg, NUMF 301) may determine whether a received routing policy request is authenticated. Authentication of a routing policy request may be performed in various ways and / or based on various types of information, such as in conjunction with Figure 4If the routing policy request is verified (step 501: Y), the method may proceed to step 503. Otherwise (step 501: N), the computing device may wait for a verified routing policy request.
[0058] In step 503, the computing device may determine whether the URSP rule for the application or service indicated in the routing policy request is stored in a database of the computing device. The computing device may have a database storing URSP rules for applications and / or services. The database may be any type of storage device. The computing device may search the database to determine whether the URSP rule corresponding to the application or service indicated in the routing policy request is stored in the database. If the URSP rule for the application or service is stored in the database of the computing device (step 503: Y), the method may proceed to step 519. In step 519, the computing device may send a message indicating the URSP rule for the application or service to the user device 101. If the routing policy request indicates multiple applications and / or services, the computing device may determine the URSP rules for multiple applications and / or services, and may send a message indicating the URSP rules for multiple applications and / or services to the user device 101.
[0059] If the URSP rules for the application or service indicated in the routing policy request are not stored in a database of the computing device (step 503: N), the method may proceed to step 505. In step 505, the computing device may obtain an application or service profile associated with the application or service. For example, the computing device may send a request for an application or service profile to a data network service server associated with the application or service. The application or service profile may indicate, for example, one or more types of traffic that the application or service may generate (e.g., enhanced mobile broadband traffic, Internet of Things traffic, ultra-reliable low latency traffic, or other types of traffic). The application or service profile may also indicate, for example, a threshold quality of service, bandwidth, transmission delay, or other performance parameters for the application or service.
[0060] The data network service server may receive a request for an application or service profile. The data network service server may, for example, generate an application or service profile based on information provided by a developer or administrator of the application or service. For example, the developer of the application or service may know what type of traffic the application or service may generate, and may input this information into the application or service profile. The developer of the application or service may also know the threshold quality of service, bandwidth, transmission delay, or other performance parameters for the application or service, and may input this information into the application or service profile. The data network service server may send the application or service profile to the computing device. In step 507, the computing device may receive the application or service profile from the data network service server, and may extract information (such as traffic type) from the application or service profile. The computing device may determine the traffic type of the application or service and / or the threshold quality of service of the application or service.
[0061] In step 509, the computing device may obtain a user profile associated with the user device 101. For example, the computing device may send a request for the user profile to the UDM 159. The user profile may indicate a user type, such as a very important person (VIP) user or a regular user. The request may indicate, for example, an identifier of the user device 101 and / or an identifier of a user of the user device 101. The UDM 159 may store user subscription information, or may manage user identification and / or access authorization. In response to receiving the request, the UDM 159 may, for example, search its user subscription database to retrieve a user profile for the user of the user device 101. The UDM 159 may send the user profile to the computing device.
[0062] The computing device may receive a user profile from the UDM 159. In step 511, the computing device may extract information (such as the user type) from the received user profile. For example, the computing device may determine whether the user is a prioritized user or a regular user. Additionally or alternatively, the computing device may receive a user profile from a data network service server. The data network service server may collect information and generate a user profile. The data network service server may distribute the user profile to both the user device 101 and the computing device. The computing device may also receive a user profile from the user device 101 and may determine to use the user profile received from the user device 101 if it matches the user profile received by the computing device from the data network service server.
[0063] In step 513, the computing device may determine a network slice and / or PDU session for the application or service indicated in the routing policy request. For example, the computing device may determine a network slice for the application or service based on the traffic type of the application or service. The computing device may select a network slice suitable for transmitting the traffic type of the application or service. For example, if the application or service profile indicates that the application or service generates enhanced mobile broadband traffic, the computing device may select a network slice of the enhanced mobile broadband type for the application or service.
[0064] The computing device may determine a network slice for an application or service based on a threshold quality of service, bandwidth, transmission latency, or other performance parameters for the application or service. The user device 101 may have access to multiple network slices, and each network slice may have its own performance parameters (e.g., performance guarantees). As an example, one of the network slices may have an aggregate throughput guarantee (e.g., greater than 100 megabits per second (Mbps) or less than 200 Mbps), guaranteed resource sharing (e.g., greater than or less than 25% of capacity), and / or a latency limit (e.g., less than 500 milliseconds). The computing device may determine one or more network slices that meet (e.g., reach or exceed) the threshold performance parameters for the application or service based on the number of network slices. The determined one or more network slices may be used for the application or service.
[0065] The computing device may determine a PDU session for an application or service, for example, based on a traffic type for the application or service and / or a threshold performance parameter associated with the application or service. For example, the computing device may select a PDU session in a network slice determined for the application or service. Additionally or alternatively, a PDU session may be associated with a traffic type and / or a performance parameter. For example, a particular PDU may be suitable for enhanced mobile broadband traffic, and / or may have certain performance guarantees. The computing device may select a PDU session that is suitable for the traffic type of the application or service and / or meets a threshold performance parameter associated with the application or service.
[0066] The computing device may additionally determine the network slice and / or PDU session based on the user type of the user of the user device 101. In this way, the network slices and / or PDU sessions for different users of the same application or service may be different. For example, if each network slice and / or PDU session meets a threshold performance parameter associated with the application or service, a higher quality of service network slice and / or PDU session may be allocated to a prioritized user, and a lower quality of service network slice and / or PDU session may be allocated to a regular user.
[0067] In step 515, the computing device may determine charging information for the determined network slice and / or PDU session. The charging information may be determined based on the network slice and / or PDU session. Each network slice and / or PDU session may be associated with a specific charging rate. This information may be stored, for example, in a database of the computing device. As an example, a higher performance network slice and / or PDU session may be charged at a higher rate.
[0068] The application or service profile received from the data network service server may indicate that if the user is a prioritized user (e.g., a very important person user), the data network service server may sponsor or pay for the cost of the network slice and / or PDU session selected for the application or service. In such a situation, if the user sending the routing policy request is a prioritized user, the computing device may set the cost of the determined network slice and / or PDU session to zero (0). If the URSP rule indicating the cost of the network slice and / or PDU session is accepted by the user device, the computing device may notify the core network 105 of the party to be charged for the use of the network slice and / or PDU session. For example, if the data network service server sponsors the cost, the core network 105 may be notified to charge the entity associated with the data network service server.
[0069] In step 517, the computing device may generate a URSP rule for the application or service indicated in the routing policy request. The URSP rule may have a data field indicating the determined network slice and / or PDU session and a data field indicating the determined charging information. The generated URSP rule may also be recorded and stored in a database of the computing device, so that if the computing device receives another routing policy request for the same application or service and the same type of user, the computing device can retrieve the URSP rule from the database. In some examples, if the computing device determines that multiple network slices and / or PDU sessions are suitable for the application or service, the computing device may, for example, include a network slice and / or PDU session with the best performance parameters and free of charge. In step 519, the computing device may send the generated URSP rule to the user device 101.
[0070] Additionally or alternatively, if the application or service indicated in the routing policy request can generate different types of traffic, the computing device can generate a URSP rule indicating multiple network slices and / or PDU sessions. For example, if the application or service generates both enhanced mobile broadband traffic and ultra-reliable low latency traffic, the computing device can generate a URSP rule indicating network slices and / or PDU sessions suitable for both types of traffic. The URSP rule can additionally indicate one or more traffic type descriptors for the network slices and / or PDU sessions. Based on the traffic type descriptors, the user device 101 can direct the traffic generated by the application or service to the appropriate network slice and / or PDU session.
[0071] Figure 6 The diagram shows that Figure 1 The example apparatus, in particular the computing device 612, used in a communication network such as the communication network shown in FIG. 1 is used to implement any one or all of the user equipment 101, the radio access network 103, the core network 105, the data network service server 109A-109C and / or other computing devices to perform the above and Figure 4-5 The computing device 612 may include a controller 625. The controller 625 may be connected to a user interface control 630, a display 636, and / or other elements as shown. The controller 625 may include circuitry such as, for example, one or more processors 628 and one or more memories 634 storing software 640 (e.g., computer executable instructions). The software 640 may include, for example, one or more of the following software options: user interface software, server software, etc., which includes a radio protocol stack, network functions 151-160, applications and / or services 321A-321C, a mapping engine 323, PDU sessions 325A-325C, etc.
[0072] Device 612 may also include a battery 650 or other power supply device, a speaker 653, and one or more antennas 654. Device 612 may include user interface circuitry, such as a user interface control unit 630. User interface control unit 630 may include a controller or adapter and other circuits, which are configured to receive input from a keyboard, touch screen, voice interface or provide output to a keyboard, touch screen, voice interface, such as via microphone 656, function keys, joystick, data gloves, mouse, etc. User interface circuitry and user interface software may be configured to facilitate user control of at least some functions of device 612 by using display 636. Display 636 may be configured to display at least a portion of a user interface of device 612. Additionally, the display may be configured to facilitate user control of at least some functions of the device (e.g., display 636 may be a touch screen).
[0073] Software 640 may be stored within memory 634 to provide instructions to processor 628 that, when executed, cause processor 628, device 612, and / or other components of device 612 to perform various functions or methods, such as those described herein (e.g., as described in Figure 4-5 6). Software may include machine-executable instructions and data used by processor 628 and other components of computing device 612, and may be stored in storage facilities such as memory 634 and / or in hardware logic in integrated circuits, ASICs, etc. Software may include both applications and / or services as well as operating system software, and may include code segments, instructions, applets, precompiled code, compiled code, computer programs, program modules, engines, program logic, and combinations thereof.
[0074] The memory 634 may include any of various types of tangible machine-readable storage media, including one or more of the following types of storage devices: read-only memory (ROM) modules, random access memory (RAM) modules, magnetic tapes, magnetic disks (e.g., fixed hard disk drives or removable floppy disks), optical disks (e.g., CD-ROM disks, CD-RW disks, DVD disks), flash memory, and EEPROM memory. As used herein (including the claims), a tangible or non-transitory machine-readable storage medium is a physical structure that can be touched by a human. A signal itself will not constitute a tangible or non-transitory machine-readable storage medium, although other embodiments may include ephemeral versions or signals of instructions that can be executed by one or more processors to perform one or more operations described herein.
[0075] As used herein, processor 628 (and any other processor or computer described herein) may include any of various types of processors, whether used alone or in combination with executable instructions stored in a memory or other computer-readable storage medium. A processor should be understood to include any of various types of computing structures, including but not limited to one or more microprocessors, special-purpose computer chips, field programmable gate arrays (FPGAs), controllers, application-specific integrated circuits (ASICs), hardware accelerators, digital signal processors, software-defined radio components, combinations of hardware / firmware / software, or other special or general-purpose processing circuits.
[0076] As used in this application, the term "circuitry" may refer to any of: (a) a hardware-only circuit implementation (such as an implementation solely in analog and / or digital circuits), and (b) a combination of circuitry and software (and / or firmware), such as (as applicable): (i) a combination of (one or more) processors, or (ii) portions of (one or more) processors / software (including (one or more) digital signal processors), software, and (one or more) memories that work together to enable an apparatus such as a mobile phone, server or other computing device to perform various functions), and (c) circuitry that requires software or firmware to operate even if the software or firmware is not physically present, such as (one or more) microprocessors or portions of (one or more) microprocessors.
[0077] These examples of "circuitry" apply to all uses of this term in this application, including in any claims. As an example, as used in this application, the term "circuitry" would also cover an implementation of only a processor (or multiple processors) or portion of a processor and its (or their) accompanying software and / or firmware. The term "circuitry" would also cover, for example, a radio frequency circuit, a baseband integrated circuit or an application processor integrated circuit for a mobile phone, or a similar integrated circuit in a server, cellular network device, or other network device.
[0078] The device 612 or its various components may be mobile and configured to receive, decode and process various types of transmissions, including transmissions in Wi-Fi networks according to wireless local area networks (e.g., IEEE 802.11 WLAN standards 802.11n, 802.11ac, etc.) and / or wireless metropolitan area network (WMAN) standards (e.g., 802.16) through specific one or more WLAN transceivers 643, one or more WMAN transceivers 641. Additionally or alternatively, the device 612 may be configured to receive, decode and process transmissions through various other transceivers, such as FM / AM radio transceivers 642 and telecommunications transceivers 644 (e.g., cellular network receivers such as CDMA, GSM, 4G LTE, 5G, etc.). The wired interface 645 (e.g., Ethernet interface) may be configured to provide communication via a wired communication medium (e.g., optical fiber, cable, Ethernet, etc.).
[0079] although Figure 6The above description in generally relates to mobile devices, but other devices or systems may include the same or similar components and perform the same or similar functions and methods. For example, a computer communicating via a wired network connection (e.g., radio access network 103, core network 105, and data network service servers 109A-109C) may include the above components or a subset of components and may be configured to perform the same or similar functions as device 612 and its components. Another access point as described herein may include a component, a subset of components, or multiple components (e.g., integrated in one or more servers) configured to perform the steps described herein.
[0080] Figure 7 The diagram shows that Figure 1 An example system for use in a communication network such as the communication network shown in FIG. 1 is used to implement various devices described herein such as a core network (e.g., core network 105), a radio access network (e.g., radio access network 103), and / or other computing devices to perform the above and Figure 4-5 The system may include one or more core networks (eg, core network 105), one or more radio access networks (eg, radio access network 103), and one or more communication links (eg, communication link 731).
[0081] The core network 105 may include a controller 701 that may include circuitry such as one or more processors 703 and one or more memories 705 storing software 707 (e.g., computer executable instructions). The software 707 may include, for example, the network functions 151-160. The software 707 may be stored in the memory 705 to provide instructions to the processor 703 so that when the instructions are executed, the processor 703, the core network 105, and / or other components of the core network 105 perform various functions or methods, such as those described herein (e.g., as described in Figure 4-5 ). The core network 105 may include a general purpose processor, a digital signal processor, a hardware accelerator, or a software defined radio component.
[0082] The core network 105 may include a battery 709 or other power supply device, and one or more wired interfaces 711. The wired interface 711 (e.g., an Ethernet interface) may be configured to provide communication via a wired communication medium (e.g., optical fiber, cable, Ethernet, etc.). The wired interface 711 may communicate with a wired interface 761 in the radio access network 103 via a communication link 731. The wired interface 711 may also communicate with a network (e.g., a data network 107).
[0083] The radio access network 103 may include a controller 751 that may include circuitry such as one or more processors 753 and one or more memories 755 storing software 757 (e.g., computer executable instructions). The software 757 may include, for example, a radio protocol stack implemented by the radio access network 103. The software 757 may be stored within the memory 755 to provide instructions to the processor 753 such that, when executed, the processor 753, the radio access network 103, and / or other components of the radio access network 103 perform various functions or methods, such as those described herein.
[0084] The radio access network 103 may include a battery 759 or other power supply device, one or more wired interfaces 761, one or more wireless transceivers 763, and one or more antennas 765. The radio access network 103 or its various components may be configured to receive, decode, and process transmissions through various transceivers, such as wireless transceivers 763 (e.g., cellular network receivers such as CDMA, GSM, 4G LTE, 5G, etc.). The wireless transceiver 763 may include a downlink processing component and / or an uplink processing component. The downlink processing component and / or the uplink processing component may include a radio frequency transmission component, a radio frequency reception component, or a baseband processing component. The processing component may include a general purpose processor, a digital signal processor, a software defined radio component, a hardware accelerator, or a software component. Using the wireless transceiver 763 and the antenna 765, the radio access network 103 may be configured to communicate with a user device (e.g., user device 101) according to various aspects described herein. The wired interface 761 (eg, an Ethernet interface) may be configured to provide communication via a wired communication medium (eg, optical fiber, cable, Ethernet, etc.) The wired interface 761 may communicate with the wired interface 711 in the core network 105 via the communication link 731 .
[0085] The software may include machine-executable instructions and data used by processors and other components of the core network 105 and / or radio access network 103, and may be stored in storage facilities such as memories 705, 755 and / or in hardware logic in integrated circuits, ASICs, etc. The software may include both applications and / or services as well as operating system software, and may include code segments, instructions, applets, pre-compiled code, compiled code, computer programs, program modules, engines, program logic, and combinations thereof.
[0086] The memories 705, 755 may include any of various types of tangible machine-readable storage media, including one or more of the following types of storage devices: read-only memory (ROM) modules, random access memory (RAM) modules, magnetic tapes, magnetic disks (e.g., fixed hard disk drives or removable floppy disks), optical disks (e.g., CD-ROM disks, CD-RW disks, DVD disks), flash memory, and EEPROM memory. As used herein (including the claims), a tangible or non-transitory machine-readable storage medium is a physical structure that can be touched by a human. A signal itself will not constitute a tangible or non-transitory machine-readable storage medium, although other embodiments may include a transient version or signal of an instruction that can be executed by one or more processors to perform one or more operations described herein.
[0087] As used herein, processor 628 (and any other processor or computer described herein) may include any of various types of processors, whether used alone or in combination with executable instructions stored in a memory or other computer-readable storage medium. A processor should be understood to include any of various types of computing structures, including but not limited to one or more microprocessors, special-purpose computer chips, field programmable gate arrays (FPGAs), controllers, application-specific integrated circuits (ASICs), combinations of hardware / firmware / software, or other special or general-purpose processing circuits.
[0088] Although specific examples of implementing the present disclosure have been described, those skilled in the art will appreciate that there are many variations and permutations of the above-described systems and methods that are included within the spirit and scope of the present disclosure. Any and all permutations, combinations, and sub-combinations of the features described herein, including but not limited to the features specifically recited in the claims, are within the scope of the present disclosure.
Claims
1. A method for configuring a routing policy, comprising: Receiving, by a computing device (301) from a user device (101) and via a network (100), a routing policy request for obtaining a routing policy for routing one or more types of traffic from one or more applications or services, wherein the routing policy request indicates the one or more applications or services; receiving, from a data network server (109A, 109B, 109C) associated with an application or service indicated in the routing policy request, a message indicating one or more types of traffic associated with the application or service, the one or more types of traffic comprising enhanced mobile broadband traffic, Internet of Things traffic, ultra-reliable low latency traffic, or other types of traffic; Determining a routing policy associated with the application or service based on the one or more types of traffic, wherein the routing policy indicates one or more of a protocol data unit session for the application or service or a network slice for the application or service; and Send the routing policy to the user equipment.
2. The method according to claim 1 further includes selecting a network slice suitable for routing the one or more types of traffic from a plurality of network slices.
3. The method according to claim 1 or 2, further comprising: determining a user type associated with the user equipment, wherein determining the routing strategy is further based on the user type; and Based on the one or more types of traffic and the type of user, a charging rate for the application or service is determined, wherein the routing policy further indicates the charging rate.
4. The method according to claim 1 or 2, further comprising: receiving a negotiation request from a user device and based on the routing policy, the negotiation request indicating a second routing policy associated with the application or service; determining a scope associated with a routing policy; and Based on determining whether the second routing policy is within a range associated with the routing policy, a determination is made whether to accept the second routing policy.
5. The method according to claim 4, further comprising: Based on determining to accept the second routing selection policy, a message for applying the second routing selection policy is sent to the user equipment.
6. The method of claim 4, wherein determining the scope associated with the routing policy is based on one or more of a user type associated with the user device or a current condition of the network.
7. The method according to claim 4, further comprising: determining whether to allow the user equipment to negotiate based on one or more of a user type associated with the user equipment or a current condition of the network; and Based on determining that the user equipment is not allowed to conduct the negotiation, a message rejecting the negotiation request is sent to the user equipment.
8. The method according to claim 4, further comprising: determining a number of negotiation requests associated with the application or service received from a user device; and Based on determining that the number of negotiation requests meets the threshold number, a message rejecting the negotiation request is sent to the user equipment.
9. The method according to any one of claims 1-2, further comprising determining whether the routing policy request is valid based on a verification parameter associated with the routing policy request, wherein determining the routing policy is based on determining that the routing policy request is valid.
10. The method according to any one of claims 1-2, further comprising: Based on determining that no verification parameter is indicated in the routing policy request, sending a challenge request for the verification parameter to the user equipment; receiving a message indicating authentication parameters from a user device; sending a second message indicating authentication parameters to the data network server (109A, 109B, 109C); and A message is received from the data network server (109A, 109B, 109C) indicating that a routing policy request is valid.
11. The method according to any one of claims 1-2, further comprising determining whether a routing selection policy is stored in a database of the computing device based on the identification of the application or service, wherein determining the routing selection policy is based on determining that the routing selection policy is not stored in the database of the computing device.
12. A device for configuring a routing strategy, comprising: one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the apparatus to: receiving, from a user device and via a network, a routing policy request for obtaining a routing policy for routing one or more types of traffic from one or more applications or services, wherein the routing policy request indicates the one or more applications or services; receiving, from a data network server (109A, 109B, 109C) associated with an application or service indicated in the routing policy request, a message indicating one or more types of traffic associated with the application or service, the one or more types of traffic comprising enhanced mobile broadband traffic, Internet of Things traffic, ultra-reliable low latency traffic, or other types of traffic; Determining a routing policy associated with the application or service based on the one or more types of traffic, wherein the routing policy indicates one or more of a protocol data unit session for the application or service or a network slice for the application or service; and Send the routing policy to the user equipment.
13. An apparatus according to claim 12, wherein the memory stores instructions that, when executed by the one or more processors, further cause the apparatus to select a network slice from a plurality of network slices suitable for routing the one or more types of traffic.
14. The apparatus of claim 12 or 13, wherein the memory stores instructions which, when executed by the one or more processors, further cause the apparatus to: determining a user type associated with the user device, wherein determining the routing strategy is further based on the user type; and Based on the one or more types of traffic and the type of user, a charging rate for the application or service is determined, wherein the routing policy further indicates the charging rate.
15. The apparatus of claim 12 or 13, wherein the memory stores instructions which, when executed by the one or more processors, further cause the apparatus to: receiving a negotiation request from a user device and based on the routing policy, the negotiation request indicating a second routing policy associated with the application or service; determining a scope associated with a routing policy; and Based on determining whether the second routing policy is within a range associated with the routing policy, a determination is made whether to accept the second routing policy.
16. The apparatus of claim 15, wherein the memory stores instructions that, when executed by the one or more processors, further cause the apparatus to: Based on determining to accept the second routing selection policy, a message for applying the second routing selection policy is sent to the user equipment.
17. The apparatus of claim 15, wherein the memory stores instructions that, when executed by the one or more processors, further cause the apparatus to determine a scope associated with a routing selection strategy based on one or more of a user type associated with a user device or a current condition of a network.
18. The apparatus of claim 15, wherein the memory stores instructions that, when executed by the one or more processors, further cause the apparatus to: determining whether to allow the user equipment to negotiate based on one or more of a user type associated with the user equipment or a current condition of the network; and Based on determining that the user equipment is not allowed to conduct the negotiation, a message rejecting the negotiation request is sent to the user equipment.
19. The apparatus of claim 15, wherein the memory stores instructions that, when executed by the one or more processors, further cause the apparatus to: determining a number of negotiation requests associated with the application or service received from a user device; and Based on determining that the number of negotiation requests meets the threshold number, a message rejecting the negotiation request is sent to the user equipment.
20. A computer readable medium storing computer program instructions which, when executed by a computing device, cause the computing device to perform the method according to any one of claims 1-11.
