WO2022111462A1 - 数据传输方法、核心、计算机可读介质、电子设备 - Google Patents

数据传输方法、核心、计算机可读介质、电子设备 Download PDF

Info

Publication number
WO2022111462A1
WO2022111462A1 PCT/CN2021/132381 CN2021132381W WO2022111462A1 WO 2022111462 A1 WO2022111462 A1 WO 2022111462A1 CN 2021132381 W CN2021132381 W CN 2021132381W WO 2022111462 A1 WO2022111462 A1 WO 2022111462A1
Authority
WO
WIPO (PCT)
Prior art keywords
core
data
request signaling
cluster
read
Prior art date
Application number
PCT/CN2021/132381
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 WO2022111462A1 publication Critical patent/WO2022111462A1/zh

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00Digital computers in general; Data processing equipment in general
    • G06F15/76Architectures of general purpose stored program computers
    • G06F15/78Architectures of general purpose stored program computers comprising a single central processing unit
    • G06F15/7807System on chip, i.e. computer system on a single chip; System in package, i.e. computer system on one or more chips in a single package
    • G06F15/7825Globally asynchronous, locally synchronous, e.g. network on chip
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00Digital computers in general; Data processing equipment in general
    • G06F15/76Architectures of general purpose stored program computers
    • G06F15/78Architectures of general purpose stored program computers comprising a single central processing unit
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00Energy efficient computing, e.g. low power processors, power management or thermal management

