CN108616555B - Capability control method, device and system - Google Patents
Capability control method, device and system Download PDFInfo
- Publication number
- CN108616555B CN108616555B CN201611147504.1A CN201611147504A CN108616555B CN 108616555 B CN108616555 B CN 108616555B CN 201611147504 A CN201611147504 A CN 201611147504A CN 108616555 B CN108616555 B CN 108616555B
- Authority
- CN
- China
- Prior art keywords
- capability
- network
- identifier
- requester
- request
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/566—Grouping or aggregating service requests, e.g. for unified processing
Abstract
The embodiment of the invention provides a capacity control method, a capacity control device and a capacity control system, wherein the capacity control method comprises the following steps: receiving a capacity request for using the capacity sent by a requester; determining the identifier of the first network and the identifier of the capability in the first network corresponding to the capability request according to the capability request; determining an authorization result of the use capability of the requester according to the identifier of the first network and the identifier of the capability in the first network; and sending the authorization result of the use capability of the requester to the requester. By the method, a unified authorization principle can be provided for the capacity.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method, an apparatus, and a system for capability management and control.
Background
5G is to realize control reconstruction (easy assembly and easy cutting), and the capability is divided into an atomic capability set, such as Access, Mobility management, session management and the like.
The capability shown in fig. 1 is a basis for 5G capability opening, and it is necessary to establish a principle of Function opening of 5G NF (Network Function, capability), such as Access, Mobility Management, Session Management, and the like, however, there is no unified authorization scheme for capability opening at present.
Disclosure of Invention
In view of the foregoing technical problems, embodiments of the present invention provide a method, an apparatus, and a system for capability management and control, which open towards capability and provide a unified authorization principle.
According to a first aspect of the embodiments of the present invention, there is provided a capability management method, including:
receiving a capacity request for using the capacity sent by a requester;
according to the capability request, determining a first network identifier corresponding to the capability request and an identifier of the capability in the first network;
determining an authorization result of the use capability of the requester according to the identifier of the first network and the identifier of the capability in the first network;
and sending the authorization result of the use capability of the requester to the requester.
Optionally, the determining, according to the capability request, an identifier of a first network and an identifier of a capability in the first network, which correspond to the capability request, includes:
analyzing the capability request, mapping the capability request to the identifier of the first network and the identifier of the capability in the first network, and performing authorization query on the first network element;
the determining the authorization result of the use capability of the requester according to the identifier of the first network and the identifier of the capability in the first network includes:
sending a query request for using the capability to a first network element, wherein the query request comprises an identifier of the first network and an identifier of the capability in the first network;
and receiving the authorization result of the use capability of the requester, which is sent by the first network element.
Optionally, the determining, according to the capability request, an identifier of a first network and an identifier of a capability in the first network, which correspond to the capability request, includes:
analyzing the capability request and identifying the identifier of the requester;
requesting the capability opening authorization data of the requester from a first network element according to the identifier of the requester;
receiving capability opening authorization data sent by the first network element, wherein the capability opening authorization data carries a first network identifier corresponding to the identifier of the requester and a first network capability identifier;
the determining the authorization result of the use capability of the requester according to the identifier of the first network and the identifier of the capability in the first network includes:
and analyzing the capability opening authorization data and determining an authorization result of the use capability of the requester.
Optionally, the first network element records therein: authorizing capabilities in the open first network, un-opening authorized capabilities in the first network, and/or conditionally authorized capabilities in the first network.
Optionally, the first network element is a capability open authorization rule base or an operation support system OSS/service support system BSS or an operation system.
Optionally, the sending, to the requester, an authorization result of the requester to use the capability includes:
if the capability authorization result is open or the condition is open, returning a successful response to the request party; otherwise, if the capability authorization result is not open, rejecting the request of the request party.
Optionally, the first network is a private network or a network slice.
According to a second aspect of the embodiments of the present invention, there is also provided a capability management and control apparatus, including:
the receiving module is used for receiving a capacity request of the use capacity sent by a requester;
a first determining module, configured to determine, according to the capability request, an identifier of a first network and an identifier of capability in the first network, which correspond to the capability request;
a second determining module, configured to determine, according to the identifier of the first network and the identifier of the capability in the first network, an authorization result of the capability of the requester;
and the sending module is used for sending the authorization result of the use capability of the requester to the requester.
Optionally, the first determining module includes:
a first parsing unit, configured to parse the capability request, map the capability request to an identifier of a first network and an identifier of a capability in the first network, and perform authorization query on a first network element;
the second determining module includes:
a sending unit, configured to send an inquiry request for using a capability to a first network element, where the inquiry request includes an identifier of the first network and an identifier of a capability in the first network;
a first receiving unit, configured to receive an authorization result of the usage capability of the requester, where the authorization result is sent by the first network element.
Optionally, the first determining module includes:
the second analysis unit is used for analyzing the capability request and identifying the identifier of the requester;
a requesting unit, configured to request, according to the identifier of the requestor, capability opening authorization data of the requestor from a first network element;
a second receiving unit, configured to receive capability opening authorization data sent by the first network element, where the capability opening authorization data carries an identifier of the first network and an identifier of capability in the first network, where the identifier of the first network corresponds to the identifier of the requester;
the second determining module includes:
and the third analysis unit is used for analyzing the capability opening authorization data and determining the authorization result of the use capability of the requester.
Optionally, the first network element records therein: authorizing capabilities in the open first network, un-opening authorized capabilities in the first network, and/or conditionally authorized capabilities in the first network.
Optionally, the first network element is a capability open authorization rule base or an operation support system OSS/service support system BSS or an operation system.
Optionally, the sending module is further configured to: if the capability authorization result is open or the condition is open, returning a successful response to the request party; otherwise, if the capability authorization result is not open, rejecting the request of the request party.
Optionally, the first network is a private network or a network slice.
According to a third aspect of the embodiments of the present invention, there is also provided a capability management and control system, including: a capability opening entity, wherein,
the capability openness entity is used for receiving a capability request for using the capability sent by a requester; determining the identifier of the first network and the identifier of the capability in the first network corresponding to the capability request according to the capability request; determining an authorization result of the use capability of the requester according to the identifier of the first network and the identifier of the capability in the first network; and sending the authorization result of the use capability of the requester to the requester.
Optionally, the system further comprises: a first network element;
the capability openness entity is further configured to: analyzing the capability request, mapping the capability request to the identifier of the first network and the identifier of the capability in the first network, and performing authorization query on the first network element; sending a query request for using the capability to a first network element, wherein the query request comprises an identifier of the first network and an identifier of the capability in the first network; and receiving the authorization result of the use capability of the requester, which is sent by the first network element.
Optionally, the system further comprises: a first network element;
the capability openness entity is further configured to: analyzing the capability request and identifying the identifier of the requester; requesting the capability opening authorization data of the requester from a first network element according to the identifier of the requester; receiving capability opening authorization data sent by the first network element, wherein the capability opening authorization data carries a first network identifier corresponding to the identifier of the requester and a first network capability identifier; and analyzing the capability opening authorization data and determining an authorization result of the use capability of the requester.
One of the above technical solutions has the following advantages or beneficial effects: firstly, receiving a capacity request of using capacity sent by a requester; then, according to the capability request, determining the identifier of the first network corresponding to the capability request and the identifier of the capability in the first network; determining an authorization result of the use capability of the requester according to the identifier of the first network and the identifier of the capability in the first network; and sending the authorization result of the ability used by the requester to the requester, so that a uniform authorization principle can be provided for the ability.
Drawings
FIG. 1 is a diagram illustrating a conventional control function division;
FIG. 2 is a flowchart of a method for controlling energy consumption according to an embodiment of the present invention;
fig. 3 is a schematic diagram of recording information by a first network element according to a first embodiment of the present invention;
FIG. 4 is a flowchart of a power management and control method according to a second embodiment of the present invention;
FIG. 5 is a flowchart of a power management method according to a third embodiment of the present invention;
fig. 6 is a block diagram of a power management and control device in the fourth embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
As will be appreciated by one skilled in the art, embodiments of the present invention may be embodied as a system, apparatus, device, method, or computer program product. Thus, embodiments of the invention may be embodied in the form of: entirely hardware, entirely software (including firmware, resident software, micro-code, etc.), or a combination of hardware and software.
Example one
Referring to fig. 2, a capacity management and control method is shown, which includes the following specific steps:
the requesting party may be a third party (3)rdParty) or may be an operator.
The above capability may be Access, Mobility management, session management, etc.
the first Network may be a private Network or a Network slice (Network Slicing).
In this embodiment, step 202 and step 203 may determine the authorization result of the usage capability of the requester in two ways:
the first method is as follows:
analyzing the capability request, mapping the capability request to the identifier of the first network and the identifier of the capability in the first network, and performing authorization query to the first network element (step 202); sending a query request for using the capability to a first network element, wherein the query request comprises an identifier of the first network and an identifier of the capability in the first network; receiving the authorization result of the usage capability of the requester sent by the first network element (step 203).
The second method comprises the following steps:
analyzing the capability request and identifying the identifier of the requester; requesting the capability opening authorization data of the requester from a first network element according to the identifier of the requester; receiving capability opening authorization data sent by the first network element, where the capability opening authorization data carries an identifier of the first network and an identifier of capability in the first network, where the identifier of the first network corresponds to the identifier of the requester (step 202); and analyzing the capability opening authorization data, and determining an authorization result of the use capability of the requester (step 203).
Referring to fig. 3, a schematic diagram of a first network element recording information is shown, where the first network element records: authorizing capabilities in the open first network, un-opening authorized capabilities in the first network, and/or conditionally authorized capabilities in the first network.
Optionally, the first network element is a capability open authorization rule base or an operation support system OSS/service support system BSS or an operation system.
And step 204, sending the authorization result of the use capability of the requester to the requester.
Specifically, if the capability authorization result is open or conditional open, a successful response is returned to the requester; otherwise, if the capability authorization result is not open, rejecting the request of the request party.
By executing steps 201-204, a unified authorization principle can be provided for the capability.
Example two
Referring to fig. 4, a flow of the capacity management and control method is shown, and the specific steps are as follows:
step 401, the request side requests the capability openness entity to use the capability, and carries the capability request ID and related parameters, where the related parameters include but are not limited to the UE ID (terminal identification).
The requesting party may be a third party (3)rdParty) or may be an operator.
The above capability may be Access, Mobility management, session management, etc.
Step 402, the capability openness entity resolves the request and maps the request to the corresponding subnet ID (and NF-SubF ID (such as Policy subset function) and the capability in the subnet;
the subnetworks may be private networks or network slices.
Step 403, the capability openness entity queries whether the Network Instance ID and the NF-SubF ID can be authorized from the capability library;
the capability library may also be referred to as a capability open authorization rule library.
Step 404, the capability library returns a query result to the capability open entity;
the query result may be: open, not open or conditionally open.
Step 405, if the capability authorization is successful, the capability openness entity returns a successful response to the requester; otherwise, the request of the requesting party is refused.
In this embodiment, the capability openness entity can query the capability library for the right of the requester for using the capability according to the request of the requester, and then feed back the query result to the requester, so that a uniform authorization principle can be provided for the capability through the above manner.
EXAMPLE III
Referring to fig. 5, a flow of the capacity management and control method is shown, and the specific steps are as follows:
step 501, requesting a capability openness entity to request a use capability, which carries a requester identifier, which may be, but is not limited to, carrying a requested capability ID;
the requesting party may be a third party (3)rdParty) or may be an operator.
The above capability may be Access, Mobility management, session management, etc.
Step 502, the capability opening entity analyzes the request, identifies the identifier of the requester and requests the capability use authorization data from the capability library with the identifier of the requester;
the capability repository may be a capability open authorization rule repository.
Step 503, the capability library issues capability authorization data to the capability openness entity, wherein the capability authorization data comprises a subnet ID and a capability ID;
the subnetworks may be private networks or network slices.
Step 504, the capability openness entity analyzes the authorization parameter and judges the authorization result and the requested capability;
the authorization result is whether the requester can use the capability.
The requested capability is open, not open, or conditional open.
Step 505, if the capability authorization is successful, the capability openness entity returns a successful response to the requester; otherwise, the request of the requesting party is refused.
In this embodiment, the capability openness entity can query the capability library for capability openness authorization data (or referred to as capability openness authorization parameters) of the requester according to the request of the requester, and the capability openness entity determines the authorization result of the requester according to the capability openness authorization data, so that a uniform authorization principle can be provided for the capability through the above manner.
Example four
Referring to fig. 6, a capacity management apparatus is shown, the apparatus 600 comprising:
a receiving module 601, configured to receive a capability request for using a capability sent by a requester;
a first determining module 602, configured to determine, according to the capability request, an identifier of a first network and an identifier of capabilities in the first network, which correspond to the capability request;
a second determining module 603, configured to determine, according to the identifier of the first network and the identifier of the capability in the first network, an authorization result of the use capability of the requestor;
a sending module 604, configured to send an authorization result of the capability of the requester to the requester.
In this embodiment, optionally, the first determining module 602 includes:
a first parsing unit, configured to parse the capability request, map the capability request to an identifier of a first network and an identifier of a capability in the first network, and perform authorization query on a first network element;
the second determining module 603 comprises:
a sending unit, configured to send an inquiry request for using a capability to a first network element, where the inquiry request includes an identifier of the first network and an identifier of a capability in the first network;
a first receiving unit, configured to receive an authorization result of the usage capability of the requester, where the authorization result is sent by the first network element.
In this embodiment, the capability openness entity can query the capability library for the right of the requester for using the capability according to the request of the requester, and then feed back the query result to the requester, so that a uniform authorization principle can be provided for the capability through the above manner.
In this embodiment, optionally, the first determining module 602 includes:
the second analysis unit is used for analyzing the capability request and identifying the identifier of the requester;
a requesting unit, configured to request, according to the identifier of the requestor, capability opening authorization data of the requestor from a first network element;
a second receiving unit, configured to receive capability opening authorization data sent by the first network element, where the capability opening authorization data carries an identifier of the first network and an identifier of capability in the first network, where the identifier of the first network corresponds to the identifier of the requester;
the second determining module 603 comprises:
and the third analysis unit is used for analyzing the capability opening authorization data and determining the authorization result of the use capability of the requester.
In this embodiment, optionally, the first network element records: authorizing capabilities in the open first network, un-opening authorized capabilities in the first network, and/or conditionally authorized capabilities in the first network.
In this embodiment, optionally, the first network element is a capability open authorization rule base or an operation support system OSS/service support system BSS or an operation system.
In this embodiment, the capability openness entity can query the capability library for capability openness authorization data (or referred to as capability openness authorization parameters) of the requester according to the request of the requester, and the capability openness entity determines the authorization result of the requester according to the capability openness authorization data, so that a uniform authorization principle can be provided for the capability through the above manner.
In this embodiment, optionally, the sending module is further configured to: if the capability authorization result is open or the condition is open, returning a successful response to the request party; otherwise, if the capability authorization result is not open, rejecting the request of the request party.
In this embodiment, optionally, the first network element includes: authorizing capabilities in the open first network, un-opening authorized capabilities in the first network, and/or conditionally authorized capabilities in the first network.
In this embodiment, optionally, the first network is a private network or a network slice.
EXAMPLE five
An embodiment of the present invention further provides a capability management and control system, including: a capability opening entity, wherein,
the capability openness entity is used for receiving a capability request for using the capability sent by a requester; determining the identifier of the first network and the identifier of the capability in the first network corresponding to the capability request according to the capability request; determining an authorization result of the use capability of the requester according to the identifier of the first network and the identifier of the capability in the first network; and sending the authorization result of the use capability of the requester to the requester.
In this embodiment, optionally, the system further includes: a first network element;
the capability openness entity is further configured to: analyzing the capability request, mapping the capability request to the identifier of the first network and the identifier of the capability in the first network, and performing authorization query on the first network element; sending a query request for using the capability to a first network element, wherein the query request comprises an identifier of the first network and an identifier of the capability in the first network; and receiving the authorization result of the use capability of the requester, which is sent by the first network element.
In this embodiment, optionally, the system further includes: a first network element;
the capability openness entity is further configured to: analyzing the capability request and identifying the identifier of the requester; requesting the capability opening authorization data of the requester from a first network element according to the identifier of the requester; receiving capability opening authorization data sent by the first network element, wherein the capability opening authorization data carries a first network identifier corresponding to the identifier of the requester and a first network capability identifier; and analyzing the capability opening authorization data and determining an authorization result of the use capability of the requester.
It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
In various embodiments of the present invention, it should be understood that the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention
In addition, the terms "system" and "network" are often used interchangeably herein.
It should be understood that the term "and/or" herein is merely one type of association relationship that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.
In the embodiments provided herein, it should be understood that "B corresponding to a" means that B is associated with a from which B can be determined. It should also be understood that determining B from a does not mean determining B from a alone, but may be determined from a and/or other information.
In the several embodiments provided in the present application, it should be understood that the disclosed method and apparatus may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be physically included alone, or two or more units may be integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device) to execute some steps of the transceiving method according to various embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
While the preferred embodiments of the present invention have been described, it should be understood that modifications and adaptations to those embodiments may occur to one skilled in the art without departing from the principles of the present invention and are within the scope of the present invention.
Claims (9)
1. A capacity management and control method is characterized by comprising the following steps:
receiving a capacity request for using the capacity sent by a requester; wherein the capability is mobility management or session management;
according to the capability request, determining a first network identifier corresponding to the capability request and an identifier of the capability in the first network;
determining an authorization result of the use capability of the requester according to the identifier of the first network and the identifier of the capability in the first network;
sending an authorization result of the use capability of the requester to the requester;
the sending the authorization result of the request party using the capability to the request party comprises:
if the authorization result of the use capability is open or the condition is open, returning a successful response to the requester; otherwise, if the authorization result of the use capability is not open, rejecting the request of the request party;
the determining, according to the capability request, an identifier of a first network and an identifier of a capability in the first network, which correspond to the capability request, includes:
analyzing the capability request, mapping the capability request to the identifier of the first network and the identifier of the capability in the first network, and performing authorization query on the first network element;
the determining the authorization result of the use capability of the requester according to the identifier of the first network and the identifier of the capability in the first network includes:
sending a query request for using the capability to a first network element, wherein the query request comprises an identifier of the first network and an identifier of the capability in the first network;
receiving an authorization result of the use capability of the requester, which is sent by the first network element;
alternatively, the first and second electrodes may be,
the determining, according to the capability request, an identifier of a first network and an identifier of a capability in the first network, which correspond to the capability request, includes:
analyzing the capability request and identifying the identifier of the requester;
requesting the capability opening authorization data of the requester from a first network element according to the identifier of the requester;
receiving capability opening authorization data sent by the first network element, wherein the capability opening authorization data carries a first network identifier corresponding to the identifier of the requester and a first network capability identifier;
the determining the authorization result of the use capability of the requester according to the identifier of the first network and the identifier of the capability in the first network includes:
and analyzing the capability opening authorization data and determining an authorization result of the use capability of the requester.
2. The method of claim 1, wherein the first network element has recorded therein: authorizing capabilities in the open first network, un-opening authorized capabilities in the first network, and/or conditionally authorized capabilities in the first network.
3. The method of claim 2, wherein the first network element is a capability open authorization rule base (OSS)/service support system (BSS)/operation system.
4. The method according to any one of claims 1 to 3, wherein the first network is a private network or a network slice.
5. A capacity management and control apparatus, comprising:
the receiving module is used for receiving a capacity request of the use capacity sent by a requester; wherein the capability is mobility management or session management;
a first determining module, configured to determine, according to the capability request, an identifier of a first network and an identifier of capability in the first network, which correspond to the capability request;
a second determining module, configured to determine, according to the identifier of the first network and the identifier of the capability in the first network, an authorization result of the capability of the requester;
the sending module is used for sending the authorization result of the use capability of the requester to the requester;
the sending module is further configured to: if the authorization result of the use capability is open or the condition is open, returning a successful response to the requester; otherwise, if the authorization result of the use capability is not open, rejecting the request of the request party;
the first determining module includes:
a first parsing unit, configured to parse the capability request, map the capability request to an identifier of a first network and an identifier of a capability in the first network, and perform authorization query on a first network element;
the second determining module includes:
a sending unit, configured to send an inquiry request for using a capability to a first network element, where the inquiry request includes an identifier of the first network and an identifier of a capability in the first network;
a first receiving unit, configured to receive an authorization result of the usage capability of the requester, where the authorization result is sent by the first network element;
the first determining module further comprises:
the second analysis unit is used for analyzing the capability request and identifying the identifier of the requester;
a requesting unit, configured to request, according to the identifier of the requestor, capability opening authorization data of the requestor from a first network element;
a second receiving unit, configured to receive capability opening authorization data sent by the first network element, where the capability opening authorization data carries an identifier of the first network and an identifier of capability in the first network, where the identifier of the first network corresponds to the identifier of the requester;
the second determining module further comprises:
and the third analysis unit is used for analyzing the capability opening authorization data and determining the authorization result of the use capability of the requester.
6. The apparatus of claim 5, wherein the first network element has recorded therein: authorizing capabilities in the open first network, un-opening authorized capabilities in the first network, and/or conditionally authorized capabilities in the first network.
7. The apparatus of claim 6, wherein the first network element is a capability open authorization rule base (OSS)/service support system (BSS)/operation system.
8. The apparatus of any of claims 5 to 7, wherein the first network is a private network or a network slice.
9. A capacity management system, comprising: a capability openness entity and a first network element, wherein,
the capability openness entity is used for receiving a capability request for using the capability sent by a requester; wherein the capability is mobility management or session management; determining the identifier of the first network and the identifier of the capability in the first network corresponding to the capability request according to the capability request; determining an authorization result of the use capability of the requester according to the identifier of the first network and the identifier of the capability in the first network; sending an authorization result of the use capability of the requester to the requester;
the capability openness entity is further configured to return a successful response to the requester if the authorization result of the usage capability is open or conditional open; otherwise, if the authorization result of the use capability is not open, rejecting the request of the request party;
the capability openness entity is further configured to: analyzing the capability request, mapping the capability request to the identifier of the first network and the identifier of the capability in the first network, and performing authorization query on the first network element; sending a query request for using the capability to a first network element, wherein the query request comprises an identifier of the first network and an identifier of the capability in the first network; receiving an authorization result of the use capability of the requester, which is sent by the first network element;
the capability openness entity is further configured to: analyzing the capability request and identifying the identifier of the requester; requesting the capability opening authorization data of the requester from a first network element according to the identifier of the requester; receiving capability opening authorization data sent by the first network element, wherein the capability opening authorization data carries a first network identifier corresponding to the identifier of the requester and a first network capability identifier; and analyzing the capability opening authorization data and determining an authorization result of the use capability of the requester.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611147504.1A CN108616555B (en) | 2016-12-13 | 2016-12-13 | Capability control method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611147504.1A CN108616555B (en) | 2016-12-13 | 2016-12-13 | Capability control method, device and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108616555A CN108616555A (en) | 2018-10-02 |
| CN108616555B true CN108616555B (en) | 2020-04-17 |
Family
ID=63656941
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611147504.1A Active CN108616555B (en) | 2016-12-13 | 2016-12-13 | Capability control method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108616555B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020207607A1 (en) * | 2019-04-11 | 2020-10-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Optimization of services applied to data packet sessions |
| CN111859418A (en) * | 2020-06-24 | 2020-10-30 | 华为技术有限公司 | Atomic capability calling method and terminal equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1980164A (en) * | 2005-12-06 | 2007-06-13 | 华为技术有限公司 | Method for selecting service call conversation control function physical body |
| CN102004987A (en) * | 2010-10-21 | 2011-04-06 | 中国移动通信集团北京有限公司 | Method, device and system for realizing application service |
| CN102196569A (en) * | 2010-03-01 | 2011-09-21 | 中兴通讯股份有限公司 | NGSN (next generation service network) system and method thereof for realizing service application |
| CN102571693A (en) * | 2010-12-07 | 2012-07-11 | 中国移动通信集团公司 | Capability safety calling method, device and system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8982893B2 (en) * | 2010-03-04 | 2015-03-17 | Telefonaktiebolaget L M Ericsson (Publ) | System and method of quality of service enablement for over the top applications in a telecommunications system |
-
2016
- 2016-12-13 CN CN201611147504.1A patent/CN108616555B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1980164A (en) * | 2005-12-06 | 2007-06-13 | 华为技术有限公司 | Method for selecting service call conversation control function physical body |
| CN102196569A (en) * | 2010-03-01 | 2011-09-21 | 中兴通讯股份有限公司 | NGSN (next generation service network) system and method thereof for realizing service application |
| CN102004987A (en) * | 2010-10-21 | 2011-04-06 | 中国移动通信集团北京有限公司 | Method, device and system for realizing application service |
| CN102571693A (en) * | 2010-12-07 | 2012-07-11 | 中国移动通信集团公司 | Capability safety calling method, device and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108616555A (en) | 2018-10-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11126484B2 (en) | Invoking external table functions from a data system | |
| CN107508795B (en) | Cross-container cluster access processing device and method | |
| CN107491519B (en) | Method and device for inquiring block chain account book | |
| RU2719437C1 (en) | Method of administering nf network function and nf administration device | |
| US20130054611A1 (en) | Apparatus and method for processing partitioned data for securing content | |
| WO2019041738A1 (en) | Client resource obtaining method and apparatus, terminal device, and storage medium | |
| CN101958838A (en) | Data access method and device | |
| CN101018227A (en) | Data management device, storage medium having data management program, protocol switching device and method | |
| US9215294B2 (en) | Management of communications between a client equipment and a server equipment providing to the client equipment computer resources represented according to a file system | |
| CN108616555B (en) | Capability control method, device and system | |
| TW201814645A (en) | Data processing method, apparatus and device | |
| CN114363029B (en) | Differentiated network access authentication method, device, equipment and medium | |
| CN114374965A (en) | User subscription data processing method, system, device and medium | |
| CN116097691A (en) | Service request handling | |
| US9231957B2 (en) | Monitoring and controlling a storage environment and devices thereof | |
| CN113966602B (en) | Distributed storage of blocks in a blockchain | |
| US20220345925A1 (en) | Distribution of Consolidated Analytics Reports in a Wireless Core Network | |
| CN109815351B (en) | Information query method and related product | |
| CN107547382B (en) | Neighbor relation discovery method and device | |
| CN105554134A (en) | Information synchronization and device | |
| CN115599982A (en) | Data query method and device of hybrid cloud | |
| CN107493181B (en) | Indication method and device of virtual expansion port | |
| CN111327666B (en) | Service management method, device and system, computer equipment and storage medium | |
| US10623492B2 (en) | Service processing method, related device, and system | |
| CN112804335B (en) | Data processing method, data processing device, computer readable storage medium and processor |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |