Method, device, electronic device and storage medium for implementing data distribution service

Abstract

The application provides a method and device for realizing data distribution service, electronic equipment and storage medium, and relates to the technical field of communication. The method comprises the following steps: obtaining a target topic identifier by analyzing a data distribution service request through a target communication component; searching a local topic cache through the target communication component based on the target topic identifier, and determining whether a target matching table item corresponding to the target topic identifier exists; and if the target matching table item exists, forwarding the data distribution service request to a peer terminal indicated by the target matching table item through the target communication component. The data distribution service request can be distributed to the corresponding peer terminal based on the data distribution information in the target matching table item in the wireless network, so that the advantages of DDS can be fully utilized in the wireless network environment, and the implementation can be compatible with the application program corresponding to the deployed DDS mechanism, and has the characteristics of strong applicability.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method, apparatus, electronic device and storage medium for implementing data distribution services. Background Technology

[0002] Data Distribution Service (DDS) is middleware that employs a publish / subscribe model and provides various QoS (Quality of Service) policies to ensure real-time, efficient, and flexible data distribution, meeting the needs of various distributed real-time communication applications. Furthermore, DDS's real-time performance effectively supports high-speed and frequent data exchange.

[0003] In existing technologies, DDS is mainly designed for wired network environments. The data distribution mechanism based on DDS mainly relies on each DDS communication peer to maintain a list of other peer IP addresses to achieve data distribution.

[0004] However, due to the special nature of wireless network environments, existing DDS methods are not suitable for wireless network environments, meaning that the advantages of DDS cannot be fully utilized in wireless network environments. Summary of the Invention

[0005] The purpose of this application is to address the shortcomings of the prior art by providing a method, apparatus, electronic device, and storage medium for implementing data distribution services, which can fully leverage the advantages of DDS in a wireless network environment.

[0006] To achieve the above objectives, the technical solutions adopted in the embodiments of this application are as follows:

[0007] In a first aspect, the present invention provides a method for implementing a data distribution service, the method being applied to a communication device, the communication device including a target communication component, the method comprising:

[0008] The target topic identifier is obtained by parsing the data distribution service request through the target communication component.

[0009] Based on the target topic identifier, the local topic cache is retrieved through the target communication component to determine whether there is a target matching entry corresponding to the target topic identifier;

[0010] If present, the data distribution service request is forwarded to the peer terminal indicated by the target matching entry via the target communication component.

[0011] In an optional implementation, the communication device is a target terminal, and the local topic cache includes: an internal identifier of a virtual network group corresponding to at least one topic identifier during historical data distribution. The step of forwarding the data distribution service request to the peer terminal indicated by the target matching entry through the target communication component includes:

[0012] Based on the local topic cache, the internal identifier of the target virtual network group corresponding to the target topic identifier is determined by the target communication component;

[0013] Based on the local message forwarding table, the target PDU session identifier corresponding to the target topic identifier is determined by the target communication component. The local message forwarding table includes: at least one PDU session identifier corresponding to a topic identifier in the historical data distribution process.

[0014] Based on the internal identifier of the target virtual network group and the target PDU session indicated by the target PDU session identifier, the data distribution service request is forwarded to the peer terminal that is in the same target virtual network group as the target terminal through the target communication component.

[0015] In an optional implementation, the method further includes:

[0016] If the local topic cache does not contain a target matching entry corresponding to the target topic identifier, then a user subscription data modification request is sent to the target management server through the target communication component. The user subscription data modification request includes: target topic identifier and target terminal identifier.

[0017] The target communication component receives user subscription data modification feedback returned by the target management server. This feedback is generated by the unified data management network element based on a user subscription data modification request forwarded by the network open function network element, and then forwarded to the target management server through the network open function network element. The user subscription data modification feedback includes: the external identifier of the target virtual network group where the target terminal is located, the internal identifier corresponding to the external identifier of the target virtual network group, and the target network slice identifier corresponding to the target terminal. The external identifier of the target virtual network group is set according to the target topic identifier.

[0018] Based on the user subscription data modification feedback, a PDU session request is sent to the session management function network element. The PDU session request includes: the target network slice identifier corresponding to the target terminal.

[0019] The target communication component receives the PDU session creation completion response returned by the session management function network element and creates a local target message forwarding item; wherein, after receiving the PDU session request, the session management function network element creates a target user plane function network element according to the target network slice identifier, and creates a target virtual network group with the target topic identifier as the external identifier in the target user plane function network element.

[0020] In an optional implementation, forwarding the data distribution service request to a peer terminal within the same target virtual network group as the target terminal via the target PDU session indicated by the target PDU session identifier includes:

[0021] The data distribution service request is forwarded to the target user plane function network element corresponding to the target terminal through the target PDU session indicated by the target PDU session identifier, so that the target user plane function network element replicates the corresponding number of data distribution service requests according to the number of peer terminals in the target virtual network group and forwards them to the peer terminal.

[0022] In an optional implementation, the communication device is a target user plane function network element, and the local topic cache includes at least one terminal address identifier corresponding to a topic identifier during the historical data distribution process, and the topic processing status corresponding to each terminal identifier.

[0023] The step of forwarding the data distribution service request to the peer terminal indicated by the target matching entry via the target communication component includes:

[0024] Based on the topic processing status corresponding to the target topic identifier in the target matching entry, the data distribution service request is forwarded to the peer terminal indicated by the terminal address identifier in the target matching entry through the target communication component.

[0025] In an optional implementation, the step of forwarding the data distribution service request to the peer terminal indicated by the terminal address identifier in the target matching entry through the target communication component based on the topic processing status corresponding to the target topic identifier in the target matching entry includes:

[0026] If the topic processing status corresponding to the target topic identifier in the target matching entry is in the write state, and the data distribution service request is a data subscription request, then the data subscription request is forwarded to the peer terminal indicated by the terminal identifier in the target matching entry through the target communication component;

[0027] If the topic processing status corresponding to the target topic identifier in the target matching entry is in the read state, and the data distribution service request is a data publishing request, then the data publishing request is forwarded to the peer terminal indicated by the terminal identifier in the target matching entry through the target communication component.

[0028] In an optional implementation, the method further includes:

[0029] If the local topic cache does not contain a target matching entry corresponding to the target topic identifier, then according to the data distribution service request, the target communication component adds a new target entry in the local topic cache. The target entry includes: the target topic identifier, the address identifier of the target terminal, and the processing status of the target terminal for the target topic identifier in the data distribution service request.

[0030] In a second aspect, the present invention provides an apparatus for implementing a data distribution service, the apparatus being applied to a communication device, the communication device including a target communication component, the apparatus comprising:

[0031] The acquisition module is used to obtain the target topic identifier by parsing the data distribution service request through the target communication component;

[0032] The determination module is used to retrieve the local topic cache through the target communication component based on the target topic identifier to determine whether there is a target matching entry corresponding to the target topic identifier.

[0033] The forwarding module is used to forward the data distribution service request to the peer terminal indicated by the target matching entry through the target communication component, if such a request exists.

[0034] In an optional implementation, the communication device is a target terminal, and the local topic cache includes: an internal identifier of a virtual network group corresponding to at least one topic identifier during the historical data distribution process. The forwarding module is specifically used to determine the internal identifier of the target virtual network group corresponding to the target topic identifier through the target communication component based on the local topic cache.

[0035] Based on the local message forwarding table, the target PDU session identifier corresponding to the target topic identifier is determined by the target communication component. The local message forwarding table includes: at least one PDU session identifier corresponding to a topic identifier in the historical data distribution process.

[0036] Based on the internal identifier of the target virtual network group and the target PDU session indicated by the target PDU session identifier, the data distribution service request is forwarded to the peer terminal that is in the same target virtual network group as the target terminal through the target communication component.

[0037] In an optional implementation, the forwarding module is further configured to send a user subscription data modification request to the target management server through the target communication component if the local topic cache does not contain a target matching entry corresponding to the target topic identifier. The user subscription data modification request includes: target topic identifier and target terminal identifier.

[0038] The target communication component receives user subscription data modification feedback returned by the target management server. This feedback is generated by the unified data management network element based on a user subscription data modification request forwarded by the network open function network element, and then forwarded to the target management server through the network open function network element. The user subscription data modification feedback includes: the external identifier of the target virtual network group where the target terminal is located, the internal identifier corresponding to the external identifier of the target virtual network group, and the target network slice identifier corresponding to the target terminal. The external identifier of the target virtual network group is set according to the target topic identifier.

[0039] Based on the user subscription data modification feedback, a PDU session request is sent to the session management function network element. The PDU session request includes: the target network slice identifier corresponding to the target terminal.

[0040] The target communication component receives the PDU session creation completion response returned by the session management function network element and creates a local target message forwarding item; wherein, after receiving the PDU session request, the session management function network element creates a target user plane function network element according to the target network slice identifier, and creates a target virtual network group with the target topic identifier as the external identifier in the target user plane function network element.

[0041] In an optional implementation, the forwarding module is specifically configured to forward the data distribution service request to the target user plane function network element corresponding to the target terminal through the target PDU session indicated by the target PDU session identifier, so that the target user plane function network element replicates a corresponding number of data distribution service requests according to the number of peer terminals in the target virtual network group and forwards them to the peer terminal.

[0042] In an optional implementation, the communication device is a target user plane function network element, and the local topic cache includes at least one terminal address identifier corresponding to a topic identifier during the historical data distribution process, and the topic processing status corresponding to each terminal identifier.

[0043] The forwarding module is specifically used to forward the data distribution service request to the peer terminal indicated by the terminal address identifier in the target matching entry, based on the topic processing status corresponding to the target topic identifier in the target matching entry, through the target communication component.

[0044] In an optional implementation, the forwarding module is specifically used to forward the data subscription request to the peer terminal indicated by the terminal identifier in the target matching entry through the target communication component if the topic processing status corresponding to the target topic identifier in the target matching entry is a write status and the data distribution service request is a data subscription request.

[0045] If the topic processing status corresponding to the target topic identifier in the target matching entry is in the read state, and the data distribution service request is a data publishing request, then the data publishing request is forwarded to the peer terminal indicated by the terminal identifier in the target matching entry through the target communication component.

[0046] In an optional implementation, the forwarding module is further configured to, if the local topic cache does not contain a target matching entry corresponding to the target topic identifier, add a target entry in the local topic cache through the target communication component according to the data distribution service request. The target entry includes: the target topic identifier, the address identifier of the target terminal, and the processing status of the target terminal for the target topic identifier in the data distribution service request.

[0047] Thirdly, the present invention provides an electronic device, comprising: a processor, a storage medium, and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the steps of the method for implementing a data distribution service as described in any of the foregoing embodiments.

[0048] Fourthly, the present invention provides a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the method for implementing a data distribution service as described in any of the foregoing embodiments.

[0049] The beneficial effects of this application are:

[0050] The method, apparatus, electronic device, and storage medium for implementing data distribution services provided in this application can be applied to communication devices, which include a target communication component. The method includes: obtaining a target topic identifier by parsing a data distribution service request through the target communication component; based on the target topic identifier, searching the local topic cache through the target communication component to determine whether a target matching entry corresponding to the target topic identifier exists; if it exists, forwarding the data distribution service request to the peer terminal indicated by the target matching entry through the target communication component. This enables the data distribution service request to be distributed to the corresponding peer terminal in a wireless network based on the data distribution information in the target matching entry. This allows the advantages of DDS to be fully utilized in a wireless network environment, and the implementation is compatible with applications corresponding to the deployed DDS mechanism. That is, no further modifications to the applications corresponding to the DDS mechanism are required to implement data distribution operations in a wireless network. Attached Figure Description

[0051] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0052] Figure 1 A flowchart illustrating a method for implementing a data distribution service, provided as an embodiment of this application;

[0053] Figure 2 A system architecture diagram for implementing a data distribution service is provided in an embodiment of this application;

[0054] Figure 3 A flowchart illustrating another method for implementing a data distribution service provided in an embodiment of this application;

[0055] Figure 4 A flowchart illustrating another method for implementing a data distribution service provided in an embodiment of this application;

