WO2020124930A1 - 一种资源的调度、处理方法及装置 - Google Patents

一种资源的调度、处理方法及装置 Download PDF

Info

Publication number
WO2020124930A1
WO2020124930A1 PCT/CN2019/085578 CN2019085578W WO2020124930A1 WO 2020124930 A1 WO2020124930 A1 WO 2020124930A1 CN 2019085578 W CN2019085578 W CN 2019085578W WO 2020124930 A1 WO2020124930 A1 WO 2020124930A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
capability
information
resource
scef
Prior art date
Application number
PCT/CN2019/085578
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 WO2020124930A1 publication Critical patent/WO2020124930A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5019—Ensuring fulfilment of SLA
    • H04L41/5022—Ensuring fulfilment of SLA by giving priorities, e.g. assigning classes of service

Definitions

  • This application relates to the field of communication but is not limited to the field of communication, and in particular to a method and device for scheduling and processing resources.
  • unused system resources idle network call capabilities and data transmission capabilities
  • unused system data user location information, movement trajectory, authentication information
  • the system support capabilities that have not been fully exploited billing capabilities and billing strategy customization capabilities
  • value-added service provision capabilities such as CDNs that provide local service acceleration according to third-party needs.
  • NEF network open network element
  • Embodiments of the present application provide a resource scheduling and processing method and device.
  • a resource scheduling method which includes: a first network element receives capability request information sent by a second network element for requesting capability opening resources; the first network element calls the network Query the database in the element, determine a third network element that meets the preset condition corresponding to the capability request information, and send the capability request information to the third network element; receive the third network element for the The capability response information fed back by the capability request information, and the capability response information is fed back to the second network element.
  • a resource scheduling apparatus which is located in a first network element and includes: a first receiving module, configured to receive capability request information sent by a second network element for requesting capability opening resources; The processing module is used to call a database for query, determine a third network element that meets the preset condition corresponding to the capability request information, and send the capability request information to the third network element; a second receiving module is used to Receiving capability response information fed back by the third network element to the capability request information, and feeding back the capability response information to the second network element.
  • a resource processing device which is located in a third network element and includes: a third receiving module configured to receive capability request information sent by the first network element for requesting capability opening resources, Wherein, the capability request information is initiated by the second network element; the feedback module is configured to determine whether the currently available resources meet the requirements of the capability open resource, and carry the result of the determination in the capability response information to feed back to the first Network element.
  • a storage medium in which a computer program is stored, wherein the computer program is configured to execute the steps in any one of the above method embodiments during runtime.
  • an electronic device including a memory and a processor, the memory stores a computer program, the processor is configured to run the computer program to perform any of the above The steps in the method embodiment.
  • FIG. 1 is a block diagram of a hardware structure of a mobile terminal of a resource scheduling method according to an embodiment of the present application
  • FIG. 2 is a flowchart of a resource scheduling method according to an embodiment of the present application.
  • FIG. 3 is a flowchart of a resource processing method according to an embodiment of the present application.
  • FIG. 11 is a flowchart based on scenario 8 according to an embodiment of the present application.
  • FIG. 13 is a structural block diagram of a resource scheduling apparatus according to an embodiment of the present application.
  • FIG. 14 is a structural block diagram of a resource processing apparatus according to an embodiment of the present application.
  • FIG. 1 is a block diagram of a hardware structure of a mobile terminal of a resource scheduling method according to an embodiment of the present application.
  • the mobile terminal 10 may include one or more (only one is shown in FIG. 1) processor 102 (the processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA, etc. ) And a memory 104 for storing data.
  • the above mobile terminal may further include a transmission device 106 for communication functions and an input/output device 108.
  • FIG. 1 is merely an illustration, which does not limit the structure of the mobile terminal described above.
  • the mobile terminal 10 may further include more or fewer components than those shown in FIG. 1, or have a different configuration from that shown in FIG.
  • the memory 104 may be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the resource scheduling method in the embodiments of the present application, and the processor 102 executes the computer program stored in the memory 104 to execute Various functional applications and data processing, namely to achieve the above method.
  • the memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory.
  • the memory 104 may further include memories remotely provided with respect to the processor 102, and these remote memories may be connected to the mobile terminal 10 through a network. Examples of the above network include but are not limited to the Internet, intranet, local area network, mobile communication network, and combinations thereof.
  • the transmission device 106 is configured to receive or transmit data via a network.
  • the above-mentioned specific example of the network may include a wireless network provided by a communication provider of the mobile terminal 10.
  • the transmission device 106 includes a network adapter (Network Interface Controller, referred to as NIC for short), which can be connected to other network devices through a base station to communicate with the Internet.
  • the transmission device 106 may be a radio frequency (Radio Frequency, RF for short) module, which is used to communicate with the Internet in a wireless manner.
  • RF Radio Frequency
  • FIG. 2 is a flowchart of a resource scheduling method according to an embodiment of the present application. As shown in FIG. 2, the process includes The following steps:
  • Step S202 The first network element receives capability request information sent by the second network element for requesting capability opening resources
  • Step S204 the first network element calls a database in the network element to query, determine a third network element that meets the preset condition corresponding to the capability request information, and send the capability request to the third network element information;
  • Step S206 Receive capability response information fed back by the third network element to the capability request information, and feed back the capability response information to the second network element.
  • the method before the first network element receives the capability request information sent by the second network element, the method further includes: the first network element receives the data sent by the second network element.
  • the registration information and capability information of the third network element and store the registration information and capability information of the third network element in the database.
  • the first network element calls the database to query and determine the third network element, including: the first network element determines whether the queried capability information of the third network element satisfies all The preset condition; when the judgment result is yes, the first network element sends the capability request information to the inquired third network element; when the judgment result is no, the first network element The element determines whether there is a third network element that satisfies the preset condition among other third network elements in the database.
  • the method when there is no third network element that satisfies the preset condition in the database, the method further includes: the first network element returns capability request failure information to the second network element , And/or, the first network element determines whether the sum of capability information of a plurality of third network elements in the database satisfies the preset condition; if the judgment result is yes, the first network element The three network elements separately send the capability request information.
  • the method further includes: when the queried third network element satisfying the preset condition is SCEF, the first network element sends to the SCEF a request for 4G network element resources Capability request information; when the third network element that meets the preset condition is a network element slice management module, the first network element sends a 5G network element resource request to the network element slice management module Capability request information.
  • the method when it is queried that both the SCEF and the network element slice management module satisfy the preset condition, the method further includes: according to the priority information of the SCEF and the network element slice management module, determining the use A third network element requesting the capability request information; wherein the priority information is determined in at least one of the following ways: according to the size relationship between the capability information of the SCEF and the capability information of the network element slice management module ; According to the time sequence of the registration information of the SCEF and the registration information of the network element slice management module; according to the priority order pre-configured by the user.
  • receiving the capability response information fed back by the third network element and feeding back the capability response information to the second network element includes: the first network element determining the capability response Whether there is a response resource in the information; when the judgment result is yes, the first network element sends the response resource to the second network element; when the judgment result is no, the first network element The element sends a capability request failure message to the second network element, or the first network element queries the database again whether there are other third network elements that satisfy preset conditions, and sends a request to the determined third network Yuan sends the capability request information.
  • the first network element includes at least: UDM, and the second network element includes at least: NEF.
  • the method according to the above embodiments can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware, but in many cases the former is Better implementation.
  • the technical solution of the present application can essentially be embodied in the form of software products, and the computer software products are stored in a storage medium (such as ROM/RAM, magnetic disk,
  • the CD-ROM includes several instructions to enable a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the embodiments of the present application.
  • FIG. 3 is a flowchart of a resource processing method according to an embodiment of the present application. As shown in FIG. 3, the process includes The following steps:
  • Step S302 The third network element receives the capability request information sent by the first network element for requesting capability opening resources, where the capability request information is initiated by the second network element;
  • Step S304 The third network element determines whether the resource currently available meets the demand for the capability opening resource, and carries the result of the determination in the capability response information and feeds it back to the first network element.
  • the third network element is registered with the second network element, wherein the registration information and capability information of the third network element are stored in the database of the first network element.
  • the types of the third network element include: SCEF and a network element slice management module.
  • the method when the third network element is the SCEF, the method further includes: the SCEF requests the NFMF to obtain the capability open resource according to the capability request information; and receives the NFMF report Capability opening resources and determine whether the capability opening resources meet the requirements of the capability request information; carry the judgment result corresponding to the capability resource in the capability response information and feed it back to the first network element.
  • the method further includes: when it is determined that the capability open resource does not meet the requirements of the capability request information, the SCEF requests the NFMF again to obtain the capability open resource; at a preset time When the SCEF determines that the capability open resource reported by the NFMF does not meet the requirements of the capability request information, the SCEF feeds back the capability request failure information to the first network element.
  • the method further includes: the network element slice management module searches for the capability request information according to the capability request information The first slice of demand.
  • the method further includes: when the first slice is found, the network element slice management module feeds back the first slice to the first network element; when it is not found During the first slice, the network element slice management module generates a second slice according to the requirements of the capability request information, and feeds back the second slice to the first network element; when judging the current resources When it is not enough to generate the second slice, the network element slice management module feeds back capability request failure information to the first network element.
  • the first network element includes at least: UDM, and the second network element includes at least: NEF.
  • the third-party application module AF accesses the operator's network and sends a capability request to the second network element.
  • the first network element is: UDM
  • the second network element is: NEF
  • the third network element is: SCEF
  • only the capability range of 4G network elements falls into the capability requirements of third parties.
  • 4G network elements can provide sufficient resources.
  • 4 is a flowchart based on scenario 1 according to an embodiment of the present application. As shown in Figure 4:
  • Step 1 The 4G SCEF has completed registration and registered the SCEF's scope of capabilities.
  • Step 2 Query UDM for the currently registered capability opening information.
  • Step 3 The UDM queries the database to obtain the SCEF or 5G slice management module that is currently registered to meet the capability request.
  • the query result is that only the SCEF registered capability range can meet the conditions, so the capability request is initiated to the SCEF.
  • Step 4 SCEF requests open capability resources from NFMF.
  • Step 5 NFMF requests resources from 4G network elements, such as NF, according to SCEF requests.
  • Step 6 NF receives the capability request of NFMF, and reports its capability resources according to the capability request.
  • Step 7 NFMF receives the reported information of NF and reports the returned capability resource information to SCEF.
  • Step 8 SCEF receives the capability request result returned by NFMF, determines that the returned capability resource can meet the requirements of the third-party application, and reports the resource to UDM.
  • Step 9 UDM receives the capability request successfully returned by SCEF and reports the capability resource, and reports the resource to NEF.
  • Step 10 The NEF receives the capability request successfully returned by the UDM and reports the capability resource, and provides the resource to a third-party application for use.
  • the third-party application module AF accesses the operator's network and sends a capability request to the second network element.
  • the first network element is: UDM
  • the second network element is: NEF
  • the third network element is: SCEF
  • only the capability range of 4G network elements falls into the capability requirements of third parties.
  • 4G network elements currently cannot provide sufficient resources.
  • FIG. 5 is a flowchart based on scenario 2 according to an embodiment of the present application. As shown in Figure 5:
  • Step 1 The 4G SCEF has completed registration and registered the SCEF's scope of capabilities.
  • Step 2 Query UDM for the currently registered capability opening information.
  • Step 3 The UDM queries the database to obtain the SCEF or 5G slice management module that is currently registered to meet the capability request.
  • the query result is that only the SCEF registered capability range can meet the conditions, so the capability request is initiated to the SCEF.
  • Step 4 SCEF requests open capability resources from NFMF.
  • Step 5 NFMF requests resources from 4G network elements, such as NF, according to SCEF requests.
  • Step 6 NF receives the capability request of NFMF, and reports its capability resources according to the capability request.
  • Step 7 NFMF receives the report information of NF and reports the capability resource information returned by NF to SCEF.
  • Step 8 SCEF receives the capability request result returned by NFMF, and determines that the returned capability resource cannot meet the usage requirements of the third-party application. Therefore, it sends a request to NFMF again to request additional resource allocation.
  • Step 9 NFMF receives the request of SCEF to increase resource allocation, and sends it to each 4G network element, such as NF, 6.
  • Step 10 The NF receives the NFMF request to increase resource allocation, completes the resource allocation, and returns the newly added capability information to the NFMF.
  • Step 11 NFMF reports the new capability resource information returned by NF to SCEF.
  • Step 12 SCEF receives the capability request result returned by NFMF, determines that the returned capability resource can meet the usage requirements of the third-party application, and reports the resource to UDM.
  • Step 13 The UDM receives the capability response successfully returned by the SCEF and the reported capability resource, and reports the resource to the NEF.
  • Step 14 The NEF receives the capability request successfully returned by the UDM and reports the capability resource, and provides the resource to a third-party application for use.
  • the third-party application module AF accesses the operator's network and sends a capability request to the second network element.
  • the first network element is: UDM
  • the second network element is: NEF
  • the third network element is: SCEF or 5G slice management module.
  • the capabilities of 4G and 5G network elements fall into the capabilities requirements of third parties.
  • Step 1 The 4G SCEF has completed registration and registered the SCEF's scope of capabilities.
  • Step 2 NEF queries UDM for the current registered capability opening information.
  • Step 3 The UDM queries the database, and the obtained query result is that both the 4G registered and 5G capability ranges can meet the conditions. Therefore, the network element with the highest priority is determined according to the priority information in the SCEF and 5G slice management modules. The result is SCEF, so the capability request is initiated to SCEF.
  • Step 4 SCEF requests open capability resources from NFMF.
  • Step 5 NFMF requests resources from 4G network elements, such as NF, according to SCEF requests.
  • Step 6 NF receives the capability request of NFMF, and reports its capability resources according to the capability request.
  • Step 7 NFMF receives the report information of NF and reports the capability resource information returned by NF to SCEF.
  • Step 8 SCEF receives the capability request result returned by NFMF, determines that the returned capability resource meets the usage requirements of the third-party application, and reports the resource to UDM.
  • Step 9 UDM receives the capability request successfully returned by SCEF and reports the capability resource, and reports the resource to NEF.
  • Step 10 The NEF receives the capability request successfully returned by the UDM and reports the capability resource, and provides the resource to a third-party application for use.
  • the third-party application module AF accesses the operator's network and sends a capability request to the second network element.
  • the first network element is: UDM
  • the second network element is: NEF
  • the third network element is: SCEF or 5G slice management module.
  • the capabilities of 4G and 5G network elements fall into the capabilities requirements of third parties.
  • Step 1 The 4G SCEF has completed registration and registered the SCEF's scope of capabilities.
  • Step 2 NEF queries UDM for the current registered capability opening information.
  • Step 3 The UDM queries the database, and the obtained query result is that both the 4G registered and 5G capability ranges can meet the conditions. Therefore, the network element with the highest priority is determined according to the priority information in the SCEF and 5G slice management modules. The result is SCEF, so the capability request is initiated to SCEF.
  • Step 4 SCEF requests open capability resources from NFMF.
  • Step 5 NFMF requests resources from 4G network elements, such as NF, according to SCEF requests.
  • Step 6 NF receives the capability request of NFMF, and reports its capability resources according to the capability request.
  • Step 7 NFMF receives the report information of NF and reports the capability resource information returned by NF to SCEF.
  • Step 8 SCEF receives the result of the capability request returned by NFMF, and determines that the returned capability resource cannot meet the usage requirements of the third-party application, so it sends a request to NFMF again to request additional resource allocation.
  • Step 9 The NFMF receives a request from SCEF to increase resource allocation, and requests each 4G network element, such as NF, to increase resource allocation.
  • Step 10 The NF receives the NFMF request to increase resource allocation, completes the resource allocation, and returns the newly added capability information to the NFMF.
  • Step 11 NFMF reports the new capability resource information returned by NF to SCEF.
  • Step 12 SCEF receives the capability request result returned by NFMF, determines that the returned capability resource can meet the usage requirements of the third-party application, and reports the resource to UDM.
  • Step 13 The UDM receives the capability response successfully returned by the SCEF and the reported capability resource, and reports the resource to the NEF.
  • Step 14 The NEF receives the capability request successfully returned by the UDM and reports the capability resource, and provides the resource to a third-party application for use.
  • the third-party application module AF accesses the operator's network and sends a capability request to the second network element.
  • the first network element is: UDM
  • the second network element is: NEF
  • the third network element is: SCEF or 5G slice management module.
  • the capabilities of 4G and 5G network elements fall into the capabilities of third parties.
  • the resources of 4G network elements are used preferentially and the current and reallocated resources provide insufficient capacity resources.
  • FIG. 8 is a flowchart based on scenario 5 according to an embodiment of the present application. As shown in Figure 8:
  • Step 1 The 4G SCEF has completed registration and registered the SCEF's scope of capabilities.
  • Step 2 Query UDM for the currently registered capability opening information.
  • Step 3 The UDM queries the database to obtain the SCEF or 5G slice management module that is currently registered to meet the capability request.
  • the query result is that only the SCEF registered capability range can meet the conditions, so the capability request is initiated to the SCEF.
  • Step 4 SCEF requests open capability resources from NFMF.
  • Step 5 NFMF requests resources from 4G network elements, such as NF, according to SCEF requests.
  • Step 6 NF receives the capability request of NFMF, and reports its capability resources according to the capability request.
  • Step 7 NFMF receives the report information of NF and reports the capability resource information returned by NF to SCEF.
  • Step 8 SCEF receives the capability request result returned by NFMF, and determines that the returned capability resource cannot meet the usage requirements of the third-party application. Therefore, it sends a request to NFMF again to request additional resource allocation.
  • Step 9 NFMF receives a request from SCEF to increase resource allocation, and requests each 4G network element, such as NF, to increase resource allocation.
  • Step 10 The NF receives the NFMF request to increase resource allocation, completes the resource allocation, and returns the newly added capability information to the NFMF.
  • Step 11 NFMF reports the new capability resource information returned by NF to SCEF.
  • Step 12 SCEF receives the capability request result returned by NFMF, determines that the returned capability resource still does not meet the requirements, and fails to report the UDM capability resource request.
  • Step 13 UDM receives the capability request failure response returned by SCEF, and UDM continues to request capability resources from the 5G slice management module.
  • Step 14 The 5G slice management module receives the UDM capability request, selects the slice that meets the capability request, and reports the slice to the UDM.
  • Step 15 If a slice that satisfies the capability request is not found, create a new slice according to the request and report the slice to the UDM.
  • Step 16 In the case that the 5G slice management module returns the capability request successfully, the 5G slice management module reports the resource to UDM.
  • Step 17 The UDM receives the successful response of the capability request and the reported capability slice returned by the 5G slice management module, and reports the slice to the NEF.
  • Step 18 The NEF receives the successful response of the capability request returned by the UDM and the reported capability slice, and provides the resource to a third-party application for use.
  • the third-party application module AF accesses the operator's network and sends a capability request to the second network element.
  • the first network element is: UDM
  • the second network element is: NEF
  • the third network element is: SCEF or 5G slice management module.
  • the capabilities of 4G and 5G network elements fall into the capabilities requirements of third parties.
  • the resources of 5G network elements are used preferentially and the currently available capacity resources are insufficient.
  • Step 1 The 4G SCEF has completed registration and registered the SCEF's scope of capabilities.
  • Step 2 NEF queries UDM for the current registered capability opening information.
  • Step 3 The UDM queries the database, and the obtained query result is that both the 4G registered and 5G capability ranges can meet the conditions. Therefore, the network element with the highest priority is determined according to the priority information in the SCEF and 5G slice management modules. The result is a 5G slice management module, so a capability request is initiated to the 5G slice management module.
  • Step 4 The 5G slice management module receives the UDM capability request, and finds the slice that meets the capability request. However, a slice that satisfies the capability request was not found. Although a new slice was created based on the request for resources, it was still due to insufficient resources that caused the creation to fail.
  • Step 5 The 5G slicing management module reports the application capability slicing failure response to the UDM.
  • Step 6 UDM initiates a capability request to SCEF.
  • Step 7 SCEF requests open capability resources from NFMF.
  • Step 8 NFMF requests resources from 4G network elements, such as NF, according to SCEF requests.
  • Step 9 NF receives the capability request of NFMF, and reports its capability resources according to the capability request.
  • Step 10 NFMF receives the report information of NF, and reports the capability resource information returned by NF to SCEF.
  • Step 11 SCEF receives the capability request result returned by NFMF, determines that the returned capability resource meets the usage requirements of the third-party application, and reports the resource to UDM.
  • Step 12 The UDM receives the capability request successfully returned by the SCEF and reports the capability resource, and reports the resource to the NEF.
  • Step 13 The NEF receives the capability request successfully returned by the UDM and reports the capability resource, and provides the resource to a third-party application for use.
  • the third-party application module AF accesses the operator's network and sends a capability request to the second network element.
  • the first network element is: UDM
  • the second network element is: NEF
  • the third network element is: SCEF or 5G slice management module.
  • the capabilities of 4G and 5G network elements fall into the capabilities requirements of third parties.
  • the resources of 5G network elements are used preferentially and the current and created capacity resources are insufficient.
  • Fig. 10 is a flowchart based on scenario 7 according to an embodiment of the present application. As shown in Figure 10:
  • Step 1 The 4G SCEF has completed registration and registered the SCEF's scope of capabilities.
  • Step 2 NEF queries UDM for the current registered capability opening information.
  • Step 3 The UDM queries the database, and the obtained query result is that both the 4G registered and 5G capability ranges can meet the conditions. Therefore, the network element with the highest priority is determined according to the priority information in the SCEF and 5G slice management modules. The result is a 5G slice management module, so a capability request is initiated to the 5G slice management module.
  • Step 4 The 5G slice management module receives the UDM capability request, and finds the slice that meets the capability request. However, a slice that satisfies the capability request was not found. Although a new slice was created based on the request for resources, it was still due to insufficient resources that caused the creation to fail.
  • Step 5 The 5G slicing management module reports the application capability slicing failure response to the UDM.
  • Step 6 UDM initiates a capability request to SCEF.
  • Step 7 SCEF requests open capability resources from NFMF.
  • Step 8 NFMF requests resources from 4G network elements, such as NF, according to SCEF requests.
  • Step 9 NF receives the capability request of NFMF, and reports its capability resources according to the capability request.
  • Step 10 NFMF receives the report information of NF, and reports the capability resource information returned by NF to SCEF.
  • Step 11 SCEF receives the result of the capability request returned by NFMF, and determines that the returned capability resource cannot meet the usage requirements of the third-party application, so it sends a request to NFMF again to request additional resource allocation.
  • Step 12 The NFMF receives a request from SCEF to increase resource allocation, and requests each 4G network element, such as NF, to increase resource allocation.
  • Step 13 NF receives the NFMF request to increase resource allocation, completes resource allocation, and returns the newly added capability information to NFMF.
  • Step 14 NFMF reports the new capability resource information returned by NF to SCEF.
  • Step 15 SCEF receives the capability request result returned by NFMF, determines that the returned capability resource can meet the usage requirements of the third-party application, and reports the resource to UDM.
  • Step 16 UDM receives the capability request successfully returned by SCEF and reports the capability resource, and reports the resource to NEF.
  • Step 17 The NEF receives the capability request successfully returned by the UDM and reports the capability resource, and provides the resource to a third-party application for use.
  • the third-party application module AF accesses the operator's network and sends a capability request to the second network element.
  • the first network element is: UDM
  • the second network element is: NEF
  • the third network element is: SCEF or 5G slice management module.
  • only the capabilities of 5G network elements fall into the capability requirements of third parties.
  • 5G network elements provide sufficient capacity resources.
  • FIG. 11 is a flowchart based on scenario 8 according to an embodiment of the present application. As shown in Figure 11:
  • Step 1 The 4G SCEF has completed registration and registered the SCEF's scope of capabilities.
  • Step 2 Query UDM for the currently registered capability opening information
  • Step 3 The UDM queries the database, and the obtained query result is that both the 4G registered and 5G capability ranges can meet the conditions. Therefore, the network element with the highest priority is determined according to the priority information in the SCEF and 5G slice management modules. The result is a 5G slice management module, so a capability request is initiated to the 5G slice management module.
  • Step 4 The 5G slice management module receives the UDM capability request, selects the slice that meets the capability request, and reports the slice to the UDM.
  • Step 5 If no slice satisfying the capability request is found, a new slice is created according to the request and the slice is reported to UDM.
  • Step 6 In the case that the 5G slice management module returns the capability request successfully, the 5G slice management module reports the resource to UDM
  • Step 7 UDM receives the successful response of the capability request and the reported capability slice returned by the 5G slice management module, and reports the slice to NEF.
  • Step 8 The NEF receives the successful response of the capability request returned by the UDM and the reported capability slice, and provides the resource to a third-party application for use.
  • the third-party application module AF accesses the operator's network and sends a capability request to the second network element.
  • the first network element is: UDM
  • the second network element is: NEF
  • the third network element is: SCEF or 5G slice management module.
  • the capability range of 4G and 5G network elements cannot independently fall into the capability requirements of third parties .
  • the capability resources jointly provided by 4G and 5G network elements can meet the demand.
  • FIG. 12 is a flowchart based on scenario 9 according to an embodiment of the present application. As shown in Figure 12:
  • Step 1 The 4G SCEF has completed registration and registered the SCEF's scope of capabilities.
  • Step 2 Query UDM for the currently registered capability opening information.
  • Step 3 The UDM queries the database.
  • the obtained query result is that the 4G registered and 5G capabilities can only meet part of the conditions, but the combination of the two can meet the conditions. Therefore, the capability requirements are split, so capability requests are jointly initiated to the SCEF and 5G slice management modules.
  • Step 4 The 5G slice management module receives the UDM capability request, selects the slice that meets the capability request, and reports the slice to the UDM.
  • Step 5 SCEF receives the capability request from UDM and requests the NFMF to open the capability resource.
  • Step 6 NFMF requests resources from 4G network elements, such as NF, according to SCEF requests.
  • Step 7 NF receives the capability request of NFMF, and reports its capability resources according to the capability request.
  • Step 8 NFMF receives the report information of NF and reports the capability resource information returned by NF to SCEF.
  • Step 9 SCEF receives the capability request result returned by NFMF, determines that the returned capability resource meets the usage requirements of the third-party application, and reports the resource to UDM.
  • Step 10 UDM combines the capabilities of 4G and 5G and reports resources to NEF.
  • Step 11 The NEF receives the successful response of the capability request returned by the UDM and the reported 5G capability slice and 4G capability resource, and provides the resource to a third-party application for use.
  • a resource scheduling device is also provided.
  • the device is used to implement the above-mentioned embodiments and preferred implementation modes, and those that have already been described will not be repeated.
  • the term "module” may implement a combination of software and/or hardware with predetermined functions.
  • the devices described in the following embodiments are preferably implemented in software, implementation of hardware or a combination of software and hardware is also possible and conceived.
  • the apparatus includes: a first receiving module 1302, a processing module 1304, and a second receiving module 1306.
  • the first receiving module 1302 receives capability request information sent by the second network element for requesting capability opening resources;
  • the processing module 130 calls a database to query, determine a third network element that meets the preset condition corresponding to the capability request information, and send the capability request information to the third network element;
  • the second receiving module 1306, receives the capability response information fed back by the third network element for the capability request information, and feeds back the capability response information to the second network element.
  • the above modules can be implemented by software or hardware, and the latter can be implemented by the following methods, but not limited to this: the above modules are all located in the same processor; or, the above modules can be combined in any combination The forms are located in different processors.
  • a resource processing device is also provided.
  • the device is used to implement the above embodiments and preferred implementation modes, and those that have already been described will not be repeated.
  • the term "module” may implement a combination of software and/or hardware that performs predetermined functions.
  • the devices described in the following embodiments are preferably implemented in software, implementation of hardware or a combination of software and hardware is also possible and conceived.
  • FIG. 14 is a structural block diagram of a resource processing apparatus according to an embodiment of the present application. As shown in FIG. 14, the apparatus includes: a third receiving module 1402 and a feedback module 1404.
  • the third receiving module 1402 is configured to receive capability request information sent by the first network element for requesting capability opening resources, where the capability request information is initiated by the second network element;
  • the feedback module 1404 is configured to determine whether the currently available resources meet the requirements of the capability opening resource, and carry the determination result in the capability response information and feed it back to the first network element.
  • the above modules can be implemented by software or hardware, and the latter can be implemented by the following methods, but not limited to this: the above modules are all located in the same processor; or, the above modules can be combined in any combination The forms are located in different processors.
  • An embodiment of the present application further provides a storage medium in which a computer program is stored, wherein the computer program is configured to execute any of the steps in the above method embodiments during runtime.
  • the above storage medium may be set to store a computer program for performing the following steps:
  • the first network element receives capability request information sent by the second network element to request capability opening resources
  • the first network element calls a database in the network element for query, determines a third network element that meets the preset condition corresponding to the capability request information, and sends the capability request information to the third network element ;
  • the above storage medium may also be set to store a computer program for performing the following steps:
  • the third network element receives capability request information sent by the first network element for requesting capability opening resources, where the capability request information is initiated by the second network element;
  • the third network element determines whether the currently available resources meet the requirements of the capability opening resource, and carries the determination result in the capability response information and feeds back to the first network element.
  • the above storage medium may include, but is not limited to: a USB flash drive, a read-only memory (Read-Only Memory, ROM for short), a random access memory (Random Access Memory, RAM for short), Various media that can store computer programs, such as removable hard disks, magnetic disks, or optical disks.
  • An embodiment of the present application also provides an electronic device, including a memory and a processor, where the computer program is stored in the memory, and the processor is configured to run the computer program to perform the steps in any one of the foregoing method embodiments.
  • the electronic device may further include a transmission device and an input-output device, wherein the transmission device is connected to the processor, and the input-output device is connected to the processor.
  • the above processor may be configured to perform the following steps through a computer program:
  • the first network element receives capability request information sent by the second network element to request capability opening resources
  • the first network element calls a database in the network element for query, determines a third network element that meets the preset condition corresponding to the capability request information, and sends the capability request information to the third network element ;
  • the above processor may be further configured to perform the following steps through a computer program:
  • the third network element receives capability request information sent by the first network element for requesting capability opening resources, where the capability request information is initiated by the second network element;
  • the third network element determines whether the currently available resources meet the requirements of the capability opening resource, and carries the determination result in the capability response information and feeds back to the first network element.
  • modules or steps of the present application can be implemented by a general-purpose computing device, they can be concentrated on a single computing device, or distributed in a network composed of multiple computing devices Above, optionally, they can be implemented with program code executable by the computing device, so that they can be stored in the storage device to be executed by the computing device, and in some cases, can be in a different order than here
  • the steps shown or described are performed, or they are made into individual integrated circuit modules respectively, or multiple modules or steps among them are made into a single integrated circuit module to achieve. In this way, this application is not limited to any specific combination of hardware and software.

Abstract

本申请提供了一种资源的调度、处理方法及装置。具体而言，资源的调度方法包括：第一网元接收第二网元发送的用于请求能力开放资源的能力请求信息；所述第一网元调用该网元中的数据库进行查询，确定满足所述能力请求信息对应的预设条件的第三网元，并向所述第三网元发送所述能力请求信息；接收所述第三网元针对所述能力请求信息反馈的能力响应信息，并将所述能力响应信息反馈至所述第二网元。

Description

一种资源的调度、处理方法及装置
相关申请的交叉引用
本申请基于申请号为201811573708.0、申请日为2018年12月21日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及通信领域但不限于通信领域，尤其涉及一种资源的调度、处理方法及装置。
背景技术
通讯系统中，实际存在很多的资源并未充分利用，如未使用的系统资源：空闲的网络的通话能力和数据传输能力；未利用的系统数据：用户的位置信息，移动轨迹，鉴权信息；未充分挖掘使用的系统支撑能力：计费能力及计费策略定制能力；增值业务提供能力：如按照第三方需求提供本地服务加速的CDN。
在5G网络技术领域中，也定义了专门的网络开放网元(Network Exposure Function,简称NEF)负责对外开放5G网络能力，在收到用户的业务需求后，NEF网元会提供相应的资源，完成对第三方的能力开放。
但是目前5G独立组网并且彻底替换现有的4G网络投资过于巨大，时间上也不会一蹴而就。现状是运营商在4G时代的大量投入还在使用和收回成本的阶段。因此，从目前来看，4G和5G混合组网共存是不可跨越的阶段，甚至在早期可以预见一定是4G网络的资源远大于5G网络的资源。然而相关技术中由于建设成本等原因，网络部署不够完善，对于多种不同制式网 络(例如上述具体的4G网络与5G网络)之间如何进行资源协助以来实现第三方的能力开放，还没有一种比较好的解决方案。
发明内容
本申请实施例提供了一种资源的调度、处理方法及装置。
根据本申请的一个实施例，提供了一种资源的调度方法，包括：第一网元接收第二网元发送的用于请求能力开放资源的能力请求信息；所述第一网元调用该网元中的数据库进行查询，确定满足所述能力请求信息对应的预设条件的第三网元，并向所述第三网元发送所述能力请求信息；接收所述第三网元针对所述能力请求信息反馈的能力响应信息，并将所述能力响应信息反馈至所述第二网元。
根据本申请的一个实施例，提供了一种资源的调度装置，位于第一网元，包括：第一接收模块，用于接收第二网元发送的用于请求能力开放资源的能力请求信息；处理模块，用于调用数据库进行查询，确定满足所述能力请求信息对应的预设条件的第三网元，并向所述第三网元发送所述能力请求信息；第二接收模块，用于接收所述第三网元针对所述能力请求信息反馈的能力响应信息，并将所述能力响应信息反馈至所述第二网元。
根据本申请的一个实施例，提供了一种资源的处理装置，位于第三网元，包括：第三接收模块，配置为接收第一网元发送的用于请求能力开放资源的能力请求信息，其中，所述能力请求信息由第二网元发起；反馈模块，配置为判断当前具有的资源是否满足所述能力开放资源的需求，并将判断结果携带在能力响应信息中反馈至所述第一网元。
根据本申请的又一个实施例，还提供了一种存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
根据本申请的又一个实施例，还提供了一种电子装置，包括存储器和 处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行上述任一项方法实施例中的步骤。
通过本申请，在请求能力开放资源时，通过网元查询并调用数据库以来确定能够作为满足能力开放资源的提供者的其他网元，因此，在不针对网络系统进行额外构建的情况下，能够满足用户对于第三方的能力开放的需求，解决了相关技术中，由于建设成本等原因，网络部署不够完善，难以实现不同制式网络，尤其是针对4G网络和5G网络，如何进行资源协助以来实现第三方的能力开放的问题。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1是本申请实施例的一种资源的调度方法的移动终端的硬件结构框图；
图2是根据本申请实施例的一种资源的调度方法的流程图；
图3是根据本申请实施例的一种资源的处理方法的流程图；
图4是根据本申请实施例的基于场景1的流程图；
图5是根据本申请实施例的基于场景2的流程图；
图6是根据本申请实施例的基于场景3的流程图；
图7是根据本申请实施例的基于场景4的流程图；
图8是根据本申请实施例的基于场景5的流程图；
图9是根据本申请实施例的基于场景6的流程图；
图10是根据本申请实施例的基于场景7的流程图；
图11是根据本申请实施例的基于场景8的流程图；
图12是根据本申请实施例的基于场景9的流程图；
图13是根据本申请实施例的一种资源的调度装置的结构框图；
图14是根据本申请实施例的一种资源的处理装置的结构框图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本申请。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
本申请实施例一所提供的方法实施例可以在移动终端、计算机终端或者类似的运算装置中执行。以运行在移动终端上为例，图1是本申请实施例的一种资源的调度方法的移动终端的硬件结构框图。如图1所示，移动终端10可以包括一个或多个(图1中仅示出一个)处理器102(处理器102可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等的处理装置)和用于存储数据的存储器104，可选地，上述移动终端还可以包括用于通信功能的传输设备106以及输入输出设备108。本领域普通技术人员可以理解，图1所示的结构仅为示意，其并不对上述移动终端的结构造成限定。例如，移动终端10还可包括比图1中所示更多或者更少的组件，或者具有与图1所示不同的配置。
存储器104可用于存储计算机程序，例如，应用软件的软件程序以及模块，如本申请实施例中的资源的调度方法对应的计算机程序，处理器102通过运行存储在存储器104内的计算机程序，从而执行各种功能应用以及数据处理，即实现上述的方法。存储器104可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器104可进一步包括相对于处理器102远程设置的存储器，这些远程存储器可以通过网络连接至移动终端10。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通 信网及其组合。
传输设备106配置为经由一个网络接收或者发送数据。上述的网络具体实例可包括移动终端10的通信供应商提供的无线网络。在一个实例中，传输设备106包括一个网络适配器(Network Interface Controller，简称为NIC)，其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例中，传输设备106可以为射频(Radio Frequency，简称为RF)模块，其用于通过无线方式与互联网进行通讯。
在本实施例中提供了一种运行于上述移动终端的一种资源的调度方法，图2是根据本申请实施例的一种资源的调度方法的流程图，如图2所示，该流程包括如下步骤：
步骤S202，第一网元接收第二网元发送的用于请求能力开放资源的能力请求信息；
步骤S204，所述第一网元调用该网元中的数据库进行查询，确定满足所述能力请求信息对应的预设条件的第三网元，并向所述第三网元发送所述能力请求信息；
步骤S206，接收所述第三网元针对所述能力请求信息反馈的能力响应信息，并将所述能力响应信息反馈至所述第二网元。
在一些实施例中，所述第一网元接收所述第二网元发送的所述能力请求信息之前，所述方法还包括：所述第一网元接收所述第二网元发送的所述第三网元的注册信息和能力信息，并将所述第三网元的注册信息和能力信息存储在所述数据库中。
在一些实施例中，所述第一网元调用所述数据库进行查询，确定所述第三网元，包括：所述第一网元判断查询的所述第三网元的能力信息是否满足所述预设条件；在判断结果为是的情况下，所述第一网元向查询的所述第三网元发送所述能力请求信息；在判断结果为否的情况下，所述第一网元判断所述数据库中其他的第三网元中是否存在满足所述预设条件的第三网元。
在一些实施例中，当所述数据库中不存在满足所述预设条件的第三网 元时，所述方法还包括：所述第一网元向所述第二网元返回能力请求失败信息，和/或，所述第一网元判断所述数据库中多个第三网元的能力信息之和是否满足所述预设条件；在判断结果为是的情况下，向所述多个第三网元分别发送所述能力请求信息。
在一些实施例中，所述方法还包括：当查询到的满足所述预设条件的第三网元是SCEF时，所述第一网元向所述SCEF发送用于请求4G网元资源的能力请求信息；当查询到的满足所述预设条件的第三网元是网元切片管理模块时，所述第一网元向所述网元切片管理模块发送用于请求5G网元资源的能力请求信息。
在一些实施例中，当查询到SCEF和网元切片管理模块均满足所述预设条件时，所述方法还包括：根据所述SCEF与所述网元切片管理模块的优先级信息，确定用于请求所述能力请求信息的第三网元；其中，所述优先级信息通过以下至少之一的方式确定：根据所述SCEF的能力信息和所述网元切片管理模块的能力信息的大小关系；根据所述SCEF的注册信息和所述网元切片管理模块的注册信息的时间先后顺序；根据用户预先配置的优先级顺序。
在一些实施例中，接收所述第三网元反馈的所述能力响应信息，并将所述能力响应信息反馈至所述第二网元，包括：所述第一网元判断所述能力响应信息中是否存在响应资源；在判断结果为是的情况下，所述第一网元将所述响应资源发送至所述第二网元；在判断结果为否的情况下，所述第一网元向所述第二网元发送能力请求失败消息，或，所述第一网元再次查询所述数据库中是否存在其他满足预设条件的第三网元，并向确定的所述第三网元发送所述能力请求信息。
在一些实施例中，所述第一网元至少包括：UDM，所述第二网元至少包括：NEF。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软 件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本申请各个实施例所述的方法。
在本实施例中提供了一种运行于上述移动终端的一种资源的处理方法，图3是根据本申请实施例的一种资源的处理方法的流程图，如图3所示，该流程包括如下步骤：
步骤S302，第三网元接收第一网元发送的用于请求能力开放资源的能力请求信息，其中，所述能力请求信息由第二网元发起；
步骤S304，所述第三网元判断当前具有的资源是否满足所述能力开放资源的需求，并将判断结果携带在能力响应信息中反馈至所述第一网元。
在一些实施例中，所述第三网元在所述第二网元注册，其中，所述第三网元的注册信息和能力信息存储在所述第一网元的数据库中。
在一些实施例中，所述第三网元的类型包括：SCEF以及网元切片管理模块。
在一些实施例中，当所述第三网元为所述SCEF时，所述方法还包括：所述SCEF根据所述能力请求信息，向NFMF请求获取所述能力开放资源；接收所述NFMF上报的能力开放资源，并判断所述能力开放资源是否满足所述能力请求信息的需求；将所述能力资源对应的判断结果携带在能力响应信息中反馈至所述第一网元。
在一些实施例中，所述方法还包括：当判断所述能力开放资源不满足所述能力请求信息的需求时，所述SCEF再次向所述NFMF请求获取所述能力开放资源；在预设时间内，所述SCEF判断所述NFMF上报的所述能力开放资源不满足所述能力请求信息的需求时，所述SCEF向所述第一网元反馈能力请求失败信息。
在一些实施例中，当所述第三网元为所述网元切片管理模块时，所述 方法还包括：所述网元切片管理模块根据所述能力请求信息，查找满足所述能力请求信息的需求的第一切片。
在一些实施例中，所述方法还包括：在查找到所述第一切片时，所述网元切片管理模块将所述第一切片反馈至所述第一网元；在未查找到所述第一切片时，所述网元切片管理模块根据所述能力请求信息的需求生成第二切片，并将所述第二切片反馈至所述第一网元；当判断当前具有的资源不足以生成所述第二切片时，所述网元切片管理模块向所述第一网元反馈能力请求失败信息。
在一些实施例中，所述第一网元至少包括：UDM，所述第二网元至少包括：NEF。
为了更好的理解上述实施例中记载的方案，还提供了如下的场景进行说明。
场景1：
第三方应用模块AF接入到运营商的网络中，向第二网元发送能力请求。第一网元为：UDM，第二网元为：NEF，第三网元为：SCEF，同时，仅有4G网元的能力范围落入到第三方的能力要求中。同时4G网元能够提供的能力资源充足。图4是根据本申请实施例的基于场景1的流程图。如图4所示：
步骤1：4G的SCEF已经完成注册，登记了该SCEF的能力范围。
步骤2：向UDM查询当前注册的能力开放信息。
步骤3：UDM查询数据库，获取当前注册为可以满足能力请求的SCEF或者5G切片管理模块，查询结果为只有SCEF注册的能力范围可以满足条件，于是向SCEF发起能力请求。
步骤4：SCEF向NFMF请求开放能力资源。
步骤5：NFMF根据SCEF的请求，向4G网元中的网元，例如NF，请求资源。
步骤6：NF接收NFMF的能力请求，根据能力请求上报自身的能力资源。
步骤7：NFMF收到NF的上报信息，向SCEF上报返回的能力资源信息。
步骤8：SCEF收到NFMF返回的能力请求结果，判断返回的能力资源能 够满足第三方应用的满足要求，将该资源上报给UDM。
步骤9：UDM收到SCEF返回的能力请求成功应答和上报的能力资源，将该资源上报给NEF。
步骤10：NEF收到UDM返回的能力请求成功应答和上报的能力资源，将该资源提供给第三方应用使用。
场景2：
第三方应用模块AF接入到运营商的网络中，向第二网元发送能力请求。第一网元为：UDM，第二网元为：NEF，第三网元为：SCEF，同时，仅有4G网元的能力范围落入到第三方的能力要求中。同时4G网元当前能够提供的能力资源不足。图5是根据本申请实施例的基于场景2的流程图。如图5所示：
步骤1：4G的SCEF已经完成注册，登记了该SCEF的能力范围。
步骤2：向UDM查询当前注册的能力开放信息。
步骤3：UDM查询数据库，获取当前注册为可以满足能力请求的SCEF或者5G切片管理模块，查询结果为只有SCEF注册的能力范围可以满足条件，于是向SCEF发起能力请求。
步骤4：SCEF向NFMF请求开放能力资源。
步骤5：NFMF根据SCEF的请求，向4G各网元，例如NF，请求资源。
步骤6：NF接收NFMF的能力请求，根据能力请求上报自身的能力资源。
步骤7：NFMF收到NF的上报信息，向SCEF上报NF返回的能力资源信息。
步骤8：SCEF收到NFMF返回的能力请求结果，判断返回的能力资源不能够满足第三方应用的使用要求，因此，重新向NFMF发送请求，请求增加资源分配。
步骤9：NFMF收到SCEF增加资源分配的请求，向4G各网元，例如NF，6。
步骤10：NF接收到NFMF增加资源分配的请求，完成资源分配，并将新增的能力信息返回至NFMF。
步骤11：NFMF上报NF返回的新增能力资源信息到SCEF。
步骤12：SCEF收到NFMF返回的能力请求结果，判断返回的能力资源能够满足第三方应用的使用要求，并将该资源上报给UDM。
步骤13：UDM收到SCEF返回的能力请求成功应答和上报的能力资源，将该资源上报给NEF。
步骤14：NEF收到UDM返回的能力请求成功应答和上报的能力资源，将该资源提供给第三方应用使用。
场景3：
第三方应用模块AF接入到运营商的网络中，向第二网元发送能力请求。第一网元为：UDM，第二网元为：NEF，第三网元为：SCEF或5G切片管理模块，同时，4G和5G网元的能力范围均落入到第三方的能力要求中。4G网元的资源优先使用且当前能够提供的能力资源充足。图6是根据本申请实施例的基于场景3的流程图。如图6所示：
步骤1：4G的SCEF已经完成注册，登记了该SCEF的能力范围。
步骤2：NEF向UDM查询当前注册的能力开放信息。
步骤3：UDM查询数据库，获取的查询结果为4G注册的和5G的能力范围都可以满足条件。因此，根据SCEF和5G切片管理模块中优先级信息确定优先级最高的网元。结果为SCEF，因此向SCEF发起能力请求。
步骤4：SCEF向NFMF请求开放能力资源。
步骤5：NFMF根据SCEF的请求，向4G各网元，例如NF，请求资源。
步骤6：NF接收NFMF的能力请求，根据能力请求上报自身的能力资源。
步骤7：NFMF收到NF的上报信息，向SCEF上报NF返回的能力资源信息。
步骤8：SCEF收到NFMF返回的能力请求结果，判断返回的能力资源满 足第三方应用的使用要求，将该资源上报给UDM。
步骤9：UDM收到SCEF返回的能力请求成功应答和上报的能力资源，将该资源上报给NEF。
步骤10：NEF收到UDM返回的能力请求成功应答和上报的能力资源，将该资源提供给第三方应用使用。
场景4：
第三方应用模块AF接入到运营商的网络中，向第二网元发送能力请求。第一网元为：UDM，第二网元为：NEF，第三网元为：SCEF或5G切片管理模块，同时，4G和5G网元的能力范围均落入到第三方的能力要求中。4G网元的资源优先使用且当前能够提供的能力资源不足。图7是根据本申请实施例的基于场景4的流程图。如图7所示：
步骤1：4G的SCEF已经完成注册，登记了该SCEF的能力范围。
步骤2：NEF向UDM查询当前注册的能力开放信息。
步骤3：UDM查询数据库，获取的查询结果为4G注册的和5G的能力范围都可以满足条件。因此，根据SCEF和5G切片管理模块中优先级信息确定优先级最高的网元。结果为SCEF，因此向SCEF发起能力请求。
步骤4：SCEF向NFMF请求开放能力资源。
步骤5：NFMF根据SCEF的请求，向4G各网元，例如NF，请求资源。
步骤6：NF接收NFMF的能力请求，根据能力请求上报自身的能力资源。
步骤7：NFMF收到NF的上报信息，向SCEF上报NF返回的能力资源信息。
步骤8：SCEF收到NFMF返回的能力请求结果，判断返回的能力资源不能满足第三方应用的使用要求，因此重新向NFMF发送请求，请求增加资源分配。
步骤9：NFMF收到SCEF增加资源分配的请求，向4G各网元，例如NF， 请求增加资源分配。
步骤10：NF接收到NFMF增加资源分配的请求，完成资源分配，并将新增的能力信息返回至NFMF。
步骤11：NFMF上报NF返回的新增能力资源信息到SCEF。
步骤12：SCEF收到NFMF返回的能力请求结果，判断返回的能力资源能够满足第三方应用的使用要求，并将该资源上报给UDM。
步骤13：UDM收到SCEF返回的能力请求成功应答和上报的能力资源，将该资源上报给NEF。
步骤14：NEF收到UDM返回的能力请求成功应答和上报的能力资源，将该资源提供给第三方应用使用。
场景5：
第三方应用模块AF接入到运营商的网络中，向第二网元发送能力请求。第一网元为：UDM，第二网元为：NEF，第三网元为：SCEF或5G切片管理模块，同时，4G和5G网元的能力范围均落入到第三方的能力要求中。4G网元的资源优先使用且当前和再分配资源后提供的能力资源均不足。图8是根据本申请实施例的基于场景5的流程图。如图8所示：
步骤1：4G的SCEF已经完成注册，登记了该SCEF的能力范围。
步骤2：向UDM查询当前注册的能力开放信息。
步骤3：UDM查询数据库，获取当前注册为可以满足能力请求的SCEF或者5G切片管理模块，查询结果为只有SCEF注册的能力范围可以满足条件，于是向SCEF发起能力请求。
步骤4：SCEF向NFMF请求开放能力资源。
步骤5：NFMF根据SCEF的请求，向4G各网元，例如NF，请求资源。
步骤6：NF接收NFMF的能力请求，根据能力请求上报自身的能力资源。
步骤7：NFMF收到NF的上报信息，向SCEF上报NF返回的能力资源信息。
步骤8：SCEF收到NFMF返回的能力请求结果，判断返回的能力资源不能够满足第三方应用的使用要求，因此，重新向NFMF发送请求，请求增加资源分配。
步骤9：NFMF收到SCEF增加资源分配的请求，向4G各网元，例如NF，请求增加资源分配。
步骤10：NF接收到NFMF增加资源分配的请求，完成资源分配，并将新增的能力信息返回至NFMF。
步骤11：NFMF上报NF返回的新增能力资源信息到SCEF。
步骤12：SCEF收到NFMF返回的能力请求结果，判断返回的能力资源仍然不满足要求，于是上报UDM能力资源请求失败。
步骤13：UDM收到SCEF返回的能力请求失败应答，UDM改为继续向5G切片管理模块请求能力资源。
步骤14：5G切片管理模块接收UDM的能力请求，选择满足能力请求的切片上报切片给UDM。
步骤15：如果未找到满足能力请求的切片，则根据请求创建新的切片并上报切片给UDM。
步骤16：在5G切片管理模块返回能力请求成功的情况下，5G切片管理模块将该资源上报给UDM。
步骤17：UDM收到5G切片管理模块返回的能力请求成功应答和上报的能力切片，将该切片上报给NEF。
步骤18：NEF收到UDM返回的能力请求成功应答和上报的能力切片，将该资源提供给第三方应用使用。
场景6：
第三方应用模块AF接入到运营商的网络中，向第二网元发送能力请求。第一网元为：UDM，第二网元为：NEF，第三网元为：SCEF或5G切片管理模块，同时，4G和5G网元的能力范围均落入到第三方的能力要求中。5G网元的资源优先使用且当前提供的能力资源均不足。图9是根据本申请实施例的基于场景6的流程图。如图9所示：
步骤1：4G的SCEF已经完成注册，登记了该SCEF的能力范围。
步骤2：NEF向UDM查询当前注册的能力开放信息。
步骤3：UDM查询数据库，获取的查询结果为4G注册的和5G的能力范围都可以满足条件。因此，根据SCEF和5G切片管理模块中优先级信息确定优先级最高的网元。结果为5G切片管理模块，因此向5G切片管理模块发起能力请求。
步骤4：5G切片管理模块接收UDM的能力请求，查找满足能力请求的切片。然而未找到满足能力请求的切片，虽然根据请求申请资源创建新的切片，但是仍然是资源不足导致了创建失败。
步骤5：5G切片管理模块上报申请能力切片失败应答给UDM。
步骤6：UDM向SCEF发起能力请求。
步骤7：SCEF向NFMF请求开放能力资源。
步骤8：NFMF根据SCEF的请求，向4G各网元，例如NF，请求资源。
步骤9：NF接收NFMF的能力请求，根据能力请求上报自身的能力资源。
步骤10：NFMF收到NF的上报信息，向SCEF上报NF返回的能力资源信息。
步骤11：SCEF收到NFMF返回的能力请求结果，判断返回的能力资源满足第三方应用的使用要求，将该资源上报给UDM。
步骤12：UDM收到SCEF返回的能力请求成功应答和上报的能力资源，将该资源上报给NEF。
步骤13：NEF收到UDM返回的能力请求成功应答和上报的能力资源，将该资源提供给第三方应用使用。
场景7：
第三方应用模块AF接入到运营商的网络中，向第二网元发送能力请求。第一网元为：UDM，第二网元为：NEF，第三网元为：SCEF或5G切片管理模块，同时，4G和5G网元的能力范围均落入到第三方的能力要求中。5G网元的资源优先使用且当前和创建提供的能力资源均不足。图10是根据本申 请实施例的基于场景7的流程图。如图10所示：
步骤1：4G的SCEF已经完成注册，登记了该SCEF的能力范围。
步骤2：NEF向UDM查询当前注册的能力开放信息。
步骤3：UDM查询数据库，获取的查询结果为4G注册的和5G的能力范围都可以满足条件。因此，根据SCEF和5G切片管理模块中优先级信息确定优先级最高的网元。结果为5G切片管理模块，因此向5G切片管理模块发起能力请求。
步骤4：5G切片管理模块接收UDM的能力请求，查找满足能力请求的切片。然而未找到满足能力请求的切片，虽然根据请求申请资源创建新的切片，但是仍然是资源不足导致了创建失败。
步骤5：5G切片管理模块上报申请能力切片失败应答给UDM。
步骤6：UDM向SCEF发起能力请求。
步骤7：SCEF向NFMF请求开放能力资源。
步骤8：NFMF根据SCEF的请求，向4G各网元，例如NF，请求资源。
步骤9：NF接收NFMF的能力请求，根据能力请求上报自身的能力资源。
步骤10：NFMF收到NF的上报信息，向SCEF上报NF返回的能力资源信息。
步骤11：SCEF收到NFMF返回的能力请求结果，判断返回的能力资源不能满足第三方应用的使用要求，因此重新向NFMF发送请求，请求增加资源分配。
步骤12：NFMF收到SCEF增加资源分配的请求，向4G各网元，例如NF，请求增加资源分配。
步骤13：NF接收到NFMF增加资源分配的请求，完成资源分配，并将新增的能力信息返回至NFMF。
步骤14：NFMF上报NF返回的新增能力资源信息到SCEF。
步骤15：SCEF收到NFMF返回的能力请求结果，判断返回的能力资源能够满足第三方应用的使用要求，并将该资源上报给UDM。
步骤16：UDM收到SCEF返回的能力请求成功应答和上报的能力资源，将该资源上报给NEF。
步骤17：NEF收到UDM返回的能力请求成功应答和上报的能力资源，将该资源提供给第三方应用使用。
场景8：
第三方应用模块AF接入到运营商的网络中，向第二网元发送能力请求。第一网元为：UDM，第二网元为：NEF，第三网元为：SCEF或5G切片管理模块，同时，仅有5G网元的能力范围均落入到第三方的能力要求中。5G网元提供的能力资源充足。图11是根据本申请实施例的基于场景8的流程图。如图11所示：
步骤1：4G的SCEF已经完成注册，登记了该SCEF的能力范围。
步骤2：向UDM查询当前注册的能力开放信息
步骤3：UDM查询数据库，获取的查询结果为4G注册的和5G的能力范围都可以满足条件。因此，根据SCEF和5G切片管理模块中优先级信息确定优先级最高的网元。结果为5G切片管理模块，因此向5G切片管理模块发起能力请求。
步骤4：5G切片管理模块接收UDM的能力请求，选择满足能力请求的切片上报切片给UDM。
步骤5：如果未找到满足能力请求的切片，则根据请求创建新的切片并上报切片给UDM。
步骤6：在5G切片管理模块返回能力请求成功的情况下，5G切片管理模块将该资源上报给UDM
步骤7：UDM收到5G切片管理模块返回的能力请求成功应答和上报的能力切片，将该切片上报给NEF.
步骤8：NEF收到UDM返回的能力请求成功应答和上报的能力切片，将该资源提供给第三方应用使用。
场景9：
第三方应用模块AF接入到运营商的网络中，向第二网元发送能力请求。第一网元为：UDM，第二网元为：NEF，第三网元为：SCEF或5G切片管理模块，同时，4G和5G网元的能力范围无法独立落入到第三方的能力要求中。且4G和5G网元共同提供的能力资源才能够满足需求。图12是根据本申请实施例的基于场景9的流程图。如图12所示：
步骤1：4G的SCEF已经完成注册，登记了该SCEF的能力范围。
步骤2：向UDM查询当前注册的能力开放信息。
步骤3：UDM查询数据库，获取的查询结果为4G注册的和5G的能力范围只能够满足部分的条件，但是二者的结合能够满足条件。因此将能力需求进行拆分，故而分别向SCEF和5G切片管理模块共同发起能力请求。
步骤4：5G切片管理模块接收UDM的能力请求，选择满足能力请求的切片，上报切片给UDM。
步骤5：SCEF接收到UDM的能力请求，向NFMF请求开放能力资源。
步骤6：NFMF根据SCEF的请求，向4G各网元，例如NF，请求资源。
步骤7：NF接收NFMF的能力请求，根据能力请求上报自身的能力资源。
步骤8：NFMF收到NF的上报信息，向SCEF上报NF返回的能力资源信息。
步骤9：SCEF收到NFMF返回的能力请求结果，判断返回的能力资源满足第三方应用的使用要求，将该资源上报给UDM。
步骤10：UDM综合4G和5G的能力上报，将资源上报给NEF。
步骤11：NEF收到UDM返回的能力请求成功应答和上报的5G能力切片及4G能力资源，将该资源提供给第三方应用使用。
需要说明的是，上述举例仅仅是列举，而非穷举，然而基于上述场景思路的实施例均在本实施例的保护范围之内。
在本实施例中还提供了一种资源的调度装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术 语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图13是根据本申请实施例的一种资源的调度装置的结构框图，如图13所示，该装置包括：第一接收模块1302，处理模块1304以及第二接收模块1306。
第一接收模块1302，在一些实施例中接收第二网元发送的用于请求能力开放资源的能力请求信息；
处理模块1304，在一些实施例中调用数据库进行查询，确定满足所述能力请求信息对应的预设条件的第三网元，并向所述第三网元发送所述能力请求信息；
第二接收模块1306，在一些实施例中接收所述第三网元针对所述能力请求信息反馈的能力响应信息，并将所述能力响应信息反馈至所述第二网元。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
在本实施例中还提供了一种资源的处理装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图14是根据本申请实施例的一种资源的处理装置的结构框图，如图14所示，该装置包括：第三接收模块1402和反馈模块1404。
第三接收模块1402，配置为接收第一网元发送的用于请求能力开放资源的能力请求信息，其中，所述能力请求信息由第二网元发起；
反馈模块1404，配置为判断当前具有的资源是否满足所述能力开放资 源的需求，并将判断结果携带在能力响应信息中反馈至所述第一网元。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
本申请的实施例还提供了一种存储介质，该存储介质中存储有计算机程序，其中，该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的计算机程序：
S1，第一网元接收第二网元发送的用于请求能力开放资源的能力请求信息；
S2，所述第一网元调用该网元中的数据库进行查询，确定满足所述能力请求信息对应的预设条件的第三网元，并向所述第三网元发送所述能力请求信息；
S3，接收所述第三网元针对所述能力请求信息反馈的能力响应信息，并将所述能力响应信息反馈至所述第二网元。
可选地，在本实施例中，上述存储介质还可以被设置为存储用于执行以下步骤的计算机程序：
S1，第三网元接收第一网元发送的用于请求能力开放资源的能力请求信息，其中，所述能力请求信息由第二网元发起；
S2，所述第三网元判断当前具有的资源是否满足所述能力开放资源的需求，并将判断结果携带在能力响应信息中反馈至所述第一网元。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
本申请的实施例还提供了一种电子装置，包括存储器和处理器，该存 储器中存储有计算机程序，该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
可选地，上述电子装置还可以包括传输设备以及输入输出设备，其中，该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
可选地，在本实施例中，上述处理器可以被设置为通过计算机程序执行以下步骤：
S1，第一网元接收第二网元发送的用于请求能力开放资源的能力请求信息；
S2，所述第一网元调用该网元中的数据库进行查询，确定满足所述能力请求信息对应的预设条件的第三网元，并向所述第三网元发送所述能力请求信息；
S3，接收所述第三网元针对所述能力请求信息反馈的能力响应信息，并将所述能力响应信息反馈至所述第二网元。
可选地，在本实施例中，上述处理器还可以被设置为通过计算机程序执行以下步骤：
S1，第三网元接收第一网元发送的用于请求能力开放资源的能力请求信息，其中，所述能力请求信息由第二网元发起；
S2，所述第三网元判断当前具有的资源是否满足所述能力开放资源的需求，并将判断结果携带在能力响应信息中反馈至所述第一网元。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本申请的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本申请不限制于任何特 定的硬件和软件结合。
以上所述仅为本申请的优选实施例而已，并不用于限制本申请，对于本领域的技术人员来说，本申请可以有各种更改和变化。凡在本申请的原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (20)

  1. 一种资源的调度方法，包括：
    第一网元接收第二网元发送的用于请求能力开放资源的能力请求信息；
    所述第一网元调用该网元中的数据库进行查询，确定满足所述能力请求信息对应的预设条件的第三网元，并向所述第三网元发送所述能力请求信息；
    接收所述第三网元针对所述能力请求信息反馈的能力响应信息，并将所述能力响应信息反馈至所述第二网元。
  2. 根据权利要求1所述的方法，其中，所述第一网元接收所述第二网元发送的所述能力请求信息之前，所述方法还包括：
    所述第一网元接收所述第二网元发送的所述第三网元的注册信息和能力信息，并将所述第三网元的注册信息和能力信息存储在所述数据库中。
  3. 根据权利要求2所述的方法，其中，所述第一网元调用所述数据库进行查询，确定所述第三网元，包括：
    所述第一网元判断查询的所述第三网元的能力信息是否满足所述预设条件；
    在判断结果为是的情况下，所述第一网元向查询的所述第三网元发送所述能力请求信息；
    在判断结果为否的情况下，所述第一网元判断所述数据库中其他的第三网元中是否存在满足所述预设条件的第三网元。
  4. 根据权利要求3所述的方法，其中，当所述数据库中不存在满足所述预设条件的第三网元时，所述方法还包括：
    所述第一网元向所述第二网元返回能力请求失败信息，和/或，
    所述第一网元判断所述数据库中多个第三网元的能力信息之和是否满足所述预设条件；
    在判断结果为是的情况下，向所述多个第三网元分别发送所述能力请求信息。
  5. 根据权利要求3所述的方法，其中，所述方法还包括：
    当查询到的满足所述预设条件的第三网元是服务能力开放网元SCEF时，所述第一网元向所述SCEF发送用于请求4G网元资源的能力请求信息；
    当查询到的满足所述预设条件的第三网元是网元切片管理模块时，所述第一网元向所述网元切片管理模块发送用于请求5G网元资源的能力请求信息。
  6. 根据权利要求3所述的方法，其中，当查询到SCEF和网元切片管理模块均满足所述预设条件时，所述方法还包括：
    根据所述SCEF与所述网元切片管理模块的优先级信息，确定用于请求所述能力请求信息的第三网元；
    其中，所述优先级信息通过以下至少之一的方式确定：
    根据所述SCEF的能力信息和所述网元切片管理模块的能力信息的大小关系；
    根据所述SCEF的注册信息和所述网元切片管理模块的注册信息的时间先后顺序；
    根据用户预先配置的优先级顺序。
  7. 根据权利要求6所述的方法，其中，接收所述第三网元反馈的所述能力响应信息，并将所述能力响应信息反馈至所述第二网元，包括：
    所述第一网元判断所述能力响应信息中是否存在响应资源；
    在判断结果为是的情况下，所述第一网元将所述响应资源发送至所述第二网元；
    在判断结果为否的情况下，所述第一网元向所述第二网元发送能力请求失败消息，或，所述第一网元再次查询所述数据库中是否存在其他满足预设条件的第三网元，并向确定的所述第三网元发送所述能力请求信息。
  8. 根据权利要求1-7任一项所述的方法，其中，所述第一网元至少包括：统一数据管理网元UDM，所述第二网元至少包括：网络开放网元NEF。
  9. 一种资源的处理方法，包括：
    第三网元接收第一网元发送的用于请求能力开放资源的能力请求信息，其中，所述能力请求信息由第二网元发起；
    所述第三网元判断当前具有的资源是否满足所述能力开放资源的需求，并将判断结果携带在能力响应信息中反馈至所述第一网元。
  10. 根据权利要求9所述的方法，其中，
    所述第三网元在所述第二网元注册，其中，所述第三网元的注册信息和能力信息存储在所述第一网元的数据库中。
  11. 根据权利要求10所述的方法，其中，所述第三网元的类型包括：服务能力开放网元SCEF以及网元切片管理模块。
  12. 根据权利要求11所述的方法，其中，当所述第三网元为所述SCEF时，所述方法还包括：
    所述SCEF根据所述能力请求信息，向网络功能管理网元NFMF请求获取所述能力开放资源；
    接收所述NFMF上报的能力开放资源，并判断所述能力开放资源是否满足所述能力请求信息的需求；
    将所述能力资源对应的判断结果携带在能力响应信息中反馈至所述第一网元。
  13. 根据权利要求12所述的方法，其中，所述方法还包括：
    当判断所述能力开放资源不满足所述能力请求信息的需求时，所述SCEF再次向所述NFMF请求获取所述能力开放资源；
    在预设时间内，所述SCEF判断所述NFMF上报的所述能力开放资源不满足所述能力请求信息的需求时，所述SCEF向所述第一网元反馈能力请求失败信息。
  14. 根据权利要求12所述的方法，其中，当所述第三网元为所述网元切片管理模块时，所述方法还包括：
    所述网元切片管理模块根据所述能力请求信息，查找满足所述能力请求信息的需求的第一切片。
  15. 根据权利要求13所述的方法，其中，所述方法还包括：在查找到所述第一切片时，所述网元切片管理模块将所述第一切片反馈至所述第一网元；
    其中，在未查找到所述第一切片时，所述网元切片管理模块根据所述能力请求信息的需求生成第二切片，并将所述第二切片反馈至所述第一网元；当判断当前具有的资源不足以生成所述第二切片时，所述网元切片管理模块向所述第一网元反馈能力请求失败信息。
  16. 根据权利要求9-15任一项所述的方法，其中，所述第一网元至少包括：统一数据管理网元UDM，所述第二网元至少包括：网络开放网元NEF。
  17. 一种资源的调度装置，位于第一网元，包括：
    第一接收模块，配置为接收第二网元发送的用于请求能力开放资源的能力请求信息；
    处理模块，配置为调用数据库进行查询，确定满足所述能力请求信息对应的预设条件的第三网元，并向所述第三网元发送所述能力请求信息；
    第二接收模块，配置为接收所述第三网元针对所述能力请求信息反馈的能力响应信息，并将所述能力响应信息反馈至所述第二网元。
  18. 一种资源的处理装置，位于第三网元，包括：
    第三接收模块，配置为接收第一网元发送的用于请求能力开放资源的能力请求信息，其中，所述能力请求信息由第二网元发起；
    反馈模块，配置为判断当前具有的资源是否满足所述能力开放资源的需求，并将判断结果携带在能力响应信息中反馈至所述第一网元。
  19. 一种存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行所述权利要求1至9,11-16任一项中所述的方法。
  20. 一种电子装置，包括存储器和处理器，其中，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行所述权利要求1至9,11-16任一项中所述的方法。
PCT/CN2019/085578 2018-12-21 2019-05-05 一种资源的调度、处理方法及装置 WO2020124930A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811573708.0A CN111356182A (zh) 2018-12-21 2018-12-21 一种资源的调度、处理方法及装置
CN201811573708.0 2018-12-21

Publications (1)

Publication Number Publication Date
WO2020124930A1 true WO2020124930A1 (zh) 2020-06-25

Family

ID=71100119

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/085578 WO2020124930A1 (zh) 2018-12-21 2019-05-05 一种资源的调度、处理方法及装置

Country Status (2)

Country Link
CN (1) CN111356182A (zh)
WO (1) WO2020124930A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112565390B (zh) * 2020-12-01 2022-05-31 武汉绿色网络信息服务有限责任公司 服务分配方法、装置、电子设备及存储介质
CN113596890B (zh) * 2021-07-28 2022-05-24 广州爱浦路网络技术有限公司 通信方法、系统、装置及存储介质
WO2024026593A1 (zh) * 2022-07-30 2024-02-08 华为技术有限公司 一种协同控车方法及相关装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106572447A (zh) * 2015-10-10 2017-04-19 中兴通讯股份有限公司 资源的控制方法和装置
CN106961743A (zh) * 2016-01-11 2017-07-18 中兴通讯股份有限公司 一种传输方法、装置及接入网网元、用户设备
CN108200606A (zh) * 2016-12-08 2018-06-22 中国移动通信集团四川有限公司 一种网络资源调度方法、智能控制中心及网关
WO2018118001A1 (en) * 2016-12-19 2018-06-28 Nokia Technologies Oy Data storage function selection

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105491557B (zh) * 2014-09-15 2020-04-21 中兴通讯股份有限公司 一种实现能力开放的系统、方法及能力开放平台
CN106211137A (zh) * 2015-04-29 2016-12-07 中国移动通信集团公司 一种移动网络能力开放方法及scef、移动网络系统
CN106304035A (zh) * 2015-05-22 2017-01-04 中兴通讯股份有限公司 一种能力开放方法及系统、能力开放功能实体
CN106657194B (zh) * 2015-11-02 2020-05-08 中兴通讯股份有限公司 一种网络切片能力开放的方法、装置及系统
CN106937362B (zh) * 2015-12-31 2020-04-14 华为技术有限公司 网络切片管理装置和网络切片管理方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106572447A (zh) * 2015-10-10 2017-04-19 中兴通讯股份有限公司 资源的控制方法和装置
CN106961743A (zh) * 2016-01-11 2017-07-18 中兴通讯股份有限公司 一种传输方法、装置及接入网网元、用户设备
CN108200606A (zh) * 2016-12-08 2018-06-22 中国移动通信集团四川有限公司 一种网络资源调度方法、智能控制中心及网关
WO2018118001A1 (en) * 2016-12-19 2018-06-28 Nokia Technologies Oy Data storage function selection

Also Published As

Publication number Publication date
CN111356182A (zh) 2020-06-30

Similar Documents

Publication Publication Date Title
JP7183416B2 (ja) 時間依存ネットワーキング通信方法及び装置
WO2018157439A1 (zh) 业务处理的方法和设备
WO2019042427A1 (zh) 选择amf的方法、amf、系统及计算机可读存储介质
WO2020124930A1 (zh) 一种资源的调度、处理方法及装置
WO2019075848A1 (zh) 协同终端切片功能和网络切片功能
WO2018024121A1 (zh) 一种网络功能nf管理方法及nf管理设备
WO2021109750A1 (zh) 节点管理方法、装置、设备、存储介质和系统
US20230300210A1 (en) Computing aware-session management method and communication apparatus
WO2011097837A1 (zh) 实现接入网关业务接入的方法、设备及系统
US20230040486A1 (en) Policy Determining Method and Apparatus, and System
CN112134730B (zh) 网络数据采集方法及装置
WO2013174171A1 (zh) 获取终端频段信息的方法及装置
US10931829B1 (en) Usage data index for wireless communication networks
CN110417876B (zh) 会话方法、分布式系统中的节点服务器及主控设备
WO2022052875A1 (zh) 终端跨区域通信方法、网元设备及存储介质
CN108259605B (zh) 一种基于多数据中心的数据调用系统及方法
WO2017185848A1 (zh) 最小化路测方法、基站及网络管理系统
WO2014177019A1 (zh) 一种接入制式的配置方法、设备及系统
US20230037402A1 (en) Communication method, apparatus, and system
US9705742B2 (en) Method and apparatus for enabling M2M service and H2H service to coexist
CN113448744A (zh) 一种应用程序选择方法及装置
WO2019214593A1 (zh) 一种通信方法及装置
TWI798807B (zh) 行固網整合ｉｐ位址資源管理系統、方法及電腦可讀媒介
US11825336B2 (en) Connection management method, apparatus, computer device and storage medium
WO2023185692A1 (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: 19900865

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 16/11/2021)

122 Ep: pct application non-entry in european phase

Ref document number: 19900865

Country of ref document: EP

Kind code of ref document: A1