WO2023071662A1 - 资源分配方法、网元、存储介质 - Google Patents

资源分配方法、网元、存储介质 Download PDF

Info

Publication number
WO2023071662A1
WO2023071662A1 PCT/CN2022/121451 CN2022121451W WO2023071662A1 WO 2023071662 A1 WO2023071662 A1 WO 2023071662A1 CN 2022121451 W CN2022121451 W CN 2022121451W WO 2023071662 A1 WO2023071662 A1 WO 2023071662A1
Authority
WO
WIPO (PCT)
Prior art keywords
shared
target
cluster
session
bandwidth
Prior art date
Application number
PCT/CN2022/121451
Other languages
English (en)
French (fr)
Inventor
石原
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2023071662A1 publication Critical patent/WO2023071662A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/08—Trunked mobile radio systems

Definitions

  • the present application relates to but not limited to the communication field, and in particular relates to a resource allocation method, a network element, and a storage medium.
  • shared bandwidth services which are user groups composed of multiple users or data network names (Data Network Name , DNN) as a shared cluster, and the shared bandwidth is pre-allocated for the shared cluster, and shared by all users in the shared cluster.
  • DNN Data Network Name
  • Policy Control Function Policy Control Functionality, PCF
  • PCF Policy Control Functionality
  • Embodiments of the present application provide a resource allocation method, a network element, and a storage medium.
  • the embodiment of the present application provides a method for resource allocation, which is applied to a first network element.
  • the method includes: determining the target shared cluster to which the PDU session to be configured belongs, wherein the PDU session to be configured is Allocating a PDU session with a bandwidth rate, the target shared cluster is pre-configured with a shared bandwidth; determining the target bandwidth rate of the PDU session to be configured, and assigning the target bandwidth rate to the PDU session to be configured from the shared bandwidth.
  • an embodiment of the present application provides a network element, including: a memory, a processor, and a computer program stored in the memory and operable on the processor, and the processor implements the following when executing the computer program.
  • a network element including: a memory, a processor, and a computer program stored in the memory and operable on the processor, and the processor implements the following when executing the computer program.
  • the embodiment of the present application provides a computer-readable storage medium, storing computer-executable instructions, where the computer-executable instructions are used to execute the resource allocation method as described in the first aspect.
  • FIG. 1 is a flowchart of a resource allocation method applied to a network element provided by an embodiment of the present application
  • FIG 2 is an architecture diagram of existing policy control and charging (Policy Control and Charging, PCC);
  • FIG. 3 is a flowchart of determining a target shared cluster provided by another embodiment of the present application.
  • FIG. 4 is a flow chart of determining the allocation of shared bandwidth provided by another embodiment of the present application.
  • Fig. 5 is a flow chart of delivering the first sharing policy provided by another embodiment of the present application.
  • FIG. 6 is a flowchart of Example 1 provided by another embodiment of the present application.
  • FIG. 7 is a flowchart of determining a target shared cluster provided by another embodiment of the present application.
  • FIG. 8 is a flow chart of determining the allocation of shared bandwidth provided by another embodiment of the present application.
  • FIG. 9 is a flowchart of Example 2 provided by another embodiment of the present application.
  • Fig. 10 is a flowchart of Example 3 provided by another embodiment of the present application.
  • FIG. 11 is a flow chart of determining a target shared cluster provided by another embodiment of the present application.
  • FIG. 12 is a flow chart of determining the allocation of shared bandwidth provided by another embodiment of the present application.
  • Fig. 13 is a flowchart of Example 4 provided by another embodiment of the present application.
  • FIG. 14 is a flowchart of determining a target bandwidth rate provided by another embodiment of the present application.
  • Fig. 15 is a flow chart of updating the occupied bandwidth rate provided by another embodiment of the present application.
  • Fig. 16 is an apparatus diagram of a network element provided by another embodiment of the present application.
  • the present application provides a resource allocation method, a network element, and a storage medium.
  • the resource allocation method includes: determining the target shared cluster to which the PDU session to be configured belongs, wherein the PDU session to be configured is a PDU session with a bandwidth rate to be allocated, The target shared cluster is pre-configured with a shared bandwidth; determining the target bandwidth rate of the PDU session to be configured, and allocating the target bandwidth rate to the PDU session to be configured from the shared bandwidth.
  • the bandwidth rate can be allocated for the PDU session to be configured from the shared bandwidth, resource allocation is realized at the granularity of the shared cluster, allocation control of the shared bandwidth is realized, and the flexibility of bandwidth configuration is improved.
  • FIG. 1 is a flowchart of a resource allocation method provided by an embodiment of the present application.
  • the resource allocation method is applied to a first network element, including but not limited to step S110 and step S120 .
  • Step S110 determining the target shared cluster to which the PDU session to be configured belongs, wherein the PDU session to be configured is a PDU session with a bandwidth rate to be allocated, and the target shared cluster is pre-configured with shared bandwidth.
  • the shared cluster can be a DNN, or a user group composed of multiple users.
  • This embodiment does not limit the specific form of the shared cluster, and can be based on a user-defined route (User Defined Routing, UDR). Sign up for a package to share bandwidth.
  • UDR User Defined Routing
  • Sign up for a package to share bandwidth It can be understood that the unified data management function (Unified Data Management, UDM) is the core network control plane entity, which belongs to the user server and can permanently store the user subscription data. Based on this, after signing the group shared bandwidth, those skilled in the art You are familiar with how to obtain contract information from UDM, so I won't repeat them here.
  • UDM Unified Data Management
  • the first network element can be a PCF, a session management function (Session Management Function, SMF) or a user plane function (User Plane Function, UPF) in the architecture shown in FIG. Calculation and allocation of the shared bandwidth can be performed during the process, and those skilled in the art can select a specific entity as the first network element according to actual needs, and there is no limitation here.
  • SMF Session Management Function
  • UPF User Plane Function
  • the PCF is the control plane entity of the core network, and is responsible for access and mobility management policies, terminal (User Equipment, UE) policies, session management policies, and charging rules.
  • the configuration information of the operator generates access and mobility management policies, UE routing policies, quality of service (Quality of Service, QoS) rules and charging rules for user data transmission.
  • relevant parameters of the shared bandwidth can be pre-configured in the PCF, such as the shared aggregate maximum bit rate (Aggregate Maximum Bit Rate, AMBR) of the shared bandwidth.
  • AMBR Access Maximum Bit Rate
  • the PDU session to be configured in this embodiment is a newly created PDU session with no bandwidth rate resources allocated. After the PDU session is allocated with a bandwidth rate, it can enter the running state and does not involve the change of the bandwidth rate. , I won’t go into details later.
  • the technical solution of this embodiment uses determining that the PDU session to be configured belongs to the shared cluster as the trigger judgment.
  • the shared bandwidth of the shared cluster is allocated to the Configure the resources of the PDU session, so as to realize the allocation of shared bandwidth at the granularity of the shared cluster, so that the service package provided for the shared cluster can be more flexible, thereby improving user experience;
  • the PDU session to be configured does not belong to any shared cluster, it does not exist
  • the existing standard can only be used to allocate bandwidth resources at the session granularity, which is out of the scope of this embodiment and will not be described in detail later.
  • Step S120 determining the target bandwidth rate of the PDU session to be configured, and allocating the target bandwidth rate for the PDU session to be configured from the shared bandwidth.
  • the target bandwidth rate of a PDU session can be specified through the session creation request, or can be determined through the subscription information of the user for the session. For example, after each user accesses the network, the session subscription information will be established in the UDM, and the session subscription information The subscription information of the shared cluster is independent of each other, and the rate requirement of each session of the user can be stipulated in the session subscription information, such as setting the subscription session AMBR. This embodiment does not limit the determination method of the target bandwidth rate, and can Get the corresponding value.
  • the resources allocated to it should also belong to the shared bandwidth.
  • the first network element can be used to allocate the target PDU session to the PDU session to be configured in the shared bandwidth. Bandwidth rate, so as to realize the control of shared bandwidth.
  • the first network element can be PCF, SMF or UPF
  • the target bandwidth rate is allocated, it is also necessary to apply the target bandwidth rate to downstream entities, such as access and mobility management functions (Access and Mobility Management, AMF) and the base station, when the first network element has the target bandwidth rate, the target bandwidth rate can be carried in the interaction information to complete the transmission according to the configuration process in the existing standard.
  • AMF Access and Mobility Management
  • step S110 of the embodiment shown in FIG. 1 also includes but is not limited to the following steps:
  • Step S310 when obtaining the first session setup request sent by the SMF, create a PDU session to be configured, wherein the first session setup request carries user information and DNN;
  • Step S320 obtaining a preset allocation granularity, obtaining a cluster identifier from the UDR according to user information, DNN, and allocation granularity, and the allocation granularity characterizes the grouping rules of the shared cluster;
  • Step S330 determining the shared cluster corresponding to the cluster identifier as the target shared cluster.
  • the SMF is the core network control plane entity, which can maintain the PDU session, and according to the relevant protocol, the creation request of the PDU session is initiated by the SMF. Therefore, in order to realize the granular control of the shared cluster, the The DNN to which the PDU session belongs sends the first session creation request to the PCF.
  • the PCF can obtain the cluster ID from the shared bandwidth package signed in the UDR according to the DNN and user information. When the acquisition is successful, it can be determined that the PDU session to be configured belongs to the target shared bandwidth package.
  • Cluster the cluster ID can be a common GroupID.
  • the shared cluster can be DNN or user group
  • PCF and UDR can agree in advance whether the GroupID belongs to DNN granularity or user group granularity, and match the shared bandwidth package through allocation granularity, DNN, and user information, so as to benefit from multiple Determine the target shared cluster among the shared clusters.
  • first session creation requests may be arbitrary, and this embodiment does not limit the number of PDU sessions to be configured.
  • step S110 of the embodiment shown in FIG. 1 it also includes but is not limited to the following steps:
  • Step S410 obtain the pre-configured shared AMBR for the shared bandwidth
  • Step S420 determining the occupied bandwidth rate, which is the sum of the bandwidth rates of the PDU sessions in the running state in the target shared cluster;
  • Step S430 determining that the sum of the occupied bandwidth rate and the target bandwidth rate is less than or equal to the shared AMBR.
  • PCF can use the cluster ID as the query basis to obtain the shared AMBR from the pre-configured shared bandwidth parameters.
  • the shared AMBR is the maximum value that the shared bandwidth rate can achieve, and can be configured according to the subscription information of the shared bandwidth package , those skilled in the art are familiar with how to configure the parameters of the shared bandwidth in the PCF.
  • the shared AMBR is the maximum value that the shared bandwidth rate can achieve.
  • the PDU sessions belonging to the same shared cluster are known, so the occupied bandwidth rate can be determined first according to the target shared cluster, and when the sum of the occupied bandwidth rate and the target bandwidth rate is less than Or in the case of sharing AMBR, perform subsequent allocation to ensure that the PDU session to be configured can be allocated to the target bandwidth rate.
  • PCF can suspend the PDU session to be configured and refuse to create a new PDU session. Until a PDU session goes offline, configure the PDU session to be configured according to the free bandwidth rate to realize shared bandwidth allocation at the granularity of the shared cluster. Considering the occupancy of the shared bandwidth, the above judgment cannot be realized, resulting in that the PDU session to be configured cannot be correctly configured.
  • step S120 of the embodiment shown in FIG. 1 also includes but is not limited to the following steps:
  • Step S510 generating a first sharing policy with a target bandwidth rate
  • Step S520 sending the first sharing policy to the SMF, so that the SMF allocates the target bandwidth rate to the PDU session to be configured in the shared bandwidth according to the target bandwidth rate.
  • the PCF is mainly responsible for formulating policies
  • the first sharing policy can be added to the returned response, and the determined target bandwidth rate can be determined through the first sharing policy Send it to SMF, for example, use the Sessionrule in the response returned by PCF to assign the target bandwidth rate to the authSessAmbr of Sessionrule, so that SMF can obtain the target bandwidth rate and directly apply the target bandwidth rate for subsequent configuration.
  • the SMF configures the PDU session to be configured according to the target bandwidth rate.
  • the SMF can establish a session with the UPF through the N4 port, thereby deploying the target bandwidth rate to the UPF, and then sending Those skilled in the art are familiar with how to implement the above-mentioned transfer method to the involved base stations, and transfer to the AMF through the N1N2TRANSFER message, and this embodiment will not repeat it here.
  • the cluster identifier is GroupID as an example
  • the first session establishment request is PDU
  • the session establishment request is taken as an example. Referring to FIG. 6, the first example includes but is not limited to the following steps:
  • Step S601 SMF initiates a PDU session establishment request to PCF, carrying user information, DNN and subscription session AMBR obtained from UDM;
  • Step S602 the PCF obtains the package GroupID of the user's subscription shared bandwidth from the UDR;
  • the PCF finds out the shared bandwidth rate AMBR pre-configured in the PCF according to the GroupID, and allocates the target bandwidth rate for the created user session according to the subscription session AMBR and the shared bandwidth rate AMBR, wherein the target bandwidth rate is the subscription session AMBR or is determined by The AMBR rate defined by PCF is smaller than the AMBR rate of the subscription session;
  • step S604 the PCF returns a response, wherein the Sessionrule carried in the response includes authSessAmbr, and the value of authSessAmbr is the target bandwidth rate;
  • Step S605 the SMF establishes an N4 session establishment request to the UPF, and carries a target bandwidth rate
  • Step S606 UPF returns N4 session establishment response to SMF;
  • Step S607 the SMF sends the target bandwidth rate to the base station
  • Step S608 the SMF carries the target bandwidth rate in the N1N2TRANSFER message
  • step S609 the AMF returns a N1N2TRANSFER response to the SMF to complete the configuration.
  • the first network element is an SMF
  • the SMF is connected to the PCF in communication
  • the PCF is connected to the UDR in communication.
  • Step S710 generating a first session establishment request, wherein the first session establishment request carries user information and DNN;
  • Step S720 sending the first session establishment request to the PCF, so that the PCF creates a PDU session to be configured;
  • Step S730 obtain the second sharing strategy delivered by the PCF, the second sharing strategy carries a sharing identifier, wherein the sharing identifier is generated by the PCF according to the cluster identifier, and the cluster identifier is obtained from the UDR by the PCF according to the user information, the DNN and the obtained allocation granularity Obtain, the PDU sessions belonging to the same shared cluster carry the same shared identifier, and the allocation granularity represents the grouping rules of the shared cluster;
  • Step S740 determine the target sharing cluster to which the PDU session to be configured belongs according to the sharing identifier.
  • the target bandwidth rate is calculated by the PCF and sent directly to the SMF for subsequent configuration.
  • the SMF is used as the first network element.
  • the target bandwidth rate is calculated and allocated through SMF. Therefore, the target bandwidth rate carried by the first sharing policy is a calculated value and can be directly applied by SMF, while the second sharing policy carries a sharing identifier, which can inform SMF of the target bandwidth rate to be used. Configuring a PDU session requires resource allocation for shared bandwidth.
  • PCF can obtain the GroupID for the entire DNN from the UDR after obtaining the DNN, and perform subsequent operations.
  • the request carries identifiers representing user groups, such as Subscription Permanent Identifier (SUPI), Generic Public Subscription Identifier (GPSI), etc., so that PCF can obtain user group IDs from UDR based on SUPI, GPSI and other information.
  • SUPI Subscription Permanent Identifier
  • GPSI Generic Public Subscription Identifier
  • GroupID the specific granularity is adjusted according to actual needs, and it only needs to reflect the granularity of the shared cluster.
  • the PCF can be used to add a shared identifier for the PDU session to be configured, so that the SMF can determine the PDU session belonging to the same target shared cluster according to the shared identifier.
  • the resources in the shared bandwidth can obtain the identifier corresponding to the GroupID, form a sharingkey field as the sharing identifier, add it to the second sharing policy and send it to the SMF, and when the SMF obtains the sharingkey field, it can be determined that the PDU session needs to be configured Allocate resources in the shared bandwidth.
  • the second sharing policy also carries a shared AMBR, and the shared AMBR is obtained by the PCF according to the cluster identifier. Referring to FIG. 8 , before performing step S120 of the embodiment shown in FIG. The following steps:
  • Step S810 determining the occupied bandwidth rate, which is the sum of the bandwidth rates of the PDU sessions in the running state in the target shared cluster;
  • Step S820 determining that the sum of the occupied bandwidth rate and the target bandwidth rate is less than or equal to the shared AMBR.
  • the target bandwidth rate carried by the first sharing policy has been verified to be feasible, but the second sharing policy does not directly carry the target bandwidth rate. Therefore, in order to enable the SMF to provide The target bandwidth rate can be allocated within the resource range, and the shared AMBR can be carried through the second sharing policy, and the SMF can identify the PDU sessions of the same shared cluster when the SMF has a shared ID. Therefore, after the SMF obtains the shared AMBR and determines the target shared After clustering, the occupied bandwidth rate can be calculated to determine that the sum of the occupied bandwidth rate and the target bandwidth rate is less than or equal to the shared AMBR.
  • the configuration of the PDU session will not be performed to ensure that after the bandwidth rate allocation of the PDU session to be configured is completed, the target The sum of the bandwidth rates of all PDU sessions in the shared cluster does not exceed the shared AMBR to ensure the normal operation of the PDU sessions.
  • the target bandwidth rate after determining the target bandwidth rate, before sending it to the UPF, calculate the sum of the bandwidth rates of all PDU sessions in the shared cluster. If the shared AMBR is exceeded, the PDU session to be configured will be suspended and the running PDU will be waited. After the session goes offline, reconfigure it with free and sufficient bandwidth resources to ensure that the PDU session is allocated enough available resources.
  • FIG. 9 is a flow chart of Example 2.
  • the grouping granularity is DNN
  • the cluster identifier is GroupID as an example
  • the first session establishment request is a PDU session establishment request as an example
  • the second session establishment request is N4
  • the session establishment request is taken as an example
  • the sharing key is taken as an example of the sharingkey identification field.
  • Example 2 includes but is not limited to the following steps:
  • Step S901 SMF initiates a session establishment request to PCF, carrying user information, DNN and subscription session AMBR obtained from UDM;
  • Step S902 the PCF obtains the package GroupID of the user's subscription shared bandwidth from the UDR;
  • Step S903 the PCF finds out the shared bandwidth rate AMBR pre-configured in the PCF according to the GroupID, combines the DNN and UDR subscription package information reported by the SMF, and decides to issue a shared bandwidth policy for the user under the DNN;
  • Step S904 the PCF returns a response containing the shared bandwidth policy, including the sum of the shared bandwidth rate and the sharingkey identification field;
  • Step S905 based on the shared bandwidth policy issued by the PCF, the SMF allocates a target bandwidth rate for the created user session according to the subscription session AMBR and the shared bandwidth rate AMBR, wherein the target bandwidth rate is the subscription session AMBR or is defined by the PCF and is less than the contracted rate.
  • AMBR rate of session AMBR based on the shared bandwidth policy issued by the PCF, the SMF allocates a target bandwidth rate for the created user session according to the subscription session AMBR and the shared bandwidth rate AMBR, wherein the target bandwidth rate is the subscription session AMBR or is defined by the PCF and is less than the contracted rate.
  • Step S906 the SMF establishes an N4 session establishment request to the UPF, and carries a target bandwidth rate
  • Step S907 the UPF returns an N4 session establishment response to the SMF;
  • Step S908 the UPF executes the shared bandwidth delivered by the SMF, and the SMF sends the target bandwidth rate to the base station;
  • Step S909 the SMF sends the target bandwidth rate to the AMF in the N1N2TRANSFER message
  • step S910 the AMF returns an N1N2TRANSFER response to the SMF to complete the configuration.
  • Figure 10 is a flow chart of Example 3.
  • the grouping granularity is user group
  • the cluster identifier is GroupID as an example
  • the first session establishment request is a PDU session establishment request as an example
  • the sharing identifier is a sharingkey identification field
  • the second session establishment request takes the N4 session establishment request as an example.
  • Example 3 includes but is not limited to the following steps:
  • Step S1001 SMF initiates a session establishment request to PCF, carrying user information, DNN and subscription session AMBR obtained from UDM;
  • Step S1002 PCF obtains the package GroupID of the user's subscription shared bandwidth from the UDR;
  • Step S1003 the PCF inquires the shared bandwidth rate AMBR pre-configured in the PCF according to the GroupID, combines the user SUPI, GPSI and other information reported by the SMF and the UDR subscription package information, and decides to issue a shared bandwidth policy for the user under the DNN;
  • Step S1004 the PCF returns a response containing the shared bandwidth policy, including the sum of the shared bandwidth rate and the sharingkey identification field;
  • Step S1005 based on the shared bandwidth policy issued by the PCF, the SMF allocates the target bandwidth rate for the created user session according to the subscription session AMBR and the shared bandwidth rate AMBR, wherein the target bandwidth rate is the subscription session AMBR or is defined by the PCF and is less than the contracted rate.
  • AMBR rate of session AMBR based on the shared bandwidth policy issued by the PCF, the SMF allocates the target bandwidth rate for the created user session according to the subscription session AMBR and the shared bandwidth rate AMBR, wherein the target bandwidth rate is the subscription session AMBR or is defined by the PCF and is less than the contracted rate.
  • Step S1006 the SMF establishes an N4 session establishment request to the UPF, and carries a target bandwidth rate
  • Step S1007 UPF returns N4 session establishment response to SMF;
  • Step S1008 the UPF executes the shared bandwidth delivered by the SMF, and the SMF sends the target bandwidth rate to the base station;
  • Step S1009 the SMF sends the target bandwidth rate to the AMF in the N1N2TRANSFER message
  • step S1010 the AMF returns an N1N2TRANSFER response to the SMF to complete the configuration.
  • the first network element is UPF
  • UPF is connected to SMF in communication
  • SMF is connected to PCF in communication
  • PCF is connected to UDR in communication
  • PCF is connected to UDR in communication
  • Step S110 also includes but is not limited to the following steps:
  • Step S1110 obtain the second session establishment request sent by the SMF, wherein the second session establishment request carries a second sharing policy, the second sharing policy carries a sharing identifier, the sharing identifier is generated by the PCF according to the cluster identifier, and the cluster identifier is generated by the PCF according to User information, DNN, and the obtained allocation granularity are obtained from UDR.
  • PDU sessions belonging to the same shared cluster carry the same shared identifier, and the allocated granularity represents the grouping rules of the shared cluster.
  • User information and DNN are obtained by SMF and passed through the first session
  • the establishment request is sent to the PCF, and the second sharing policy is generated and sent to the SMF by the PCF under the condition that the PDU session to be configured is created according to the first session creation request;
  • Step S1120 determine the target sharing cluster to which the PDU session to be configured belongs according to the sharing identifier.
  • the PCF in order to use the UPF as the first network element to allocate the target bandwidth rate, after the PCF obtains the cluster ID and the shared ID, it can be passed to the UPF through the SMF.
  • the definition, selection and acquisition method of the shared ID and the cluster ID Reference may be made to the description of the foregoing embodiments, and details are not repeated here for the sake of brevity.
  • the SMF can send the second session establishment request to the UPF through the N4 interface, thereby carrying the second sharing policy, so that the UPF can know that it needs to share the bandwidth for the PDU session to be configured.
  • the principle and manner of generating the second sharing policy may refer to the description of the embodiment shown in FIG. 7 , and details are not repeated here.
  • the SMF after the SMF obtains the second sharing policy, it obtains the sharing identifier and allocates the shared bandwidth.
  • the SMF recognizes that the second sharing policy carries After having the sharing identifier, the parameters related to the shared bandwidth can be obtained, and added to the second session establishment request and sent to the UPF, so that the UPF can calculate and allocate the target bandwidth rate, thereby realizing the control of the shared bandwidth through the UPF.
  • the second sharing policy also carries a shared AMBR, and the shared AMBR is obtained by the PCF according to the cluster identifier. Referring to FIG. 12 , before performing step S120 of the embodiment shown in FIG. The following steps:
  • Step S1210 determining the occupied bandwidth rate, which is the sum of the bandwidth rates of the PDU sessions in the running state in the target shared cluster;
  • Step S1220 determining that the sum of the occupied bandwidth rate and the target bandwidth rate is less than or equal to the shared AMBR.
  • Example 4 includes but is not limited to the following steps:
  • Step S1301 SMF initiates a session establishment request to PCF, carrying user information and DNN;
  • Step S1302 PCF obtains the package GroupID of the user's subscription shared bandwidth from the UDR;
  • step S1303 the PCF inquires the shared bandwidth rate AMBR pre-configured in the PCF according to the GroupID, combines the DNN and UDR subscription package information reported by the SMF, and decides to issue a shared bandwidth policy for the user;
  • Step S1304 the PCF returns a response containing the shared bandwidth policy, including the sum of the shared bandwidth rate and the sharingkey identification field;
  • Step S1305 the SMF sends the shared bandwidth parameter to the UPF
  • Step S1306 the SMF establishes an N4 session establishment request to the UPF, and carries the subscription session AMBR, shared bandwidth rate AMBR and sharingkey identification fields;
  • Step S1307 UPF returns N4 session establishment response to SMF;
  • step S1308 the UPF allocates a target bandwidth rate for the created user session according to the AMBR of the subscription session and the shared bandwidth rate AMBR, wherein the target bandwidth rate is the AMBR of the subscription session or an AMBR rate defined by the PCF that is lower than the AMBR of the subscription session.
  • step S110 of the embodiment shown in FIG. 1 also includes but is not limited to the following steps:
  • Step S1410 obtain the subscription session AMBR for the PDU session
  • Step S1420 determine the subscription session AMBR as the target bandwidth rate, or determine the target bandwidth rate according to the subscription session AMBR and a preset ratio, wherein the preset ratio is a positive number less than 1.
  • the PCF can obtain the shared bandwidth subscription information from the UDR according to DNN or SUPI information, thereby determining the shared AMBR for the shared bandwidth, and the shared AMBR is for the entire shared bandwidth.
  • the PDU session configures the bandwidth rate. After the user accesses the network, the AMBR of the PDU session is signed, and the subscription information is saved in the UDM.
  • the session subscription information can be obtained directly from the UDM, thereby obtaining the subscription session AMBR; when the first network element is a PCF, the SMF can obtain the subscription session AMBR from the UDM, and through the first A session establishment request is sent to the PCF; when the first network element is a UPF, the SMF can obtain the subscription session AMBR from the UDM, and send it to the UPF through the second session establishment request.
  • the subscription session AMBR is the maximum rate that the user's PDU session can achieve.
  • the subscription session AMBR can be used as the target bandwidth rate to make the allocated resources more sufficient.
  • the same user has multiple PDU sessions in the target shared cluster, or the target shared cluster can also pre-configure a preset ratio of less than 1 in the first network element in order to provide resources for more PDU sessions , the product of the preset ratio and the AMBR of the subscription session is used as the target bandwidth rate, and the specific calculation method can be selected according to actual needs.
  • step S110 of the embodiment shown in FIG. 1 after executing step S110 of the embodiment shown in FIG. 1 , it also includes but is not limited to the following steps:
  • Step S1510 when it is detected that the running PDU session in the target shared cluster is offline, re-determine the occupied bandwidth rate.
  • the sum of the bandwidth rates of all PDU sessions in the same shared cluster cannot exceed the shared AMBR, otherwise the PDU session to be configured will be suspended and new PDU sessions will be stopped.
  • the PDU session in the running state is offline, there are certain resources idle.
  • the occupied bandwidth rate can be re-determined.
  • the resource allocation process of the PDU session to be configured can be re-executed to ensure The resources of the shared bandwidth are fully utilized.
  • the network element 1600 includes: a memory 1610 , a processor 1620 , and a computer program stored in the memory 1610 and operable on the processor 1620 .
  • the processor 1620 and the memory 1610 may be connected through a bus or in other ways.
  • the non-transitory software programs and instructions required to implement the resource allocation method of the above embodiments are stored in the memory 1610, and when executed by the processor 1620, the resource allocation method applied to the network element in the above embodiments is executed, for example, executing Method step S110 to step S120 in Fig. 1 described above, method step S310 to step S330 in Fig. 3, method step S410 to step S430 in Fig. 4, method step S510 to step S520 in Fig. 5, in Fig. 6 method step S601 to step S609, method step S710 to step S740 in Fig. 7, method step S810 to step S820 in Fig. 8, method step S901 to step S910 in Fig. 9, method step S1001 to step in Fig.
  • the device embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place, or they may be distributed to multiple network units. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • an embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are executed by a processor or a controller, for example, by the above-mentioned Execution by a processor in the network element embodiment can cause the above-mentioned processor to execute the resource allocation method applied to the network element in the above-mentioned embodiment, for example, execute the method steps S110 to S120 in FIG. 1 described above, and FIG. 3 Method step S310 to step S330 in the method, method step S410 to step S430 in Fig. 4, method step S510 to step S520 in Fig. 5, method step S601 to step S609 in Fig. 6, method step S710 in Fig.
  • step S810 to step S820 in FIG. 8 method step S901 to step S910 in FIG. 9, method step S1001 to step S1010 in FIG. 10, method step S1110 to step S1120 in FIG. method step S1210 to step S1220, the method step S1301 to step S1308 in FIG. 13 , the method step S1410 to step S1420 in FIG. 14 , and the method step S1510 in FIG. 15 .
  • Those skilled in the art can understand that all or some of the steps and systems in the methods disclosed above can be implemented as software, firmware, hardware and an appropriate combination thereof.
  • Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit .
  • a processor such as a central processing unit, digital signal processor, or microprocessor
  • Such software may reside on computer readable media, respectively, which may include computer storage media (or non-transitory media) and communication media (or transitory media).
  • computer storage media includes both volatile and nonvolatile media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. permanent, removable and non-removable media.
  • Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, tape, magnetic disk storage or other magnetic storage devices, or can Any other medium used to store desired information and which can be accessed by a computer.
  • communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media .
  • This embodiment of the present application includes: determining the target shared cluster to which the PDU session to be configured belongs, wherein the PDU session to be configured is a PDU session with a bandwidth rate to be allocated, and the target shared cluster is pre-configured with shared bandwidth; Configuring the target bandwidth rate of the PDU session, and allocating the target bandwidth rate for the PDU session to be configured from the shared bandwidth.
  • the bandwidth rate can be allocated for the PDU session to be configured from the shared bandwidth, resource allocation is realized at the granularity of the shared cluster, allocation control of the shared bandwidth is realized, and the flexibility of bandwidth configuration is improved.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提供了一种资源分配方法、网元、存储介质，资源分配方法包括：确定待配置PDU会话所归属的目标共享集群，其中，所述待配置PDU会话为待分配带宽速率的PDU会话，所述目标共享集群预先配置有共享带宽（S110）；确定所述待配置PDU会话的目标带宽速率，从所述共享带宽中为所述待配置PDU会话分配所述目标带宽速率（S120）。