[0056] Figure 5 Another system architecture diagram for implementing data distribution services provided in this application embodiment;

[0057] Figure 6 A schematic diagram of functional modules of an apparatus for implementing a data distribution service provided in an embodiment of this application;

[0058] Figure 7 This is a schematic diagram of an electronic device structure provided in an embodiment of this application. Detailed Implementation

[0059] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.

[0060] Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0061] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0062] The technical solutions of this application embodiment can be applied to various local communication systems, such as: Global System for Mobile Communications (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, 5th Generation (5G) communication system, or future new radio access technology (NR), etc.

[0063] In some embodiments, the network architecture may be, for example, a non-roaming architecture.

[0064] The network architecture may specifically include the following network elements:

[0065] 1. User Equipment (UE): This can be referred to as user equipment, terminal, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication equipment, user agent, or user device. UE can also be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, terminal equipment in a 5G network, or terminal equipment in a future evolved public land mobile network (PLMN), etc. It can also be an end device, logical entity, smart device, such as a mobile phone, smart terminal, or other terminal equipment; or a server, gateway, base station, controller, or other communication equipment; or an Internet of Things (IoT) device, such as a sensor, electricity meter, water meter, etc. This application's embodiments do not limit this.

[0066] 2. Access Network (AN): Provides network access functionality for authorized users in a specific area and can use transmission tunnels of different quality depending on the user's level and service requirements. Access networks can employ different access technologies. Currently, there are two types of radio access technologies: 3rd Generation Partnership Project (3GPP) access technologies (such as those used in 3G, 4G, or 5G systems) and non-3GPP access technologies. 3GPP access technologies refer to access technologies that conform to 3GPP standards and specifications. Access networks using 3GPP access technologies are called radio access networks (RANs). In 5G systems, access network equipment is called next-generation node base stations (gNBs). Non-3GPP access technologies refer to access technologies that do not conform to 3GPP standards and specifications, such as air interface technologies represented by access points (APs) in Wi-Fi.

[0067] An access network that uses wireless communication technology to implement access network functions can be called a radio access network (RAN). A RAN manages radio resources, provides access services to terminals, and facilitates the forwarding of control signals and user data between terminals and the core network.

[0068] The access network equipment may include devices within the access network that communicate with wireless terminals via one or more sectors on the air interface. The access network system may be used to convert received air frames to and from Internet Protocol (IP) packets, and act as a router between the wireless terminal and the rest of the access network, which may include an IP network. The wireless access network system may also coordinate the attribute management of the air interface. It should be understood that access network equipment includes, but is not limited to: evolved node B (eNB), radio network controller (RNC), node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved node B, or home node B, HNB), base band unit (BBU), access point (AP), wireless relay node, wireless backhaul node, transmission and reception point (TRP or transmission point, TP) in a wireless fidelity (WIFI) system, and can also be gNB in ​​5G, such as NR, or transmission point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or can also be network nodes constituting a gNB or transmission point, such as base band unit (BBU) or distributed unit (DU), etc.

[0069] In some deployments, a gNB may include a centralized unit (CU) and a DU. The gNB may also include a radio unit (RU). The CU implements some of the gNB's functions, and the DU implements others. For example, the CU implements radio resource control (RRC) and packet data convergence protocol (PDCP) layer functions, while the DU implements radio link control (RLC), media access control (MAC), and physical (PHY) layer functions. Since RRC layer information ultimately becomes PHY layer information, or is derived from PHY layer information, in this architecture, higher-layer signaling, such as RRC layer signaling, can be considered to be sent by the DU, or by the DU+CU. It is understood that access network equipment can be a CU node, a DU node, or a device including both CU and DU nodes. Furthermore, the CU can be classified as an access network device in the radio access network (RAN) or as an access network device in the core network (CN), without any restrictions.

[0070] 3. Access and Mobility Management Function (AMF) Entity: Primarily used for mobility management and access management, it can implement functions of the Mobility Management Entity (MME) other than session management, such as lawful interception or access authorization (or authentication). In the embodiments of this application, it can be used to implement the functions of the access and mobility management network element.

[0071] 4. Session Management Function (SMF) Entity: Primarily used for session management, UE Internet Protocol (IP) address allocation and management, selection of manageable user plane functions, policy control, or endpoints for charging function interfaces, and downlink data notification, etc. In this embodiment, it can be used to implement the functions of the session management network element.

[0072] 5. User Plane Function (UPF) Entity: This is the data plane gateway. It can be used for packet routing and forwarding, or for quality of service (QoS) processing of user plane data. User data can access the data network (DN) through this network element. In this embodiment, it can be used to implement the functions of a user plane gateway.

[0073] 6. Policy control function (PCF) entity: A unified policy framework used to guide network behavior, providing policy rule information to control plane functional network elements (such as AMF, SMF, etc.).

[0074] 7. Unified Data Management (UDM) entity: Used to handle user identification, access authentication, registration, or mobility management, etc.

[0075] 8. The Network Exposure Function (NEF) entity: This is a network function that 5GC opens up to the outside world and provides standard interfaces. Based on 3GPP network functions, it discloses functions and events to other systems through NEF, providing both openness and ensuring system security.

[0076] In this network architecture, the N1 interface serves as the reference point between the terminal and the AMF entity; the N2 interface serves as the reference point between the AN and the AMF entities, used for sending non-access stratum (NAS) messages, etc.; the N3 interface serves as the reference point between the (R)AN and the UPF entity, used for transmitting user plane data, etc.; the N4 interface serves as the reference point between the SMF entity and the UPF entity, used for transmitting information such as tunnel identification information for the N3 connection, data buffer indication information, and downlink data notification messages, etc.; and the N6 interface serves as the reference point between the UPF entity and the DN, used for transmitting user plane data, etc.

[0077] It should be understood that the network architecture described above in the embodiments of this application is merely an example of a network architecture described from the perspective of a traditional point-to-point architecture and a service-oriented architecture. The network architecture applicable to the embodiments of this application is not limited to this, and any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiments of this application.

