CN112153021B - Service data acquisition method and device - Google Patents

Service data acquisition method and device Download PDF

Info

Publication number
CN112153021B
CN112153021B CN202010948941.3A CN202010948941A CN112153021B CN 112153021 B CN112153021 B CN 112153021B CN 202010948941 A CN202010948941 A CN 202010948941A CN 112153021 B CN112153021 B CN 112153021B
Authority
CN
China
Prior art keywords
node
service
service data
mec
content provider
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
Application number
CN202010948941.3A
Other languages
Chinese (zh)
Other versions
CN112153021A (en
Inventor
任梦璇
薛淼
刘千仞
王光全
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China United Network Communications Group Co Ltd
Original Assignee
China United Network Communications Group Co Ltd
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 China United Network Communications Group Co Ltd filed Critical China United Network Communications Group Co Ltd
Priority to CN202010948941.3A priority Critical patent/CN112153021B/en
Publication of CN112153021A publication Critical patent/CN112153021A/en
Application granted granted Critical
Publication of CN112153021B publication Critical patent/CN112153021B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H04L63/0442—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption
    • 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/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees

Abstract

The embodiment of the invention provides a service data acquisition method and device, relates to the technical field of communication, and can improve the efficiency of determining a target RH node (namely, an RH node with a connection relation with a MEC node (namely, a first MEC node) storing service data corresponding to a service (such as a first service)) so as to improve the service data acquisition efficiency. The method comprises the following steps: the first MEC node sends a service data registration request message to the first RH node, wherein the service data registration request message comprises a public key hash value corresponding to a first content provider, a service name of a first service and an area identifier corresponding to the first MEC node, and the service data registration request message is used for registering service data corresponding to the first service, and the first service is provided by the first content provider.

Description

Service data acquisition method and device
Technical Field
The embodiment of the invention relates to the technical field of communication, in particular to a method and a device for acquiring service data.
Background
Currently, a User Equipment (UE) may acquire service data based on a data-oriented network architecture (data-oriented (and beyond) network architecture, DONA). Specifically, in the communication system as shown in fig. 1, the content provider 103 may send a register message to the parsing (resolution handler, RH) node 102, the register message being used to register service data that the content provider 103 can provide; the RH node 102 may then notify the RH node 104 that the content provider 103 is able to provide the service data, thus completing the registration process for the service data. Similarly, the content provider 105 and the content provider 106 may also send register messages to the RH node 104 to complete the business data that the content provider 105 and the content provider 106 can provide.
When the content requester 101 needs to acquire service data of a certain service, a find message may be sent to the RH node 102, where the RH node 102 first determines whether the content provider 103 can provide the service data, and if the content provider 103 can provide the service data, acquires the service data from the content provider 103 and returns to the content requester 101; otherwise, determining, by the RH node 104, whether the content provider 105 and the content provider 106 can provide the service data; in the event that the RH node 104 determines that the service data is not present in both the content provider 105 and the content provider 106, it is determined or judged by other RH nodes (not shown) in the network which content provider the service data can be provided from and the service data is returned to the content requester 101.
In the above method, when the content requester 101 needs to acquire service data, all RH nodes in the network may be required to sequentially determine whether a certain service provider can provide the service data, so the efficiency of acquiring the service data may not be high.
Disclosure of Invention
The embodiment of the invention provides a service data acquisition method and device, which improve the efficiency of determining a target RH node (namely, an RH node with a connection relation with a mobile edge computing (mobile edge computing, MEC) node (namely, a first MEC node) of service data corresponding to a stored service (such as a first service)) and further improve the service data acquisition efficiency.
In a first aspect, an embodiment of the present invention provides a method for acquiring service data, including: the method comprises the steps that a first MEC node sends a service data registration request message to a first RH node, wherein the service data registration request message comprises a public key hash value corresponding to a first content provider, a service name of a first service and an area identifier corresponding to the first MEC node, the service data registration request message is used for registering service data corresponding to the first service, and the first service is provided by the first content provider.
In a second aspect, an embodiment of the present invention provides a method for acquiring service data, including: the method comprises the steps that a first RH node receives a service data registration request message of a first MEC node, wherein the service data registration request message comprises a public key hash value corresponding to a first content provider, a service name of a first service and an area identifier corresponding to the first MEC node, the service data registration request message is used for registering service data corresponding to the first service, and the first service is provided by the first content provider; the first RH node sends a service data notification message to a first region RH node, where the service data notification message includes a public key hash value corresponding to the first content provider, a service name of the first service and a region identifier corresponding to the first MEC node, and the service data notification message is used to notify the first region RH node, where service data corresponding to the first service is stored in the first MEC node.
In a third aspect, an embodiment of the present invention provides a method for acquiring service data, including: the method comprises the steps that a first regional RH node receives a service data notification message of the first RH node, wherein the service data notification message comprises a public key hash value corresponding to a first content provider, a service name of a first service and a regional identifier of a first MEC node, the service data notification message is used for notifying the first regional RH node, service data corresponding to the first service is stored in the first MEC node, and the first service is provided by the first content provider.
In a fourth aspect, an embodiment of the present invention provides a service data acquiring apparatus, including: a transmitting module; the sending module is configured to send a service data registration request message to a first RH node, where the service data registration request message includes a public key hash value corresponding to a first content provider, a service name of a first service, and an area identifier corresponding to an acquiring device of the service data, where the service data registration request message is used to register service data corresponding to the first service, and the first service is a service provided by the first content provider.
In a fifth aspect, an embodiment of the present invention provides a service data acquiring apparatus, including: a receiving module and a transmitting module; the receiving module is configured to receive a service data registration request message of a first MEC node, where the service data registration request message includes a public key hash value corresponding to a first content provider, a service name of a first service, and an area identifier corresponding to the first MEC node, where the service data registration request message is used to register service data corresponding to the first service, where the first service is a service provided by the first content provider; the sending module is configured to send a service data notification message to a first regional RH node, where the service data notification message includes a public key hash value corresponding to the first content provider, a service name of the first service, and a regional identifier corresponding to the first MEC node, where the service data notification message is used to notify the first regional RH node, and the first MEC node stores service data corresponding to the first service.
In a sixth aspect, an embodiment of the present invention provides a service data acquiring apparatus, including: a receiving module; the receiving module is configured to receive a service data notification message of a first RH node, where the service data notification message includes a public key hash value corresponding to a first content provider, a service name of a first service, and an area identifier of a first MEC node, where the service data notification message is used to notify an obtaining device of the service data, and the first MEC node stores service data corresponding to the first service, where the first service is a service provided by the first content provider.
In a seventh aspect, an embodiment of the present invention provides another service data acquiring apparatus, including: a processor, a memory, a bus, and a communication interface; the memory is used for storing computer execution instructions, the processor is connected with the memory through a bus, and when the service data acquisition device operates, the processor executes the computer execution instructions stored in the memory, so that the service data acquisition device executes the service data acquisition method provided in the first aspect.
In an eighth aspect, an embodiment of the present invention provides another service data acquiring apparatus, including: a processor, a memory, a bus, and a communication interface; the memory is used for storing computer-executable instructions, and the processor is connected with the memory through a bus, when the service data acquisition device runs, the processor executes the computer-executable instructions stored in the memory, so that the service data acquisition device executes the service data acquisition method provided in the second aspect.
In a ninth aspect, an embodiment of the present invention provides another service data acquiring apparatus, including: a processor, a memory, a bus, and a communication interface; the memory is used for storing computer-executable instructions, and the processor is connected with the memory through a bus, when the service data acquisition device runs, the processor executes the computer-executable instructions stored in the memory, so that the service data acquisition device executes the service data acquisition method provided by the third aspect.
In a tenth aspect, an embodiment of the present invention provides a computer readable storage medium, including a computer program, which when executed on a computer, causes the computer to perform a method for acquiring service data provided in the first aspect.
In an eleventh aspect, an embodiment of the present invention provides a computer readable storage medium including a computer program, which when executed on a computer, causes the computer to perform a method for acquiring service data provided in the second aspect.
In a twelfth aspect, an embodiment of the present invention provides a computer readable storage medium, including a computer program, which when executed on a computer, causes the computer to perform a method for acquiring service data provided in the third aspect.
In a thirteenth aspect, embodiments of the present invention provide a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of acquiring service data of the first aspect and any implementation thereof.
In a fourteenth aspect, embodiments of the present invention provide a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of acquiring traffic data of the second aspect and any one of its implementations described above.
In a fifteenth aspect, embodiments of the present invention provide a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of acquiring business data of the third aspect and any one of its implementations.
In the embodiment of the invention, a first MEC node sends a service data registration request message to a first RH node, wherein the service data registration request message comprises a public key hash value corresponding to a first content provider, a service name of a first service and a region identifier corresponding to the first MEC node; after receiving the service data registration message, the first RH node stores key information of the first service, and sends a service data notification message to the first region RH node, namely notifies the first region RH node, the first MEC node stores service data corresponding to the first service, the service data notification message comprises a public key hash value corresponding to the first content provider, a service name of the first service and a region identifier corresponding to the first MEC node; thus, the first region RH node also obtains the key information of the first service, and stores the key information of the first service. And then, the first regional RH node sends the key information of the first service to other regional RH nodes, so that all regional RH nodes and all RH nodes in the network acquire the key information of the first service, and the registration process of service data corresponding to the first service is completed. Further, after a certain RH node receives an acquisition request message for service data corresponding to a first service sent by a certain MEC node, it may be determined whether there is a certain MEC node (i.e., the first MEC node) in the network that can provide the service data corresponding to the first service based on the public key hash value corresponding to the first content provider and the service name of the first service, and based on the area identifier of the first MEC node, determine an area corresponding to the first MEC node, and acquire the service data corresponding to the first service from the area. In this way, it may not be necessary that all RH nodes in the network participate in the determining process of the first MEC node, so that efficiency of determining the target RH node (that is, the RH node having a connection relationship with the MEC node (that is, the first MEC node) storing the service data corresponding to the service (for example, the first service) is improved, and further, efficiency of acquiring the service data is improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below.
Fig. 1 is a schematic diagram of a network architecture of a communication system according to an embodiment of the present invention;
fig. 2 is a second network architecture diagram of a communication system according to an embodiment of the present invention;
fig. 3 is a schematic hardware diagram of a server according to an embodiment of the present invention;
fig. 4 is a schematic diagram one of a method for acquiring service data according to an embodiment of the present invention;
fig. 5 is a schematic diagram two of a method for acquiring service data according to an embodiment of the present invention;
fig. 6 is a schematic diagram III of a method for acquiring service data according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a first MEC node according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram ii of a first MEC node according to an embodiment of the present invention;
fig. 9 is a schematic structural diagram of a first RH node according to an embodiment of the present invention;
fig. 10 is a schematic diagram ii of a first RH node according to an embodiment of the present invention;
FIG. 11 is a schematic diagram of a first RH node in a first region according to an embodiment of the present invention;
Fig. 12 is a schematic diagram of a second structure of an RH node in a first region according to an embodiment of the present invention.
Detailed Description
The method and device for acquiring service data provided by the embodiment of the invention are described in detail below with reference to the accompanying drawings.
The terms "first" and "second" and the like in the description and the drawings of the present application are used for distinguishing between different objects and not for describing a particular order of objects, e.g., a first RH node, a second RH node, a third RH node, etc. are used for distinguishing between different RH nodes and not for describing a particular order of RH nodes.
Furthermore, references to the terms "comprising" and "having" and any variations thereof in the description of the present application are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed but may optionally include other steps or elements not listed or inherent to such process, method, article, or apparatus.
It should be noted that, in the embodiments of the present invention, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g." in an embodiment of the present invention is not to be taken as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.
The term "and/or" as used herein includes the use of either or both of these methods.
In the description of the present application, unless otherwise indicated, the meaning of "a plurality" means two or more.
Based on the problems existing in the background technology, the embodiment of the invention provides a method and a device for acquiring service data, wherein a first MEC node sends a service data registration request message to a first RH node, and the service data registration request message comprises a public key hash value corresponding to a first content provider, a service name of a first service and a region identifier corresponding to the first MEC node; after receiving the service data registration message, the first RH node stores key information of the first service, and sends a service data notification message to the first region RH node, namely notifies the first region RH node, the first MEC node stores service data corresponding to the first service, the service data notification message comprises a public key hash value corresponding to the first content provider, a service name of the first service and a region identifier corresponding to the first MEC node; thus, the first region RH node also obtains the key information of the first service, and stores the key information of the first service. And then, the first regional RH node sends the key information of the first service to other regional RH nodes, so that all regional RH nodes and all RH nodes in the network acquire the key information of the first service, and the registration process of service data corresponding to the first service is completed. Further, after a certain RH node receives an acquisition request message for service data corresponding to a first service sent by a certain MEC node, it may be determined whether there is a certain MEC node (i.e., the first MEC node) in the network that can provide the service data corresponding to the first service based on the public key hash value corresponding to the first content provider and the service name of the first service, and based on the area identifier of the first MEC node, determine an area corresponding to the first MEC node, and acquire the service data corresponding to the first service from the area. In this way, it may not be necessary that all RH nodes in the network participate in the determining process of the first MEC node, so that efficiency of determining the target RH node (that is, the RH node having a connection relationship with the MEC node (that is, the first MEC node) storing the service data corresponding to the service (for example, the first service) is improved, and further, efficiency of acquiring the service data is improved.
The method and apparatus for acquiring service data provided in the embodiments of the present invention may be applied to a wireless communication system, as shown in fig. 2, where the communication system includes 4 MEC nodes (i.e., MEC node 201, MEC node 202, MEC node 203, and MEC node 204), 3 RH nodes (i.e., RH node 205, RH node 206, and RH node 207), 2 regional RH nodes (i.e., regional RH node 208 and regional RH node 209), and 1 regional transfer device (i.e., regional transfer device 210). In general, in practical applications, the connection between the above-mentioned devices or service functions may be a wireless connection, and for convenience and intuitiveness, the connection relationship between the devices is schematically shown by a solid line in fig. 1.
The MEC node is configured to store service data corresponding to a certain service, for example, the MEC node 201 may store service data corresponding to a first service. In the embodiment of the present invention, the MEC node 201 may send a service data registration request message to the RH node 205 to complete the registration process of the service data corresponding to the first service.
The RH node is configured to store key information of the service, for example, the RH node 205 may store key information of the first service, that is, a public key hash value of the first content provider (i.e., the content provider that provides the first service), a service name of the first service, and an area identifier corresponding to the MEC node 201. In the embodiment of the present invention, the RH node 205 may send a service data notification message to the regional RH node 208 (and the RH node 206), where the service data notification message is used to notify the regional RH node 208 (and the RH node 206), and the MEC node 201 stores service data corresponding to the first service.
The regional RH node is configured to store key information of all services in one region, for example, the regional RH node 208 may store key information of all services in a first region, where the first region is a region corresponding to the MEC node 201. In the embodiment of the present invention, all the region RH nodes, all the RH nodes, and all the MEC nodes in a region correspond to the same region identifier, for example, region RH node 208, RH node 205, RH node 206, MEC node 201, MEC node 202, and MEC node 203 all correspond to the first region.
In the embodiment of the present invention, the region relay device 210 is configured to store a correspondence between a region identifier and an IP address of a region RH node, and the region relay device 210 may determine, according to the region identifier of the target region, the IP address of the region RH node corresponding to the region identifier.
Optionally, the communication system may include one or more MEC nodes, one or more RH nodes, one or more regional RH nodes, and one or more regional relay devices, where the number of each node and device shown in fig. 2 is merely an example, and the number of each node and device in the communication system is not limited in the embodiment of the present invention.
As shown in fig. 3, the RH node provided by the embodiment of the present invention may be a server, and fig. 3 is a schematic hardware structure of the server provided by the embodiment of the present invention. The server 30 includes a processor 301, a memory 302, a network interface 303, and the like.
The processor 301 is a core component of the server 30, and the processor 301 is configured to run an operating system of the server 30 and an application program (including a system application program and a third party application program) on the server 30, so as to implement a method for acquiring service data by the server 30.
In an embodiment of the present invention, the processor 301 may be a central processing unit (central processing unit, CPU), microprocessor, digital signal processor (digital signal processor, DSP), application-specific integrated circuit (application-specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or other programmable logic device, transistor logic device, hardware components, or any combination thereof, capable of implementing or executing the various exemplary logic blocks, modules and circuits described in connection with the disclosure of embodiments of the present invention; a processor may also be a combination that performs computing functions, e.g., including one or more microprocessors, a combination of a DSP and a microprocessor, and the like.
Optionally, the processor 301 of the server 30 includes one or more CPUs, either single-core or multi-core.
Memory 302 includes, but is not limited to, random access memory (random access memory, RAM), read Only Memory (ROM), erasable Programmable Read Only Memory (EPROM), flash memory, or optical memory, among others. The memory 302 stores the code of the operating system.
Optionally, the processor 301 implements the method for obtaining service data in the embodiment of the present invention by reading the instruction stored in the memory 302, or the processor 301 implements the method for obtaining service data provided in the embodiment of the present invention by using an instruction stored in the processor. In the case where the processor 301 implements the method for obtaining service data provided by the embodiment of the present invention by reading the instruction stored in the memory, the instruction for implementing the method for obtaining service data provided by the embodiment of the present invention is stored in the memory.
The network interface 303 is a wired interface such as a fiber-optic distributed data interface (fiber distributed data interface, FDDI), gigabit Ethernet (GE) interface. Alternatively, the network interface 303 is a wireless interface. The network interface 303 is used for the server 30 to communicate with other devices.
The memory 302 is configured to store a public key hash value corresponding to the first content provider and a service name of the first service. Optionally, the memory 302 is further configured to store a public key hash value corresponding to the second content provider and a service name of the second service, and so on. The at least one processor 301 further performs the method described in the embodiment of the present invention based on the public key hash value corresponding to the second content provider and the service name of the second service stored in the memory 302. For more details on the implementation of the above-described functions by the processor 301, reference is made to the description of the various method embodiments described below.
Optionally, the server 30 further comprises a bus, and the processor 301 and the memory 302 are connected to each other by a bus 304, or are connected to each other in other manners.
Optionally, the server 30 further includes an input/output interface 305, where the input/output interface 305 is configured to connect to an input device, and receive a service data acquisition request message input by a user through the input device. Input devices include, but are not limited to, a keyboard, touch screen, microphone, and the like. The input/output interface 305 is further configured to be connected to an output device, and output a result of acquiring the service data by the processor 301 (i.e., the server 30 determines whether to acquire the service data corresponding to the second service from the target MEC node). Output devices include, but are not limited to, displays, printers, and the like.
It should be understood that, in the embodiment of the present invention, the hardware structure of the MEC node and the hardware structure of the regional RH node are similar to those of the server 30 shown in fig. 3, and the description of the hardware structure of the MEC node and the hardware structure of the regional RH node may refer to the description of the hardware structure of the server 30, which is not described in detail herein.
The method and the device for acquiring the service data are applied to the scene of acquiring the service data. Specifically, when a UE (or a content provider) requests to register service data corresponding to a certain service (for example, a first service), a service data registration request message may be sent to a corresponding RH node through an adjacent MEC node, so that the RH node may determine that the MEC node having a connection relationship with the UE may provide service data corresponding to the first service, and then the RH node may send a service data notification message to an regional RH node in the same region and other RH nodes in the region.
After the RH node receives a service data acquisition request message sent by another UE (or a content requester) through an adjacent MEC node (the service data acquisition request message is used for requesting to acquire service data corresponding to the second service), the RH node may determine whether there is a target MEC node capable of providing service data corresponding to the second service, and acquire the service data corresponding to the second service from the target MEC node.
In combination with the communication system shown in fig. 2, the method for acquiring service data provided in the embodiment of the present invention is fully described below from the perspective of interaction between each device in the communication system, so as to illustrate a registration process of service data corresponding to a first service and an acquisition process of service data corresponding to a second service.
As shown in fig. 4, the method for acquiring service data provided in the embodiment of the present invention may include S101-S115.
S101, a first content provider sends a registration verification request message to a content sharing device.
It should be appreciated that the first content provider may provide service data corresponding to the first service, and the authentication request message is used to register the identity of the first content provider and authenticate the service data corresponding to the first service.
S102, the content sharing device sends a registration verification response message to the first content provider.
Wherein the registration verification response message includes the account number, the public key, and the private key of the first content provider.
Optionally, the registration verification response message further includes an IP address of a first MEC node, where the first MEC node is a MEC node that can be accessed by the first content provider.
S103, the first content provider determines a public key hash value corresponding to the first content provider and a service name of the first service.
Specifically, the first content provider may determine its corresponding public key hash value according to the public key of the first content provider, and determine a unique name for the first service, that is, a service name of the first service.
And S104, the first content provider sends the public key hash value corresponding to the first content provider, the service name of the first service and the service data corresponding to the first service to the first MEC node.
In an implementation manner of the embodiment of the present invention, when the first content provider is an intelligent vehicle (or a vehicle-mounted terminal), the service data corresponding to the first service may be road condition information, vehicle driving data, or the like, and the first content provider may send the public key hash value corresponding to the first content provider, the service name of the first service, and the service data corresponding to the first service (e.g., road condition information) to the first MEC node, so that the content requester may directly obtain the service data corresponding to the first service from the first MEC node, and the first MEC node is a new content provider corresponding to the first service at this time.
In another implementation manner of the embodiment of the present invention, when the first content provider is a common UE, the service data corresponding to the first service may be multimedia data, for example, video and audio data. The first content provider may send the public key hash value corresponding to the first content provider and the service name of the first service to the first MEC node, i.e. not send the service data corresponding to the first service. When the content requester needs to acquire service data corresponding to the first service, the service data still needs to be acquired from the original content provider (i.e., the first content provider).
In the following embodiment, the first content provider is used as an intelligent vehicle, that is, the service data acquisition method provided by the embodiment of the present invention is applied to the scene of internet of vehicles, and the service data acquisition method provided by the embodiment of the present invention is introduced.
S105, the first MEC node receives, from the first content provider, a public key hash value corresponding to the first content provider, a service name of the first service, and service data corresponding to the first service.
S106, the first MEC node sends a service data registration request message to the first RH node.
The service data registration request message is used for requesting to register service data corresponding to a first service, wherein the service data registration request message comprises a public key hash value corresponding to the first content provider, a service name of the first service and an area identifier corresponding to a first MEC node, and the first service is provided by the first content provider.
In connection with the above description of the embodiments, it should be understood that the first MEC node becomes a new content provider corresponding to the first service after receiving the public key hash value corresponding to the first content provider, the service name of the first service, and the service data corresponding to the first service, which are sent by the first content provider. The first MEC node may send a service data registration request message to the first RH node, so that the first RH node stores key information of the first service, and notifies all RH nodes and regional RH nodes in the first region (i.e., the region corresponding to the first MEC node), where service data corresponding to the first service is stored.
Note that, the identifiers of the multiple nodes in the same area, including the MEC node, the RH node, and the area corresponding to the area RH node, are the same, for example, in fig. 2, the identifiers of the areas corresponding to the MEC node 201, the MEC node 202, the MEC node 203, the RH node 205, the RH node 206, and the area RH node 208 are the same.
And S107, the first RH node receives the service data registration request message of the first MEC node.
It should be understood that, after receiving the service data registration request message of the first MEC node, the first RH node may store key information of the first service, that is, a public key hash value corresponding to the first content provider, a service name of the first service, and an area identifier corresponding to the first MEC node.
For convenience of illustration, in the following embodiment, P is used a Representing a public key hash value corresponding to an a-th content providerA is an integer greater than or equal to one; by L b B represents the service name of the b-th service, b is an integer greater than or equal to one; by D c And c is an integer greater than or equal to one.
Illustratively, table 1 is one example of key information for a plurality of services stored in a first RH node.
TABLE 1
Figure BDA0002676265050000111
It can be determined from table 1 that key information of 4 services provided by 2 content providers is stored in the first RH node.
S108, the first RH node sends a service data notification message to the first region RH node.
The service data notification message is used for notifying a first regional RH node, and the first MEC node stores service data corresponding to the first service.
It should be understood that the first MEC node, the first RH node, and the first region RH node are all devices in the same region, and in the following embodiments, the region corresponding to the first MEC node, the region corresponding to the first RH node, and the region corresponding to the first region RH node are collectively referred to as a first region.
After the first RH node stores the key information of the first service, the first RH node needs to send the key information of the first service to the first region RH node and other RH nodes in the first region. That is, the first RH node may also send service data notification messages to other RH nodes in the first area, so that all other RH nodes in the first area may determine that service data corresponding to the first service is stored in the first MEC node, and after receiving the service data notification messages, other nodes store key information of the first service.
S109, the RH node in the first area receives the service data notification message of the RH node.
Specifically, the first region RH node may be understood as a parent node of the first RH node (and other RH nodes in the first region), and may store key information of a plurality of services stored in each of a plurality of corresponding RH nodes in the first region. That is, after the first region RH node receives the service data notification message, key information of the first service may be stored; similarly, after the first regional RH node receives the service data notification message sent by the other RH nodes, the first regional RH node may also store the key information of the other services.
Optionally, the first regional RH node may further store a next hop RH node corresponding to the first service and a hop count from the first regional RH node to the first MEC node (n, n is an integer greater than or equal to 2).
Illustratively, in conjunction with table 1 and fig. 2 above, assume that the first RH node illustrated in table 1 is RH node 205 in fig. 2 and the first MEC node is MEC node 201 in fig. 2. Thus, one example of the key information for multiple services stored in the first regional RH node (i.e., regional RH node 208 in FIG. 2) as shown in Table 2 may be obtained.
TABLE 2
Figure BDA0002676265050000131
As can be seen from the above, after passing through the first region RH node (i.e., RH node 208), the first MEC node (i.e., MEC node 201) can be reached by RH node 205.
It can be understood that when the first regional RH node receives the service data notification message of the first RH node and stores the key information of the first service, all the nodes in the first region (including the first regional RH node and other RH nodes in the first region) store the key information of the first service, and then the first regional RH node sends the key information of the first service to the other regional RH nodes, so that the nodes in the whole network (or architecture) complete the registration process of the service data corresponding to the first service, that is, all the regional RH nodes and all the RH nodes in the network store the key information of the first service. After any RH node in the area or any RH node receives the service data acquisition request message sent by the content requester, the MEC node storing the service data corresponding to the first service can be found through the key information of the first service.
In the embodiment of the invention, a first MEC node sends a service data registration request message to a first RH node, wherein the service data registration request message comprises a public key hash value corresponding to a first content provider, a service name of a first service and a region identifier corresponding to the first MEC node; after receiving the service data registration message, the first RH node stores key information of the first service, and sends a service data notification message to the first region RH node, namely notifies the first region RH node, the first MEC node stores service data corresponding to the first service, the service data notification message comprises a public key hash value corresponding to the first content provider, a service name of the first service and a region identifier corresponding to the first MEC node; thus, the first region RH node also obtains the key information of the first service, and stores the key information of the first service. And then, the first regional RH node sends the key information of the first service to other regional RH nodes, so that all regional RH nodes and all RH nodes in the network acquire the key information of the first service, and the registration process of service data corresponding to the first service is completed. Further, after a certain RH node receives an acquisition request message for service data corresponding to a first service sent by a certain MEC node, it may be determined whether there is a certain MEC node (i.e., the first MEC node) in the network that can provide the service data corresponding to the first service based on the public key hash value corresponding to the first content provider and the service name of the first service, and based on the area identifier of the first MEC node, determine an area corresponding to the first MEC node, and acquire the service data corresponding to the first service from the area. In this way, it may not be necessary that all RH nodes in the network participate in the determining process of the first MEC node, so that efficiency of determining the target RH node (that is, the RH node having a connection relationship with the MEC node (that is, the first MEC node) storing the service data corresponding to the service (for example, the first service) is improved, and further, efficiency of acquiring the service data is improved.
And S110, the content requester sends the public key hash value corresponding to the second content provider and the service name of the second service to the first MEC node.
The content requester may be an intelligent vehicle or a common UE. The second content provider is a provider that provides service data corresponding to the second service (i.e., the second service is a service provided by the second content provider).
S111, the first MEC node receives, from the content requester, the public key hash value corresponding to the second content provider and the service name of the second service.
And S112, the first MEC node sends a service data acquisition request message to the first RH node.
The service data acquisition request message includes a public key hash value corresponding to a second content provider, a service name of the second service is identified by an area of a target area, the service data acquisition request message is used for requesting to acquire service data corresponding to the second service, the second service is a service provided by the second content provider, the target area is an area corresponding to a target MEC node, and the target MEC node is an MEC node storing the service data corresponding to the second service.
It should be appreciated that after the first MEC node receives the public key hash value corresponding to the second content provider and the service name of the second service from the content requester, key information of the second service, that is, the public key hash value corresponding to the second content provider, may be sent to the first RH node by the service name of the second service with the area identifier of the target area, so that the first RH node determines whether the target MEC node is one of the at least one MEC node having a connection relationship with the first RH node.
S113, the first RH node receives the service data acquisition request message of the first MEC node.
It should be understood that after the first RH node receives the service data acquisition request message sent by the first MEC node, the first RH node may determine whether service data corresponding to the second service can be acquired through the first RH node based on the key information of the second service and the key information of the plurality of services stored in the first RH node.
And S114, the first RH node determines whether the target MEC node is an MEC node with a connection relation with the first RH node according to the public key hash value corresponding to the second content provider and the service name of the second service.
It should be appreciated that one RH node may be connected to at least one MEC node, and that one MEC node is connected to only one RH node. When a certain MEC node has a connection relationship with a first RH node, it is indicated that the service data stored in the MEC node will notify the regional RH node (including the first regional RH node) or other RH nodes through the first RH node.
In one implementation manner of the embodiment of the present invention, the step S112 may be implemented through step 1 to step 3.
Step 1, the first RH node determines whether target key information exists in key information of a plurality of services stored in the first RH node according to a public key hash value corresponding to the second content provider and a service name of the second service.
The target key information comprises a public key hash value corresponding to the second content provider and a service name of the second service.
It should be understood that when key information of the second service, that is, key information including a corresponding public key hash value of the second content provider and a service name of the second service, exists among key information of the plurality of services stored in the first RH node, the first RH node can determine that the service data corresponding to the second service exists in the network.
And 2, under the condition that the target key information exists in the key information of the plurality of services stored in the first RH node, the first RH node determines whether the hop count from the first RH node to the target MEC node is 1.
It should be understood that the hop count of the first RH node and the target MEC node is 1, which indicates that the next hop device passing through the first RH node is the target MEC node, that is, the first RH node and the target MEC node have a connection relationship; otherwise, the first RH node is an intermediate node, that is, after passing through the first RH node, the first RH node needs to pass through other RH nodes, and then the first RH node can jump to the target MEC node, that is, the first RH node and the target MEC node have no connection relationship.
And 3, under the condition that the first RH node determines that the hop count from the first RH node to the target MEC node is 1, the first RH node determines that the target MEC node is the MEC node with a connection relation with the first RH node.
S115, when the first RH node determines that the target MEC node is the MEC node having the connection relation with the first RH node, the first RH node acquires service data corresponding to the second service from the target MEC node.
It should be understood that, in the case that the first RH node determines that the target MEC node is a MEC node having a connection relationship with the first RH node, it is indicated that no other node (including an area RH node or an RH node) exists between the first RH node and the target MEC node, that is, the next-hop device of the first RH node is the target MEC node, and the first RH node may directly obtain, without going through the other node, service data corresponding to the second service from the target MEC node.
Illustratively, in connection with fig. 2, assume that the first RH node is RH node 205 in fig. 2 and the first MEC node is MEC node 201 in fig. 2. In the case that the RH node 205 determines that the target MEC node is the MEC node 202, the RH node 205 obtains service data corresponding to the second service from the MEC node 202.
In the embodiment of the invention, a first MEC node sends a service data registration request message to a first RH node, wherein the service data registration request message comprises a public key hash value corresponding to a second content provider, a service name of the second service and a region identifier of a target region; after receiving the service data acquisition request message of the first MEC node, the first RH node determines whether the target MEC node is an MEC node in connection with the first RH node according to the public key hash value corresponding to the second content provider and the service name of the second service; and acquiring service data corresponding to the first service from the target MEC node under the condition that the target MEC node is determined to be the MEC node which has a connection relation with the first RH node. In the embodiment of the present invention, a first RH node may determine, according to a public key hash value corresponding to a second content provider and a service name of a second service, whether a target MEC node is a MEC node having a connection relationship with the first RH node, that is, determine whether the target MEC node is a next-hop device of the first RH node, and when the first RH node determines that the target MEC node is the next-hop device of the first RH node, indicate that the target MEC node notifies other RH nodes (or first regional RH nodes) through the first RH node, where service data corresponding to the second service is stored in the target MEC node; furthermore, the first RH node can acquire service data corresponding to the second service from the target MEC node, so that efficiency of the first MEC node in acquiring the service data from the target MEC node through the first RH node can be improved.
As shown in fig. 5, in one implementation manner, the method for acquiring service data provided in the embodiment of the present invention includes S201-S219.
S201, the first content provider transmits a registration verification request message to the content sharing device.
S202, the content sharing device sends a registration verification response message to the first content provider.
S203, the first content provider determines a public key hash value corresponding to the first content provider and a service name of the first service.
S204, the first content provider sends the public key hash value corresponding to the first content provider, the service name of the first service and the service data corresponding to the first service to the first MEC node.
S205, the first MEC node receives, from the first content provider, a public key hash value corresponding to the first content provider, a service name of the first service, and service data corresponding to the first service.
S206, the first MEC node sends a service data registration request message to the first RH node.
S207, the first RH node receives a service data registration request message of the first MEC node.
And S208, the first RH node sends a service data notification message to the first region RH node.
S209, the RH node in the first area receives the service data notification message of the RH node.
And S210, the content requester sends the public key hash value corresponding to the second content provider and the service name of the second service to the first MEC node.
S211, the first MEC node receives the public key hash value corresponding to the second content provider and the service name of the second service from the content requester.
S212, the first MEC node sends a service data acquisition request message to the first RH node.
S213, the first RH node receives the service data acquisition request message of the first MEC node.
And S214, the first RH node determines whether the target MEC node is an MEC node with a connection relation with the first RH node according to the public key hash value corresponding to the second content provider and the service name of the second service.
It should be understood that the explanation of S201-S214 may be referred to the descriptions in S101-S114 above, and will not be repeated here.
S215, when the first RH node determines that the target MEC node is not the MEC node having the connection relationship with the first RH node, the first RH node sends a service data acquisition request message to the first region RH node.
In connection with the above embodiments, it should be understood that the service data acquisition request message includes the public key hash value corresponding to the second content provider, the service name of the second service, and the area identifier of the target area.
S216, the first area RH node receives the service data acquisition request message from the first RH node.
S217, the RH node in the first area determines whether the target MEC node is one MEC node in the first area according to the area identification of the target area.
The first area is an area corresponding to the first MEC node, and the target area is an area corresponding to the target MEC node. The first region RH node determines whether the target MEC node is one MEC node in the first region according to the region identifier of the target region, namely, determines whether the region identifier of the target region is the same as the region identifier corresponding to the first MEC node. If the area identifier of the target area is the same as the area identifier corresponding to the first MEC node, the first area RH node determines the target MEC node as one MEC node in the first area; otherwise, it is determined that the target MEC node is not one of the MEC nodes in the first region.
S218, when the first region RH node determines that the target MEC node is one MEC node in the first region, the first region RH node determines a second RH node according to the public key hash value corresponding to the second content provider and the name of the second service.
The second RH node is an RH node which has a connection relation with the target MEC node in the first region.
It should be appreciated that the first region RH node determining that the target MEC node is one MEC node in the first region illustrates that the target MEC node is one MEC node in the first region. The first regional RH node can determine, according to key information of the second service (including the public key hash value corresponding to the second content provider and the name of the second service), a next hop device corresponding to the first regional RH node, and a hop count from the first regional RH node to the target MEC node, until a previous hop device of the target MEC node, that is, the second RH node (the RH node having a connection relationship with the target MEC node) is determined.
Specifically, the process of determining the second node by the first regional RH node according to the public key hash value corresponding to the second content provider and the name of the second service is similar to the process of determining whether the target MEC node is a MEC node having a connection relationship with the first RH node by the first RH node in S114 according to the public key hash value corresponding to the second content provider and the name of the second service, which is not described herein.
Illustratively, in conjunction with the example in S115 above, assuming that the RH node 205 determines that the target MEC node is not the MEC node 202, the RH node 205 sends a service data acquisition request message to the regional RH node 208. Again assuming that the region identification of the target region is D 1 (i.e. the area identifier of the target area is the same as the area identifier of the first area), the MEC node 203 is the target MEC node (i.e. the MEC node 203 stores service data corresponding to the second service), and the area RH node 208 determinesThe RH node 206 is a second RH node, and obtains service data corresponding to the second service from the MEC node 203 through the RH node.
S219, the first area RH node sends a service data acquisition request message to the second RH node.
It should be understood that the first regional RH node sends a service data acquisition request message to the second RH node, so that the second RH node acquires service data corresponding to the second service from the target MEC node.
Optionally, in the embodiment of the present invention, the service data acquisition request message sent by any one previous hop device to the next hop device includes the IP address of the first node. Namely, the service data acquisition request message sent by the first MEC node to the first RH node comprises the IP address of the first MEC node; the service data acquisition request message sent by the first RH node to the first region RH node comprises the IP address of the first RH node; the service data acquisition request message sent by the first area RH node to the second RH node includes the IP address of the first area RH node. It should be understood that when the next-hop device returns service data (for example, service data corresponding to the second service), since the next-hop device can determine the IP address of the previous-hop device, the service data may be returned in the original path, that is, by the sending sequence of the service data acquisition request message, and reversely sent to the first MEC node (that is, the MEC node that requests to acquire service data).
In the embodiment of the invention, a first MEC node sends a service data registration request message to a first RH node, wherein the service data registration request message comprises a public key hash value corresponding to a second content provider, a service name of the second service and a region identifier of a target region; after receiving the service data acquisition request message of the first MEC node, the first RH node determines whether the target MEC node is an MEC node in connection with the first RH node according to the public key hash value corresponding to the second content provider and the service name of the second service; under the condition that the first RH node determines that the target MEC node is not the MEC node with the connection relation with the first RH node, the first RH node sends a service data registration request message to the first area RH node; after the first region RH node receives the service data registration request message from the first RH node, it may determine, according to the region identifier of the target region, whether the target MEC node is one MEC node in the first region (i.e., the region corresponding to the first MEC node); when the first region RH node determines that the target MEC node is one MEC node in the first region, determining a second RH node according to the public key hash value corresponding to the second content provider and the service name of the second service, namely, the RH node having a connection relationship with the target MEC node in the first region; and then, the first regional RH node sends a service data acquisition request message to the second RH node so that the second RH node acquires service data corresponding to the second service from the target MEC node. In the embodiment of the invention, since the first RH node determines that the target MEC node is not the MEC node having the connection relationship with the first RH node, the first RH node can determine that the first RH node is not the last hop device of the target MEC node, and the first RH node needs the first region RH node to determine the last hop device of the target MEC node, namely the second RH node, so that the first region RH node can acquire the service data corresponding to the second service from the target MEC node through the second RH node, the efficiency of determining the third RH node can be improved, and the efficiency of the first MEC node acquiring the service data from the target MEC node through the second RH node in the first region can be improved.
In another implementation manner, referring to fig. 5, as shown in fig. 6, after S217, the method for acquiring service data provided in the embodiment of the present invention may also be implemented through S301-S307.
S301: and under the condition that the first area RH node determines that the target MEC node is not one MEC node in the first area, the first area RH node sends a service data acquisition request message to the area transit equipment.
In connection with the above embodiments, it should be understood that the service data acquisition request message includes the public key hash value corresponding to the second content provider, the service name of the second service, and the area identifier of the target area.
S302, the regional transfer equipment receives a service data acquisition request message from the first regional RH node.
And S303, the regional transfer equipment determines the IP address of the RH node in the second region according to the region identification of the target region.
The second region RH node is a region RH node in the network other than the first region RH node.
It should be understood that, when the first regional RH node determines that the target MEC node is not one MEC node in the first region, it is explained that the region identifier corresponding to the target region is different from the region identifier of the first region, and the first regional RH node may send a service data acquisition request message to the regional relay device, and the regional relay device allocates an IP address of the second regional RH node corresponding to the regional identifier for the region identifier of the target region. It is to be understood that the correspondence between the region identifier and the IP address of the region RH node is stored in the region relay device, and table 3 below is an example of the correspondence between the region identifier and the IP address of the region RH node stored in the region relay device.
TABLE 3 Table 3
Figure BDA0002676265050000201
Figure BDA0002676265050000211
From the above, if the area identifier of the target area is D 2 The regional transfer equipment determines the IP address of the RH node in the second region as IP address 2.
And S304, the regional transfer equipment sends a service data acquisition request message to the RH node in the second region.
In connection with the above description of the embodiments, it should be understood that the service data acquisition request message sent by the regional relay device by the second regional RH node further includes the IP address of the regional relay device.
And S305, the second area RH node receives the service data acquisition request message from the area transit equipment.
S306, the second region RH node determines a third RH node according to the public key hash value corresponding to the second content provider and the service name of the second service.
The third RH node is an RH node having a connection relationship with the target MEC node in a second area, and the second area is an area corresponding to the second area RH node.
Specifically, the process of determining the third node by the second regional RH node according to the public key hash value corresponding to the second content provider and the name of the second service is similar to the process of determining, by the first RH node in S114, whether the target MEC node is a MEC node having a connection relationship with the first RH node according to the public key hash value corresponding to the second content provider and the name of the second service, which is not described herein.
Illustratively, in connection with the example in S218 above, assume that the region of the target region is identified as D 2 (the area identifier of the target area is not the same as the area identifier corresponding to the first MEC node), that is, the area RH node 208 determines that the target MEC node is not one MEC node in the first area, and the area RH node 208 sends a service data acquisition request message to the area relay device 210. Assuming that after receiving the service data acquisition request message, the regional relay device 210 determines that the IP address of the second regional RH node is the IP address of the regional RH node 209 according to the regional identifier of the target region, then the regional relay device 210 sends the service data acquisition request message to the regional RH node 209, and the RH node 207 is the third RH node; then, the regional RH node 209 sends a service data acquisition request message to the RH node 207, so that the RH node 207 acquires service data corresponding to the second service from the MEC node 204.
S307, the second region RH node sends a service data acquisition request message to the third RH node.
It should be understood that the second regional RH node sends a service data acquisition request message to the third RH node, so that the third RH node acquires service data corresponding to the second service from the target MEC node.
In the embodiment of the invention, a first MEC node sends a service data registration request message to a first RH node, wherein the service data registration request message comprises a public key hash value corresponding to a second content provider, a service name of the second service and a region identifier of a target region; after receiving the service data acquisition request message of the first MEC node, the first RH node determines whether the target MEC node is an MEC node in connection with the first RH node according to the public key hash value corresponding to the second content provider and the service name of the second service; under the condition that the first RH node determines that the target MEC node is not the MEC node with the connection relation with the first RH node, the first RH node sends a service data registration request message to the first area RH node; after the first region RH node receives the service data registration request message from the first RH node, it may determine, according to the region identifier of the target region, whether the target MEC node is one MEC node in the first region (i.e., the region corresponding to the first MEC node); when the first region RH node determines that the target MEC node is not one MEC node in the first region, the first region RH node sends a service data acquisition request message to the region transfer device, and the region transfer device determines the IP address of the second region RH node according to the region identifier of the target region; the regional transfer device may send a service data acquisition request message to the second regional RH node, and after receiving the service data acquisition request message, the second regional RH node may determine a third RH node (i.e., an RH node in the second region that has a connection relationship with the target MEC node) according to the public key hash value corresponding to the second content provider and the service name of the second service; then, the second regional RH node sends a service data acquisition request message to the third RH node, so that the third RH node may acquire service data corresponding to the second service from the target MEC node. In the embodiment of the invention, the first regional RH node determines that the target MEC node is not one MEC node in the first region, which indicates that the regional identifier of the target region is different from the regional identifier of the first region, the first regional RH node may send a service data acquisition request message to the regional transfer device, the regional transfer device may determine the IP address of the second regional RH node (i.e., the regional RH node in the network other than the first regional RH node) based on the regional identifier of the target region, and determine the last hop device of the target MEC node, i.e., the third RH node, from the second region through the second regional RH node, so that the second regional RH node may acquire service data corresponding to the second service from the target MEC node through the third RH node, which may improve the efficiency of determining the third RH node, and improve the efficiency of the first MEC node when acquiring the service data from the target MEC node through the third RH node in the second region.
According to the embodiment of the invention, the first MEC node, the first RH node, the first region RH node and the like can be divided according to the method example, for example, each functional module can be divided corresponding to each function, and two or more functions can be integrated in one processing module. The integrated modules may be implemented in hardware or in software functional modules. It should be noted that, in the embodiment of the present invention, the division of the modules is schematic, which is merely a logic function division, and other division manners may be implemented in actual implementation.
In the case of dividing the respective functional modules with the respective functions, fig. 7 shows a schematic diagram of one possible structure of the first MEC node involved in the above embodiment, and as shown in fig. 7, the first MEC node 40 may include: a transmitting module 401.
The sending module 401 is configured to send a service data registration request message to the first RH node, where the service data registration request message includes a public key hash value corresponding to the first content provider, a service name of the first service, and an area identifier corresponding to the service data obtaining device (i.e., the first MEC node 40), where the service data registration request message is used to register service data corresponding to the first service, where the first service is a service provided by the first content provider.
Optionally, the sending module 401 is further configured to send a service data acquisition request message to the first RH node, where the service data acquisition request message includes a public key hash value corresponding to a second content provider, a service name of the second service, and an area identifier of a target area, where the service data acquisition request message is used to request to acquire service data corresponding to the second service, the second service is a service provided by the second content provider, the target area is an area corresponding to a target MEC node, and the target MEC node is a MEC node storing service data corresponding to the second service.
In case of an integrated unit, fig. 8 shows a schematic diagram of one possible structure of the first MEC node involved in the above embodiment. As shown in fig. 8, the first MEC node 50 may include: a processing module 501 and a communication module 502. The processing module 501 may be configured to control and manage the actions of the first MEC node 50. The communication module 502 may be used to support communication of the first MEC node 50 with other entities. Optionally, as shown in fig. 8, the first MEC node 50 may further comprise a storage module 503 for storing program code and data of the first MEC node 50.
The processing module 501 may be a processor or a controller (e.g., may be the processor 301 described above and shown in fig. 3). The communication module 502 may be a transceiver, a transceiver circuit, a communication interface, or the like (e.g., may be the network interface 303 described above and shown in fig. 3). The storage module 503 may be a memory (e.g., may be the memory 302 described above and shown in fig. 3).
Where the processing module 501 is a processor, the communication module 502 is a transceiver, and the storage module 503 is a memory, the processor, the transceiver, and the memory may be connected by a bus. The bus may be a peripheral component interconnect standard (peripheral component interconnect, PCI) bus or an extended industry standard architecture (extended industry standard architecture, EISA) bus, or the like. The buses may be divided into address buses, data buses, control buses, etc.
In the case of dividing the respective functional modules by the respective functions, fig. 9 shows a schematic diagram of one possible structure of the first RH node involved in the above embodiment, and as shown in fig. 9, the first RH node 60 may include: a receiving module 601 and a transmitting module 602.
The receiving module 601 is configured to receive a service data registration request message of a first MEC node, where the service data registration request message includes a public key hash value corresponding to a first content provider, a service name of a first service, and an area identifier corresponding to the first MEC node, and the service data registration request message is used to register service data corresponding to the first service, where the first service is a service provided by the first content provider.
The sending module 602 is configured to send a service data notification message to a first regional RH node, where the service data notification message includes a public key hash value corresponding to the first content provider, a service name of the first service, and a regional identifier corresponding to the first MEC node, and the service data notification message is configured to notify the first regional RH node, where service data corresponding to the first service is stored in the first MEC node.
Optionally, the first RH node 60 may further comprise: a determination module 603 and an acquisition module 604.
The receiving module 601 is further configured to receive a service data acquisition request message of the first MEC node, where the service data acquisition request message includes a public key hash value corresponding to a second content provider, a service name of the second service, and an area identifier of a target area, where the service data acquisition request message is used to request to acquire service data corresponding to the second service, the second service is a service provided by the second content provider, the target area is an area corresponding to a target MEC node, and the target MEC node is a MEC node storing service data corresponding to the second service.
A determining module 603, configured to determine whether the target MEC node is a MEC node having a connection relationship with the service data acquisition device (i.e. the first RH node 60) according to the public key hash value corresponding to the second content provider and the service name of the second service.
The obtaining module 604 is configured to obtain, when the determining module 603 determines that the target MEC node is a MEC node having a connection relationship with the service data obtaining device, service data corresponding to the second service from the target MEC node.
The sending module 602 is further configured to send the service data acquisition request message to the first regional RH node if the determining module 603 determines that the target MEC node is not a MEC node having a connection relationship with the service data acquisition device.
In case of an integrated unit, fig. 10 shows a schematic diagram of one possible structure of the first RH node involved in the above embodiment. As shown in fig. 10, the first RH node 70 may comprise: a processing module 701 and a communication module 702. The processing module 701 may be configured to control and manage the actions of the first RH node 70. The communication module 702 may be used to support communication of the first RH node 70 with other entities. Optionally, as shown in fig. 10, the first RH node 70 may further comprise a memory module 703 for storing program code and data of the first RH node 70.
The processing module 701 may be a processor or a controller (e.g., may be the processor 301 shown in fig. 3 and described above). The communication module 702 may be a transceiver, a transceiver circuit, a communication interface, or the like (e.g., may be the network interface 303 described above and shown in fig. 3). The memory module 703 may be a memory (e.g., memory 302 as described above in fig. 3).
When the processing module 701 is a processor, the communication module 702 is a transceiver, and the storage module 703 is a memory, the processor, the transceiver and the memory may be connected through a bus. The bus may be a PCI bus or an EISA bus, etc. The buses may be divided into address buses, data buses, control buses, etc.
In the case of dividing the respective functional modules by the respective functions, fig. 11 shows a schematic diagram of one possible structure of the first region RH node involved in the above embodiment, and as shown in fig. 11, the first region RH node 80 may include: a receiving module 801.
The receiving module 801 is configured to receive a service data notification message of a first RH node, where the service data notification message includes a public key hash value corresponding to a first content provider, a service name of a first service, and an area identifier of a first MEC node, where the service data notification message is used to notify an obtaining device of service data (i.e., the first area RH node 80), and the first MEC node stores service data corresponding to the first service, where the first service is a service provided by the first content provider.
Optionally, the first region RH node 80 may further comprise: a determination module 802 and a transmission module 803.
The receiving module 801 is further configured to receive a service data acquisition request message from the first RH node, where the service data request message includes a public key hash value corresponding to a second content provider, a service name of a second service, and an area identifier of a target area, where the service data acquisition request message is used to request to acquire service data corresponding to the second service, where the second service is a service provided by the second content provider, and the target area is an area corresponding to a target MEC node, and the target MEC node is a MEC node storing service data corresponding to the second service.
The determining module 802 is configured to determine, according to the area identifier of the target area, whether the target MEC node is one MEC node in a first area, where the first area is an area corresponding to the first MEC node.
The determining module 802 is further configured to determine, when the determining module 802 determines that the target MEC node is one MEC node in the first area, a second RH node according to the public key hash value corresponding to the second content provider and the service name of the second service, where the second RH node is an RH node in the first area that has a connection relationship with the target MEC node.
And a sending module 803, configured to send the service data acquisition request message to the second RH node, so that the second RH node acquires service data corresponding to the second service from the target MEC node.
In case of an integrated unit, fig. 12 shows a schematic diagram of one possible structure of the first RH-region node involved in the above embodiment. As shown in fig. 12, the first region RH node 90 may comprise: a processing module 901 and a communication module 902. The processing module 901 may be configured to control and manage the operation of the first regional RH node 90. The communication module 902 may be used to support communication of the first region RH node 90 with other entities. Optionally, as shown in fig. 12, the first region RH node 90 may further include a storage module 903 for storing program code and data of the first region RH node 90.
The processing module 901 may be a processor or a controller (e.g., may be the processor 301 shown in fig. 3 and described above). The communication module 902 may be a transceiver, a transceiver circuit, a communication interface, or the like (e.g., may be the network interface 303 described above and shown in fig. 3). The storage module 903 may be a memory (e.g., may be the memory 302 described above and shown in fig. 3).
When the processing module 901 is a processor, the communication module 902 is a transceiver, and the storage module 903 is a memory, the processor, the transceiver, and the memory may be connected through a bus. The bus may be a PCI bus or an EISA bus, etc. The buses may be divided into address buses, data buses, control buses, etc.
It should be understood that, in various embodiments of the present invention, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present invention.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber terminal line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device including one or more servers, data centers, etc. that can be integrated with the medium. The usable medium may be a magnetic medium (e.g., a floppy Disk, a hard Disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.
The foregoing is merely illustrative of the present invention, and the present invention is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims (4)

1. The service data acquisition method is characterized by comprising the following steps:
the method comprises the steps that a first RH node receives a service data registration request message of a first MEC node, wherein the service data registration request message comprises a public key hash value corresponding to a first content provider, a service name of a first service and an area identifier corresponding to the first MEC node, the service data registration request message is used for registering service data corresponding to the first service, the first service is a service provided by the first content provider, the public key hash value corresponding to the first content provider, the service name of the first service and the service data corresponding to the first service are sent to the first MEC node by the first content provider, the first content provider is used for providing the service data corresponding to the first service, one RH node is connected with at least one MEC node, and one MEC node is only connected with one RH node;
A first RH node sends a service data notification message to a first area RH node, wherein the service data notification message comprises a public key hash value corresponding to a first content provider, a service name of the first service and an area identifier corresponding to the first MEC node, the service data notification message is used for notifying the first area RH node, service data corresponding to the first service is stored in the first MEC node, key information of the first service comprises the public key hash value corresponding to the first content provider, the service name of the first service and the area identifier corresponding to the first MEC node, the first RH node sends the key information of the first service to the first area RH node and other RH nodes in the first area after storing the key information of the first service, the first area RH node sends the key information of the first service to the other area RH nodes, the first area RH node is the first RH node and the other RH nodes in the first area, and the first RH nodes in the first area are used for storing the RH nodes in multiple areas;
The first RH node receives a service data acquisition request message of the first MEC node, wherein the service data acquisition request message comprises a public key hash value corresponding to a second content provider, a service name of a second service and an area identifier of a target area, the service data acquisition request message is used for requesting to acquire service data corresponding to the second service, the second service is a service provided by the second content provider, the target area is an area corresponding to a target MEC node, and the target MEC node is an MEC node storing the service data corresponding to the second service;
the first RH node determines whether the target MEC node is an MEC node with a connection relation with the first RH node according to the public key hash value corresponding to the second content provider and the service name of the second service;
under the condition that the first RH node determines that the target MEC node is an MEC node with a connection relation with the first RH node, the first RH node acquires service data corresponding to the second service from the target MEC node;
and under the condition that the first RH node determines that the target MEC node is not the MEC node which has a connection relationship with the first RH node, the first RH node sends the service data acquisition request message to the first region RH node.
2. The service data acquisition method is characterized by comprising the following steps:
a first regional RH node receives a service data notification message of the first RH node, wherein the service data notification message comprises a public key hash value corresponding to a first content provider, a service name of the first service and a regional identifier of a first MEC node, the service data notification message is used for notifying the first regional RH node, service data corresponding to the first service is stored in the first MEC node, the first service is a service provided by the first content provider, the public key hash value corresponding to the first content provider, the service name of the first service and the service data corresponding to the first service are sent to the first MEC node by the first content provider, the first content provider is used for providing the service data corresponding to the first service, the first RH node is connected with at least one MEC node, key information of the first service only is stored in the first MEC node and comprises the public key value corresponding to the first content provider, the service name of the first service and the first MEC node are sent to the first RH node, the first RH node is used for sending the first key information to the first RH node in the first regional RH node, and the first RH node stores the RH node in the first regional RH node, and the other critical information is stored in the first regional RH node;
The first region RH node receives a service data obtaining request message from the first RH node, wherein the service data obtaining request message comprises a public key hash value corresponding to a second content provider, a service name of a second service and a region identifier of a target region, the service data obtaining request message is used for requesting to obtain service data corresponding to the second service, the second service is a service provided by the second content provider, the target region is a region corresponding to a target MEC node, and the target MEC node is a MEC node storing the service data corresponding to the second service;
the first region RH node determines whether the target MEC node is one MEC node in a first region according to the region identification of the target region, wherein the first region is a region corresponding to the first MEC node;
when the first regional RH node determines that the target MEC node is one MEC node in the first region, the first regional RH node determines a second RH node according to the public key hash value corresponding to the second content provider and the service name of the second service, where the second RH node is an RH node having a connection relationship with the target MEC node in the first region;
And the first regional RH node sends the service data acquisition request message to the second RH node so that the second RH node acquires service data corresponding to the second service from the target MEC node.
3. The device for acquiring the service data is characterized by comprising a receiving module, a sending module, a determining module and an acquiring module;
the receiving module is configured to receive a service data registration request message of a first MEC node, where the service data registration request message includes a public key hash value corresponding to a first content provider, a service name of the first service and an area identifier corresponding to the first MEC node, where the service data registration request message is used to register service data corresponding to the first service, the first service is a service provided by the first content provider, the public key hash value corresponding to the first content provider, the service name of the first service and the service data corresponding to the first service are sent by the first content provider to the first MEC node, the first content provider is used to provide service data corresponding to the first service, one RH node is connected to at least one MEC node, and one MEC node is connected to only one RH node;
The sending module is configured to send a service data notification message to a first regional RH node, where the service data notification message includes a public key hash value corresponding to the first content provider, a service name of the first service and a regional identifier corresponding to the first MEC node, the service data notification message is used to notify the first regional RH node, service data corresponding to the first service is stored in the first MEC node, key information of the first service includes the public key hash value corresponding to the first content provider, the service name of the first service and a regional identifier corresponding to the first MEC node, after storing the key information of the first service, the first RH node sends the key information of the first service to the first regional RH node and other RH nodes in the first region, the first regional RH node sends the key information of the first service to the other regional RH nodes, and the first regional RH node is the RH node in the first RH node and other RH nodes in the first region corresponding to the first regional RH nodes, and the first RH node stores multiple RH information in the first region;
The receiving module is further configured to receive a service data acquisition request message of the first MEC node, where the service data acquisition request message includes a public key hash value corresponding to a second content provider, a service name of a second service, and an area identifier of a target area, where the service data acquisition request message is used to request to acquire service data corresponding to the second service, the second service is a service provided by the second content provider, the target area is an area corresponding to a target MEC node, and the target MEC node is a MEC node storing the service data corresponding to the second service;
the determining module is configured to determine, according to the public key hash value corresponding to the second content provider and the service name of the second service, whether the target MEC node is a MEC node having a connection relationship with the service data acquiring device;
the acquiring module is configured to acquire service data corresponding to the second service from the target MEC node when the determining module determines that the target MEC node is a MEC node having a connection relationship with the service data acquiring device;
the sending module is further configured to send the service data acquisition request message to the first regional RH node if the determining module determines that the target MEC node is not a MEC node having a connection relationship with the service data acquisition device.
4. The device for acquiring the service data is characterized by comprising a receiving module, a determining module and a sending module;
the receiving module is configured to receive a service data notification message of a first RH node, where the service data notification message includes a public key hash value corresponding to a first content provider, a service name of the first service and an area identifier of a first MEC node, where the service data notification message is used to notify an obtaining device of the service data, where first MEC node stores service data corresponding to the first service, where the first service is a service provided by the first content provider, where the public key hash value corresponding to the first content provider, the service name of the first service, and service data corresponding to the first service are sent by the first content provider to the first MEC node, where one of the first content provider is used to provide service data corresponding to the first service, where one of the first MEC node is connected to only one of the first RH node, where critical information of the first service includes a public key value corresponding to the first content provider, where the service name of the first service and the first MEC node send the service corresponding to the first content provider to the first node, and the first service name of the first service are sent by the first content provider to the first node, where the first RH node stores the first node and the first node in the first RH node, and the first node stores the first RH node in the first RH node, and the first RH node stores the first RH node;
The receiving module is further configured to receive a service data acquisition request message from the first RH node, where the service data acquisition request message includes a public key hash value corresponding to a second content provider, a service name of a second service, and an area identifier of a target area, where the service data acquisition request message is used to request to acquire service data corresponding to the second service, the second service is a service provided by the second content provider, the target area is an area corresponding to a target MEC node, and the target MEC node is a MEC node storing the service data corresponding to the second service;
the determining module is configured to determine, according to the area identifier of the target area, whether the target MEC node is one MEC node in a first area, where the first area is an area corresponding to the first MEC node;
the determining module is further configured to determine, when the determining module determines that the target MEC node is one MEC node in the first area, a second RH node according to a public key hash value corresponding to the second content provider and a service name of the second service, where the second RH node is an RH node in a connection relationship with the target MEC node in the first area;
The sending module is configured to send the service data acquisition request message to the second RH node, so that the second RH node acquires service data corresponding to the second service from the target MEC node.
CN202010948941.3A 2020-09-10 2020-09-10 Service data acquisition method and device Active CN112153021B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010948941.3A CN112153021B (en) 2020-09-10 2020-09-10 Service data acquisition method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010948941.3A CN112153021B (en) 2020-09-10 2020-09-10 Service data acquisition method and device

Publications (2)

Publication Number Publication Date
CN112153021A CN112153021A (en) 2020-12-29
CN112153021B true CN112153021B (en) 2023-05-19

Family

ID=73890905

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010948941.3A Active CN112153021B (en) 2020-09-10 2020-09-10 Service data acquisition method and device

Country Status (1)

Country Link
CN (1) CN112153021B (en)

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8065417B1 (en) * 2008-11-17 2011-11-22 Amazon Technologies, Inc. Service provider registration by a content broker
CN109040259A (en) * 2018-08-09 2018-12-18 中国联合网络通信集团有限公司 A kind of CDN node distribution method and system based on MEC
CN109218363A (en) * 2017-07-03 2019-01-15 中国移动通信有限公司研究院 Content distribution method, network node and storage medium
WO2019194954A1 (en) * 2018-04-06 2019-10-10 Convida Wireless, Llc Methods of managing connections to a local area data network (ladn) in a 5g network
CN110336753A (en) * 2019-06-19 2019-10-15 腾讯科技（深圳）有限公司 A kind of service calling method, device, equipment and the storage medium in across a network region
CN110381131A (en) * 2019-07-15 2019-10-25 北京奇艺世纪科技有限公司 Implementation method, mobile terminal, server and the storage medium of MEC node identification
CN111556514A (en) * 2020-04-14 2020-08-18 北京航空航天大学 Decentralized mobile edge computing resource discovery and selection method and system
CN111629401A (en) * 2019-02-27 2020-09-04 大唐移动通信设备有限公司 Data distribution method and system for edge application

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7689711B2 (en) * 2001-03-26 2010-03-30 Salesforce.Com, Inc. System and method for routing messages between applications
CN100558038C (en) * 2006-03-31 2009-11-04 国际商业机器公司 Service logger and related system and method
US8060616B1 (en) * 2008-11-17 2011-11-15 Amazon Technologies, Inc. Managing CDN registration by a storage provider
CN102118370B (en) * 2009-12-31 2014-12-31 华为技术有限公司 Service management method, device and system
EP2782316A1 (en) * 2013-03-18 2014-09-24 Koninklijke KPN N.V. Localizing and placement of network node functions in a network
US20140359061A1 (en) * 2013-06-04 2014-12-04 Telefonaktiebolaget L M Ericsson (Publ) Method and Apparatus for Automating Access Rights Creation and Control in Machine-to-Machine Systems
CN106576074B (en) * 2015-07-31 2020-04-21 华为技术有限公司 Method, equipment and system for acquiring routing rule
CN107770815B (en) * 2017-10-18 2020-09-11 中国联合网络通信集团有限公司 MEC method and equipment based on position
CN109782695B (en) * 2017-11-13 2021-01-26 华中科技大学 Control method, device and system for manufacturing equipment
WO2019100266A1 (en) * 2017-11-22 2019-05-31 华为技术有限公司 Mobile edge host-machine service notification method and apparatus
CN110519074B (en) * 2018-05-22 2022-04-12 华为技术有限公司 Service area management method and device
CN111385317B (en) * 2018-12-27 2021-09-07 华为技术有限公司 Data transmission method, device and system
CN110381162B (en) * 2019-07-29 2021-01-05 腾讯科技（深圳）有限公司 Service processing method and related device
CN111338573B (en) * 2020-02-19 2023-06-06 中国联合网络通信集团有限公司 Terminal data management method and system, server and communication terminal

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8065417B1 (en) * 2008-11-17 2011-11-22 Amazon Technologies, Inc. Service provider registration by a content broker
CN109218363A (en) * 2017-07-03 2019-01-15 中国移动通信有限公司研究院 Content distribution method, network node and storage medium
WO2019194954A1 (en) * 2018-04-06 2019-10-10 Convida Wireless, Llc Methods of managing connections to a local area data network (ladn) in a 5g network
CN109040259A (en) * 2018-08-09 2018-12-18 中国联合网络通信集团有限公司 A kind of CDN node distribution method and system based on MEC
CN111629401A (en) * 2019-02-27 2020-09-04 大唐移动通信设备有限公司 Data distribution method and system for edge application
CN110336753A (en) * 2019-06-19 2019-10-15 腾讯科技（深圳）有限公司 A kind of service calling method, device, equipment and the storage medium in across a network region
CN110381131A (en) * 2019-07-15 2019-10-25 北京奇艺世纪科技有限公司 Implementation method, mobile terminal, server and the storage medium of MEC node identification
CN111556514A (en) * 2020-04-14 2020-08-18 北京航空航天大学 Decentralized mobile edge computing resource discovery and selection method and system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
5G核心网络关键技术和对业务的支撑;邢燕霞;魏文娟;李鹏宇;毛聪杰;;电信技术(第07期);全文 *

Also Published As

Publication number Publication date
CN112153021A (en) 2020-12-29

Similar Documents

Publication Publication Date Title
CN110311983B (en) Service request processing method, device and system, electronic equipment and storage medium
CN110383896A (en) Method for network access, terminal, access net and core net
CN111200797B (en) Internet of vehicles message notification method and device
CN107454040B (en) Application login method and device
CN114257440B (en) Network function service discovery method, system and storage medium
CN114745724B (en) Access processing method and device, electronic equipment and computer readable medium
CN109753367B (en) Communication method, communication device, computer equipment and computer readable storage medium
CN113890739B (en) Cross-blockchain authentication method and device, electronic equipment and medium
CN114095899A (en) Communication signal detection method and device, electronic equipment and computer readable medium
CN114385386A (en) Method, device, equipment and storage medium for calling micro-service
CN112714042B (en) Pressure testing method and device, electronic equipment and storage medium
CN112153021B (en) Service data acquisition method and device
CN101896917A (en) Method for moving rights object and method for managing rights of issuing rights object and system thereof
CN112416616A (en) Micro-service calling method and device, electronic equipment and storage medium
CN114125812B (en) Data synchronization method, device, server and storage medium
CN111371896A (en) Network acceleration method, terminal and storage medium
CN112788518A (en) Location service processing method and related equipment
US20220217539A1 (en) Authorization in cellular communication systems
CN114124404B (en) Data processing method, device, server and storage medium
CN113490249B (en) Transmission path determining method and device
CN112491855A (en) Method and device for determining handle identifier analysis state
CN115801686A (en) Service request processing method, device, equipment and storage medium
RU2735242C1 (en) Method of providing data packets from can-bus; control device, as well as system having can-bus
CN113271320B (en) Terminal authentication method, device, system, medium and equipment
CN108848018B (en) Method and device for determining assigned VLAN ID

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