Description

资源分配方法、网元、存储介质
相关申请的交叉引用
本申请基于申请号为202111265912.8、申请日为2021年10月28日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及但不限于通信领域，尤其涉及一种资源分配方法、网元、存储介质。
背景技术
在目前的第五代通信技术(5th Generation，5G)场景下，随着通信业务的多样化，各运营商推出了共享带宽业务，以多个用户组成的用户组或者数据网络名称(Data Network Name，DNN)作为共享集群，并且针对共享集群预先分配好共享带宽，由共享集群内的所有用户共享。
根据相关标准的规定，用户在创建协议数据单元(Protocol Data Unit，PDU)会话之后，策略控制功能(Policy Control Functionality，PCF)会针对PDU会话下发会话管理策略，基于会话粒度为每个PDU会话进行带宽速率的分配，并不能针对共享带宽进行分配控制。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本申请实施例提供了一种资源分配方法、网元、存储介质。
第一方面，本申请实施例提供了一种资源分配方法，应用于第一网元，所述方法包括：确定待配置PDU会话所归属的目标共享集群，其中，所述待配置PDU会话为待分配带宽速率的PDU会话，所述目标共享集群预先配置有共享带宽；确定所述待配置PDU会话的目标带宽速率，从所述共享带宽中为所述待配置PDU会话分配所述目标带宽速率。
第二方面，本申请实施例提供了一种网元，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现如第一方面所述的资源分配方法。
第三方面，本申请实施例提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行如第一方面所述的资源分配方法。
本申请的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本申请而了解。本申请的目的和其他优点可通过在说明书、权利要求书以及附图中所特别指出的结构来实现和获得。
附图说明
附图用来提供对本申请技术方案的进一步理解，并且构成说明书的一部分，与本申请的实施例一起用于解释本申请的技术方案，并不构成对本申请技术方案的限制。
图1是本申请一个实施例提供的应用于网元的资源分配方法的流程图；
图2是现有的策略控制和计费(Policy Control and Charging，PCC)的架构图；
图3是本申请另一个实施例提供的确定目标共享集群的流程图；
图4是本申请另一个实施例提供的确定共享带宽可分配的流程图；
图5是本申请另一个实施例提供的下发第一共享策略的流程图；
图6是本申请另一个实施例提供的示例一的流程图；
图7是本申请另一个实施例提供的确定目标共享集群的流程图；
图8是本申请另一个实施例提供的确定共享带宽可分配的流程图；
图9是本申请另一个实施例提供的示例二的流程图；
图10是本申请另一个实施例提供的示例三的流程图；
图11是本申请另一个实施例提供的确定目标共享集群的流程图；
图12是本申请另一个实施例提供的确定共享带宽可分配的流程图；
图13是本申请另一个实施例提供的示例四的流程图；
图14是本申请另一个实施例提供的确定目标带宽速率的流程图；
图15是本申请另一个实施例提供的更新已占用带宽速率的流程图；
图16是本申请另一个实施例提供的网元的装置图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅用以解释本申请，并不用于限定本申请。
需要说明的是，虽然在装置示意图中进行了功能模块划分，在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于装置中的模块划分，或流程图中的顺序执行所示出或描述的步骤。说明书、权利要求书或上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
本申请提供了一种资源分配方法、网元、存储介质，资源分配方法包括：确定待配置PDU会话所归属的目标共享集群，其中，所述待配置PDU会话为待分配带宽速率的PDU会话，所述目标共享集群预先配置有共享带宽；确定所述待配置PDU会话的目标带宽速率，从所述共享带宽中为所述待配置PDU会话分配所述目标带宽速率。根据本实施例的技术方案，能够从共享带宽中为待配置PDU会话分配带宽速率，实现了以共享集群为粒度进行资源分配，实现了共享带宽的分配控制，提高了带宽配置的灵活性。
下面结合附图，对本申请实施例作进一步阐述。
如图1所示，图1是本申请一个实施例提供的一种资源分配方法的流程图，该资源分配方法应用于第一网元，包括但不限于有步骤S110和步骤S120。
步骤S110，确定待配置PDU会话所归属的目标共享集群，其中，待配置PDU会话为待分配带宽速率的PDU会话，目标共享集群预先配置有共享带宽。
需要说明的是，共享集群可以是DNN，也可以是由多个用户组成的用户组，本实施例对共享集群的具体形式不多作限定，能够基于用户定义路径(User Defined Routing，UDR)进行套餐签约，从而实现共享带宽即可。可以理解的是，统一数据管理功能(Unified Data Management，UDM)为核心网控制面实体，归属用户服务器，能够永久存储用户签约数据，基于此，在针对群共享带宽进行签约之后，本领域技术人员熟知如何从UDM获取签约信息，在此不多作赘述。
需要说明的是，本实施例的技术方案可以基于图2所示的PCC架构实现，图2所示的PCC架构为现有架构，本实施例并不涉及对具体架构的改进，仅涉及资源分配方法的改进， 后续不多作赘述。
值得注意的是，第一网元可以是图2所示的架构中的PCF、会话管理功能(Session Management Function，SMF)或者用户面功能(User Plane Function，UPF)，能够在PDU会话的资源分配过程中进行共享带宽的计算和分配即可，本领域技术人员可以根据实际需求选取具体的实体作为第一网元，在此不多作限定。
需要说明的是，PCF是核心网控制面实体，负责接入和移动性管理策略、终端(User Equipment，UE)策略、会话管理策略和计费规则的功能实体，能够根据业务信息和用户签约信息、运营商的配置信息产生接入和移动性管理策略、UE路由选择策略、用户数据传递的服务质量(Quality of Service，QoS)规则和计费规则。基于此，在通过签约确定共享集群后，可以在PCF预先配置好共享带宽的相关参数，例如共享带宽的共享总计最大比特率(Aggregate Maximum Bit Rate，AMBR)，本领域技术人员熟知如何进行共享带宽的参数配置，在此不多作赘述。
需要说明的是，本实施例中的待配置PDU会话为新创建且未分配带宽速率资源的PDU会话，当PDU会话被分配到带宽速率之后，则可以进入运行状态，并不涉及带宽速率的变更，后续不多作赘述。
值得注意的是，本实施例的技术方案以确定待配置PDU会话归属于共享集群作为触发判断，当确定待配置PDU会话归属于某个共享集群，从该共享集群的共享带宽中分配归属于待配置PDU会话的资源，从而实现以共享集群为粒度进行共享带宽的分配，使得针对共享集群提供的业务套餐能够更加灵活，从而提高用户体验；若待配置PDU会话不属于任何共享集群，则不存在共享集群粒度，只能采用现有标准以会话粒度进行带宽资源的分配，这种情况不在本实施例讨论范围，后续不重复赘述。
步骤S120，确定待配置PDU会话的目标带宽速率，从共享带宽中为待配置PDU会话分配目标带宽速率。
需要说明的是，PDU会话的目标带宽速率可以通过会话创建请求指定，也可以通过用户针对会话的签约信息确定，例如每个用户接入网络后，会在UDM中建立会话签约信息，会话签约信息与共享集群的签约信息是相互独立的，可以在会话签约信息中约定该用户每个会话的速率需求，例如设定签约会话AMBR，本实施例对目标带宽速率的确定方式不多作限定，能够获取到对应的数值即可。
需要说明的是，由于待配置PDU会话归属于目标共享集群，因此为其分配的资源也应该归属于共享带宽，基于此，可以通过第一网元在共享带宽中，为待配置PDU会话分配目标带宽速率，从而实现共享带宽的控制。
需要说明的是，由于第一网元可以是PCF、SMF或者UPF，因此，在分配到目标带宽速率之后，还需要将目标带宽速率应用至下游实体，例如接入和移动管理功能(Access and Mobility Management，AMF)和基站，在第一网元具备目标带宽速率的情况下，可以按照现有标准中的配置流程，在交互信息中携带目标带宽速率完成传递，本领域技术人员熟知如何传递参数，在此不多作赘述。
另外，在一实施例中，第一网元为PCF，PCF分别与SMF和UDR通信连接，参照图3，图1所示实施例的步骤S110，还包括但不限于有以下步骤：
步骤S310，当获取到SMF发送的第一会话建立请求，创建待配置PDU会话，其中，第 一会话建立请求携带有用户信息和DNN；
步骤S320，获取预设的分配粒度，根据用户信息、DNN和分配粒度从UDR中获取集群标识，分配粒度表征共享集群的分组规则；
步骤S330，将集群标识所对应的共享集群确定为目标共享集群。
本领域技术人员可以理解的是，SMF是核心网控制面实体，可以对PDU会话进行维护，并且根据相关协议，PDU会话的创建请求由SMF发起，因此，为了实现共享集群粒度的控制，可以将PDU会话所属的DNN通过第一会话创建请求发送至PCF，PCF可以根据DNN和用户信息从UDR中签约的共享带宽套餐获取集群标识，当获取成功，则可以确定该待配置PDU会话归属于目标共享集群，集群标识可以是常见的GroupID。
需要说明的是，由于共享集群可以是DNN或者用户组，因此PCF和UDR之间可以预先约定GroupID属于DNN粒度还是用户组粒度，通过分配粒度、DNN和用户信息匹配出共享带宽套餐，从而从多个共享集群中确定目标共享集群。
需要说明的是，第一会话创建请求的数量可以是任意，本实施例对待配置PDU会话的数量不作限定。
另外，在一实施例中，参照图4，在执行图1所示实施例的步骤S110之前，还包括但不限于有以下步骤：
步骤S410，根据集群标识，获取针对共享带宽预先配置好的共享AMBR；
步骤S420，确定已占用带宽速率，已占用带宽速率为目标共享集群中处于运行状态的PDU会话的带宽速率之和；
步骤S430，确定已占用带宽速率与目标带宽速率之和小于或等于共享AMBR。
需要说明的是，PCF可以以集群标识作为查询依据，从预先配置好的共享带宽参数中获取共享AMBR，该共享AMBR为共享带宽速率能够达到的最大值，可以根据共享带宽套餐的签约信息进行配置，本领域技术人员熟知如何在PCF中配置共享带宽的参数。
需要说明的是，由于共享集群中的所有PDU会话共享该共享带宽，共享AMBR为共享带宽速率能够达到的最大值，在为待配置PDU会话分配共享带宽速率之前，需要确定当前剩余的资源是否足够，因此，而对于PCF而言，归属于同一个共享集群的PDU会话是可知的，因此可以根据目标共享集群中可以先确定已占用带宽速率，并在已占用带宽速率与目标带宽速率之和小于或等于共享AMBR的情况下进行后续分配，确保待配置PDU会话能够被分配到目标带宽速率。当然，也可以直接为待配置PDU会话配置目标带宽速率，并且在配置之后通过PCF确定目标共享集群中的已占用带宽速率，若已占用带宽速率超出共享AMBR，将待配置PDU会话设置为下线状态。
值得注意的是，当确定的已占用带宽速率等于共享AMBR，则说明共享带宽的资源已经全部被分配，在这种情况下，PCF可以挂起待配置PDU会话，并且拒绝创建新的PDU会话，直至有PDU会话下线，再根据空闲出来的带宽速率进行待配置PDU会话的配置，实现共享集群粒度的共享带宽分配，若以PDU会话为粒度进行分配，待配置PDU会话的资源配置并不会考虑共享带宽的占用情况，则无法实现上述判断，从而导致待配置PDU会话无法被正确配置。
另外，在一实施例中，SMF与UPF通信连接，参照图5，图1所示实施例的步骤S120，还包括但不限于有以下步骤：
步骤S510，生成携带有目标带宽速率的第一共享策略；
步骤S520，将第一共享策略下发至SMF，以使SMF根据目标带宽速率在共享带宽中为待配置PDU会话分配目标带宽速率。
需要说明的是，由于PCF主要负责制定策略，因此可以在获取到SMF发送的第一会话建立请求后，在返回的响应中添加第一共享策略，通过第一共享策略将确定好的目标带宽速率下发至SMF，例如利用PCF返回的响应中的Sessionrule，将目标带宽速率赋值于Sessionrule的authSessAmbr，使得SMF能够获取目标带宽速率，并直接应用目标带宽速率进行后续配置。
需要说明的是，SMF根据目标带宽速率对待配置PDU会话进行配置，以图2中所示的PCC架构为例，SMF可以通过N4端口与UPF建立会话，从而将目标带宽速率部署至UPF，再发送至涉及的基站，并且通过N1N2TRANSFER消息传递至AMF，本领域技术人员熟知如何实现上述传递方式，本实施例对此不多作赘述。
另外，为了更好地体现本申请在第一网元为PCF的前提下的技术方案，以下提出示例一进行解释说明，在该示例中，集群标识以GroupID为例，第一会话建立请求以PDU会话建立请求为例，参照图6，该示例一包括但不限于有以下步骤：
步骤S601，SMF向PCF发起PDU会话建立请求，携带用户信息、DNN和从UDM获取的签约会话AMBR；
步骤S602，PCF到UDR中获取用户签约共享带宽的套餐GroupID；
步骤S603，PCF依据GroupID查询到在PCF预先配置好的共享带宽速率AMBR，根据签约会话AMBR和共享带宽速率AMBR，为创建的用户会话分配目标带宽速率，其中，目标带宽速率为签约会话AMBR或者由PCF自定义的小于签约会话AMBR的AMBR速率；
步骤S604，PCF返回响应，其中，响应携带的Sessionrule包含authSessAmbr，authSessAmbr的取值为目标带宽速率；
步骤S605，SMF向UPF建立N4会话建立请求，并且携带有目标带宽速率；
步骤S606，UPF向SMF返回N4会话建立响应；
步骤S607，SMF下发目标带宽速率给基站；
步骤S608，SMF在N1N2TRANSFER消息中携带目标带宽速率；
步骤S609，AMF向SMF返回N1N2TRANSFER响应，完成配置。
另外，在一实施例中，第一网元为SMF，SMF与PCF通信连接，PCF与UDR通信连接，参照图7，在执行图1所示实施例的步骤S110之前，还包括但不限于有以下步骤：
步骤S710，生成第一会话建立请求，其中，第一会话建立请求携带有用户信息和DNN；
步骤S720，将第一会话建立请求发送至PCF，以使PCF创建待配置PDU会话；
步骤S730，获取PCF下发的第二共享策略，第二共享策略携带有共享标识，其中，共享标识由PCF根据集群标识生成，集群标识由PCF根据用户信息、DNN和获取到的分配粒度从UDR获取，归属于同一共享集群的PDU会话携带有相同的共享标识，分配粒度表征共享集群的分组规则；
步骤S740，根据共享标识确定待配置PDU会话所归属的目标共享集群。
需要说明的是，PCF创建PDU会话的方式以及获取集群标识的方法可以参考图3所示实施例的描述，为了叙述简便在此不重复赘述。
需要说明的是，在上述第一网元为PCF的实施例中，目标带宽速率是由PCF计算出并且 直接下发至SMF进行后续配置，而本实施例以SMF作为第一网元，则需要通过SMF进行目标带宽速率的计算和分配，因此，第一共享策略携带的目标带宽速率是计算好的数值，可以由SMF直接应用，而第二共享策略携带的是共享标识，可以告知SMF该待配置PDU会话需要进行共享带宽的资源分配。
值得注意的是，为了体现不同的分配粒度，在DNN粒度下，PCF可以在获取到DNN之后从UDR获取针对整个DNN的GroupID，并执行后续操作，在用户组粒度下，可以在第一会话建立请求中携带表征用户组的标识，例如用户永久标识符(Subscription Permanent Identifier，SUPI)、通用公共用户标识(Generic Public Subscription Identifier，GPSI)等，使得PCF根据SUPI、GPSI等信息从UDR获取用户组的GroupID，具体的粒度根据实际需求调整，能够体现共享集群粒度即可。
例如，参考上述实施例的描述，在计算目标带宽速率之前，需要确定待配置PDU会话所归属的目标共享集群，这对于PCF是可以直接确定的，但是SMF主要负责会话管理，并不能对共享集群进行管控，因此，可以通过PCF为待配置PDU会话添加共享标识，使得SMF能够根据共享标识确定归属于同一目标共享集群的PDU会话，例如，PCF在获取到GroupID之后，确定需要对待配置PDU会话分配共享带宽中的资源，可以获取与该GroupID相对应的标识，形成一个sharingkey字段作为共享标识，添加到第二共享策略下发至SMF，当SMF获取到sharingkey字段，则可以确定需要对待配置PDU会话分配共享带宽中的资源。
值得注意的是，为了区分不同的共享集群，可以为每个GroupID设置唯一对应的sharingkey字段的值，以使SMF在获取到sharingkey字段之后，根据取值相同的原则确定归属于同一个共享集群的PDU会话，从而确定目标共享集群，实现基于共享集群粒度的共享带宽控制。
另外，在一实施例中，第二共享策略还携带有共享AMBR，共享AMBR由PCF根据集群标识获取，参照图8，在执行图1所示实施例的步骤S120之前，还包括但不限于有以下步骤：
步骤S810，确定已占用带宽速率，已占用带宽速率为目标共享集群中处于运行状态的PDU会话的带宽速率之和；
步骤S820，确定已占用带宽速率与目标带宽速率之和小于或等于共享AMBR。
需要说明的是，参考上述实施例的描述，第一共享策略所携带的目标带宽速率已经验证过可行，但是第二共享策略并不直接携带目标带宽速率，因此，为了使得SMF在共享带宽可提供的资源范围内分配目标带宽速率，可以通过第二共享策略携带共享AMBR，并且SMF具备共享标识的情况下能够识别出同一个共享集群的PDU会话，因此SMF在获取到共享AMBR，且确定目标共享集群之后，能够计算出已占用带宽速率，从而确定已占用带宽速率与目标带宽速率之和小于或等于共享AMBR，否则不进行PDU会话的配置，确保完成待配置PDU会话的带宽速率分配后，目标共享集群中的所有PDU会话的带宽速率之和不超出共享AMBR，确保PDU会话的正常运行。
当然，可以是确定目标带宽速率之后，在下发至UPF之前，针对标共享集群中的所有PDU会话的带宽速率进行求和计算，若超出共享AMBR则挂起待配置PDU会话，等待正在运行的PDU会话下线后，利用空闲出且足够的带宽资源进行重新配置，能够确保PDU会话分配到足够的可用资源即可。
另外，为了更好地说明本申请在第一网元为SMF的前提下的技术方案，以下提出示例二和示例三：
参照图9，图9为示例二的流程图，在本示例中，分组粒度为DNN，集群标识以GroupID为例，第一会话建立请求以PDU会话建立请求为例，第二会话建立请求以N4会话建立请求为例，共享标识以sharingkey标识字段为例，示例二包括但不限于有以下步骤：
步骤S901，SMF向PCF发起会话建立请求，携带用户信息、DNN和从UDM获取的签约会话AMBR；
步骤S902，PCF到UDR中获取用户签约共享带宽的套餐GroupID；
步骤S903，PCF依据GroupID查询到在PCF预先配置好的共享带宽速率AMBR，结合SMF上报的DNN和UDR签约套餐信息，决策为DNN下该用户下发共享带宽策略；
步骤S904，PCF返回包含共享带宽策略的响应，包含共享带宽速率总和以及sharingkey标识字段；
步骤S905，SMF基于PCF下发的共享带宽策略,根据签约会话AMBR和共享带宽速率AMBR，为创建的用户会话分配目标带宽速率，其中，目标带宽速率为签约会话AMBR或者由PCF自定义的小于签约会话AMBR的AMBR速率；
步骤S906，SMF向UPF建立N4会话建立请求，并且携带有目标带宽速率；
步骤S907，UPF向SMF返回N4会话建立响应；
步骤S908，UPF执行SMF下发的共享带宽，SMF将目标带宽速率下发至基站；
步骤S909，SMF在N1N2TRANSFER消息中，携带目标带宽速率给AMF；
步骤S910，AMF向SMF返回N1N2TRANSFER响应，完成配置。
参照图10，图10为示例三的流程图，在本示例中，分组粒度为用户组，集群标识以GroupID为例，第一会话建立请求以PDU会话建立请求为例，共享标识以sharingkey标识字段为例，第二会话建立请求以N4会话建立请求为例，示例三包括但不限于有以下步骤：
步骤S1001，SMF向PCF发起会话建立请求，携带用户信息、DNN和从UDM获取的签约会话AMBR；
步骤S1002，PCF到UDR中获取用户签约共享带宽的套餐GroupID；
步骤S1003，PCF依据GroupID查询到在PCF预先配置好的共享带宽速率AMBR，结合SMF上报的用户SUPI、GPSI等信息和UDR签约套餐信息，决策为DNN下该用户下发共享带宽策略；
步骤S1004，PCF返回包含共享带宽策略的响应，包含共享带宽速率总和以及sharingkey标识字段；
步骤S1005，SMF基于PCF下发的共享带宽策略,根据签约会话AMBR和共享带宽速率AMBR，为创建的用户会话分配目标带宽速率，其中，目标带宽速率为签约会话AMBR或者由PCF自定义的小于签约会话AMBR的AMBR速率；
步骤S1006，SMF向UPF建立N4会话建立请求，并且携带有目标带宽速率；
步骤S1007，UPF向SMF返回N4会话建立响应；
步骤S1008，UPF执行SMF下发的共享带宽，SMF将目标带宽速率下发至基站；
步骤S1009，SMF在N1N2TRANSFER消息中，携带目标带宽速率给AMF；
步骤S1010，AMF向SMF返回N1N2TRANSFER响应，完成配置。
另外，在一实施例中，第一网元为UPF，UPF与SMF通信连接，SMF与PCF通信连接,PCF与UDR通信连接，PCF与UDR通信连接，参照图11，图1所示实施例的步骤S110还包括但不限于有以下步骤：
步骤S1110，获取SMF发送的第二会话建立请求，其中，第二会话建立请求携带有第二共享策略，第二共享策略携带有共享标识，共享标识由PCF根据集群标识生成，集群标识由PCF根据用户信息、DNN和获取到的分配粒度从UDR获取，归属于同一共享集群的PDU会话携带有相同的共享标识，分配粒度表征共享集群的分组规则，用户信息和DNN由SMF获取并通过第一会话建立请求发送至PCF，第二共享策略由PCF在根据第一会话创建请求创建待配置PDU会话的情况下生成并发送至SMF；
步骤S1120，根据共享标识确定待配置PDU会话所归属的目标共享集群。
需要说明的是，为了通过UPF作为第一网元进行目标带宽速率的分配，可以在PCF获取到集群标识和共享标识之后，通过SMF传递至UPF，共享标识和集群标识的定义、选择以及获取方式可以参考上述实施例的描述，为了叙述简便在此不重复赘述。
值得注意的是，在现有的PCC框架下，SMF可以通过N4接口向UPF发送的第二会话建立请求，从而携带第二共享策略，使得UPF能够得知需要为待配置PDU会话进行共享带宽的控制，第二共享策略的生成原理和方式可以参考图7所示实施例的描述，在此不重复赘述。
需要说明的是，在图7所示的实施例中，SMF获取到第二共享策略之后，从中获取共享标识并进行共享带宽的分配，而在本实施例中，SMF识别到第二共享策略携带有共享标识之后，可以获取共享带宽相关的参数，并添加至第二会话建立请求中发送至UPF，使得UPF能够计算和分配目标带宽速率，从而通过UPF实现共享带宽的控制。
另外，在一实施例中，第二共享策略还携带有共享AMBR，共享AMBR由PCF根据集群标识获取，参照图12，在执行图1所示实施例的步骤S120之前，还包括但不限于有以下步骤：
步骤S1210，确定已占用带宽速率，已占用带宽速率为目标共享集群中处于运行状态的PDU会话的带宽速率之和；
步骤S1220，确定已占用带宽速率与目标带宽速率之和小于或等于共享AMBR。
需要说明的是，判断已占用带宽速率和目标带宽速率之和小于或等于共享AMBR的原理和方式可以参考图4和图8所示实施例的描述，本实施例与图4和图8所示实施例的区别主要在于本实施例的执行主体为UPF，其余相似部分在此不重复赘述。
另外，为了更好地体现本申请在第一网元为UPF的前提下的技术方案，以下提出示例四进行解释说明，在本示例中，集群标识以GroupID为例，第一会话建立请求以PDU会话建立请求为例，第二会话建立请求以N4会话建立请求为例，共享标识以sharingkey标识字段为例，参照图13，示例四包括但不限于有以下步骤：
步骤S1301，SMF向PCF发起会话建立请求，携带用户信息和DNN；
步骤S1302，PCF到UDR中获取用户签约共享带宽的套餐GroupID；
步骤S1303，PCF依据GroupID查询到在PCF预先配置好的共享带宽速率AMBR，结合SMF上报的DNN和UDR签约套餐信息，决策为该用户下发共享带宽策略；
步骤S1304，PCF返回包含共享带宽策略的响应，包含共享带宽速率总和以及sharingkey 标识字段；
步骤S1305，SMF发送共享带宽参数至UPF；
步骤S1306，SMF向UPF建立N4会话建立请求，并且携带有签约会话AMBR、共享带宽速率AMBR和sharingkey标识字段；
步骤S1307，UPF向SMF返回N4会话建立响应；
步骤S1308，UPF根据签约会话AMBR和共享带宽速率AMBR，为创建的用户会话分配目标带宽速率，其中，目标带宽速率为签约会话AMBR或者由PCF自定义的小于签约会话AMBR的AMBR速率。
另外，在一实施例中，参照图14，图1所示实施例的步骤S110还包括但不限于有以下步骤：
步骤S1410，获取针对PDU会话的签约会话AMBR；
步骤S1420，将签约会话AMBR确定为目标带宽速率，或者，根据签约会话AMBR和预设比例确定目标带宽速率，其中，预设比例为小于1的正数。
需要说明的是，在上述实施例中，PCF可以根据DNN或者SUPI等信息从UDR中获取共享带宽签约信息，从而确定共享带宽的共享AMBR，而共享AMBR是针对整个共享带宽的，为了对具体的PDU会话进行带宽速率的配置，在用户接入网络之后，会针对PDU会话的AMBR进行签约，并且签约信息保存在UDM中。
需要说明的是，当第一网元为SMF，可以直接从UDM中获取会话签约信息，从而获取签约会话AMBR；当第一网元为PCF，可以由SMF从UDM获取签约会话AMBR，并通过第一会话建立请求发送至PCF；当第一网元为UPF，可以由SMF从UDM获取签约会话AMBR，并通过第二会话建立请求发送至UPF。
需要说明的是，签约会话AMBR为用户的PDU会话所能达到的最大速率，当用户在目标共享集群中只有一个PDU会话，可以将签约会话AMBR作为目标带宽速率，使得分配到的资源更加充分，当然，也有可能同一个用户在目标共享集群中有多个PDU会话，或者目标共享集群为了能为更多的PDU会话提供资源，还可以在第一网元中预先配置好小于1的预设比例，通过预设比例与签约会话AMBR的乘积作为目标带宽速率，具体的计算方式可以根据实际需求选取。
另外，在一实施例中，参照图15，在执行图1所示实施例的步骤S110之后，还包括但不限于有以下步骤：
步骤S1510，当检测到目标共享集群中处于运行状态的PDU会话下线，重新确定已占用带宽速率。
需要说明的是，基于上述实施例的描述，同一个共享集群内所有的PDU会话的带宽速率之和不能超过共享AMBR，否则会挂起待配置PDU会话并且停止新建新的PDU会话，而当处于运行状态的PDU会话下线之后，有一定的资源空闲，此时可以重新确定已占用带宽速率，当空闲的资源足够分配给待配置PDU会话，可以重新执行待配置PDU会话的资源分配流程，确保共享带宽的资源得到充分的利用。
另外，参照图16，本申请的一个实施例还提供了一种网元，该网元1600包括：存储器1610、处理器1620及存储在存储器1610上并可在处理器1620上运行的计算机程序。
处理器1620和存储器1610可以通过总线或者其他方式连接。
实现上述实施例的资源分配方法所需的非暂态软件程序以及指令存储在存储器1610中，当被处理器1620执行时，执行上述实施例中的应用于网元的资源分配方法，例如，执行以上描述的图1中的方法步骤S110至步骤S120、图3中的方法步骤S310至步骤S330、图4中的方法步骤S410至步骤S430、图5中的方法步骤S510至步骤S520、图6中的方法步骤S601至步骤S609、图7中的方法步骤S710至步骤S740、图8中的方法步骤S810至步骤S820、图9中的方法步骤S901至步骤S910、图10中的方法步骤S1001至步骤S1010、图11中的方法步骤S1110至步骤S1120、图12中的方法步骤S1210至步骤S1220、图13中的方法步骤S1301至步骤S1308、图14中的方法步骤S1410至步骤S1420、图15中的方法步骤S1510。
以上所描述的装置实施例仅仅是示意性的，其中作为分离部件说明的单元可以是或者也可以不是物理上分开的，即可以位于一个地方，或者也可以分别到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。
此外，本申请的一个实施例还提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机可执行指令，该计算机可执行指令被一个处理器或控制器执行，例如，被上述网元实施例中的一个处理器执行，可使得上述处理器执行上述实施例中的应用于网元的资源分配方法，例如，执行以上描述的图1中的方法步骤S110至步骤S120、图3中的方法步骤S310至步骤S330、图4中的方法步骤S410至步骤S430、图5中的方法步骤S510至步骤S520、图6中的方法步骤S601至步骤S609、图7中的方法步骤S710至步骤S740、图8中的方法步骤S810至步骤S820、图9中的方法步骤S901至步骤S910、图10中的方法步骤S1001至步骤S1010、图11中的方法步骤S1110至步骤S1120、图12中的方法步骤S1210至步骤S1220、图13中的方法步骤S1301至步骤S1308、图14中的方法步骤S1410至步骤S1420、图15中的方法步骤S1510。本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统可以被实施为软件、固件、硬件及其适当的组合。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分别在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
本申请实施例包括：确定待配置PDU会话所归属的目标共享集群，其中，所述待配置PDU会话为待分配带宽速率的PDU会话，所述目标共享集群预先配置有共享带宽；确定所述待配置PDU会话的目标带宽速率，从所述共享带宽中为所述待配置PDU会话分配所述目标带宽速率。根据本实施例的技术方案，能够从共享带宽中为待配置PDU会话分配带宽速率，实现了以共享集群为粒度进行资源分配，实现了共享带宽的分配控制，提高了带宽配置的灵活性。
以上是对本申请的若干实施进行了具体说明，但本申请并不局限于上述实施方式，熟悉本领域的技术人员在不违背本申请本质的前提下还可作出种种的等同变形或替换，这些等同的变形或替换均包含在本申请权利要求所限定的范围内。