[0078] It should also be understood that Figure 1The AMF, SMF, UPF, PCF, and UDM entities shown can be understood as network elements in the core network used to implement different functions, such as network slices that can be combined as needed. These core network elements can be independent devices or integrated into the same device to implement different functions; this application does not limit this.

[0079] In the following text, for ease of explanation, the entity used to implement AMF will be referred to as AMF, and the entity used to implement PCF will be referred to as PCF. It should be understood that the above naming is only for distinguishing different functions and does not mean that these network elements are independent physical devices. This application does not limit the specific form of the above network elements; for example, they can be integrated into the same physical device or they can be different physical devices. Furthermore, the above naming is only for distinguishing different functions and should not constitute any limitation on this application. This application does not exclude the possibility of using other naming in 5G networks and other future networks. For example, in 6G networks, some or all of the above network elements may use the terminology from 5G, or they may use other names, etc. This is explained uniformly here and will not be repeated below.

[0080] It should also be understood that Figure 1 The interface names between the various network elements are merely examples; in actual implementations, the interface names may differ, and this application does not impose any specific limitations on them. Furthermore, the names of the messages (or signaling) transmitted between the aforementioned network elements are also merely examples and do not constitute any limitation on the function of the messages themselves.

[0081] Figure 1 This is a flowchart illustrating a method for implementing a data distribution service, provided as an embodiment of this application. This method can be applied to a communication device, which includes a target communication component. Figure 1 As shown, the method includes:

[0082] S101. Obtain the target topic identifier by parsing the data distribution service request through the target communication component.

[0083] Optionally, a Data Distribution Service (DDS) request can be generated by a terminal in a wireless network environment. In some embodiments, an application corresponding to the DDS mechanism can be deployed on the terminal, and the data distribution service request can be generated by triggering the application.

[0084] The target communication component can be deployed on the communication device. This target communication component can intercept and parse the generated data distribution service request to extract the target topic identifier. The target topic identifier serves as the medium for information transmission between the two parties (data publisher and data subscriber) during data interaction, and can provide real-time information transmission for both parties.

[0085] S102. Based on the target topic identifier, retrieve the local topic cache through the target communication component to determine whether there is a target matching entry corresponding to the target topic identifier.

[0086] The local topic cache may include data distribution information corresponding to at least one topic identifier during historical data distribution. For example, it may include the address of the peer terminal corresponding to each topic identifier, the communication channel identifier corresponding to each topic identifier, etc., without limitation. It is understood that by searching the local topic cache for a target matching entry corresponding to the target topic identifier through the target communication component, the data distribution information of the peer terminal corresponding to that target topic identifier can be quickly determined.

[0087] S103. If it exists, then forward the data distribution service request to the peer terminal indicated by the target matching entry through the target communication component.

[0088] Based on the above description, if a target matching entry corresponding to the target topic identifier exists in the local topic cache, the data distribution information of the peer terminal can be extracted from the target matching entry. Then, the data distribution service request can be distributed to the corresponding peer terminal in the wireless network based on the data distribution information. In this way, the advantages of DDS can be fully utilized in the wireless network environment. Moreover, the implementation of this application embodiment can be compatible with the application corresponding to the deployed DDS mechanism. That is, no further modification to the application corresponding to the DDS mechanism is required to realize the data distribution operation in the wireless network.

[0089] In summary, this application provides a method for implementing a data distribution service. This method can be applied to a communication device, which includes a target communication component. The method includes: obtaining a target topic identifier by parsing a data distribution service request through the target communication component; based on the target topic identifier, searching the local topic cache through the target communication component to determine whether a target matching entry corresponding to the target topic identifier exists; if it exists, forwarding the data distribution service request to the peer terminal indicated by the target matching entry through the target communication component. This enables the data distribution service request to be distributed to the corresponding peer terminal in a wireless network based on the data distribution information in the target matching entry. In this way, the advantages of DDS can be fully utilized in the wireless network environment, and this implementation is compatible with the application corresponding to the deployed DDS mechanism. That is, no further modification to the application corresponding to the DDS mechanism is required to implement data distribution operations in the wireless network.

[0090] Figure 2 This application provides a system architecture diagram for implementing a data distribution service. Figure 3 This is a flowchart illustrating another method for implementing a data distribution service provided in an embodiment of this application. Wherein, as... Figure 2 As shown, the communication device can be the target terminal UE, and the local topic cache includes: the internal identifier of the virtual network group corresponding to at least one topic identifier during the historical data distribution process.

[0091] Reference Figure 3 As shown, the above-mentioned forwarding of data distribution service requests to the peer terminal indicated by the target matching entry through the target communication component includes:

[0092] S201. Based on the local topic cache, determine the internal identifier of the target virtual network group corresponding to the target topic identifier through the target communication component.