Definitions

  • the present disclosure relates to the field of computer technology, and in particular, to a data transmission method based on a many-core system, a core, a computer-readable medium, an electronic device, and a computer program product.
  • a many-core system can be composed of at least one chip, each chip has multiple computing units, and the smallest computing unit in each chip that can be independently scheduled and has complete computing power is called a core.
  • multiple cores can work together, and each core can run program instructions independently, using parallel computing capabilities to speed up program execution and provide multitasking capabilities.
  • cores in many-core systems are less flexible in performing computing tasks.
  • Embodiments of the present disclosure provide a data transmission method based on a many-core system, a core, a computer-readable medium, an electronic device, and a computer program product.
  • an embodiment of the present disclosure provides a data transmission method based on a many-core system
  • the many-core system includes a plurality of preconfigured core clusters, each of the core clusters includes a plurality of cores, and the method is applied to a first core, where the first core is a core in any core cluster, the method includes: in response to a first request signaling sent by a second core, acquiring data pointed to by the first request signaling, and the The second core and the first core belong to different core clusters; the data pointed to by the first request signaling is transmitted to the second core.
  • an embodiment of the present disclosure provides a data transmission method based on a many-core system, where the many-core system includes a plurality of preconfigured core clusters, each of the core clusters includes a plurality of cores, and the method is applied to A second core, where the second core is a core in any core cluster, the method includes: sending a first request signaling to a first core, where the second core and the first core belong to different cores cluster; in the case of receiving the response information from the first core to the first request signaling, obtain the data pointed to by the first request signaling.
  • an embodiment of the present disclosure provides a core, applied to a many-core system, the core includes: one or more processing units; a storage unit, on which one or more programs are stored, when the one or more A program is executed by the one or more processing units, so that the one or more processing units implement the above-mentioned data transmission method.
  • an embodiment of the present disclosure provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, the above-mentioned data transmission method is implemented.
  • embodiments of the present disclosure provide an electronic device, including: a plurality of cores; and a network-on-chip configured to exchange data and external data among the plurality of cores; One or more instructions, one or more of which are executed by one or more of said cores, to enable one or more of said cores to perform the data transfer method described above.
  • an embodiment of the present disclosure provides a computer program product, which, when running on a computer, causes the computer to execute the above-mentioned data transmission method.
  • the first core in the many-core system can transmit the data pointed to by the request signaling to the second core according to the request signaling sent by the second core belonging to different core clusters, thereby realizing different core clusters.
  • the data interaction between them improves the flexibility of the core in processing computing tasks and improves the computing power of the many-core system.
  • FIG. 1 is a flowchart of a data transmission method in an embodiment of the present disclosure
  • FIG. 2 is a schematic diagram of a many-core system in an embodiment of the present disclosure
  • FIG. 3 is a flowchart of a data transmission method in an embodiment of the present disclosure.
  • FIG. 4 is a block diagram of a data transmission device in an embodiment of the present disclosure.
  • Fig. 5 is the composition block diagram of a kind of core in the embodiment of the present disclosure.
  • FIG. 6 is a block diagram of an electronic device in an embodiment of the present disclosure.
  • each core in the many-core system the main functions of each core in the many-core system are: to store the input data of the input device, and the arithmetic unit in the core performs operations according to the input data and stores the operation results in the memory. , notify the output device to receive the output result.
  • each core passively executes computing power according to the running program instructions, and the core itself has weak control ability and poor flexibility.
  • a core cluster is dynamically formed according to computing tasks
  • the core cluster includes multiple cores, and there may be multiple core clusters in a many-core system, and each core cluster performs a corresponding computing task, Thereby strengthening the control of each core and improving the flexibility of performing computing tasks.
  • each core cluster is independent of each other and cannot perform data interaction, and the cores in the many-core system still have limited flexibility in performing computing tasks.
  • an embodiment of the present disclosure provides a data transmission method based on a many-core system, where the many-core system includes a plurality of pre-configured core clusters, each core cluster includes a plurality of cores, and the method is applied to the cores on the receiving side , called the first core, the first core is the core in any core cluster.
  • FIG. 1 is a flowchart of a data transmission method in an embodiment of the present disclosure. Referring to Figure 1, the method includes:
  • step S11 in response to the first request signaling sent by the second core, the data pointed to by the first request signaling is obtained, and the second core and the first core belong to different core clusters;
  • step S12 the data pointed to by the first request signaling is transmitted to the second core.
  • FIG. 2 is a schematic diagram of a many-core system.
  • the many-core system includes core A and core B.
  • Core A and core B have different control capabilities and different functions in the many-core system.
  • the core A may be the control core of the many-core system, and is used for receiving instructions and tasks of the external system; controlling each core in the many-core system to perform processing tasks and the like.
  • Multiple core Bs can be pre-formed into core clusters (as shown by the dotted box in Figure 2), and perform corresponding processing tasks respectively.
  • Core B and at least one core B serving as a slave core of the core cluster the master core is used to receive instructions and tasks of core A; split tasks; control each slave core in the core cluster to execute subtasks, etc.; slave cores Used to execute the corresponding subtask.
  • the present disclosure does not limit the specific functional classification of the cores and the types of tasks performed by each core.
  • the core cluster to which the first core belongs is called the first core cluster
  • the core that sends the first request signaling is called the second core
  • the core cluster to which the second core belongs is called the second core cluster.
  • the second core may be the master core in the second core cluster, or may be the slave core in the second core cluster. This embodiment of the present disclosure does not limit this.
  • configuration information and data may be included in the core.
  • the configuration information in the core includes the operators, parameters, and permission scope information required by the core to complete the computing task;
  • the data in the core includes private data, public data, and friend data.
  • Private data refers to the data that only the core itself and/or the core in the core cluster to which the core belongs has read permission;
  • public data refers to the data that any core in the many-core system has read permission;
  • friend data refers to Only the core's friend core has read access to the data.
  • the first request instruction may be a signaling requesting to acquire configuration information, or may be a signaling requesting to read data in the core.
  • the data pointed to by the first request command is the configuration information;
  • the first request command is a signaling requesting to obtain data in the core, the data pointed to by the first request command It can be private data, friend metadata, or public data; in addition, the data pointed to by the first request instruction can also be other information required to complete data interaction between core clusters. This embodiment of the present disclosure does not limit this.
  • the first core may acquire data pointed to by the first request signaling in response to the first request signaling sent by the second core. If the first request signaling requests to obtain configuration information or requests to obtain public data, the corresponding data can be directly determined; if the first request signaling requests to obtain private data, it can be determined according to the situation whether to grant the second core read permission, and A verification token is generated when the read permission is given; if the first request signaling requests to obtain friend data, the second core can judge whether the second core has the read permission according to the situation, and when it has the read permission, determine whether the second core has the read permission. corresponding data.
  • the first core may transmit the data to the second core through a network on chip (NOC, Network On Chip) in step S12.
  • NOC Network On Chip
  • the first core in the many-core system can transmit the data pointed to by the request signaling to the second core according to the request signaling sent by the second core belonging to different core clusters, thereby It realizes data interaction between different core clusters, improves the flexibility of cores in processing computing tasks, and improves the computing power of many-core systems.
  • the second core can perform data interaction with the master core or the slave core of different core clusters, and obtain the configuration information required to complete the computing task from the master core or the slave core.
  • the first request signaling includes a signaling requesting to obtain configuration information.
  • the data pointed to by the first request signaling is configuration information.
  • the embodiment of the present disclosure does not specifically limit the specific form of the configuration information.
  • the configuration information includes at least one of operators, parameters, and permission scope information necessary to request and complete the computing task.
  • the permission scope information includes but is not limited to the data scope information that can be read by the second core.
  • the first request signaling includes a signaling requesting to obtain configuration information
  • step S11 includes: reading configuration information pointed to by the first request signaling, and the configuration information includes the second core At least one of the operator, parameter, and permission scope information required to complete the operation task.
  • the first core can directly read the configuration information pointed to by the first request signaling, and transmit the configuration information through the on-chip network in step S12 to the second core. In this way, the interaction of configuration information can be realized.
  • the second core may also access private data of cores in the first core cluster.
  • the first core is the main core
  • the first request signaling includes a signaling requesting to read data of a target core
  • the target core and the first core belong to the same core cluster
  • step S11 may include:
  • the verification token carries at least one of the identity of the second core, read permission information of the second core, data address information, and token encoding.
  • the master core in the first core cluster when the second core requests to access private data in the cores in the first core cluster, the master core in the first core cluster performs unified scheduling and control. For example, the main core in the first core cluster generates a token according to the request signaling of the second core, and the cores in the first core cluster only allow the second core holding a valid token to access its private data, thereby ensuring data security. .
  • a message to read the data of the target core may be sent to the master core (ie, the first core) of the first core cluster order (ie, the first request signaling).
  • the first core can determine whether to grant the read permission to the second core according to the situation; if it is determined not to grant the read permission to the second core, it can directly return the information of refusing to read the data.
  • the present disclosure does not limit the specific conditions for granting the read permission to the second core.
  • a verification token may be generated according to the first request signaling.
  • the verification token carries at least one of the identity of the second core, the read permission information of the second core, the data address information, and the token code.
  • the identity identifier (ID) of the second core may be the number of the second core in the many-core system; the read permission information may indicate that the second core has the authority to read the data of the target core; the data address information may indicate the second core The storage address of the data readable by the core; the token encoding can indicate the number of the verification token.
  • the present disclosure does not limit the generation method of the verification token and the content it includes.
  • the first core may send the verification token to the second core through the on-chip network, so that the second core requests the target core to read data according to the verification token.
  • the first core is a slave core
  • the first request signaling includes a signaling requesting to read data of the first core.
  • step S11 includes:
  • the verification token carries at least one of the identity of the second core, read permission information of the second core, data address information, and token encoding.
  • the second core after the second core obtains the verification token from the master core of the first core cluster, it can request the corresponding slave core (ie, the first core) to read the data of the core.
  • the second core may send the first request signaling and the verification token to the first core together, that is, the first core receives the first request signaling and the verification token synchronously.
  • the second core may also generate a new first request signaling according to the verification token, and send it to the first core, and the first core obtains the verification token by parsing the new first request signaling.
  • the disclosure does not limit the specific processing methods.
  • the first core may determine whether the verification token is valid. For example, the identity of the second core can be verified according to the identity identifier of the second core carried in the verification token; the authenticity of the verification token can be verified according to the token code carried in the verification token; The read permission information and data address information carried in the token verifies whether the second core has the access permission to the data pointed to by the request signaling.
  • the present disclosure does not limit the specific verification method.
  • a refusal to read the data may be returned directly. If the verification token is valid, the data requested to be read by the first request signaling can be read, a corresponding data packet, etc. can be generated, and in step S12, the data packet is sent to the second core through the on-chip network, thereby completing the data read process of taking.
  • the second core may also implement access to friend data of the master core or the slave core in the first core cluster.
  • step S11 may include:
  • the core in the friend core cluster has the authority to read the data of the core in the core cluster to which the first core belongs;
  • the core cluster to which the second core belongs is in the friend list of the first core, acquire the data pointed to by the first request signaling.
  • each core in the core cluster may be preset with a friend list, the friend list includes identification information of the friend core cluster, and the core in the friend core cluster has a core cluster that reads the belonging of the first core (ie Permission to the data of the cores in the first core cluster).
  • the friend core cluster may be a core cluster whose identity is trusted, or may be a core cluster that frequently interacts with the data of the first core cluster. The present disclosure does not limit the way of defining friend core clusters.
  • any two core clusters that meet the conditions may be friend core clusters of each other, or may be unidirectional friend core clusters, for example, core cluster C is the friend core cluster of core cluster D, and core cluster D is not a friend core cluster of core cluster C.
  • Each core in a friend core cluster can be called a friend core, and the data that can be read by a friend core can be called friend data.
  • the present disclosure does not limit the conditions of the friend core clusters and the specific relationship between the friend core clusters.
  • the first core may determine whether the core cluster (second core cluster) to which the second core belongs is in the friend list of the first core; In the friend list of the first core, the information that refuses to read the data can be directly returned; if it is in the friend list of the first core, the data requested by the first request signaling can be read, and the corresponding data can be generated. data packets, etc., and in step S12, the data packets are sent to the second core through the on-chip network, so as to complete the process of data reading.
  • the first core is a master core in the first core cluster
  • the data transmission method further includes: sending an instruction for setting a friend list to a slave core in the core cluster to which the first core belongs.
  • the first core can set a friend list for itself, and send the set friend list to the secondary core in the first core cluster to which the first core belongs directive to make friends list for each set from core.
  • each core in the first core cluster can determine whether the second core is a core in the friend core cluster according to the friend list, so as to realize direct access to friend data.
  • the first core is a slave core in the first core cluster
  • the data transmission method further includes: setting a friend list according to an instruction of the master core of the core cluster to which the first core belongs.
  • the first core can set a friend list according to the instruction of the master core of the first core cluster to which the first core belongs, so as to determine the first core according to the friend list. Whether the second core is the core in the friend core cluster, and realizes direct access to friend data.
  • a data transmission method based on a many-core system where the many-core system includes a plurality of preconfigured core clusters, each core cluster includes a plurality of cores, and the method is applied to the sending side A core, referred to as a second core, is a core in any core cluster.
  • FIG. 3 is a flowchart of a data transmission method in an embodiment of the present disclosure. 3, the method includes:
  • step S31 a first request signaling is sent to a first core, and the second core and the first core belong to different core clusters;
  • step S32 in the case of receiving the response information from the first core to the first request signaling, acquire the data pointed to by the first request signaling.
  • the second core may send the first request signaling to the first core in step S31.
  • the second core may be the master core in the core cluster, or may be the slave core in the core cluster, which is not limited in this embodiment of the present disclosure.
  • the first request instruction may be a signaling requesting to acquire configuration information, or may be a signaling requesting to read data in the core.
  • the data pointed to by the first request command is configuration information
  • the first request command is a signaling requesting to obtain data in the core
  • the first The data pointed to by a request instruction may be private data, friend data, or public data; in addition, the data pointed to by the first request instruction may also be other information required to complete data interaction between core clusters. This embodiment of the present disclosure does not limit this.
  • the second core can directly read from the first core; for private data or friend data, the embodiment of the present disclosure is configured with a proprietary interface, and the corresponding private interface is read through the proprietary interface data or friend data.
  • the first core may acquire data pointed to by the first request signaling in response to the first request signaling sent by the second core. If the first request signaling requests to obtain configuration information or requests to obtain public data, the corresponding data can be directly determined; if the first request signaling requests to obtain private data, it can be determined according to the situation whether to grant the second core read permission, and A verification token is generated when the read permission is granted; if the first request signaling requests to obtain friend data, the second core can judge whether the second core has the read permission according to the situation, and returns the corresponding response when it has the read permission. response information.
  • the first core may transmit response information for the first request signaling to the second core through the on-chip network, where the response information may be data pointed to by the first request signaling, or may be used to verify the read permission , which is not limited in this disclosure.
  • the second core may acquire the data pointed to by the first request signaling in the case of receiving the response information.
  • the data read in the response information is directly determined, or data is requested from the target core having the data to be read according to the verification token in the response information.
  • the core in the many-core system can send request signaling from the core belonging to a different core cluster from the second core, and obtain data according to the corresponding response information, so as to realize the communication between different core clusters. It improves the flexibility of the core in processing computing tasks and improves the computing power of the many-core system.
  • the second core may access configuration information in a core (a master core or a slave core) in the first core cluster.
  • the first request signaling includes a signaling requesting to obtain configuration information, where the configuration information includes at least one of an operator, a parameter, and permission scope information required by the second core to complete a computing task,
  • the response information includes the configuration information obtained by the first request signaling request.
  • the first core can directly read the configuration information pointed to by the first request signaling, generate response information, and transmit the response information to the second core.
  • the second core may directly acquire the configuration information according to the response information in step S32. In this way, the interaction of configuration information can be realized.
  • the second core may access private data of cores in the first core cluster.
  • the first core is the main core
  • the first request signaling includes a signaling requesting to read data of a target core
  • the target core and the first core belong to the same core cluster
  • the response information includes an authentication token for the target core.
  • step S32 may include:
  • the verification token carries at least one of the identity of the second core, read permission information of the second core, data address information, and token encoding.
  • the second core when the second core wants to access the private data of the slave core in the first core cluster, it needs to first apply for a verification token to the master core in the first core cluster, and then use the verification token to access the first core cluster. Private data from the core.
  • the second core may send signaling (ie, first request signaling) to read data of the target core to the master core (ie, the first core) of the first core cluster.
  • the first core After receiving the first request signaling, the first core can determine whether to grant the read permission to the second core according to the situation; if it is determined not to grant the read permission to the second core, it can directly return the information of refusing to read the data.
  • the present disclosure does not limit the specific conditions for granting the read permission to the second core.
  • a verification token may be generated according to the first request signaling.
  • the first core may generate response information according to the verification token and send it to the second core.
  • the verification token carries at least one of the identity of the second core, read permission information of the second core, data address information, and token encoding.
  • the identity identifier (ID) of the second core may be the number of the second core in the many-core system; the read permission information may indicate that the second core has the authority to read the data of the target core; the data address information may indicate the second core The storage address of the data readable by the core; the token encoding can indicate the number of the verification token.
  • the present disclosure does not limit the generation method of the verification token and the content it includes.
  • the second core may request the target core to read data according to the verification token.
  • the second core may send the first request signaling and the verification token to the target core together, that is, the target core receives the first request signaling and the verification token synchronously.
  • the second core may also generate a new first request signaling according to the verification token, and send it to the target core, and the target core obtains the verification token by parsing the new first request signaling.
  • the present disclosure does not limit the specific processing manner.
  • the target core (slave core) can determine whether the verification token is valid.
  • the verification method of the verification token is similar to that described above, and the description is not repeated here.
  • a refusal to read the data may be returned directly. If the verification token is valid, the data requested by the first request signaling can be read, and a corresponding data packet is generated and sent to the second core, thereby completing the process of data reading.
  • the second core may receive data sent by the target core and requested to be read by the first request signaling, so as to perform corresponding processing according to the data.
  • the second core may also implement access to friend data of the master core or the slave core in the first core cluster.
  • the first request signaling includes a signaling requesting to read data of the first core, a friend list is set in the first core, and the friend list includes friend cores
  • the identification information of the cluster, the core in the friend core cluster has the authority to read the data of the core in the core cluster to which the first core belongs;
  • the response information includes the data requested by the first request signaling to be read.
  • a friend list may be preset in the first core, the friend list includes identification information of the friend core cluster, and the cores in the friend core cluster have the core cluster that reads the belonging of the first core (that is, the first core cluster). Permissions for the data of the cores in the core cluster).
  • the first core if the first core is the master core in the first core cluster, it can set a friend list for itself, and send an instruction to set the friend list to the slave cores in the first core cluster, so that each The slave core sets a friend list; if the first core is a slave core in the first core cluster, the friend list can be set according to an instruction of the master core.
  • the second core may directly send the first request signaling to the first core (the master core or the slave core) in step S31, requesting to read the data of the first core.
  • the first core receives the first request signaling, it can determine whether the core cluster (second core cluster) to which the second core belongs is in the friend list of the first core; if it is not in the friend list of the first core , the information of refusing to read the data can be directly returned; if it is in the friend list of the first core, the data requested to be read by the first request signaling can be read, and the response information can be generated and sent to the second core, thereby Complete the process of data reading.
  • the second core may directly acquire the data requested to be read according to the response information in step S32.
  • a data transmission apparatus based on a many-core system includes multiple pre-configured core clusters, each core cluster includes multiple cores, the device is applied to the core on the receiving side, which is called the first core, and the first core is a core in any core cluster.
  • FIG. 4 is a block diagram of a data transmission apparatus in an embodiment of the present disclosure.
  • the device includes:
  • a data acquisition module 41 configured to acquire data pointed to by the first request signaling in response to a first request signaling sent by a second core, where the second core and the first core belong to different core clusters;
  • a data transmission module 42 configured to transmit the data pointed to by the first request signaling to the second core.
  • the first request signaling includes a signaling requesting to acquire configuration information
  • the data acquisition module is configured to: read the configuration information pointed to by the first request signaling, and the configuration information includes At least one of operators, parameters, and permission scope information required by the second core to complete the computing task.
  • the core cluster of the many-core system includes a master core and a slave core
  • the first core is the master core
  • the first request signaling includes a signaling requesting to read data of the target core, so the target core and the first core belong to the same core cluster
  • the data acquisition module is configured to: generate a verification token according to the first request signaling sent by the second core; send the verification token to the second core, so that the second core
  • the verification token requests the target core to read data; wherein, the verification token carries the identity of the second core, the read permission information of the second core, the data address information, and the token code. at least one of the.
  • the core cluster of the many-core system includes a master core and a slave core
  • the first core is a slave core
  • the first request signaling includes a signal requesting to read data of the first core make
  • the data acquisition module is used for: acquiring the first request signaling and the verification token sent by the second core; judging whether the verification token is valid; when the verification token is valid, acquiring the verification token The data pointed to by the first request signaling, wherein the verification token carries at least one of the identity of the second core, read permission information of the second core, data address information, and token encoding .
  • the data acquisition module is configured to: in the case of receiving the first request signaling, determine whether the core cluster to which the second core belongs is in the friend list of the first core In the friend list, the identification information of the friend core cluster is included, and the core in the friend core cluster has the authority to read the data of the core in the core cluster to which the first core belongs; When the core cluster to which the second core belongs is in the friend list of the first core, the data pointed to by the first request signaling is acquired.
  • a data transmission apparatus based on a many-core system includes a plurality of pre-configured core clusters, each core cluster includes a plurality of cores, the device is applied to the core on the sending side, which is called a second core, and the second core is a core in any core cluster.
  • the device includes:
  • a signaling sending module configured to send a first request signaling to a first core, where the second core and the first core belong to different core clusters;
  • An obtaining module configured to obtain the data pointed to by the first request signaling in the case of receiving the response information from the first core to the first request signaling.
  • the first request signaling includes a signaling requesting to obtain configuration information, where the configuration information includes at least one of an operator, a parameter, and permission scope information required by the second core to complete a computing task,
  • the response information includes the configuration information obtained by the first request signaling request.
  • the core cluster includes a master core and a slave core
  • the first core is a master core
  • the first request signaling includes a signaling requesting to read data of a target core
  • the target core and the The first core belongs to the same core cluster
  • the response information includes a verification token for the target core
  • the acquisition module is configured to: send the first request signaling and the verification token to the target core, so that the target core verifies whether the verification token is valid, and when the verification token is valid Obtain the data requested to be read by the first request signaling; receive the data sent by the target core and requested to be read by the first request signaling, wherein the verification token carries the second At least one of the identity identifier of the core, the read permission information of the second core, the data address information, and the token code.
  • the first request signaling includes a signaling requesting to read data of the first core, a friend list is set in the first core, and the friend list includes friend cores
  • the identification information of the cluster, the core in the friend core cluster has the authority to read the data of the core in the core cluster to which the first core belongs; wherein, the core cluster to which the second core belongs is located in the friend
  • the response information includes the data requested by the first request signaling to be read.
  • FIG. 5 is a block diagram of the composition of a core in an embodiment of the present disclosure.
  • an embodiment of the present disclosure further provides a core, applied to a many-core system, which includes:
  • processing units 101 one or more processing units 101;
  • the storage unit 102 on which one or more programs are stored, when the one or more programs are executed by one or more processing units, so that the one or more processing units implement the above-mentioned data transmission method;
  • the processor 101 is a device with data processing capability, including but not limited to an arithmetic unit, etc.
  • the memory 102 is a device with data storage capability, including but not limited to random access memory (RAM), read only memory (ROM) ), electrified erasable programmable read-only memory (EEPROM), flash memory (FLASH).
  • RAM random access memory
  • ROM read only memory
  • EEPROM electrified erasable programmable read-only memory
  • FLASH flash memory
  • a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, the above-mentioned data transmission method is implemented.
  • FIG. 6 is a block diagram of an electronic device in an embodiment of the present disclosure. Referring to FIG. 6 , an embodiment of the present disclosure further provides an electronic device, including:
  • a network-on-chip 202 configured to exchange data among the plurality of cores 201 and external data
  • One or more of the cores 201 store one or more instructions, and one or more of the instructions are executed by the one or more of the cores 201, so that the one or more of the cores 201 can execute the above-mentioned data transfer method.
  • a computer program product which, when running on a computer, causes the computer to execute the above-mentioned data transmission method.
  • the second core initiates request signaling to the first core in the first core cluster, requesting to obtain configuration information, and the first core is the master core or the slave core of the first core cluster; the first core responds to the request signaling and reads the request The configuration information pointed to by the signaling; the first core transmits the configuration information to the second core.
  • the second core initiates request signaling to the main core of the first core cluster, requesting to obtain a verification token capable of reading the data of the target core, and the target core is any core other than the main core in the first core cluster;
  • the main core of the first core cluster returns a verification token to the second core in response to the request signaling;
  • the second core initiates request signaling to the target core, and at the same time sends the verification token to the target core;
  • the target core interprets the verification token to determine whether the token is valid; if valid, it sends the data pointed to by the request signaling to the second core through the on-chip network; if invalid, rejects it.
  • the second core initiates request signaling to the first core (master core or slave core) in the first core cluster, requesting to read the data of the first core;
  • the first core When the first core receives the request signaling that the second core obtains data, it determines whether the core cluster to which the second core belongs is in the friend list of the first core; if the friend list includes the identifier of the core cluster where the second core is located. information, send the data pointed to by the request signaling to the second core; if not included, reject;
  • the first core may set a friend list for itself in advance, and send an instruction for setting the friend list to the slave cores in the first core cluster, so that each slave core sets the friend list ; If the first core is the slave core, the friend list can be set according to the instruction of the master core.
  • Such software may be distributed on computer-readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media).
  • computer storage media includes both volatile and nonvolatile implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules or other data flexible, removable and non-removable media.
  • Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, magnetic tape, magnetic disk storage or other magnetic storage devices, or may Any other medium used to store desired information and that can be accessed by a computer.
  • communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and can include any information delivery media, as is well known to those of ordinary skill in the art .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Microelectronics & Electronic Packaging (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开提供了一种数据传输方法、核心、计算机可读介质、电子设备。众核系统包括预先配置的多个核心簇,每个核心簇包括多个核心,该方法应用于第一核心,第一核心为任一核心簇中的核心,该方法包括:响应于第二核心发送的第一请求信令,获取第一请求信令指向的数据,第二核心与第一核心归属于不同的核心簇;将第一请求信令指向的数据传输到第二核心。

Description

数据传输方法、核心、计算机可读介质、电子设备 技术领域
本公开涉及计算机技术领域,特别涉及一种基于众核系统的数据传输方法、一种核心、一种计算机可读介质、一种电子设备、一种计算机程序产品。
背景技术
众核系统可以是由至少一个芯片构成的,每个芯片具有多个计算单元,每个芯片中可独立调度并拥有完整计算能力的最小计算单元称为核心。在众核系统中,多个核心可以联合工作,各个核心可以分别独立运行程序指令,利用并行计算的能力加快程序的运行速度,并提供多任务处理能力。在一些相关技术中,众核系统中的核心在执行计算任务时的灵活性较差。
发明内容
本公开实施例提供一种基于众核系统的数据传输方法、一种核心、一种计算机可读介质、一种电子设备、一种计算机程序产品。
第一方面,本公开实施例提供一种基于众核系统的数据传输方法,所述众核系统包括预先配置的多个核心簇,每个所述核心簇包括多个核心,所述方法应用于第一核心,所述第一核心为任一核心簇中的核心,所述方法包括:响应于第二核心发送的第一请求信令,获取所述第一请求信令指向的数据,所述第二核心与所述第一核心归属于不同的核心簇;将所述第一请求信令指向的数据传输到所述第二核心。
第二方面,本公开实施例提供一种基于众核系统的数据传输方法,所述众核系统包括预先配置的多个核心簇,每个所述核心簇包括多个核心,所述方法应用于第二核心,所述第二核心为任一核心簇中的核心,所述方法包括:向第一核心发送第一请求信令,所述第二核心与所述第一核心归属于不同的核心簇;在接收到所述第一核心针对所述第一请求信令的响应信息的情况下,获取所述第一请求信令指向的数据。
第三方面,本公开实施例提供一种核心,应用于众核系统,所述核心包括:一个或多个处理单元;存储单元,其上存储有一个或多个程序,当所述一个或多个程序被所述一个或多个处理单元执行,使得所述一个或多个处理单元实现上述的数据传输方法。
第四方面,本公开实施例提供一种计算机可读介质,其上存储有计算机程序,所述程序被处理器执行时实现上述的数据传输方法。
第五方面,本公开实施例提供一种电子设备,包括:多个核心;以及片上网络,被配置为交互所述多个核心间的数据和外部数据;一个或多个所述核心中存储有一个或多个指令,一个或多个所述指令被一个或多个所述核心执行,以使一个或多个所述核心能够执行上述的数据传输方法。
第六方面,本公开实施例提供一种计算机程序产品,所述计算机程序产品在计算机 上运行时,使得计算机执行上述的数据传输方法。
在本公开实施例中,众核系统中的第一核心能够根据归属于不同核心簇的第二核心发送的请求信令,将请求信令指向的数据传输到第二核心,从而实现不同核心簇之间的数据交互,提高了核心在处理计算任务时的灵活性,提升了众核系统的运算能力。
应当理解,本部分所描述的内容并非旨在标识本公开的实施例的关键或重要特征,也不用于限制本公开的范围。本公开的其它特征将通过以下的说明书而变得容易理解。
附图说明
附图用来提供对本公开的进一步理解,并且构成说明书的一部分,与本公开的实施例一起用于解释本公开,并不构成对本公开的限制。通过参考附图对详细示例实施例进行描述,以上和其他特征和优点对本领域技术人员将变得更加显而易见,在附图中:
图1是本公开实施例中一种数据传输方法的流程图;
图2是本公开实施例中众核系统的示意图;
图3是本公开实施例中一种数据传输方法的流程图;
图4是本公开实施例中一种数据传输装置的组成框图;
图5是本公开实施例中一种核心的组成框图;
图6是本公开实施例中一种电子设备的组成框图。
具体实施方式
为使本领域的技术人员更好地理解本公开的技术方案,以下结合附图对本公开的示范性实施例做出说明,其中包括本公开实施例的各种细节以助于理解,应当将它们认为仅仅是示范性的。因此,本领域普通技术人员应当认识到,可以对这里描述的实施例做出各种改变和修改,而不会背离本公开的范围和精神。同样,为了清楚和简明,以下的描述中省略了对公知功能和结构的描述。
在不冲突的情况下,本公开各实施例及实施例中的各特征可相互组合。
如本文所使用的,术语“和/或”包括一个或多个相关列举条目的任何和所有组合。
本文所使用的术语仅用于描述特定实施例,且不意欲限制本公开。如本文所使用的,单数形式“一个”和“该”也意欲包括复数形式,除非上下文另外清楚指出。还将理解的是,当本说明书中使用术语“包括”和/或“由……制成”时,指定存在所述特征、整体、步骤、操作、元件和/或组件,但不排除存在或添加一个或多个其它特征、整体、步骤、操作、元件、组件和/或其群组。“连接”或者“相连”等类似的词语并非限定于物理的或者机械的连接,而是可以包括电性的连接,不管是直接的还是间接的。
除非另外限定,否则本文所用的所有术语(包括技术和科学术语)的含义与本领域普通技术人员通常理解的含义相同。还将理解,诸如那些在常用字典中限定的那些术语应当被解释为具有与其在相关技术以及本公开的背景下的含义一致的含义,且将不解释为具有理想化或过度形式上的含义,除非本文明确如此限定。
经本公开的发明人研究发现,在一些相关技术中,众核系统中各个核心的主要功能是:存储输入设备的输入数据,核心中的运算器根据输入数据进行运算并将运算结果存入存储器中,通知输出设备接收输出结果。但是,各个核心均为被动的根据运行程序指令执行运算能,核心本身的控制能力较弱、灵活性较差。
为了解决上述问题,在本公开实施例中,根据计算任务动态的组建核心簇,核心簇中包括多个核心,众核系统中可以有多个核心簇,每个核心簇执行相应的计算任务,从而加强对各核心的控制,提高执行计算任务的灵活性。但是,各个核心簇之间相互独立,无法进行数据交互,众核系统中的核心在执行计算任务时的灵活性仍有限。
有鉴于此,本公开实施例提供一种基于众核系统的数据传输方法,该众核系统包括预先配置的多个核心簇,每个核心簇包括多个核心,该方法应用于接收侧的核心,称为第一核心,该第一核心为任一核心簇中的核心。
图1是本公开实施例中一种数据传输方法的流程图。参照图1,所述方法包括:
在步骤S11中,响应于第二核心发送的第一请求信令,获取所述第一请求信令指向的数据,所述第二核心与所述第一核心归属于不同的核心簇;
在步骤S12中,将所述第一请求信令指向的数据传输到所述第二核心。
图2为众核系统的示意图。如图2所示,众核系统中包括核心A和核心B,核心A与核心B的控制能力不同、在众核系统中的功能不同。核心A可以为众核系统的控制核心,用于接收外部系统的指令、任务;控制众核系统中的各个核心执行处理任务等。多个核心B可预先组建成为核心簇(如图2中虚线框所示),分别执行相应的处理任务,在每个核心簇的多个核心B中,包括一个作为该核心簇的主核心的核心B、以及至少一个作为该核心簇的从核心的核心B,主核心用于接收核心A的指令、任务;对任务进行拆分;控制核心簇内的各个从核心执行子任务等;从核心用于执行相应的子任务。本公开对核心的具体功能分类及各个核心所执行的任务类型等均不作限制。
在本公开实施例中,第一核心归属的核心簇称为第一核心簇,发送第一请求信令的核心称为第二核心,第二核心归属的核心簇称为第二核心簇。第二核心可以是第二核心簇中的主核心,也可以是第二核心簇中的从核心。本公开实施例对此不做限定。
在本公开实施例中,核心中可包括配置信息和数据。核心中的配置信息包括核心完成运算任务所需要的算子、参数、权限范围信息等;核心中的数据包括私有数据、公有数据、友元数据。私有数据是指核心本身、和/或该核心所属核心簇中的核心才具有读取权限的数据;公有数据是指众核系统中任一核心都具有读取权限的数据;友元数据是指只有该核心的友元核心才具有读取权限的数据。
在本公开实施例中,第一请求指令可以为请求获取配置信息的信令,也可以为请求读取核心中数据的信令。在第一请求指令为请求获取配置信息的信令时,第一请求指令指向的数据即为配置信息;在第一请求指令为请求获取核心中数据的信令时,第一请求指令指向的数据可以是私有数据,也可以是友元数据,还可以是公有数据;此外,第一请求指令指向的数据还可以是完成核心簇间数据交互所需要的其他信息。本公开实施例 对此不做限定。
在本公开实施例中,在步骤S11中,第一核心响应于第二核心发送的第一请求信令,可获取第一请求信令指向的数据。如果第一请求信令请求获取配置信息或请求获取公有数据,则可直接确定相应的数据;如果第一请求信令请求获取私有数据,则可根据情况确定是否赋予第二核心读取权限,并在赋予读取权限时生成验证令牌;如果第一请求信令请求获取友元数据,则可根据情况判断第二核心判断第二核心是否具有读取权限,并在具有读取权限时确定出相应的数据。
作为一种可选的实施方式,在获取到第一请求信令指向的数据后,第一核心可在步骤S12中,通过片上网络(NOC,Network On Chip)将数据传输到第二核心。
本公开实施例提供的数据传输方法中,众核系统中的第一核心能够根据归属于不同核心簇的第二核心发送的请求信令,将请求信令指向的数据传输到第二核心,从而实现了不同核心簇之间的数据交互,提高了核心在处理计算任务时的灵活性,提升了众核系统的运算能力。
在本公开实施例中,第二核心能够与不同核心簇的主核心或从核心进行数据交互,从主核心或从核心获取完成计算任务所需要的配置信息。
在一些实施例中,所述第一请求信令包括请求获取配置信息的信令。第一请求信令指向的数据为配置信息。本公开实施例对配置信息的具体形式不做特殊限定。例如,配置信息包括请求和完成计算任务所必须的算子、参数、权限范围信息中的至少一者。需要说明的是,权限范围信息包括但不限于第二核心能够读取的数据范围信息。
在一些实施例中,所述第一请求信令包括请求获取配置信息的信令,步骤S11包括:读取所述第一请求信令指向的配置信息,所述配置信息包括所述第二核心完成运算任务所需要的算子、参数、权限范围信息中的至少一者。
也就是说,如果第一请求信令为请求获取配置信息的信令,则第一核心可直接读取第一请求信令指向的配置信息,并在步骤S12中通过片上网络将该配置信息传输到第二核心。通过这种方式,能够实现配置信息的交互。
在本公开实施例中,第二核心还可以访问第一核心簇中的核心的私有数据。
在一些实施例中,所述第一核心为主核心,所述第一请求信令包括请求读取目标核心的数据的信令,所述目标核心与所述第一核心归属于同一核心簇,其中,步骤S11可包括:
根据所述第二核心发送的第一请求信令,生成验证令牌;向所述第二核心发送所述验证令牌,以使所述第二核心根据所述验证令牌向所述目标核心请求读取数据;
其中,所述验证令牌携带有所述第二核心的身份标识、所述第二核心的读取权限信息、数据地址信息、令牌编码中的至少一者。
也就是说,当第二核心请求访问第一核心簇中的核心中的私有数据时,由第一核心簇中的主核心进行统一调度和控制。例如,第一核心簇中的主核心根据第二核心的请求信令生成令牌,第一核心簇中的核心只允许持有有效令牌的第二核心访问其私有数据, 从而能够保证数据安全。
在一些实施例中,如果第二核心想要读取第一核心簇中的目标核心的数据,则可向第一核心簇的主核心(即第一核心)发送读取目标核心的数据的信令(即第一请求信令)。第一核心在接收到该第一请求信令后,可根据情况确定是否赋予第二核心读取权限;如果确定不赋予第二核心读取权限,则可直接返回拒绝读取数据的信息。本公开对赋予第二核心读取权限的具体条件不作限制。
在一些实施例中,如果确定赋予第二核心读取权限,则可根据第一请求信令生成验证令牌。该验证令牌携带有第二核心的身份标识、第二核心的读取权限信息、数据地址信息、令牌编码中的至少一者。其中,第二核心的身份标识(ID)可为第二核心在众核系统中的编号;读取权限信息可指示第二核心具有读取目标核心的数据的权限;数据地址信息可指示第二核心可读取的数据的存储地址;令牌编码可指示该验证令牌的编号。本公开对验证令牌的生成方式及其包括的内容均不作限制。
在一些实施例中,第一核心在生成验证令牌后,可将验证令牌通过片上网络发送到第二核心,以使第二核心根据验证令牌向目标核心请求读取数据。
通过这种方式,能够提高数据读取的安全性。
在一些实施例中,所述第一核心为从核心,所述第一请求信令包括请求读取所述第一核心的数据的信令。其中,步骤S11包括:
获取所述第二核心发送的第一请求信令和验证令牌;判断所述验证令牌是否有效;在所述验证令牌有效的情况下,获取所述第一请求信令指向的数据,
其中,所述验证令牌携带有所述第二核心的身份标识、所述第二核心的读取权限信息、数据地址信息、令牌编码中的至少一者。
也就是说,在第二核心从第一核心簇的主核心获取到验证令牌后,可向相应的从核心(即第一核心)请求读取该核心的数据。其中,第二核心可将第一请求信令和验证令牌一起发送到第一核心,即,第一核心同步接收第一请求信令和验证令牌。
在一些实施例中,第二核心还可根据验证令牌生成新的第一请求信令,并发送到第一核心,第一核心通过解析该新的第一请求信令获取验证令牌,本公开对具体的处理方式不作限制。
在一些实施例中,第一核心(从核心)可判断验证令牌是否有效。例如,可以根据验证令牌中携带的第二核心的身份标识对第二核心的身份进行验证;可以根据验证令牌中携带的令牌编码对验证令牌的真实性进行验证;还可以根据验证令牌中携带的读取权限信息、数据地址信息对第二核心是否具有请求信令指向的数据的访问权限进行验证。本公开对具体的验证方式不作限制。
在一些实施例中,如果验证令牌无效,则可直接返回拒绝读取数据的信息。如果验证令牌有效,则可读取该第一请求信令请求读取的数据,生成相应的数据包等,并在步骤S12中将数据包通过片上网络发送到第二核心,从而完成数据读取的过程。
通过这种方式,能够实现不同核心簇的私有数据的访问,提高执行计算任务的灵活 性。
在本公开实施例中,第二核心还可以实现第一核心簇中主核心或从核心的友元数据的访问。
在一些实施例中,步骤S11可包括:
在接收到所述第一请求信令的情况下,判断所述第二核心归属的核心簇是否处于所述第一核心的友元列表中,所述友元列表中包括友元核心簇的标识信息,所述友元核心簇中的核心具有读取所述第一核心归属的核心簇中的核心的数据的权限;
在所述第二核心归属的核心簇处于所述第一核心的友元列表中的情况下,获取所述第一请求信令指向的数据。
举例来说,核心簇中各个核心中可预先设置有友元列表,友元列表中包括友元核心簇的标识信息,友元核心簇中的核心具有读取第一核心归属的核心簇(即第一核心簇)中的核心的数据的权限。例如,友元核心簇可以是身份可信任的核心簇,也可以是与第一核心簇数据交互频繁的核心簇。本公开对友元核心簇的限定方式不作限制。
在一些实施例中,满足条件的任意两个核心簇可互为友元核心簇,也可以为单向的友元核心簇,例如核心簇C为核心簇D的友元核心簇,而核心簇D不为核心簇C的友元核心簇。友元核心簇中的各个核心可称为友元核心,友元核心可读取的数据可称为友元数据。本公开对友元核心簇的条件及友元核心簇之间的具体关系不作限制。
在一些实施例中,第一核心在接收到第一请求信令的情况下,可判断第二核心归属的核心簇(第二核心簇)是否处于第一核心的友元列表中;如果未处于第一核心的友元列表中,则可直接返回拒绝读取数据的信息;如果处于第一核心的友元列表中,则可读取该第一请求信令请求读取的数据,生成相应的数据包等,并在步骤S12中将数据包通过片上网络发送到第二核心,从而完成数据读取的过程。
在一些实施例中,第一核心为第一核心簇中的主核心,所述数据传输方法还包括:向第一核心归属的核心簇中的从核心发送设置友元列表的指令。
也就是说,如果第一核心为第一核心簇中的主核心,则第一核心可为自身设置友元列表,并向第一核心归属的第一核心簇中的从核心发送设置友元列表的指令,以使各个从核心设置友元列表。
这样,能够使得第一核心簇中的各个核心均能够根据友元列表判断第二核心是否为友元核心簇中的核心,实现友元数据的直接访问。
在一些实施例中,第一核心为第一核心簇中的从核心,所述数据传输方法还包括:根据第一核心归属的核心簇的主核心的指令设置友元列表。
也就是说,如果第一核心为第一核心簇中的从核心,则第一核心可根据第一核心归属的第一核心簇的主核心的指令设置友元列表,以便根据友元列表判断第二核心是否为友元核心簇中的核心,实现友元数据的直接访问。
通过上述的处理方式,可以实现友元数据的直接访问,从而提高数据交互效率,进一步提高核心簇之间数据访问的灵活性。
根据本公开的实施例,还提供了一种基于众核系统的数据传输方法,该众核系统包括预先配置的多个核心簇,每个核心簇包括多个核心,该方法应用于发送侧的核心,称为第二核心,该第二核心为任一核心簇中的核心。
图3是本公开实施例中一种数据传输方法的流程图。参照图3,所述方法包括:
在步骤S31中,向第一核心发送第一请求信令,所述第二核心与所述第一核心归属于不同的核心簇;
在步骤S32中,在接收到所述第一核心针对所述第一请求信令的响应信息的情况下,获取所述第一请求信令指向的数据。
举例来说,第二核心可在步骤S31中向第一核心发送第一请求信令。其中,第二核心可以是核心簇中的主核心,也可以是核心簇中的从核心,本公开实施例对此不做限定。第一请求指令可以为请求获取配置信息的信令,也可以为请求读取核心中数据的信令。
在一些实施例中,在第一请求指令为请求获取配置信息的信令时,第一请求指令指向的数据即为配置信息;在第一请求指令为请求获取核心中数据的信令时,第一请求指令指向的数据可以是私有数据,也可以是友元数据,还可以是公有数据;此外,第一请求指令指向的数据还可以是完成核心簇间数据交互所需要的其他信息。本公开实施例对此不做限定。
在一些实施例中,对于公有数据,第二核心可以直接从第一核心中读取;对于私有数据或友元数据,本公开实施例配置有专有接口,通过专有接口读取相应的私有数据或友元数据。
在一些实施例中,第一核心响应于第二核心发送的第一请求信令,可获取第一请求信令指向的数据。如果第一请求信令请求获取配置信息或请求获取公有数据,则可直接确定相应的数据;如果第一请求信令请求获取私有数据,则可根据情况确定是否赋予第二核心读取权限,并在赋予读取权限时生成验证令牌;如果第一请求信令请求获取友元数据,则可根据情况判断第二核心判断第二核心是否具有读取权限,并在具有读取权限时返回相应的响应信息。
在一些实施例中,第一核心可通过片上网络向第二核心传输针对第一请求信令的响应信息,响应信息可以为第一请求信令指向的数据,也可以为用于验证读取权限的验证令牌,本公开对此不作限制。
在一些实施例中,在步骤S32中,第二核心在接收到响应信息的情况下,可获取所述第一请求信令指向的数据。例如直接确定出响应信息中读取到的数据,或者根据响应信息中的验证令牌,向具有待读取数据的目标核心请求数据。
本公开实施例提供的数据传输方法中,众核系统中的核心能够从与第二核心归属于不同核心簇的核心发送请求信令,根据相应的响应信息获取数据,从而实现不同核心簇之间的数据交互,提高了核心在处理计算任务时的灵活性,提升了众核系统的运算能力。
在本公开实施例中,第二核心可以访问第一核心簇中的核心(主核心或从核心)中的配置信息。
在一些实施例中,所述第一请求信令包括请求获取配置信息的信令,所述配置信息包括第二核心完成运算任务所需要的算子、参数、权限范围信息中的至少一者,
其中,所述响应信息包括所述第一请求信令请求获取的配置信息。
也就是说,如果第一请求信令为请求获取配置信息的信令,则第一核心可直接读取第一请求信令指向的配置信息,生成响应信息并通过片上网络将该响应信息传输到第二核心。第二核心在接收到响应信息后,可在步骤S32中,根据响应信息直接获取配置信息。通过这种方式,能够实现配置信息的交互。
在本公开实施例中,第二核心可以访问第一核心簇中的核心的私有数据。
在一些实施例中,所述第一核心为主核心,所述第一请求信令包括请求读取目标核心的数据的信令,所述目标核心与所述第一核心归属于同一核心簇,所述响应信息包括针对所述目标核心的验证令牌。其中,步骤S32可包括:
向所述目标核心发送第一请求信令及所述验证令牌,以使所述目标核心验证所述验证令牌是否有效,并在所述验证令牌有效的情况下获取所述第一请求信令请求读取的数据;接收所述目标核心发送的、所述第一请求信令请求读取的数据,
其中,所述验证令牌携带有所述第二核心的身份标识、所述第二核心的读取权限信息、数据地址信息、令牌编码中的至少一者。
也就是说,当第二核心想要访问第一核心簇中从核心的私有数据时,需要先向第一核心簇中的主核心申请验证令牌,然后利用验证令牌访问第一核心簇中从核心的私有数据。
在一些实施例中,第二核心可向第一核心簇的主核心(即第一核心)发送读取目标核心的数据的信令(即第一请求信令)。第一核心在接收到该第一请求信令后,可根据情况确定是否赋予第二核心读取权限;如果确定不赋予第二核心读取权限,则可直接返回拒绝读取数据的信息。本公开对赋予第二核心读取权限的具体条件不作限制。
在一些实施例中,如果第一核心确定赋予第二核心读取权限,则可根据第一请求信令生成验证令牌。第一核心可根据验证令牌生成响应信息,并发送到第二核心。
在一些实施例中,该验证令牌携带有第二核心的身份标识、第二核心的读取权限信息、数据地址信息、令牌编码中的至少一者。其中,第二核心的身份标识(ID)可为第二核心在众核系统中的编号;读取权限信息可指示第二核心具有读取目标核心的数据的权限;数据地址信息可指示第二核心可读取的数据的存储地址;令牌编码可指示该验证令牌的编号。本公开对验证令牌的生成方式及其包括的内容均不作限制。
在一些实施例中,第二核心在接收到响应信息后,根据验证令牌,可向目标核心请求读取数据。其中,第二核心可将第一请求信令和验证令牌一起发送到目标核心,即,目标核心同步接收第一请求信令和验证令牌。在一些实施例中,第二核心还可根据验证令牌生成新的第一请求信令,并发送到目标核心,目标核心通过解析该新的第一请求信令获取验证令牌。本公开对具体的处理方式不作限制。
在一些实施例中,目标核心(从核心)可判断验证令牌是否有效。验证令牌的验证 方式与前面描述的方式类似,此处不再重复描述。在一些实施例中,如果验证令牌无效,则可直接返回拒绝读取数据的信息。如果验证令牌有效,则可读取该第一请求信令请求读取的数据,生成相应的数据包并发送到第二核心,从而完成数据读取的过程。
在一些实施例中,第二核心可接收目标核心发送的、第一请求信令请求读取的数据,从而根据该数据执行相应的处理。
通过这种方式,能够实现不同核心簇的私有数据的访问,提高执行计算任务的灵活性。
在本公开实施例中,第二核心还可以实现第一核心簇中主核心或从核心的友元数据的访问。
在一些实施例中,所述第一请求信令包括请求读取所述第一核心的数据的信令,所述第一核心中设置有友元列表,所述友元列表中包括友元核心簇的标识信息,所述友元核心簇中的核心具有读取所述第一核心归属的核心簇中的核心的数据的权限;
其中,在所述第二核心归属的核心簇处于所述友元列表中的情况下,所述响应信息包括所述第一请求信令请求读取的数据。
举例来说,第一核心中可预先设置有友元列表,友元列表中包括友元核心簇的标识信息,友元核心簇中的核心具有读取第一核心归属的核心簇(即第一核心簇)中的核心的数据的权限。
在一些实施例中,如果第一核心为第一核心簇中的主核心,则可为自身设置友元列表,并向第一核心簇中的从核心发送设置友元列表的指令,以使各个从核心设置友元列表;如果第一核心为第一核心簇中的从核心,则可根据主核心的指令设置友元列表。
在一些实施例中,第二核心可在步骤S31中直接向第一核心(主核心或从核心)发送第一请求信令,请求读取第一核心的数据。第一核心在接收到第一请求信令时,可判断第二核心归属的核心簇(第二核心簇)是否处于第一核心的友元列表中;如果未处于第一核心的友元列表中,则可直接返回拒绝读取数据的信息;如果处于第一核心的友元列表中,则可读取该第一请求信令请求读取的数据,生成响应信息并发送到第二核心,从而完成数据读取的过程。
在一些实施例中,第二核心接收到响应信息后,可在步骤S32中,根据响应信息直接获取到请求读取的数据。
通过这种方式,可以实现友元数据的直接访问,从而提高数据交互效率,进一步提高核心簇之间数据访问的灵活性。
根据本公开的实施例,还提供了一种基于众核系统的数据传输装置。该众核系统包括预先配置的多个核心簇,每个核心簇包括多个核心,该装置应用于接收侧的核心,称为第一核心,该第一核心为任一核心簇中的核心。
图4是本公开实施例中一种数据传输装置的组成框图。参照图4,该装置包括:
数据获取模块41,用于响应于第二核心发送的第一请求信令,获取所述第一请求信令指向的数据,所述第二核心与所述第一核心归属于不同的核心簇;
数据传输模块42,用于将所述第一请求信令指向的数据传输到所述第二核心。
在一些实施例中,所述第一请求信令包括请求获取配置信息的信令;所述数据获取模块,用于:读取所述第一请求信令指向的配置信息,所述配置信息包括所述第二核心完成运算任务所需要的算子、参数、权限范围信息中的至少一者。
在一些实施例中,所述众核系统的核心簇包括主核心和从核心,所述第一核心为主核心,所述第一请求信令包括请求读取目标核心的数据的信令,所述目标核心与所述第一核心归属于同一核心簇,
所述数据获取模块,用于:根据所述第二核心发送的第一请求信令,生成验证令牌;向所述第二核心发送所述验证令牌,以使所述第二核心根据所述验证令牌向所述目标核心请求读取数据;其中,所述验证令牌携带有所述第二核心的身份标识、所述第二核心的读取权限信息、数据地址信息、令牌编码中的至少一者。
在一些实施例中,所述众核系统的核心簇包括主核心和从核心,所述第一核心为从核心,所述第一请求信令包括请求读取所述第一核心的数据的信令,
所述数据获取模块,用于:获取所述第二核心发送的第一请求信令和验证令牌;判断所述验证令牌是否有效;在所述验证令牌有效的情况下,获取所述第一请求信令指向的数据,其中,所述验证令牌携带有所述第二核心的身份标识、所述第二核心的读取权限信息、数据地址信息、令牌编码中的至少一者。
在一些实施例中,所述数据获取模块,用于:在接收到所述第一请求信令的情况下,判断所述第二核心归属的核心簇是否处于所述第一核心的友元列表中,所述友元列表中包括友元核心簇的标识信息,所述友元核心簇中的核心具有读取所述第一核心归属的核心簇中的核心的数据的权限;在所述第二核心归属的核心簇处于所述第一核心的友元列表中的情况下,获取所述第一请求信令指向的数据。
根据本公开的实施例,还提供了一种基于众核系统的数据传输装置。该众核系统包括预先配置的多个核心簇,每个核心簇包括多个核心,该装置应用于发送侧的核心,称为第二核心,该第二核心为任一核心簇中的核心。该装置包括:
信令发送模块,用于向第一核心发送第一请求信令,所述第二核心与所述第一核心归属于不同的核心簇;
获取模块,用于在接收到所述第一核心针对所述第一请求信令的响应信息的情况下,获取所述第一请求信令指向的数据。
在一些实施例中,所述第一请求信令包括请求获取配置信息的信令,所述配置信息包括第二核心完成运算任务所需要的算子、参数、权限范围信息中的至少一者,其中,所述响应信息包括所述第一请求信令请求获取的配置信息。
在一些实施例中,所述核心簇包括主核心和从核心,所述第一核心为主核心,所述第一请求信令包括请求读取目标核心的数据的信令,所述目标核心与所述第一核心归属于同一核心簇,所述响应信息包括针对所述目标核心的验证令牌,
所述获取模块,用于:向所述目标核心发送第一请求信令及所述验证令牌,以使所 述目标核心验证所述验证令牌是否有效,并在所述验证令牌有效的情况下获取所述第一请求信令请求读取的数据;接收所述目标核心发送的、所述第一请求信令请求读取的数据,其中,所述验证令牌携带有所述第二核心的身份标识、所述第二核心的读取权限信息、数据地址信息、令牌编码中的至少一者。
在一些实施例中,所述第一请求信令包括请求读取所述第一核心的数据的信令,所述第一核心中设置有友元列表,所述友元列表中包括友元核心簇的标识信息,所述友元核心簇中的核心具有读取所述第一核心归属的核心簇中的核心的数据的权限;其中,在所述第二核心归属的核心簇处于所述友元列表中的情况下,所述响应信息包括所述第一请求信令请求读取的数据。
图5是本公开实施例中一种核心的组成框图。参照图5,本公开实施例还提供一种核心,应用于众核系统,其包括:
一个或多个处理单元101;
存储单元102,其上存储有一个或多个程序,当一个或多个程序被一个或多个处理单元执行,使得一个或多个处理单元实现上述的数据传输方法;
其中,处理器101为具有数据处理能力的器件,其包括但不限于运算器等;存储器102为具有数据存储能力的器件,其包括但不限于随机存取存储器(RAM)、只读存储器(ROM)、带电可擦可编程只读存储器(EEPROM)、闪存(FLASH)。
根据本公开的实施例,还提供一种计算机可读介质,其上存储有计算机程序,程序被处理器执行时实现上述的数据传输方法。
图6是本公开实施例中一种电子设备的组成框图。参照图6,本公开实施例还提供一种电子设备,包括:
多个核心201;以及
片上网络202,被配置为交互所述多个核心201间的数据和外部数据;
一个或多个所述核心201中存储有一个或多个指令,一个或多个所述指令被一个或多个所述核心201执行,以使一个或多个所述核心201能够执行上述的数据传输方法。
根据本公开的实施例,还提供一种计算机程序产品,所述计算机程序产品在计算机上运行时,使得计算机执行上述的数据传输方法。
为了使本领域技术人员能够更清楚地理解本公开实施例提供的技术方案,下面通过具体的实施例,对本公开实施例提供的技术方案进行详细说明:
第二核心向第一核心簇中的第一核心发起请求信令,请求获取配置信息,第一核心为第一核心簇的主核心或从核心;第一核心响应于请求信令,读取请求信令指向的配置信息;第一核心将配置信息传输到第二核心。
第二核心向第一核心簇的主核心发起请求信令,请求获取能够读取目标核心的数据的验证令牌,目标核心为第一核心簇中主核心以外的任一核心;
第一核心簇的主核心响应于请求信令,返回给第二核心一个验证令牌;
第二核心向目标核心发起请求信令,同时将验证令牌发送给目标核心;
目标核心响应于请求信令,对验证令牌进行解译,判断令牌是否有效;若有效,则将请求信令指向的数据通过片上网络发给第二核心;若无效,则拒绝。
第二核心向第一核心簇中的第一核心(主核心或从核心)发起请求信令,请求读取第一核心的数据;
第一核心在接收到第二核心获取数据的请求信令时,判断第二核心归属的核心簇是否处于第一核心的友元列表中;如果友元列表中包括第二核心所在核心簇的标识信息,则将请求信令指向的数据发送给第二核心;若不包括,则拒绝;
其中,如果第一核心为主核心,则第一核心可预先为自身设置友元列表,并向第一核心簇中的从核心发送设置友元列表的指令,以使各个从核心设置友元列表;如果第一核心为从核心,则可根据主核心的指令设置友元列表。
本领域普通技术人员可以理解,上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中,在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分;例如,一个物理组件可以具有多个功能,或者一个功能或步骤可以由若干物理组件合作执行。某些物理组件或所有物理组件可以被实施为由处理器,如中央处理器、数字信号处理器或微处理器执行的软件,或者被实施为硬件,或者被实施为集成电路,如专用集成电路。这样的软件可以分布在计算机可读介质上,计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的,术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其它数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其它存储器技术、CD-ROM、数字多功能盘(DVD)或其它光盘存储、磁盒、磁带、磁盘存储或其它磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其它的介质。此外,本领域普通技术人员公知的是,通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其它传输机制之类的调制数据信号中的其它数据,并且可包括任何信息递送介质。
本文已经公开了示例实施例,并且虽然采用了具体术语,但它们仅用于并仅应当被解释为一般说明性含义,并且不用于限制的目的。在一些实例中,对本领域技术人员显而易见的是,除非另外明确指出,否则可单独使用与特定实施例相结合描述的特征、特性和/或元素,或可与其它实施例相结合描述的特征、特性和/或元件组合使用。因此,本领域技术人员将理解,在不脱离由所附的权利要求阐明的本公开的范围的情况下,可进行各种形式和细节上的改变。

Claims (13)

  1. 一种基于众核系统的数据传输方法,其中,所述众核系统包括预先配置的多个核心簇,每个所述核心簇包括多个核心,所述方法应用于第一核心,所述第一核心为任一核心簇中的核心,所述方法包括:
    响应于第二核心发送的第一请求信令,获取所述第一请求信令指向的数据,所述第二核心与所述第一核心归属于不同的核心簇;
    将所述第一请求信令指向的数据传输到所述第二核心。
  2. 根据权利要求1所述的数据传输方法,其中,所述第一请求信令包括请求获取配置信息的信令;所述获取所述第一请求信令指向的数据,包括:
    读取所述第一请求信令指向的配置信息,所述配置信息包括所述第二核心完成运算任务所需要的算子、参数、权限范围信息中的至少一者。
  3. 根据权利要求1所述的数据传输方法,其中,所述众核系统的核心簇包括主核心和从核心,所述第一核心为主核心,所述第一请求信令包括请求读取目标核心的数据的信令,所述目标核心与所述第一核心归属于同一核心簇,
    所述响应于第二核心发送的第一请求信令,获取所述第一请求信令指向的数据,包括:
    根据所述第二核心发送的第一请求信令,生成验证令牌;
    向所述第二核心发送所述验证令牌,以使所述第二核心根据所述验证令牌向所述目标核心请求读取数据;
    其中,所述验证令牌携带有所述第二核心的身份标识、所述第二核心的读取权限信息、数据地址信息、令牌编码中的至少一者。
  4. 根据权利要求1所述的数据传输方法,其中,所述众核系统的核心簇包括主核心和从核心,所述第一核心为从核心,所述第一请求信令包括请求读取所述第一核心的数据的信令,
    所述响应于所述第二核心发送的第一请求信令,获取所述第一请求信令指向的数据,包括:
    获取所述第二核心发送的第一请求信令和验证令牌;
    判断所述验证令牌是否有效;
    在所述验证令牌有效的情况下,获取所述第一请求信令指向的数据,
    其中,所述验证令牌携带有所述第二核心的身份标识、所述第二核心的读取权限信息、数据地址信息、令牌编码中的至少一者。
  5. 根据权利要求1所述的数据传输方法,其中,所述响应于第二核心发送的第一请求信令,获取所述第一请求信令指向的数据,包括:
    在接收到所述第一请求信令的情况下,判断所述第二核心归属的核心簇是否处于所述第一核心的友元列表中,所述友元列表中包括友元核心簇的标识信息,所述友元核心簇中的核心具有读取所述第一核心归属的核心簇中的核心的数据的权限;
    在所述第二核心归属的核心簇处于所述第一核心的友元列表中的情况下,获取所述第一请求信令指向的数据。
  6. 一种基于众核系统的数据传输方法,其中,所述众核系统包括预先配置的多个核心簇,每个所述核心簇包括多个核心,所述方法应用于第二核心,所述第二核心为任一核心簇中的核心,所述方法包括:
    向第一核心发送第一请求信令,所述第二核心与所述第一核心归属于不同的核心簇;
    在接收到所述第一核心针对所述第一请求信令的响应信息的情况下,获取所述第一请求信令指向的数据。
  7. 根据权利要求6所述的数据传输方法,其中,所述第一请求信令包括请求获取配置信息的信令,所述配置信息包括第二核心完成运算任务所需要的算子、参数、权限范围信息中的至少一者,
    其中,所述响应信息包括所述第一请求信令请求获取的配置信息。
  8. 根据权利要求6所述的数据传输方法,其中,所述核心簇包括主核心和从核心,所述第一核心为主核心,所述第一请求信令包括请求读取目标核心的数据的信令,所述目标核心与所述第一核心归属于同一核心簇,所述响应信息包括针对所述目标核心的验证令牌,
    所述在接收到所述第一核心针对所述第一请求信令的响应信息的情况下,获取所述第一请求信令指向的数据,包括:
    向所述目标核心发送第一请求信令及所述验证令牌,以使所述目标核心验证所述验证令牌是否有效,并在所述验证令牌有效的情况下获取所述第一请求信令请求读取的数据;
    接收所述目标核心发送的、所述第一请求信令请求读取的数据,
    其中,所述验证令牌携带有所述第二核心的身份标识、所述第二核心的读取权限信息、数据地址信息、令牌编码中的至少一者。
  9. 根据权利要求6所述的数据传输方法,其中,所述第一请求信令包括请求读取所述第一核心的数据的信令,所述第一核心中设置有友元列表,所述友元列表中包括友元核心簇的标识信息,所述友元核心簇中的核心具有读取所述第一核心归属的核心簇中的 核心的数据的权限;
    其中,在所述第二核心归属的核心簇处于所述友元列表中的情况下,所述响应信息包括所述第一请求信令请求读取的数据。
  10. 一种核心,应用于众核系统,所述核心包括:
    一个或多个处理单元;
    存储单元,其上存储有一个或多个程序,当所述一个或多个程序被所述一个或多个处理单元执行,使得所述一个或多个处理单元实现根据权利要求1-5中任意一项所述的数据传输方法,和/或根据权利要求6-9中任意一项所述的数据传输方法。
  11. 一种计算机可读介质,其上存储有计算机程序,所述计算机程序被处理器执行时实现根据权利要求1-5中任意一项所述的数据传输方法,和/或根据权利要求6-9中任意一项所述的数据传输方法。
  12. 一种电子设备,包括:
    多个核心;以及
    片上网络,被配置为交互所述多个核心间的数据和外部数据;
    一个或多个所述核心中存储有一个或多个指令,一个或多个所述指令被一个或多个所述核心执行,以使一个或多个所述核心能够执行根据权利要求1-5中任意一项所述的数据传输方法,和/或根据权利要求6-9中任意一项所述的数据传输方法。
  13. 一种计算机程序产品,所述计算机程序产品在计算机上运行时,使得计算机执行根据权利要求1-5中任意一项所述的数据传输方法,和/或根据权利要求6-9中任意一项所述的数据传输方法。
PCT/CN2021/132381 2020-11-24 2021-11-23 数据传输方法、核心、计算机可读介质、电子设备 WO2022111462A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011333155.9A CN114546927B (zh) 2020-11-24 2020-11-24 数据传输方法、核心、计算机可读介质、电子设备
CN202011333155.9 2020-11-24

Publications (1)

Publication Number Publication Date
WO2022111462A1 true WO2022111462A1 (zh) 2022-06-02

Family

ID=81659837

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/132381 WO2022111462A1 (zh) 2020-11-24 2021-11-23 数据传输方法、核心、计算机可读介质、电子设备

Country Status (2)

Country Link
CN (1) CN114546927B (zh)
WO (1) WO2022111462A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101802790A (zh) * 2007-09-21 2010-08-11 美普思科技公司 对多个一致域的支持
CN105988970A (zh) * 2015-02-12 2016-10-05 华为技术有限公司 共享存储数据的处理器和芯片
CN108322366A (zh) * 2017-01-17 2018-07-24 阿里巴巴集团控股有限公司 接入网络的方法、装置和系统
CN111381885A (zh) * 2018-12-29 2020-07-07 畅想芯科有限公司 非对称多核异构并行处理系统
WO2020225615A1 (en) * 2019-05-09 2020-11-12 International Business Machines Corporation Executing multiple data requests of multiple-core processors

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9569634B1 (en) * 2013-12-16 2017-02-14 Amazon Technologies, Inc. Fine-grained structured data store access using federated identity management
US10515049B1 (en) * 2017-07-01 2019-12-24 Intel Corporation Memory circuits and methods for distributed memory hazard detection and error recovery
US10579531B2 (en) * 2017-08-30 2020-03-03 Oracle International Corporation Multi-line data prefetching using dynamic prefetch depth
CN108132834B (zh) * 2017-12-08 2020-08-18 西安交通大学 多级共享高速缓冲存储器架构下的任务分配方法和系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101802790A (zh) * 2007-09-21 2010-08-11 美普思科技公司 对多个一致域的支持
CN105988970A (zh) * 2015-02-12 2016-10-05 华为技术有限公司 共享存储数据的处理器和芯片
CN108322366A (zh) * 2017-01-17 2018-07-24 阿里巴巴集团控股有限公司 接入网络的方法、装置和系统
CN111381885A (zh) * 2018-12-29 2020-07-07 畅想芯科有限公司 非对称多核异构并行处理系统
WO2020225615A1 (en) * 2019-05-09 2020-11-12 International Business Machines Corporation Executing multiple data requests of multiple-core processors

Also Published As

Publication number Publication date
CN114546927A (zh) 2022-05-27
CN114546927B (zh) 2023-08-08

Similar Documents

Publication Publication Date Title
US20210099516A1 (en) Technologies for transparent function as a service arbitration for edge systems
CN108924125B (zh) 接口调用权限的控制方法、装置、计算机设备和存储介质
CN109561226B (zh) 一种api混合多租户路由方法、系统和api网关
EP3056028B1 (en) Method and apparatus for providing a data feed for internet of things
US9444803B2 (en) Authentication method and system oriented to heterogeneous network
US20170329978A1 (en) Device and methods for management and access of distributed data sources
CN108881228B (zh) 云端注册激活方法、装置、设备和存储介质
US20160261607A1 (en) Techniques for identity-enabled interface deployment
WO2018063666A1 (en) System and method for digital brokerage service for iot micro compute services
US20050117587A1 (en) Distributed computing system for resource reservation and user verification
CN111552936A (zh) 一种基于调度机构级别的跨系统访问权限控制方法及系统
JP2024105429A (ja) 証明書管理システムのサービス品質の提供
GB2599273A (en) Fine-grained token based access control
JP2017519308A (ja) マルチテナントアプリケーションサーバ環境におけるワークマネージャを提供するためのシステムおよび方法
CN111756542A (zh) 用于对边缘设备信任链进行加速编排和证明的技术
CN111526111B (zh) 登录轻应用的控制方法、装置和设备及计算机存储介质
US20180007024A1 (en) Methods and apparatus for obtaining a scoped token
EP4260517A1 (en) Pervasive resource identification
WO2022111462A1 (zh) 数据传输方法、核心、计算机可读介质、电子设备
US20220060328A1 (en) Method and apparatus for supporting secure data routing
JPWO2020225616A5 (zh)
WO2023015574A1 (zh) 用于账号关联的方法、装置、计算机设备及存储介质
CN103312505A (zh) 一种易用的单点登录实现的构建方法
WO2016139911A1 (ja) 情報処理装置、情報処理方法及びプログラムを格納した非一時的なコンピュータ可読媒体
WO2021124342A1 (en) Resource authorization

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: 21896963

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 200923)

122 Ep: pct application non-entry in european phase

Ref document number: 21896963

Country of ref document: EP

Kind code of ref document: A1