Claims (12)

  1. 一种资源分配方法，应用于第一网元，所述方法包括：
    确定待配置协议数据单元PDU会话所归属的目标共享集群，其中，所述待配置PDU会话为待分配带宽速率的PDU会话，所述目标共享集群预先配置有共享带宽；
    确定所述待配置PDU会话的目标带宽速率，从所述共享带宽中为所述待配置PDU会话分配所述目标带宽速率。
  2. 根据权利要求1所述的方法，其中，所述第一网元为策略控制功能PCF，所述PCF分别与会话管理功能SMF和用户定义路径UDR通信连接，所述确定待配置PDU会话所归属的目标共享集群，包括：
    当获取到所述SMF发送的第一会话建立请求，创建所述待配置PDU会话，其中，所述第一会话建立请求携带有用户信息和数据网络名称DNN；
    获取预设的分配粒度，根据所述用户信息、所述DNN和所述分配粒度从所述UDR中获取集群标识，所述分配粒度表征所述共享集群的分组规则；
    将所述集群标识所对应的共享集群确定为所述目标共享集群。
  3. 根据权利要求2所述的方法，其中，在所述从所述共享带宽中为所述待配置PDU会话分配所述目标带宽速率之前，包括：
    根据所述集群标识，获取针对所述共享带宽预先配置好的共享总计最大比特率AMBR；
    确定已占用带宽速率，所述已占用带宽速率为所述目标共享集群中处于运行状态的PDU会话的带宽速率之和；
    确定所述已占用带宽速率与所述目标带宽速率之和小于或等于所述共享AMBR。
  4. 根据权利要求2所述的方法，其中，所述SMF与UPF通信连接，所述从所述共享带宽中为所述待配置PDU会话分配所述目标带宽速率，包括：
    生成携带有所述目标带宽速率的第一共享策略；
    将所述第一共享策略下发至所述SMF，以使所述SMF根据所述目标带宽速率在所述共享带宽中为所述待配置PDU会话分配所述目标带宽速率。
  5. 根据权利要求1所述的方法，其中，所述第一网元为SMF，所述SMF与PCF通信连接，所述PCF与UDR通信连接，所述确定待配置PDU会话所归属的目标共享集群，包括：
    生成第一会话建立请求，其中，所述第一会话建立请求携带有用户信息和DNN；
    将所述第一会话建立请求发送至所述PCF，以使所述PCF创建所述待配置PDU会话；
    获取所述PCF下发的第二共享策略，所述第二共享策略携带有共享标识，其中，所述共享标识由所述PCF根据集群标识生成，所述集群标识由所述PCF根据所述用户信息、所述DNN和获取到的分配粒度从UDR获取，归属于同一共享集群的PDU会话携带有相同的所述共享标识，所述分配粒度表征所述共享集群的分组规则；
    根据所述共享标识确定所述待配置PDU会话所归属的所述目标共享集群。
  6. 根据权利要求5所述的方法，其中，所述第二共享策略还携带有共享AMBR，所述共享AMBR由所述PCF根据所述集群标识获取，在所述从所述共享带宽中为所述待配置PDU会话分配所述目标带宽速率之前，所述方法还包括：
    确定已占用带宽速率，所述已占用带宽速率为所述目标共享集群中处于运行状态的PDU 会话的带宽速率之和；
    确定所述已占用带宽速率与所述目标带宽速率之和小于或等于所述共享AMBR。
  7. 根据权利要求1所述的方法，其中，所述第一网元为UPF，所述UPF与SMF通信连接，所述SMF与PCF通信连接,所述PCF与UDR通信连接，所述确定待配置PDU会话所归属的目标共享集群，包括：
    获取所述SMF发送的第二会话建立请求，其中，所述第二会话建立请求携带有第二共享策略，所述第二共享策略携带有共享标识，所述共享标识由所述PCF根据集群标识生成，所述集群标识由所述PCF根据所述用户信息、DNN和获取到的分配粒度从UDR获取，归属于同一共享集群的PDU会话携带有相同的所述共享标识，所述分配粒度表征所述共享集群的分组规则，所述用户信息和所述DNN由所述SMF获取并通过所述第一会话建立请求发送至所述PCF，所述第二共享策略由所述PCF在根据第一会话创建请求创建待配置PDU会话的情况下生成并发送至所述SMF；
    根据所述共享标识确定所述待配置PDU会话所归属的所述目标共享集群。
  8. 根据权利要求7所述的方法，其中，所述第二共享策略还携带有共享AMBR，所述共享AMBR由所述PCF根据所述集群标识获取，在所述从所述共享带宽中为所述待配置PDU会话分配所述目标带宽速率之前，所述方法还包括：
    确定已占用带宽速率，所述已占用带宽速率为所述目标共享集群中处于运行状态的PDU会话的带宽速率之和；
    确定所述已占用带宽速率与所述目标带宽速率之和小于或等于所述共享AMBR。
  9. 根据权利要求1至8任意一项所述的方法，其中，所述确定所述待配置PDU会话的目标带宽速率，包括：
    获取针对PDU会话的签约会话AMBR；
    将所述签约会话AMBR确定为所述目标带宽速率，或者，根据所述签约会话AMBR和预设比例确定所述目标带宽速率，其中，所述预设比例为小于1的正数。
  10. 根据权利要求3、6或8任意一项所述的方法，其中，在所述确定已占用带宽速率之后，所述方法还包括：
    当检测到所述目标共享集群中处于运行状态的PDU会话下线，重新确定所述已占用带宽速率。
  11. 一种网元，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其中，所述处理器执行所述计算机程序时实现如权利要求1至10中任意一项所述的资源分配方法。
  12. 一种计算机可读存储介质，存储有计算机可执行指令，其中，所述计算机可执行指令用于执行如权利要求1至10中任意一项所述的资源分配方法。