[0093] Optionally, the local topic cache may include: an internal identifier of a virtual network group corresponding to at least one topic identifier during historical data distribution. In some embodiments, its specific form may be [<T_ID,V_ID> []., where [.] represents a list.<T_ID,V_ID> For an entry in the list, T_ID indicates the topic identifier in the data distribution service request sent by the target terminal, and V_ID indicates the internal identifier of the VN group corresponding to T_ID.

[0094] In some embodiments, an application corresponding to the DDS mechanism can be deployed on the target terminal. Data distribution service requests can be sent through this application and intercepted and parsed by the target communication component deployed on the target terminal. The target topic identifier is read and used as an index to retrieve the local topic cache, thereby determining the internal identifier of the target virtual network group corresponding to the target topic identifier.

[0095] S202. Based on the local message forwarding table, determine the target PDU session identifier corresponding to the target topic identifier through the target communication component.

[0096] The target terminal may further include a local message forwarding table, which may include: at least one PDU session identifier corresponding to a topic identifier during historical data distribution. Optionally, each PDU session identifier corresponding to a topic identifier may correspond to a message forwarding item, and its representation may be as follows:<Topic,PDU_ID> In other words, a local message forwarding table can include at least one message forwarding item.

[0097] Based on the above explanation, after reading the target topic identifier, the local message forwarding table can be indexed using the target topic identifier as an index to retrieve the target PDU session identifier corresponding to the target topic identifier.

[0098] S203. Based on the target PDU session indicated by the internal identifier of the target virtual network group and the target PDU session identifier, forward the data distribution service request to the peer terminal that is in the same target virtual network group as the target terminal through the target communication component.

[0099] After determining the internal identifier of the target virtual network group and the target PDU session identifier, the data distribution service request can be forwarded to the peer terminal in the same target virtual network group as the target terminal through the target communication component based on the target PDU session indicated by the target PDU session identifier.

[0100] Optionally, the peer terminal located in the same target virtual network group as the target terminal may include one or more, which is not limited here and may vary depending on the actual application scenario.

[0101] In summary, by applying the embodiments of this application, data distribution service requests and the virtual network group communication mechanism of the wireless network can be combined to achieve efficient data distribution. When the target terminal acts as the data publishing peer, it only needs to send data once on the wireless link to enable all data subscription peers to obtain the subscribed data, without having to send data to each data subscription peer separately in a unicast manner. This can avoid the consumption of a large amount of underlying network bandwidth, avoid severe network congestion, and improve the utilization efficiency of wireless network resources.

[0102] Figure 4 This is a flowchart illustrating another method for implementing a data distribution service provided in an embodiment of this application. Optionally, refer to... Figure 4 and the above Figure 2 As shown, the above method also includes:

[0103] S301. If the local topic cache does not contain a target matching entry corresponding to the target topic identifier, a user subscription data modification request is sent to the target management server through the target communication component.

[0104] The user subscription data modification request includes: target topic identifier and target terminal identifier. For example... Figure 4 As shown, the target management server can establish a communication connection with the target terminal through the base station NG-RAN and UPF.

[0105] If no target matching entry corresponding to the target topic identifier exists in the local topic cache, the target terminal can send a user subscription data modification request to the base station NG-RAN in the communication system through the target communication component, and forward the user subscription data modification request to the target management server through the forwarding of the base station NG-RAN and other network elements.

[0106] S302, Receive user subscription data modification feedback returned by the target management server through the target communication component.

[0107] The user subscription data modification feedback is generated by the UDM network element based on the user subscription data modification request forwarded by the NEF network element, and then forwarded to the target management server through the NEF network element. The user subscription data modification feedback includes: the external identifier of the target virtual network group where the target terminal is located, the internal identifier corresponding to the external identifier of the target virtual network group, and the target network slice identifier corresponding to the target terminal. The external identifier of the target virtual network group is set according to the target topic identifier, and the internal identifier corresponding to the external identifier of the target virtual network group can be automatically generated by the UDM network element according to preset rules, which is not limited here.

[0108] Based on the above description, after receiving the user subscription data modification request, the target management server can forward the request to the NEF, which will then forward it to the UDM. Upon receiving the request, the UDM can modify the target terminal's user subscription data, adding the target terminal to the target virtual network group identified by the target topic identifier, adding the target network slice identifier (S-NSSAI) corresponding to the target terminal to the user subscription data associated with the target terminal, and generating user subscription data modification feedback. This feedback can be used to instruct the target communication component on the target terminal side to create a PDU session oriented towards the target topic identifier using the target network slice identifier. The target network slice identifier corresponding to the target terminal can be determined by the UDM.

[0109] Furthermore, the UDM can return the generated user subscription data modification feedback to the NEF. After receiving the user subscription data modification feedback from the UDM, the NEF forwards it to the target management server. The target management server then forwards the user subscription data modification feedback to the target communication component.

[0110] S303. Based on the user's subscription data modification feedback, send a PDU session request to the SMF network element. The PDU session request includes: the target network slice identifier corresponding to the target terminal.

[0111] The target communication component modifies the feedback based on the received user subscription data, and can read the target network slice identifier and the internal identifier of the target virtual network group where the target terminal is located, and drive the target terminal to initiate a PDU session request to the SMF network element through the base station NG-RAN.

[0112] S304. Receive the PDU session creation completion response returned by the SMF network element through the target communication component, and create a local target message forwarding item.

[0113] When an SMF network element receives a PDU session request, it creates a target UPF network element based on the target network slice identifier, and then creates a target virtual network group in the target UPF network element with the target topic identifier as the external identifier.

[0114] In some embodiments, the SMF network element can read the target network slice identifier S-NSSAI from the PDU session request and create a target UPF network element accordingly to process user plane data associated with S-NSSAI. Further, after creating the target UPF network element, the SMF network element reads the user subscription data associated with the target terminal from the UDM and establishes a target VN group in the target UPF network element with the target topic identifier as the external identifier. In addition, after completing the PDU session creation-related operations, the SMF network element sends a PDU session creation completion response to the target terminal. Upon receiving the PDU session creation completion response from the SMF network element, the target terminal can send this result back to the target communication component.

[0115] Furthermore, after receiving the PDU session creation completion response, the target communication component can create a local target message forwarding entry locally. Optionally, the created local target message forwarding entry can be appended to the local message forwarding table. In some embodiments, the local target message forwarding entry can be represented as follows:<Topic_A,PDU_ID_A> , where Topic_A is the target topic identifier in the data distribution service request, and PDU_ID_A is the PDU session identifier of the PDU session request initiated by the target terminal.

[0116] Optionally, the above-mentioned forwarding of the target PDU session data distribution service request indicated by the target PDU session identifier to the peer terminal within the same target virtual network group as the target terminal includes:

[0117] The target PDU session, indicated by the target PDU session identifier, forwards the data distribution service request to the target user plane function network element corresponding to the target terminal. This allows the target user plane function network element to copy the corresponding number of data distribution service requests based on the number of peer terminals in the target virtual network group and forward them to the peer terminals.

[0118] Based on the above explanation, after a target UPF network element is created according to the target network slice identifier, the target terminal can forward data distribution service requests to the target UPF network element through the target PDU session. Furthermore, for the target UPF network element, since a target VN group with the target topic identifier as the external identifier is established in the target UPF network element, the target UPF network element can copy a corresponding number of data distribution service requests according to the number of peer terminals in the target VN group, and forward the data distribution service requests to each peer terminal respectively, so that DDS can use the VN group communication capability to achieve efficient data distribution.

[0119] In summary, taking the method for implementing data distribution services provided in the embodiments of this application as an example of applying it to a 5G wireless network, the target terminal can have a built-in target communication component. When the application on the target terminal starts the DDS service locally, the built-in target communication component of the target terminal can drive the target terminal to request the creation of the corresponding PDU session and target VN group in the 5G network according to the DDS message type and content. The 5G core network can create the corresponding UPF according to the target network slice identifier in the PDU session establishment request to support data communication oriented towards the target topic identifier.

[0120] Figure 5 This is a system architecture diagram for implementing a data distribution service, provided as an embodiment of this application. Optionally, refer to... Figure 5 As shown, the communication device mentioned above is the target UPF. The local topic cache includes the terminal address identifier corresponding to at least one topic identifier during the historical data distribution process, and the topic processing status corresponding to each terminal identifier. Optionally, the terminal address identifier can be the terminal's IP address, MAC address, etc., which are not limited here.

[0121] In some embodiments, the local topic cache may exist as a list and include multiple entries; optionally, its representation may be [<T_ID,IP_List> ], where [.] represents a local theme cache list,<T_ID,IP_List> This is an entry in the local topic cache list. T_ID indicates the topic identifier issued by the local terminal application, and IP_List is a list of IP addresses, specifically represented as [...].<UE_IP,State> ], UE_IP represents the IP address of the terminal that has subscribed to or published the corresponding T_ID, and State represents the topic processing status of the terminal corresponding to this entry. When State = Writer in an entry in the IP address list, it means that the UE corresponding to this entry has published its corresponding Topic. When State = Reader, it means that the UE corresponding to this entry has subscribed to its corresponding Topic.

