CN112153021A - Method and device for acquiring service data - Google Patents

Method and device for acquiring service data Download PDF

Info

Publication number
CN112153021A
CN112153021A CN202010948941.3A CN202010948941A CN112153021A CN 112153021 A CN112153021 A CN 112153021A CN 202010948941 A CN202010948941 A CN 202010948941A CN 112153021 A CN112153021 A CN 112153021A
Authority
CN
China
Prior art keywords
service
node
service data
mec
mec node
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.)
Granted
Application number
CN202010948941.3A
Other languages
Chinese (zh)
Other versions
CN112153021B (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 method and a device for acquiring service data, relates to the technical field of communication, and can improve the efficiency of determining a target RH node (namely, an RH node having a connection relation with an MEC node (namely, a first MEC node) storing service data corresponding to a service (for example, a first service)) so as to improve the efficiency of acquiring the service data. 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, the service data registration request message is used for registering service data corresponding to the first service, and the first service is a service provided by the first content provider.

Description

Method and device for acquiring service data
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, User Equipment (UE) may obtain service data based on a data-oriented (and beyond) network architecture (DONA). Specifically, in the communication system shown in fig. 1, the content provider 103 may send a register message to the Resolution Handler (RH) node 102, where the register message is 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 providers 105 and 106 can also send register messages to the RH node 104 to complete the service data that the content providers 105 and 106 can provide.
When the content requester 101 needs to obtain service data of a certain service, a find message may be sent to the RH node 102, 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, obtains the service data from the content provider 103 and returns to the content requester 101; otherwise, the RH node 104 determines whether the content provider 105 and the content provider 106 can provide the service data; in the case where the RH node 104 determines that the service data does not exist in both the content provider 105 and the content provider 106, it is determined or judged by other RH nodes (not shown in the figure) in the network which content provider the service data can be provided by, and the service data is returned to the content requester 101.
In the above method, when the content requester 101 needs to acquire the service data, all RH nodes in the network may be required to sequentially determine whether a certain service provider is capable of providing the service data, and thus, the acquisition efficiency of the service data may not be high.
Disclosure of Invention
Embodiments of the present invention provide a method and an apparatus for acquiring service data, which improve efficiency of determining a target RH node (i.e., an RH node having a connection relationship with a Mobile Edge Computing (MEC) node (i.e., a first MEC node) storing service data corresponding to a service (e.g., a first service)), and further improve efficiency of acquiring service data.
In a first aspect, an embodiment of the present invention provides a method for acquiring service data, including: the method includes that a first MEC node sends a service data registration request message to a first RH node, 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, the service data registration request message is used for registering service data corresponding to the first service, and the first service is a service provided by the first content provider.
In a second aspect, an embodiment of the present invention provides a method for acquiring service data, including: 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 a service provided by the first content provider; the first RH node sends 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 region identifier corresponding to the first MEC node, and 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 third aspect, an embodiment of the present invention provides a method for acquiring service data, including: the method includes that a first regional RH node receives a service data notification message of the 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 a regional identifier of the first MEC node, and the service data notification message is used to notify the first regional RH node, where the first MEC node stores service data corresponding to the first service, and the first service is a service provided by the first content provider.
In a fourth aspect, an embodiment of the present invention provides an apparatus for acquiring service data, including: a sending module; the sending module 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 apparatus, 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 an apparatus for acquiring service data, including: the device comprises a receiving module and a sending 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, 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 is configured to send 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, and the first MEC node stores service data corresponding to the first service.
In a sixth aspect, an embodiment of the present invention provides an apparatus for acquiring service data, 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, and the service data notification message is used to notify an obtaining apparatus of the service data, where the first MEC node stores service data corresponding to the first service, and the first service is a service provided by the first content provider.
In a seventh aspect, an embodiment of the present invention provides another apparatus for acquiring service data, 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 runs, 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 by the first aspect.
In an eighth aspect, an embodiment of the present invention provides another apparatus for acquiring service data, 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 runs, 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 by the second aspect.
In a ninth aspect, an embodiment of the present invention provides another apparatus for acquiring service data, including: a processor, a memory, a bus, and a communication interface; the memory is used for storing computer-executable instructions, the processor is connected with the memory through a bus, and 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, which includes a computer program, and when the computer program runs on a computer, the computer is caused to execute the 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, which includes a computer program, and when the computer program runs on a computer, the computer is caused to execute the 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, which includes a computer program, and when the computer program runs on a computer, the computer is caused to execute the method for acquiring service data provided in the third aspect.
In a thirteenth aspect, an embodiment of the present invention provides a computer program product containing instructions, which, when running on a computer, causes the computer to execute the method for acquiring service data of the first aspect and any implementation manner thereof.
In a fourteenth aspect, an embodiment of the present invention provides a computer program product including instructions, which, when running on a computer, causes the computer to execute the method for acquiring service data of the second aspect and any implementation manner thereof.
In a fifteenth aspect, an embodiment of the present invention provides a computer program product containing instructions, which, when run on a computer, causes the computer to execute the method for acquiring service data of the third aspect and any implementation manner thereof.
In the embodiment of the present invention, a first MEC node sends 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 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 regional RH node, that is, notifies the first regional RH node, where the first MEC node stores service data corresponding to the first service, and 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; in this way, the first region RH node also acquires 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 the RH nodes in other regions, so that all the regional RH nodes and all the RH nodes in the network obtain the key information of the first service, that is, the registration process of the service data corresponding to the first service is completed. Furthermore, after a certain RH node receives a request message for acquiring service data corresponding to a first service, which is sent by a certain MEC node, it may be determined, based on a public key hash value corresponding to a first content provider and a service name of the first service, whether a certain MEC node (i.e., a first MEC node) may provide the service data corresponding to the first service exists in the network, and based on an area identifier of the first MEC node, an area corresponding to the first MEC node is determined, and the service data corresponding to the first service is acquired from the area. Therefore, all RH nodes in the network may not be required to participate in the determining process of the first MEC node, so as to improve the efficiency of determining the target RH node (i.e., the RH node having a connection relationship with the MEC node (i.e., the first MEC node) storing the service data corresponding to the service (e.g., the first service)), and further improve the acquisition efficiency of the service data.
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 first schematic diagram of a network architecture of a communication system according to an embodiment of the present invention;
fig. 2 is a schematic diagram of a network architecture of a communication system according to an embodiment of the present invention;
fig. 3 is a hardware schematic diagram of a server according to an embodiment of the present invention;
fig. 4 is a first schematic diagram illustrating a method for acquiring service data according to an embodiment of the present invention;
fig. 5 is a second schematic diagram illustrating a method for acquiring service data according to an embodiment of the present invention;
fig. 6 is a third schematic diagram of a method for acquiring service data according to an embodiment of the present invention;
fig. 7 is a first schematic structural diagram of a first MEC node according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of a first MEC node according to an embodiment of the present invention;
fig. 9 is a first schematic structural diagram of a first RH node according to an embodiment of the present invention;
fig. 10 is a second schematic structural diagram of a first RH node according to an embodiment of the present invention;
fig. 11 is a first schematic structural diagram of an RH node in a first region according to an embodiment of the present invention;
fig. 12 is a second schematic structural diagram of an RH node in a first region according to an embodiment of the present invention.
Detailed Description
The following describes in detail a method and an apparatus for acquiring service data according to an embodiment of the present invention with reference to the accompanying drawings.
The terms "first" and "second" etc. in the description and drawings of the present application are used to distinguish between different objects and not to describe a particular order of the objects, e.g., a first RH node, a second RH node, a third RH node, etc. are used to distinguish between different RH nodes and not to describe a particular order of the RH nodes.
Furthermore, the terms "including" and "having," and any variations thereof, as referred to in the description of the present application, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements but may alternatively include other steps or elements not expressly 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 "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "e.g.," an embodiment of the present invention is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.
The term "and/or" as used herein includes the use of either or both of the two methods.
In the description of the present application, the meaning of "a plurality" means two or more unless otherwise specified.
Based on the problems existing in the background art, embodiments of the present invention provide a method and an apparatus for acquiring service data, where a first MEC node sends 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 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 regional RH node, that is, notifies the first regional RH node, where the first MEC node stores service data corresponding to the first service, and 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; in this way, the first region RH node also acquires 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 the RH nodes in other regions, so that all the regional RH nodes and all the RH nodes in the network obtain the key information of the first service, that is, the registration process of the service data corresponding to the first service is completed. Furthermore, after a certain RH node receives a request message for acquiring service data corresponding to a first service, which is sent by a certain MEC node, it may be determined, based on a public key hash value corresponding to a first content provider and a service name of the first service, whether a certain MEC node (i.e., a first MEC node) may provide the service data corresponding to the first service exists in the network, and based on an area identifier of the first MEC node, an area corresponding to the first MEC node is determined, and the service data corresponding to the first service is acquired from the area. Therefore, all RH nodes in the network may not be required to participate in the determining process of the first MEC node, so as to improve the efficiency of determining the target RH node (i.e., the RH node having a connection relationship with the MEC node (i.e., the first MEC node) storing the service data corresponding to the service (e.g., the first service)), and further improve the acquisition efficiency of the service data.
The method and apparatus for acquiring service data provided in the embodiment of the present invention may be applied to a wireless communication system, as shown in fig. 2, 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 area RH nodes (i.e., area RH node 208 and area RH node 209), and 1 area transit device (i.e., area transit device 210). In general, in practical applications, the connections between the above-mentioned devices or service functions may be wireless connections, and fig. 1 illustrates the connections between the devices by solid lines for convenience of intuitively representing the connections between the devices.
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 this embodiment of the present invention, the MEC node 201 may send a service data registration request message to the RH node 205, so as to complete a registration process of 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 a first content provider (that is, a content provider providing the first service), a service name of the first service, and an area identifier corresponding to the MEC node 201. In this embodiment of the present invention, the RH node 205 may send a service data notification message to the area RH node 208 (and RH node 206), where the service data notification message is used to notify the area RH node 208 (and RH node 206), and the MEC node 201 stores service data corresponding to the first service.
The area RH node is configured to store key information of all services in an area, for example, the area RH node 208 may store key information of all services in a first area, where the first area is an area corresponding to the MEC node 201. In the embodiment of the present invention, all the RH nodes, and all the MEC nodes in an area correspond to the same area identifier, for example, the RH node 208, the RH node 205, the RH node 206, the MEC node 201, the MEC node 202, and the MEC node 203 in the area all correspond to the first area.
In this embodiment of the present invention, the area relay device 210 is configured to store a correspondence between the area identifier and the IP address of the area RH node, and the area relay device 210 may determine the IP address of the area RH node corresponding to the area identifier according to the area identifier of the target area.
Optionally, the communication system may include one or more MEC nodes, one or more RH nodes, one or more area RH nodes, and one or more area transit devices, where the number of each node and each device shown in fig. 2 is only an example, and the number of each node and each device in the communication system is not limited in the embodiment of the present invention.
For example, as shown in fig. 3, an RH node provided in the embodiment of the present invention may be a server, and fig. 3 is a schematic diagram of a hardware structure of the server provided in 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 application programs (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 this embodiment, the processor 301 may be a Central Processing Unit (CPU), a microprocessor, a Digital Signal Processor (DSP), an application-specific integrated circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof, which is capable of implementing or executing various exemplary logic blocks, modules, and circuits described in connection with the disclosure of the embodiment of the present invention; a processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, a DSP and a microprocessor, or the like.
Optionally, the processor 301 of the server 30 includes one or more CPUs, which are single-core CPUs (single-CPUs) or multi-core CPUs (multi-CPUs).
The memory 302 includes, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical memory, or the like. The memory 302 holds the code for the operating system.
Optionally, the processor 301 implements the method for acquiring the 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 acquiring the service data provided in the embodiment of the present invention by using an instruction stored inside. In the case that the processor 301 implements the method for acquiring service data provided by the embodiment of the present invention by reading the memory, the memory stores instructions for implementing the method for acquiring service data provided by the embodiment of the present invention.
The network interface 303 is a wired interface, such as a Fiber Distributed Data Interface (FDDI) interface or a 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 used for storing 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, a service name of the second service, and the like. The at least one processor 301 further executes the method according to the embodiment of the present invention according to 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 of the processor 301 to implement the above functions, reference is made to the following description of various method embodiments.
Optionally, the server 30 further includes a bus, and the processor 301 and the memory 302 are connected to each other through the bus 304, or in other manners.
Optionally, the server 30 further includes an input/output interface 305, where the input/output interface 305 is configured to connect with an input device, and receive a service data obtaining request message input by a user through the input device. Input devices include, but are not limited to, a keyboard, a touch screen, a microphone, and the like. The input/output interface 305 is further configured to connect with an output device, and output the obtained result of the service data of the processor 301 (i.e., the server 30 determines whether to obtain the service data corresponding to the second service from the target MEC node). Output devices include, but are not limited to, a display, a printer, and the like.
It should be understood that, in the embodiment of the present invention, the hardware structures of the MEC node and the area RH node are similar to the hardware structure of the server 30 shown in fig. 3, and the description of the hardware structures of the MEC node and the area 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 provided by the embodiment of the invention are applied to a scene of acquiring the service data. Specifically, when a certain UE (or content provider) requests to register service data corresponding to a certain service (e.g., 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 RH node can provide the service data corresponding to the first service, and then the RH node may send a service data notification message to an area RH node in the same area and other RH nodes in the area.
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 to request to acquire service data corresponding to a second service), the RH node may determine whether a target MEC node capable of providing the service data corresponding to the second service exists, and acquire the service data corresponding to the second service from the target MEC node.
With reference to the communication system shown in fig. 2, the following completely describes the method for acquiring service data provided by the embodiment of the present invention from the perspective of interaction between devices in the communication system, so as to describe 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 according to the embodiment of the present invention may include S101 to S115.
S101, the first content provider sends a registration verification request message to the content sharing device.
It should be understood that the first content provider may provide service data corresponding to the first service, 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 of the first content provider, the public key and the private key.
Optionally, the registration verification response message further includes an IP address of the first MEC node, where the first MEC node is an MEC node accessible 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 the hash value of the public key corresponding to the first content provider according to the public key of the first content provider, and determine a unique name for the first service, that is, the service name of the first service.
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, and 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 (for example, road condition information) corresponding to the first service 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, such as 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, that is, does not send service data corresponding to the first service. When the content requester needs to obtain the service data corresponding to the first service, the content requester still needs to obtain the service data from the original content provider (i.e., the first content provider).
In the following embodiments, a first content provider is used as an intelligent vehicle, that is, the method for acquiring service data provided by the embodiments of the present invention is applied to an internet of vehicles scenario, and the method for acquiring service data provided by the embodiments of the present invention is described.
S105, the first MEC node receives 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 from the first content provider.
S106, the first MEC node sends a service data registration request message to the first RH node.
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 first MEC node, and is used to request registration of service data corresponding to the first service, where the first service is a service provided by the first content provider.
With reference to the description of the foregoing embodiments, it should be understood that, 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, sent by the first content provider, the first MEC node becomes a new content provider corresponding to the first service. 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 area RH nodes in the first area (i.e., an area corresponding to the first MEC node), where the first MEC node stores service data corresponding to the first service.
It should be noted that the area identifications of the plurality of nodes in the same area, including the MEC node, the RH node, and the area RH node, are the same, for example, in fig. 2, the area identifications of 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.
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 embodiments, P is usedaRepresenting a public key hash value corresponding to the a-th content provider, wherein a is an integer greater than or equal to one; by LbRepresenting the name of the service of the b-th service, wherein b is an integer greater than or equal to one; by DcAnd c is an integer greater than or equal to one.
Illustratively, table 1 is an example of key information of a plurality of services stored in the first RH node.
TABLE 1
Figure BDA0002676265050000111
As can be determined from table 1, the first RH node stores therein key information of 4 services provided by 2 content providers.
And S108, the first RH node sends a service data notification message to the first region RH node.
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 an area identifier corresponding to the first MEC node, and is used to notify the first area RH node, where 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 storing the key information of the first service, the first RH node needs to send the key information of the first service to the first area RH node and other RH nodes in the first area. That is, the first RH node may further send a service data notification message to other RH nodes in the first area, so that the other RH nodes in the first area may all determine that the first MEC node stores service data corresponding to the first service, and after receiving the service data notification message, the other nodes store key information of the first service.
S109, the first region RH node receives the service data notification message of the first 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 by 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 region RH node receives the service data notification message sent by another RH node, key information of another service may also be stored.
Optionally, the first region RH node may further store a next hop RH node corresponding to the first service and a hop count from the first region RH node to the first MEC node (n, n is an integer greater than or equal to 2).
Exemplarily, in combination with the above table 1 and fig. 2, it is assumed that the first RH node illustrated in table 1 is the RH node 205 in fig. 2, and the first MEC node is the MEC node 201 in fig. 2. Thus, an example of the key information of the plurality of services stored in the first region RH node (i.e., the region RH node 208 in fig. 2) as shown in table 2 can be obtained.
TABLE 2
Figure BDA0002676265050000131
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 through RH node 205.
It can be understood that, after the first area RH node receives the service data notification message of the first RH node and stores the key information of the first service, all nodes in the first area (including the first area RH node and other RH nodes in the first area) store the key information of the first service, and then the first area RH node sends the key information of the first service to the other area RH nodes, so that the nodes in the entire network (or architecture) complete the registration process of the service data corresponding to the first service, that is, all the area RH nodes and all the RH nodes in the network store the key information of the first service. After any regional RH node or any RH node receives a service data acquisition request message sent by a content requester, an MEC node storing 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 an area 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 regional RH node, that is, notifies the first regional RH node, where the first MEC node stores service data corresponding to the first service, and 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; in this way, the first region RH node also acquires 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 the RH nodes in other regions, so that all the regional RH nodes and all the RH nodes in the network obtain the key information of the first service, that is, the registration process of the service data corresponding to the first service is completed. Furthermore, after a certain RH node receives a request message for acquiring service data corresponding to a first service, which is sent by a certain MEC node, it may be determined, based on a public key hash value corresponding to a first content provider and a service name of the first service, whether a certain MEC node (i.e., a first MEC node) may provide the service data corresponding to the first service exists in the network, and based on an area identifier of the first MEC node, an area corresponding to the first MEC node is determined, and the service data corresponding to the first service is acquired from the area. Therefore, all RH nodes in the network may not be required to participate in the determining process of the first MEC node, so as to improve the efficiency of determining the target RH node (i.e., the RH node having a connection relationship with the MEC node (i.e., the first MEC node) storing the service data corresponding to the service (e.g., the first service)), and further improve the acquisition efficiency of the service data.
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).
And S111, 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.
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, the service name of the second service is identified by the region of the target region, 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 region is a region corresponding to the target MEC node, and the target MEC node is an MEC node storing the service data corresponding to the second service.
It should be understood 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, the key information of the second service, that is, the public key hash value corresponding to the second content provider, and the service name of the second service may be sent to the first RH node 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 obtaining 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 the service data corresponding to the second service can be acquired by the first RH node based on the key information of the second service and the key information of the multiple services stored in the first RH node.
And S114, the first RH node determines whether the target MEC node is an MEC node which has 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 is to be understood 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 the first RH node, it means that the service data stored in the MEC node will be notified to the regional RH node (including the first regional RH node) or other RH nodes through the first RH node.
In an implementation manner of the embodiment of the present invention, the step S112 may be implemented by steps 1 to 3.
Step 1, the first RH node determines whether target key information exists in the key information of the plurality of services stored in 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.
The target key information includes 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 there is key information of the second service among the key information of the plurality of services stored in the first RH node, that is, there is key information including a corresponding public key hash value of the second content provider and a service name of the second service, the first RH node can determine that there is service data corresponding to the second service in the network.
And 2, under the condition that the target key information exists in the key information of the 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 may jump to the target MEC node only after passing through another RH 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 an MEC node which has a connection relation with the first RH node.
And S115, under the condition that the first RH node determines that the target MEC node is an MEC node which has 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.
It should be understood that, when the first RH node determines that the target MEC node is an MEC node having a connection relationship with the first RH node, it is described 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 service data corresponding to the second service from the target MEC node without passing through other nodes.
For example, in conjunction 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. When the RH node 205 determines that the target MEC node is the MEC node 202, the RH node 205 acquires service data corresponding to the second service from the MEC node 202.
In the embodiment of the present invention, a first MEC node sends 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 second content provider, a service name of a 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 a target MEC node is an MEC node which has 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; 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 the connection relation with the first RH node. In this 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 an MEC node having a connection relationship with the first RH node, that is, whether the target MEC node is a next hop device of the first RH node, when the first RH node determines that the target MEC node is the next hop device of the first RH node, it indicates that the target MEC node notifies other RH nodes (or first area RH nodes) through the first RH node, and the target MEC node stores service data corresponding to the second service; furthermore, the first RH node may obtain the service data corresponding to the second service from the target MEC node, and may improve efficiency of the first MEC node in obtaining the service data from the target MEC node through the first RH node.
As shown in fig. 5, in an implementation manner, a method for acquiring service data provided by the embodiment of the present invention includes S201 to S219.
S201, the first content provider sends 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 the public key hash value corresponding to the first content provider and the 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, 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.
S206, the first MEC node sends a service data registration request message to the first RH node.
S207, the first RH node receives the service data registration request message of the first MEC node.
S208, the first RH node sends a service data notification message to the first region RH node.
S209, the first region RH node receives the service data notification message of the first RH node.
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, from the content requester, the public key hash value corresponding to the second content provider and the service name of the second service.
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 obtaining request message of the first MEC node.
And S214, the first RH node determines whether the target MEC node is an MEC node which has 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 can refer to the description of S101-S114 above, and the description is omitted here.
S215, when the first RH node determines that the target MEC node is not an MEC node having a connection relationship with the first RH node, the first RH node sends a service data acquisition request message to the first area RH node.
In conjunction with the description of the foregoing embodiment, it should be understood that the service data acquisition request message includes a public key hash value corresponding to the second content provider, a service name of the second service, and a zone identifier of the target zone.
S216, the first region RH node receives the service data acquisition request message from the first RH node.
S217, the first region RH node determines whether the target MEC node is an MEC node in the first region according to the region identifier of the target region.
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, according to the region identifier of the target region, whether the target MEC node is one MEC node in the first region, that is, 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 that the target MEC node is an MEC node in the first area; otherwise, it is determined that the target MEC node is not an MEC node in the first area.
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 the second RH node according to the public key hash value corresponding to the second content provider and the name of the second service.
And the second RH node is an RH node which has a connection relation with the target MEC node in the first area.
It should be understood that the first region RH node determining the target MEC node as one MEC node in the first region means that the target MEC node is one MEC node in the first region. The first region RH node can determine, according to key information of the second service (including a public key hash value corresponding to the second content provider and a name of the second service), a next-hop device corresponding to the first region RH node and a hop count from the first region RH node to the target MEC node, until determining a last-hop device of the target MEC node, that is, a second RH node (an RH node having a connection relationship with the target MEC node).
Specifically, the process of determining the second node by the first region 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 according to the public key hash value corresponding to the second content provider and the name of the second service, whether the target MEC node is an MEC node having a connection relationship with the first RH node, and details are not repeated here.
Exemplarily, in connection with the example in S115 described 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. Assume again that the region identification of the target region is D1(that is, the area identifier of the target area is the same as the area identifier of the first area), the MEC node 203 is a target MEC node (that is, the MEC node 203 stores service data corresponding to the second service), and the area RH node 208 determines the RH node 206 as a second RH node, and obtains the service data corresponding to the second service from the MEC node 203 through the RH node.
And S219, the first region RH node sends the service data acquisition request message to the second RH node.
It should be understood that the first region RH node sends the service data acquisition request message to the second RH node, so that the second RH node acquires the 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 previous-hop device to the next-hop device includes the IP address of the first node. Namely, a service data acquisition request message sent by a first MEC node to a first RH node comprises an 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 region RH node to the second RH node includes the IP address of the first region 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 can be returned as it is, that is, the service data can be sent back to the first MEC node (that is, the MEC node that requests to obtain the service data) in the reverse direction according to the sending sequence of the service data obtaining request message.
In the embodiment of the present invention, a first MEC node sends 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 second content provider, a service name of a 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 a target MEC node is an MEC node which has 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 not the MEC node which has the connection relation with the first RH node, the first RH node sends a service data registration request message to the first region 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 an MEC node in the first region (i.e., a region corresponding to the first MEC node); and 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, that is, an RH node in the first region having a connection relationship with the target MEC node; then, the first region RH node sends the service data acquisition request message to the second RH node, so that the second RH node acquires the service data corresponding to the second service from the target MEC node. In the embodiment of the present invention, because the first RH node determines that the target MEC node is not an MEC node having a connection relationship with the first RH node, the first RH node may determine that the first RH node is not a previous-hop device of the target MEC node, and the first RH node requires the first area RH node to determine the previous-hop device of the target MEC node, that is, the second RH node, so that the first area RH node may obtain, from the target MEC node, service data corresponding to the second service through the second RH node, which may improve efficiency of determining the third RH node, and improve efficiency of the first MEC node when obtaining the service data from the target MEC node through the second RH node in the first area.
In another implementation manner, referring to fig. 5, as shown in fig. 6, after the above step S217, the method for acquiring service data provided in the embodiment of the present invention may also be implemented through steps S301 to S307.
S301: and under the condition that 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 equipment.
In conjunction with the description of the foregoing embodiment, it should be understood that the service data acquisition request message includes a public key hash value corresponding to the second content provider, a service name of the second service, and a zone identifier of the target zone.
S302, the area transfer device receives a service data acquisition request message from the first area RH node.
S303, the area transfer equipment determines the IP address of the RH node of the second area according to the area identification of the target area.
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 area RH node determines that the target MEC node is not one MEC node in the first area, it indicates that the area identifier corresponding to the target area is different from the area identifier of the first area, the first area RH node may send the service data acquisition request message to the area transit device, and the area transit device allocates the IP address of the second area RH node corresponding to the area identifier of the target area. It is to be understood that the area relay device stores therein a correspondence relationship between the area identifier and the IP address of the area RH node, and the following table 3 is an example of a correspondence relationship between the area identifier stored in the area relay device and the IP address of the area RH node.
TABLE 3
Figure BDA0002676265050000201
Figure BDA0002676265050000211
From above, if the region of the target region is identified as D2The area relay device determines that the IP address of the second area RH node is IP address 2.
S304, the region transfer equipment sends a service data acquisition request message to a second region RH node.
With reference to the description of the foregoing embodiment, it should be understood that the service data acquisition request message sent by the regional relay device to the second regional RH node further includes an IP address of the regional relay device.
S305, the second region RH node receives the service data acquisition request message from the region transfer device.
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.
And the third RH node is an RH node which has a connection relation with the target MEC node in a second area, and the second area is an area corresponding to the RH node of the second area.
Specifically, the process of determining the third node by the second region 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 according to the public key hash value corresponding to the second content provider and the name of the second service, whether the target MEC node is an MEC node having a connection relationship with the first RH node, and details thereof are not repeated here.
Illustratively, in connection with the example in S218 above, assume that the region identification of the target region is D2(the area identifier of the target area is different from the area identifier corresponding to the first MEC node), that is, the area RH node 208 determines that the target MEC node is not an MEC node in the first area, and the area RH node 208 sends a service data acquisition request message to the area transit device 210. Further, assuming that the regional transfer 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 after receiving the service data acquisition request message, the regional transfer device 210 sends a service data acquisition request message to the regional RH node 209The RH node 207 is a 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 the service data corresponding to the second service from the MEC node 204.
And 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 region RH node sends a service data acquisition request message to the third RH node, so that the third RH node acquires the service data corresponding to the second service from the target MEC node.
In the embodiment of the present invention, a first MEC node sends 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 second content provider, a service name of a 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 a target MEC node is an MEC node which has 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 not the MEC node which has the connection relation with the first RH node, the first RH node sends a service data registration request message to the first region 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 an MEC node in the first region (i.e., a region corresponding to the first MEC node); under the condition that 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 equipment, and the region transfer equipment 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 (that is, 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 region RH node sends a service data acquisition request message to the third RH node, so that the third RH node can acquire the service data corresponding to the second service from the target MEC node. In the embodiment of the present invention, the first area RH node determines that the target MEC node is not an MEC node in the first area, which indicates that the area identifier of the target area is different from the area identifier of the first area, the first area RH node may send the service data acquisition request message to the area transit device, the area transit device may determine the IP address of the second area RH node (i.e., the area RH node other than the first area RH node in the network) based on the area identifier of the target area, and determining the last hop device of the target MEC node from the second area through the second area RH node, namely, the third RH node, so that the second region RH node can obtain the service data corresponding to the second service from the target MEC node through the third RH node, the efficiency of determining the third RH node can be improved, and improving the efficiency of the first MEC node in acquiring the service data from the target MEC node through the third RH node in the second area.
In the embodiment of the present invention, the functional modules of the first MEC node, the first RH node, the first region RH node, and the like may be divided according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, the division of the modules in the embodiment of the present invention is schematic, and is only a logic function division, and there may be another division manner in actual implementation.
In the case of dividing each functional module by corresponding functions, fig. 7 shows a possible structural schematic diagram of the first MEC node involved in the foregoing embodiment, as shown in fig. 7, the first MEC node 40 may include: a sending module 401.
A sending module 401, 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 obtaining apparatus of service data (i.e., a first MEC node 40), 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.
Optionally, the sending module 401 is further configured to send a service data obtaining request message to the first RH node, where the service data obtaining 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, the service data obtaining request message is used to request to obtain 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 service data corresponding to the second service.
In case of integrated units, fig. 8 shows a possible structural schematic of the first MEC node involved in the above embodiments. 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 used 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 include a storage module 503 for storing program codes and data of the first MEC node 50.
The processing module 501 may be a processor or a controller (for example, the processor 301 shown in fig. 3). The communication module 502 may be a transceiver, a transceiver circuit, or a communication interface, etc. (e.g., may be the network interface 303 as shown in fig. 3 described above). The storage module 503 may be a memory (e.g., may be the memory 302 described above with reference to fig. 3).
When 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 (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc.
In the case of dividing the functional modules by corresponding functions, fig. 9 shows a possible structural diagram of the first RH node involved in the foregoing embodiments, and as shown in fig. 9, the first RH node 60 may include: a receiving module 601 and a sending module 602.
A receiving module 601, 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.
A sending module 602, configured to send 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, and the first MEC node stores service data corresponding to the first service.
Optionally, the first RH node 60 may further include: 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 a second service, and an area identifier of a target area, 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 an MEC node in which service data corresponding to the second service is stored.
A determining module 603, 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 an MEC node that has a connection relationship with an acquiring apparatus of service data (i.e., the first RH node 60).
An obtaining module 604, configured to obtain, when the determining module 603 determines that the target MEC node is an MEC node having a connection relationship with the apparatus for obtaining the service data, 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 region RH node when the determining module 603 determines that the target MEC node is not an MEC node having a connection relationship with the acquisition apparatus of the service data.
In the case of integrated cells, fig. 10 shows a possible structural diagram of the first RH node involved in the above-described embodiments. As shown in fig. 10, the first RH node 70 may include: a processing module 701 and a communication module 702. The processing module 701 may be used 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 include a storage module 703 for storing program codes and data of the first RH node 70.
The processing module 701 may be a processor or a controller (for example, the processor 301 shown in fig. 3). The communication module 702 may be a transceiver, a transceiver circuit, or a communication interface, etc. (e.g., may be the network interface 303 as shown in fig. 3 described above). The storage module 703 may be a memory (e.g., may be the memory 302 described above with reference to 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 by a bus. The bus may be a PCI bus or an EISA bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc.
In the case of dividing each functional module by corresponding functions, fig. 11 shows a possible structural diagram of the first region RH node involved in the foregoing embodiment, and as shown in fig. 11, the first region RH node 80 may include: a module 801 is received.
A receiving module 801, 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, and the service data notification message is used to notify an obtaining apparatus of service data (i.e., a first area RH node 80), where the first MEC node stores service data corresponding to the first service, and the first service is a service provided by the first content provider.
Optionally, the first region RH node 80 may further include: a determination module 802 and a sending 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, 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 an MEC node storing service data corresponding to the second service.
A determining module 802, configured to determine, according to the area identifier of the target area, whether the target MEC node is an 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, when the determining module 802 determines that the target MEC node is an MEC node in the first area, determine 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 and in connection with the target MEC node.
A sending module 803, configured to send the service data obtaining request message to the second RH node, so that the second RH node obtains the service data corresponding to the second service from the target MEC node.
In the case of integrated cells, fig. 12 shows a possible structural representation of the first RH area node involved in the above-described embodiments. As shown in fig. 12, the first region RH node 90 may include: a processing module 901 and a communication module 902. The processing module 901 may be configured to control and manage the actions of the first region 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, configured to store program codes and data of the first region RH node 90.
The processing module 901 may be a processor or a controller (for example, the processor 301 shown in fig. 3). The communication module 902 may be a transceiver, a transceiver circuit, or a communication interface, etc. (e.g., may be the network interface 303 as shown in fig. 3 described above). The storage module 903 may be a memory (e.g., may be the memory 302 described above with reference to 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 bus may be divided into an address bus, a data bus, a control bus, etc.
It should be understood that, in various embodiments of the present invention, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation 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 implementation. 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 is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
The units described as separate parts may or may not be physically separate, and parts displayed 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 can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented using a software program, 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. The procedures or functions described in accordance with the embodiments of the invention are all or partially effected when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optics, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or can comprise one or more data storage devices, such as a server, a data center, etc., that can be integrated with the medium. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered 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 (12)

1. A method for acquiring service data is characterized by comprising the following steps:
a first mobile edge computing MEC node sends a service data registration request message to a first analysis processing 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 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.
2. The method of claim 1, further comprising:
the first MEC node sends a service data acquisition request message to the first RH node, wherein 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 a region identifier of a target region, 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 region is a region corresponding to a target MEC node, and the target MEC node is an MEC node storing service data corresponding to the second service.
3. A method for acquiring service data is characterized by comprising the following steps:
a first analysis processing RH node receives a service data registration request message of a first mobile edge computing 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 a service provided by the first content provider;
the first RH node sends 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 region identifier corresponding to the first MEC node, and the service data notification message is used to notify the first regional RH node, and the first MEC node stores therein service data corresponding to the first service.
4. The method of claim 3, further comprising:
the first RH node receives 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, 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 an MEC node storing service data corresponding to the second service;
the first RH node determines whether the target MEC node is an MEC node which has 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;
when the first RH node determines that the target MEC node is an MEC node having a connection relationship with the first RH node, the first RH node acquires, from the target MEC node, service data corresponding to the second service;
and under the condition that the first RH node determines that the target MEC node is not an MEC node having a connection relation with the first RH node, the first RH node sends the service data acquisition request message to the first region RH node.
5. A method for acquiring service data is characterized by comprising the following steps:
a first region parsing processing RH node receives 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 a region identifier of a first mobile edge computing 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, and the first service is a service provided by the first content provider.
6. The method of claim 5, further comprising:
the first regional RH node receives 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 a region identifier of a target region, 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 region is a region corresponding to a target MEC node, and the target MEC node is an MEC node storing service data corresponding to the second service;
the first region RH node determines whether the target MEC node is an MEC node in a first region according to the region identifier of the target region, wherein the first region is a 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, 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 service name of the second service, where the second RH node is an RH node in the first region that has a connection relationship with the target MEC node;
and the first region RH node sends the service data acquisition request message to the second RH node, so that the second RH node acquires the service data corresponding to the second service from the target MEC node.
7. The device for acquiring the service data is characterized by comprising a sending module;
the sending module is configured to send a service data registration request message to a first RH node for resolution processing, 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 acquisition device of the service data, and the service data registration request message is used to register the service data corresponding to the first service, where the first service is a service provided by the first content provider.
8. The apparatus for acquiring service data according to claim 7,
the sending module 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 a second service, and an area identifier of a target area, 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 mobile edge computing MEC node, and the target MEC node is an MEC node in which service data corresponding to the second service is stored.
9. The device for acquiring the service data is characterized by comprising a receiving module and a sending module;
the receiving module is configured to receive a service data registration request message of a first mobile edge computing 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, 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;
the sending module is configured to send a service data notification message to a first regional analysis processing 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 regional RH node, and the first MEC node stores service data corresponding to the first service.
10. The apparatus for acquiring service data according to claim 9, wherein the apparatus for acquiring service data further comprises a determining module and an acquiring module;
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, 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 an MEC node in which service data corresponding to the second service is stored;
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 an MEC node having a connection relationship with the service data acquiring apparatus;
the acquiring module is configured to acquire, from the target MEC node, service data corresponding to the second service when the determining module determines that the target MEC node is an MEC node having a connection relationship with the apparatus for acquiring service data;
the sending module is further configured to send the service data acquisition request message to the first region RH node when the determining module determines that the target MEC node is not an MEC node having a connection relationship with the apparatus for acquiring service data.
11. The device for acquiring the service data is characterized by comprising 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 mobile edge computing MEC node, and the service data notification message is used to notify an obtaining apparatus of the service data, where the first MEC node stores service data corresponding to the first service, and the first service is a service provided by the first content provider.
12. The apparatus for acquiring service data according to claim 11, wherein the apparatus for acquiring service data further comprises a determining module and a sending module;
the receiving module 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, 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 an MEC node storing 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 an 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 the first area and having a connection relationship with the target MEC node;
the sending module is configured to send the service data obtaining request message to the second RH node, so that the second RH node obtains the 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 true CN112153021A (en) 2020-12-29
CN112153021B 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 (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030041178A1 (en) * 2001-03-26 2003-02-27 Lev Brouk System and method for routing messages between applications
CN101047512A (en) * 2006-03-31 2007-10-03 国际商业机器公司 Service logger and correlation system and method
CN102118370A (en) * 2009-12-31 2011-07-06 华为技术有限公司 Service management method, device and system
US8060616B1 (en) * 2008-11-17 2011-11-15 Amazon Technologies, Inc. Managing CDN registration by a storage provider
US8065417B1 (en) * 2008-11-17 2011-11-22 Amazon Technologies, Inc. Service provider registration by a content broker
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
US20160301598A1 (en) * 2013-03-18 2016-10-13 Koninklijke Npn N.V. Localizing and Placement of Network Node Functions in a Network
CN106576074A (en) * 2015-07-31 2017-04-19 华为技术有限公司 Routing rule acquisition method, device and system
CN107770815A (en) * 2017-10-18 2018-03-06 中国联合网络通信集团有限公司 A kind of location-based MEC method and apparatus
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
CN109782695A (en) * 2017-11-13 2019-05-21 华中科技大学 A kind of control method for manufacturing equipment, device and system
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
CN110381162A (en) * 2019-07-29 2019-10-25 腾讯科技（深圳）有限公司 A kind of method and relevant apparatus of business processing
CN110519074A (en) * 2018-05-22 2019-11-29 华为技术有限公司 A kind of coverage management method and device
CN111338573A (en) * 2020-02-19 2020-06-26 中国联合网络通信集团有限公司 Terminal data management method and system, server and communication terminal
CN111345008A (en) * 2017-11-22 2020-06-26 华为技术有限公司 Mobile edge host service notification method and device
CN111385317A (en) * 2018-12-27 2020-07-07 华为技术有限公司 Data transmission method, device and system
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

Patent Citations (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030041178A1 (en) * 2001-03-26 2003-02-27 Lev Brouk System and method for routing messages between applications
CN101047512A (en) * 2006-03-31 2007-10-03 国际商业机器公司 Service logger and correlation system and method
US8060616B1 (en) * 2008-11-17 2011-11-15 Amazon Technologies, Inc. Managing CDN registration by a storage provider
US8065417B1 (en) * 2008-11-17 2011-11-22 Amazon Technologies, Inc. Service provider registration by a content broker
CN102118370A (en) * 2009-12-31 2011-07-06 华为技术有限公司 Service management method, device and system
US20160301598A1 (en) * 2013-03-18 2016-10-13 Koninklijke Npn 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
CN106576074A (en) * 2015-07-31 2017-04-19 华为技术有限公司 Routing rule acquisition method, device and system
CN109218363A (en) * 2017-07-03 2019-01-15 ***通信有限公司研究院 Content distribution method, network node and storage medium
CN107770815A (en) * 2017-10-18 2018-03-06 中国联合网络通信集团有限公司 A kind of location-based MEC method and apparatus
CN109782695A (en) * 2017-11-13 2019-05-21 华中科技大学 A kind of control method for manufacturing equipment, device and system
CN111345008A (en) * 2017-11-22 2020-06-26 华为技术有限公司 Mobile edge host service notification method and device
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
CN110519074A (en) * 2018-05-22 2019-11-29 华为技术有限公司 A kind of coverage management method and device
CN109040259A (en) * 2018-08-09 2018-12-18 中国联合网络通信集团有限公司 A kind of CDN node distribution method and system based on MEC
CN111385317A (en) * 2018-12-27 2020-07-07 华为技术有限公司 Data transmission method, device and system
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
CN110381162A (en) * 2019-07-29 2019-10-25 腾讯科技（深圳）有限公司 A kind of method and relevant apparatus of business processing
CN111338573A (en) * 2020-02-19 2020-06-26 中国联合网络通信集团有限公司 Terminal data management method and system, server and communication terminal
CN111556514A (en) * 2020-04-14 2020-08-18 北京航空航天大学 Decentralized mobile edge computing resource discovery and selection method and system

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
汪润等: "服务发布与发现在面向服务的架构中的研究与应用", 《电脑知识与技术》 *
赵立志: "基于面向服务体系结构SOA的ICT业务集成研究", 《科技资讯》 *
邢燕霞;魏文娟;李鹏宇;毛聪杰;: "5G核心网络关键技术和对业务的支撑", 电信技术 *

Also Published As

Publication number Publication date
CN112153021B (en) 2023-05-19

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
CN110691384A (en) Network slice using method and device
CN111432001B (en) Method, apparatus, electronic device and computer readable medium for jumping scenes
CN114257440B (en) Network function service discovery method, system and storage medium
CN114745724B (en) Access processing method and device, electronic equipment and computer readable medium
CN113127168A (en) Service distribution method, system, device, server and medium
CN111209306A (en) Business logic judgment method and device, electronic equipment and storage medium
CN113498110B (en) Service message transmission method and related equipment
CN111510466A (en) Data updating method and device for client, electronic equipment and readable medium
CN112714042B (en) Pressure testing method and device, electronic equipment and storage medium
WO2018076712A1 (en) Terminal authentication method and device
CN112153021B (en) Service data acquisition method and device
CN112306685A (en) Task isolation method and device, electronic equipment and computer readable medium
US20230208659A1 (en) Blockchain apparatus and method for mobile edge computing
CN112148320A (en) Application program upgrading method, device, equipment and storage medium
US20220217539A1 (en) Authorization in cellular communication systems
CN113365272B (en) Method and system for preventing network from being rubbed
CN115801686A (en) Service request processing method, device, equipment and storage medium
KR101104066B1 (en) Authentication system and method for wireless fidelity connection authentication
US20130137461A1 (en) Method and apparatus for inserting location data into messages at a communication gateway
CN113271320B (en) Terminal authentication method, device, system, medium and equipment
CN116319322B (en) Power equipment node communication connection method, device, equipment and computer medium
CN113282391B (en) Cluster switching method, cluster switching device, electronic equipment and readable storage medium
CN116455652A (en) Processing method, device, equipment and medium based on authentication routing rule

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