PCT/CN2022/121451 2021-10-28 2022-09-26 资源分配方法、网元、存储介质 WO2023071662A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111265912.8A CN116056023A (zh) 2021-10-28 2021-10-28 资源分配方法、网元、存储介质
CN202111265912.8 2021-10-28

Publications (1)

Publication Number Publication Date
WO2023071662A1 true WO2023071662A1 (zh) 2023-05-04

Family

ID=86111938

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/121451 WO2023071662A1 (zh) 2021-10-28 2022-09-26 资源分配方法、网元、存储介质

Country Status (2)

Country Link
CN (1) CN116056023A (zh)
WO (1) WO2023071662A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102075900A (zh) * 2009-11-23 2011-05-25 中兴通讯股份有限公司 一种实现用量监测控制的方法及系统
US20190253916A1 (en) * 2018-02-09 2019-08-15 Verizon Patent And Licensing Inc. Systems and methods for tracking and calculating aggregate maximum bit rate across multiple sessions
CN111771394A (zh) * 2018-02-17 2020-10-13 华为技术有限公司 用于ue上下文和pdu会话上下文管理的系统和方法
US20210084524A1 (en) * 2017-12-22 2021-03-18 Telefonaktiebolaget Lm Ericsson (Publ) QoS in Hybrid Communication Networks

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102075900A (zh) * 2009-11-23 2011-05-25 中兴通讯股份有限公司 一种实现用量监测控制的方法及系统
US20210084524A1 (en) * 2017-12-22 2021-03-18 Telefonaktiebolaget Lm Ericsson (Publ) QoS in Hybrid Communication Networks
US20190253916A1 (en) * 2018-02-09 2019-08-15 Verizon Patent And Licensing Inc. Systems and methods for tracking and calculating aggregate maximum bit rate across multiple sessions
CN111771394A (zh) * 2018-02-17 2020-10-13 华为技术有限公司 用于ue上下文和pdu会话上下文管理的系统和方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ZTE: "Npcf_AMPolicyControl support of UE-AMBR", 3GPP TSG-CT3 MEETING #117E, C3-214197, 11 August 2021 (2021-08-11), XP052040933 *