[0122] It should be noted that, comparing the cases where the communication device is the target terminal, it can be seen that the local topic caches corresponding to the two are different.

[0123] Optionally, the above-mentioned forwarding of the data distribution service request to the peer terminal indicated by the target matching entry through the target communication component includes:

[0124] Based on the topic processing status corresponding to the target topic identifier in the target matching table, the data distribution service request is forwarded to the peer terminal indicated by the terminal address identifier in the target matching table through the target communication component.

[0125] Optionally, an application corresponding to the DDS mechanism can be deployed on the terminal. This application allows the IP address of the target communication component on the target UPF side to be pre-set as the DDS communication peer. It should be noted, however, that the method for setting the IP address of the target communication component on the target UPF side is not limited to this; for example, it can be achieved through other network elements connected to the target UPF.

[0126] In some embodiments, a data distribution service request can be generated by the terminal. During the data distribution process, after the application on the terminal side issues a data distribution service request, the terminal sends it to the target UPF via NG-RAN. The target UPF forwards the data distribution service request from the terminal to the built-in target communication component.

[0127] Furthermore, the target communication component can read the target topic identifier in the data distribution service request and use it as an index to retrieve the local topic cache. If there is a target matching entry corresponding to the target topic identifier in the local topic cache, that is, there is an entry for the terminal address identifier corresponding to the target topic identifier and the topic processing status corresponding to each terminal identifier, then the target communication component can forward the data distribution service request to the peer terminal indicated by each terminal address identifier in the target matching entry, thereby realizing data communication oriented towards the target topic identifier.

[0128] Optionally, the above-mentioned forwarding of a data distribution service request to the peer terminal indicated by the terminal address identifier in the target matching entry, based on the topic processing status corresponding to the target topic identifier in the target matching entry, through the target communication component, includes:

[0129] If the topic processing status corresponding to the target topic identifier in the target matching entry is in the write state, and the data distribution service request is a data subscription request, then the data subscription request is forwarded to the peer terminal indicated by the terminal identifier in the target matching entry through the target communication component; if the topic processing status corresponding to the target topic identifier in the target matching entry is in the read state, and the data distribution service request is a data publishing request, then the data publishing request is forwarded to the peer terminal indicated by the terminal identifier in the target matching entry through the target communication component.

[0130] It should be noted that different data forwarding operations can be performed during the data distribution process depending on the processing status of the topic corresponding to the target topic identifier.

[0131] Specifically, if the topic processing state corresponding to the target topic identifier in the target matching table is in the write state (i.e., State is Writer), and the data distribution service request received by the UPF-side target communication component is a data subscription request, then the target communication component forwards the data subscription request to the UE with the IP address listed in the target matching table; if the topic processing state corresponding to the target topic identifier in the target matching table is in the write state (i.e., State is Reader), and the data distribution service request received by the UPF-side target communication component is a data publishing request, then the target communication component forwards the data publishing request to the UE with the IP address listed in the target matching table.

[0132] In summary, by applying the embodiments of this application, successful data distribution can be achieved for both data subscription requests and data publishing requests, thereby improving the applicability of the method of this application.

[0133] Optionally, the above method further includes:

[0134] If the local topic cache does not have a target matching entry corresponding to the target topic identifier, then according to the data distribution service request, a target entry is newly added to the local topic cache through the target communication component. The target entry includes: the target topic identifier, the address identifier of the target terminal, and the processing status of the target terminal for the target topic identifier in the data distribution service request.

[0135] Among them, during the data distribution process, there is of course also a situation where the local topic cache does not have a target matching entry corresponding to the target topic identifier. Optionally, in this case, a target entry <T_ID_B, IP_List_B> can be newly added to the local Topic cache through the target communication component, and an entry <UE_IP_B, State_B> is added to IP_List_B, where T_ID_B is the target topic identifier, <UE_IP_B is the address identifier of the target terminal, and State_B is the processing status of the target terminal for the target topic identifier. It can be understood that if the obtained data distribution service request is a subscription request, then State = Reader, otherwise, State = Writer.

[0136] In summary, taking the method for implementing the data distribution service provided in the embodiments of the present application applied to a 5G wireless network as an example, the target UPF can be built with the target communication component. When the application program on the target terminal starts the DDS service locally, the 5G network forwards the DDS-related data messages to the target communication component built in the target UPF. The target communication component can create a corresponding data forwarding table according to the DDS message type and content to support data communication oriented to the target topic identifier.

[0137] In addition, based on the above description, it can also be seen that when implementing the method provided in the embodiments of the present application in combination with the application program corresponding to the DDS mechanism already deployed on the target terminal, there is no need to modify the code corresponding to the application program, and rapid deployment can be achieved. Moreover, in the prior art, since the data interaction of DDS is addressed by DDS Domain and DDS Topic, and the 5G network performs data interaction with IP addresses, this causes the 5G network devices that use DDS for data interaction to achieve data-centric inter-module cooperation only through frequent device discovery operations. These frequent device discovery operations will quickly consume the wireless resources in the 5G network, thereby affecting the actual data transmission. However, the method provided in the embodiments of the present application does not require the DDS communication peer to perform device discovery operations, which can effectively save network resources and improve data transmission efficiency.

[0138] Figure 6This is a functional module diagram of an apparatus for implementing a data distribution service provided in an embodiment of this application. This apparatus can be applied to a communication device, which may include a target communication component, such as the aforementioned target terminal or target UPF. The basic principle and technical effects of this apparatus are the same as those in the corresponding method embodiments described above. For the sake of brevity, parts not mentioned in this embodiment can be referred to the corresponding content in the method embodiments. Figure 6 As shown, the device 100 may include:

[0139] The acquisition module 110 is used to obtain the target topic identifier by parsing the data distribution service request through the target communication component;

[0140] The determination module 120 is used to determine, based on the target topic identifier, whether there is a target matching entry corresponding to the target topic identifier by retrieving the local topic cache through the target communication component.

[0141] The forwarding module 130 is used to forward the data distribution service request to the peer terminal indicated by the target matching entry through the target communication component, if such a request exists.

[0142] In an optional implementation, the communication device is a target terminal, and the local topic cache includes: an internal identifier of a virtual network group corresponding to at least one topic identifier during the historical data distribution process. The forwarding module 130 is specifically used to determine the internal identifier of the target virtual network group corresponding to the target topic identifier through the target communication component based on the local topic cache.

[0143] Based on the local message forwarding table, the target PDU session identifier corresponding to the target topic identifier is determined by the target communication component. The local message forwarding table includes: at least one PDU session identifier corresponding to a topic identifier in the historical data distribution process.

[0144] Based on the internal identifier of the target virtual network group and the target PDU session indicated by the target PDU session identifier, the data distribution service request is forwarded to the peer terminal that is in the same target virtual network group as the target terminal through the target communication component.

[0145] In an optional implementation, the forwarding module 130 is further configured to send a user subscription data modification request to the target management server through the target communication component if the local topic cache does not contain a target matching entry corresponding to the target topic identifier. The user subscription data modification request includes: target topic identifier and target terminal identifier.

[0146] The target communication component receives user subscription data modification feedback returned by the target management server. This feedback is generated by the unified data management network element based on a user subscription data modification request forwarded by the network open function network element, and then forwarded to the target management server through the network open function network element. The user subscription data modification feedback includes: the external identifier of the target virtual network group where the target terminal is located, the internal identifier corresponding to the external identifier of the target virtual network group, and the target network slice identifier corresponding to the target terminal. The external identifier of the target virtual network group is set according to the target topic identifier.

[0147] Based on the user subscription data modification feedback, a PDU session request is sent to the session management function network element. The PDU session request includes: the target network slice identifier corresponding to the target terminal.

[0148] The target communication component receives the PDU session creation completion response returned by the session management function network element and creates a local target message forwarding item; wherein, after receiving the PDU session request, the session management function network element creates a target user plane function network element according to the target network slice identifier, and creates a target virtual network group with the target topic identifier as the external identifier in the target user plane function network element.

[0149] In an optional implementation, the forwarding module 130 is specifically configured to forward the data distribution service request to the target user plane function network element corresponding to the target terminal through the target PDU session indicated by the target PDU session identifier, so that the target user plane function network element copies a corresponding number of data distribution service requests according to the number of peer terminals in the target virtual network group and forwards them to the peer terminal.

[0150] In an optional implementation, the communication device is a target user plane function network element, and the local topic cache includes at least one terminal address identifier corresponding to a topic identifier during the historical data distribution process, and the topic processing status corresponding to each terminal identifier.

[0151] The forwarding module 130 is specifically used to forward the data distribution service request to the peer terminal indicated by the terminal address identifier in the target matching entry through the target communication component, based on the topic processing status corresponding to the target topic identifier in the target matching entry.

[0152] In an optional implementation, the forwarding module 130 is specifically used to forward the data subscription request to the peer terminal indicated by the terminal identifier in the target matching entry through the target communication component if the topic processing status corresponding to the target topic identifier in the target matching entry is a write status and the data distribution service request is a data subscription request.

[0153] If the topic processing status corresponding to the target topic identifier in the target matching entry is in the read state, and the data distribution service request is a data publishing request, then the data publishing request is forwarded to the peer terminal indicated by the terminal identifier in the target matching entry through the target communication component.

[0154] In an optional implementation, the forwarding module 130 is further configured to, if the local topic cache does not contain a target matching entry corresponding to the target topic identifier, add a target entry in the local topic cache through the target communication component according to the data distribution service request. The target entry includes: the target topic identifier, the address identifier of the target terminal, and the processing status of the target terminal for the target topic identifier in the data distribution service request.

[0155] The above-described device is used to execute the method provided in the foregoing embodiments, and its implementation principle and technical effect are similar, so they will not be described again here.

[0156] These modules can be one or more integrated circuits configured to implement the above methods, such as one or more Application Specific Integrated Circuits (ASICs), one or more microprocessors, or one or more Field Programmable Gate Arrays (FPGAs). Alternatively, when a module is implemented using processing element scheduler code, the processing element can be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. Furthermore, these modules can be integrated together as a system-on-a-chip (SOC).

[0157] Figure 7 This is a schematic diagram of an electronic device structure provided in an embodiment of this application. The electronic device can be the aforementioned target terminal or target UPF. For example... Figure 7 As shown, the electronic device may include a processor 210, a storage medium 220, and a bus 230. The storage medium 220 stores machine-readable instructions executable by the processor 210. When the electronic device is running, the processor 210 communicates with the storage medium 220 via the bus 230, and the processor 210 executes the machine-readable instructions to perform the steps of the above method embodiment. The specific implementation and technical effects are similar and will not be described in detail here.