Also Published As

Publication number Publication date
CN116056023A (zh) 2023-05-02

Similar Documents

Publication Publication Date Title
EP3530037B1 (en) System and method for network slice management in a management plane
EP3595244B1 (en) Network slice management method, unit and system
CN109417719B (zh) 一种网络资源的管理方法、装置及系统
EP3461087B1 (en) Network-slice resource management method and apparatus
US20190230004A1 (en) Network slice management method and management unit
US11750453B2 (en) Network slice configuration method, apparatus, and system
EP4132213A1 (en) Method for controlling media streaming service transmission, user terminal, network node, system, storage medium, and electronic device
CN107533484A (zh) 用于动态管理虚拟网络功能描述符的系统和方法
CN108632063B (zh) 管理网络切片实例的方法、装置和系统
CN105682069B (zh) 一种配置网络资源的方法、装置及系统
WO2019174000A1 (zh) 用于业务管理的方法和装置
KR20200108049A (ko) 디폴트 서비스 품질(QoS) 제어 방법 및 장치
WO2018090191A1 (zh) 网络功能的管理方法、管理单元及系统
WO2019047769A1 (zh) 一种处理网络切片实例的方法、装置及系统
US20220014903A1 (en) Retrieving a core network or access network assigned user equipment identifier
WO2017211161A1 (zh) 基于软件定义网络的资源管理方法及装置
CN114301914A (zh) 一种云边协同方法、装置及存储介质
WO2018036521A1 (zh) 资源调整方法、装置及系统
WO2023071662A1 (zh) 资源分配方法、网元、存储介质
CN110753093A (zh) 云计算系统中设备的管理方法和装置
US20230074779A1 (en) Service relations in provisioning of communication service instance
CN112584337B (zh) 一种网络切片的计费方法及装置
WO2023124685A1 (zh) Pcc策略的控制方法、pcf、smf及通信系统
WO2018014351A1 (zh) 一种资源配置方法及装置
WO2023103649A1 (zh) 会话创建方法、网元、存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22885549

Country of ref document: EP

Kind code of ref document: A1