[0158] Optionally, this application also provides a storage medium storing a computer program, which, when run by a processor, executes the steps of the above-described method embodiments. The specific implementation and technical effects are similar and will not be repeated here.

[0159] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0160] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0161] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in a combination of hardware and software functional units.

[0162] The integrated units implemented as software functional units described above can be stored in a computer-readable storage medium. These software functional units, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0163] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element.

[0164] The above are merely preferred embodiments of this application and are not intended to limit this application. Various modifications and variations are possible for those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application. It should be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need further definition and explanation in subsequent figures. The above are merely preferred embodiments of this application and are not intended to limit this application. Various modifications and variations are possible for those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for implementing a data distribution service, characterized in that, The method is applied to a communication device, the communication device including a target communication component, and the method includes: The target topic identifier is obtained by parsing the data distribution service request through the target communication component. Based on the target topic identifier, the local topic cache is retrieved through the target communication component to determine whether there is a target matching entry corresponding to the target topic identifier; If it exists, the data distribution service request is forwarded to the peer terminal indicated by the target matching entry through the target communication component; The communication device is the target terminal, and the local topic cache includes: an internal identifier of a virtual network group corresponding to at least one topic identifier during historical data distribution. Forwarding the data distribution service request to the peer terminal indicated by the target matching entry through the target communication component includes: Based on the local topic cache, the internal identifier of the target virtual network group corresponding to the target topic identifier is determined by the target communication component; Based on the local message forwarding table, the target PDU session identifier corresponding to the target topic identifier is determined by the target communication component. The local message forwarding table includes: at least one PDU session identifier corresponding to a topic identifier in the historical data distribution process. Based on the internal identifier of the target virtual network group and the target PDU session indicated by the target PDU session identifier, the data distribution service request is forwarded to the peer terminal that is in the same target virtual network group as the target terminal through the target communication component; If the local topic cache does not contain a target matching entry corresponding to the target topic identifier, then a user subscription data modification request is sent to the target management server through the target communication component. The user subscription data modification request includes: target topic identifier and target terminal identifier. Based on the feedback from the user's subscription data modification, a PDU session request is sent to the session management function network element. The PDU session request includes: the target network slice identifier corresponding to the target terminal. The target communication component receives the PDU session creation completion response returned by the session management function network element and creates a local target message forwarding item; or, The communication device is a target user plane function network element, and the local topic cache includes at least one terminal address identifier corresponding to a topic identifier during the historical data distribution process, and the topic processing status corresponding to each terminal identifier. The step of forwarding the data distribution service request to the peer terminal indicated by the target matching entry via the target communication component includes: Based on the topic processing status corresponding to the target topic identifier in the target matching entry, the data distribution service request is forwarded to the peer terminal indicated by the terminal address identifier in the target matching entry through the target communication component; If the local topic cache does not contain a target matching entry corresponding to the target topic identifier, then according to the data distribution service request, the target communication component adds a new target entry in the local topic cache. The target entry includes: the target topic identifier, the address identifier of the target terminal, and the processing status of the target terminal for the target topic identifier in the data distribution service request.

2. The method according to claim 1, characterized in that, If the communication device is the target terminal, before sending the PDU session request to the session management function network element based on the user subscription data modification feedback, the method further includes: The target communication component receives user subscription data modification feedback returned by the target management server. This feedback is generated by the unified data management network element based on a user subscription data modification request forwarded by the network open function network element, and then forwarded to the target management server through the network open function network element. The user subscription data modification feedback includes: the external identifier of the target virtual network group where the target terminal is located, the internal identifier corresponding to the external identifier of the target virtual network group, and the target network slice identifier corresponding to the target terminal. The external identifier of the target virtual network group is set according to the target topic identifier. Upon receiving the PDU session request, the session management function network element creates a target user plane function network element based on the target network slice identifier, and creates a target virtual network group with the target topic identifier as the external identifier in the target user plane function network element.

3. The method according to claim 2, characterized in that, The forwarding of the data distribution service request to a peer terminal within the same target virtual network group as the target terminal, based on the target PDU session indicated by the internal identifier of the target virtual network group and the target PDU session identifier, through the target communication component, includes: The data distribution service request is forwarded to the target user plane function network element corresponding to the target terminal through the target PDU session indicated by the target PDU session identifier, so that the target user plane function network element replicates the corresponding number of data distribution service requests according to the number of peer terminals in the target virtual network group and forwards them to the peer terminal.

4. The method according to claim 1, characterized in that, If the communication device is a target user plane function network element, the step of forwarding the data distribution service request to the peer terminal indicated by the terminal address identifier in the target matching entry through the target communication component based on the topic processing status corresponding to the target topic identifier in the target matching entry includes: If the topic processing status corresponding to the target topic identifier in the target matching entry is in the write state, and the data distribution service request is a data subscription request, then the data subscription request is forwarded to the peer terminal indicated by the terminal identifier in the target matching entry through the target communication component; If the topic processing status corresponding to the target topic identifier in the target matching entry is in the read state, and the data distribution service request is a data publishing request, then the data publishing request is forwarded to the peer terminal indicated by the terminal identifier in the target matching entry through the target communication component.

5. An apparatus for implementing data distribution services, characterized in that, The apparatus is applied to a communication device, the communication device including a target communication component, the apparatus being used to perform the steps of the method for implementing a data distribution service according to any one of claims 1-4, the apparatus comprising: The acquisition module is used to obtain the target topic identifier by parsing the data distribution service request through the target communication component; The determination module is used to retrieve the local topic cache through the target communication component based on the target topic identifier to determine whether there is a target matching entry corresponding to the target topic identifier. The forwarding module is used to forward the data distribution service request to the peer terminal indicated by the target matching entry through the target communication component, if such a request exists.

6. An electronic device, characterized in that, include: The device includes a processor, a storage medium, and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the steps of the method for implementing a data distribution service as described in any one of claims 1-4.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, performs the steps of the method for implementing a data distribution service as described in any one of claims 1-4.

Images