Message transmission method and device and readable storage medium

Abstract

The application discloses a message transmission method and device and a readable storage medium, relates to the technical field of communication, and is used for reducing message transmission delay. The method comprises the following steps: acquiring a to-be-transmitted message of a target terminal device; a source Internet Protocol (IP) address or a destination IP address of the to-be-transmitted message is an IP address of the target terminal device; transmitting the to-be-transmitted message based on a target transmission rate; the target transmission rate is a transmission rate of the bandwidth of a target DN interface of the to-be-transmitted message; and the bandwidth of the target DN interface is the same as the bandwidth of the target terminal device.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a message transmission method, apparatus and readable storage medium. Background Technology

[0002] When a multi-access edge computing (MEC) node transmits service packets, it needs to perform three-layer detection on each service packet to determine the user's bandwidth information. Then, a specific thread can perform statistics and rate limiting, or multiple service threads can perform rate limiting on the packet transmission process by locking.

[0003] However, when there are many business messages, rate limiting takes a long time, consumes more resources, and results in a larger message transmission delay. Summary of the Invention

[0004] This application provides a message transmission method, apparatus, and readable storage medium for reducing message transmission latency.

[0005] To achieve the above objectives, this application adopts the following technical solution:

[0006] In a first aspect, a message transmission method is provided, the method comprising: acquiring a message to be transmitted from a target terminal device; the source Internet Protocol IP address or the destination IP address of the message to be transmitted being the IP address of the target terminal device; the target transmission rate being the transmission rate of the bandwidth of the target DN interface of the message to be transmitted; and the bandwidth of the target DN interface being the same as the bandwidth of the target terminal device.

[0007] Optionally, if the message to be transmitted is an uplink message, after obtaining the message to be transmitted from the target terminal device, the method further includes: determining the DN interface receiving the message to be transmitted as the target DN interface; determining that the target DN interface and the target N6 interface are associated interfaces; and the target N6 interface is the N6 interface of the edge UPF network element that sends the message to be transmitted.

[0008] Optionally, the target DN interface is connected to the target N6 interface via a target virtual LAN VLAN; the VLAN identifier of the target DN interface is the same as that of the target N6 interface.

[0009] Optionally, the target N6 interface is determined by the edge UPF network element based on the IP address of the target terminal device and the first mapping relationship; the first mapping relationship includes the correspondence between different IP addresses and different N6 interface identifiers; the IP address of the target terminal device is determined by the edge UPF network element after performing session matching on the packet to be transmitted.

[0010] Optionally, the target data network name (DNN) is associated with the target DN interface and the target N6 interface; the target DNN is the DNN configured for the target terminal device.

[0011] Optionally, if the message to be transmitted is a downlink message, after obtaining the message to be transmitted from the target terminal device, the method further includes: parsing the DN interface identifier carried in the message to be transmitted; and determining the target DN interface from multiple preset DN interfaces based on the DN interface identifier carried in the message to be transmitted.

[0012] Optionally, if the message to be transmitted is a downlink message, after obtaining the message to be transmitted from the target terminal device, the method further includes: determining the corresponding target N6 interface based on the target DN interface; and transmitting the message to be transmitted based on the target DN interface and the target N6 interface.

[0013] Optionally, transmitting the message to be transmitted based on the target transmission rate includes: determining whether the required bandwidth of the message to be transmitted is less than or equal to the bandwidth of the target DN interface; and transmitting the message to be transmitted based on the target transmission rate if the required bandwidth is less than or equal to the bandwidth of the target DN interface.

[0014] Optionally, the method further includes: discarding the message to be transmitted if the required bandwidth is greater than the bandwidth of the target DN interface.

[0015] Based on the technical solution provided in this application, the message to be transmitted from the target terminal device is obtained and transmitted based on the target transmission rate. Since the target transmission rate is the transmission rate of the bandwidth of the target DN interface of the message to be transmitted, the message to be transmitted is transmitted using the transmission rate of the target DN interface bandwidth. Because the bandwidth of the target DN interface is the same as that of the target terminal device, there is no need to parse the message to be transmitted to obtain the user's bandwidth information. This allows for rate limiting of messages from different terminals, reducing message transmission latency and network computing resources.

[0016] Secondly, a message transmission apparatus is provided, comprising: an acquisition unit and a processing unit; the acquisition unit is used to acquire a message to be transmitted from a target terminal device; the source Internet Protocol (IP) address or destination IP address of the message to be transmitted is the IP address of the target terminal device; the processing unit is used to transmit the message to be transmitted based on a target transmission rate; the target transmission rate is the transmission rate of the bandwidth of the target DN interface of the message to be transmitted; the bandwidth of the target DN interface is the same as the bandwidth of the target terminal device.

[0017] Optionally, the device further includes a determining unit; if the message to be transmitted is an uplink message, after acquiring the message to be transmitted from the target terminal device, the determining unit is used to determine the DN interface for acquiring the message to be transmitted as the target DN interface; determine that the target DN interface and the target N6 interface are associated interfaces; and determine that the target N6 interface is the N6 interface for the edge UPF network element to send the message to be transmitted.

[0018] Optionally, the target DN interface is connected to the target N6 interface via a target virtual LAN VLAN; the VLAN identifier of the target DN interface is the same as that of the target N6 interface.

[0019] Optionally, the target N6 interface is determined by the edge UPF network element based on the IP address of the target terminal device and the first mapping relationship; the first mapping relationship includes the correspondence between different IP addresses and different N6 interface identifiers; the IP address of the target terminal device is determined by the edge UPF network element after performing session matching on the packet to be transmitted.

[0020] Optionally, the target data network name (DNN) is associated with the target DN interface and the target N6 interface; the target DNN is the DNN configured for the target terminal device.

[0021] Optionally, if the message to be transmitted is a downlink message, after obtaining the message to be transmitted from the target terminal device, the processing unit is further configured to parse the DN interface identifier carried in the message to be transmitted; the determining unit is further configured to determine the target DN interface from multiple preset DN interfaces based on the DN interface identifier carried in the message to be transmitted.

[0022] Optionally, if the message to be transmitted is a downlink message, after obtaining the message to be transmitted from the target terminal device, the method further includes: determining the corresponding target N6 interface based on the target DN interface; and transmitting the message to be transmitted based on the target DN interface and the target N6 interface.

[0023] Optionally, the processing unit is specifically used to: determine whether the required bandwidth of the message to be transmitted is less than or equal to the bandwidth of the target DN interface; and if the required bandwidth is less than or equal to the bandwidth of the target DN interface, transmit the message to be transmitted based on the target transmission rate.

[0024] Optionally, the processing unit is also configured to discard packets to be transmitted if the required bandwidth is greater than the bandwidth of the target DN interface.

[0025] Thirdly, a message transmission device is provided, which can realize the functions performed by the message transmission device in the above aspects or possible designs. The functions can be implemented by hardware. For example, in one possible design, the message transmission device may include a processor and a communication interface. The processor can be used to support the message transmission device in realizing the functions involved in the first aspect or any possible design of the first aspect.

[0026] In another possible design, the message transmission device may further include a memory for storing necessary computer execution instructions and data. When the message transmission device is running, the processor executes the computer execution instructions stored in the memory to cause the message transmission device to perform the first aspect or any of the possible message transmission methods described above.

[0027] Fourthly, a computer-readable storage medium is provided, which may be a readable non-volatile storage medium storing computer instructions or programs that, when executed on a computer, enable the computer to perform the message transmission method described in the first aspect or any of the possible message transmission methods described above.

[0028] Fifthly, a computer program product containing instructions is provided, which, when run on a computer, enables the computer to execute the message transmission method of the first aspect or any possible design of the above aspects.

[0029] A sixth aspect provides an electronic device comprising one or more processors and one or more memories. The one or more memories are coupled to the one or more processors, and the one or more memories are used to store computer program code, including computer instructions, which, when executed by the one or more processors, cause the electronic device to perform a message transmission method as described in the first aspect or any possible design of the first aspect.

[0030] In a seventh aspect, a chip system is provided, comprising a processor and a communication interface, which can be used to implement the functions performed by the message transmission device in the first aspect or any possible design of the first aspect. In one possible design, the chip system further includes a memory for storing program instructions and / or data. The chip system may be composed of chips or may include chips and other discrete devices, without limitation. Attached Figure Description

[0031] Figure 1 A schematic diagram of the architecture of an MEC management system provided in an embodiment of this application;

[0032] Figure 2 A schematic diagram of a message transmission system provided in an embodiment of this application;

[0033] Figure 3 This is a schematic diagram of the structure of a message transmission device provided in an embodiment of this application;

[0034] Figure 4 A flowchart illustrating a message transmission method provided in an embodiment of this application;

[0035] Figure 5 This is a schematic diagram of another message transmission device provided in the embodiments of this application. Detailed Implementation

[0036] To enable those skilled in the art to better understand the technical solutions of this disclosure, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0037] It should be noted that the terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this disclosure described herein can be implemented in orders other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the embodiments of this application as detailed in the appended claims.

[0038] It should also be understood that the term "comprising" indicates the presence of the described feature, whole, step, operation, element and / or component, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements and / or components.

[0039] The technical terms used in this application are explained below.

[0040] 1. User Plane Function (UPF) node: Used for traffic distribution, traffic statistics, service packet caching, and Quality of Service (QoS) control of terminal user data traffic on the private network.

[0041] 2. MEC Node: Used to provide IT service environment and cloud computing capabilities at the edge of 5G private network, enabling localized, near-field, and distributed deployment of applications, services, and content.

[0042] Figure 1 This is a schematic diagram of the architecture of a MEC management system provided in this application. Figure 1As shown, the MEC management system includes: MEC host module, MEC platform module, MEC application module, and MEC system-level management module. The descriptions of each part are as follows:

[0043] MEC host module: Composed of MEC platform, MEC applications, and virtualization infrastructure. In addition to providing computing, storage, and network resources for MEC applications, the virtualization infrastructure also provides data plane forwarding, which routes and forwards data between applications, services, Domain Name System (DNS), 3GPP networks, other access networks, local networks, and external networks according to traffic routing rules received from the MEC platform.

[0044] MEC Platform Module: Provides an environment for the discovery, publication, use, and service of MEC applications; receives traffic routing rules from the MEC platform management unit, applications, or services, and builds a data plane in the virtualization infrastructure; receives DNS records from the MEC platform management unit and configures DNS proxies or servers; serves as the owner of MEC services such as wireless network information, location information, and bandwidth management; and provides access to permanent storage and time information services.

[0045] MEC Application Module: MEC applications run as virtual machines (VMs) on the virtualization infrastructure provided by the MEC host. They can use or provide MEC services by interacting with the MEC platform. In special cases, MEC applications can also support MEC application lifecycle management processes by interacting with the MEC platform. Examples include availability indication and preparation for user state information migration. MEC applications have certain requirements regarding traffic rules, required virtual resources, maximum latency, and required MEC services. These requirements only take effect after being verified by the MEC system-level management unit; otherwise, the default values ​​are used.

[0046] MEC system-level management module: includes MEC orchestrator, operation support system and user application lifecycle management module.

[0047] The MEC orchestrator is responsible for maintaining an overall view of the MEC system, including the MEC hosts, available resources, available MEC services, and topology. It performs steps necessary for MEC application loading and deployment, such as checking the integrity and reliability of MEC application packages, verifying application rules and requirements, maintaining application package loading records, and preparing virtualization infrastructure. Based on the resources, latency, and services required by the MEC application, it selects appropriate MEC hosts for MEC application instantiation and production. When migration is required and the MEC system supports migration, it selectively triggers MEC application migration.

[0048] The Operations Support System is primarily responsible for receiving requests from the Customer Facing Services (CFS) portal and user terminal applications for the instantiation and termination of MEC applications. It also decides whether to authorize these requests and sends the authorized requests to the MEC orchestrator for further processing.

[0049] The user application lifecycle management module is mainly responsible for handling the MEC application loading, instantiation, and termination requests from user terminal applications, and selectively supports the migration of MEC applications within or outside the MEC system.

[0050] The MEC host-level management module includes the MEC platform management module and the virtualization infrastructure management module. The MEC platform management module comprises three functions: MEC platform operation and maintenance management, MEC application rules and requirements management, and MEC application lifecycle management. The MEC platform operation and maintenance management submodule provides basic MEC platform management functions. The MEC application rules and requirements management submodule manages tasks including MEC service authentication and authorization, traffic rules, DNS configuration, and conflict handling. Additionally, the MEC platform management module receives virtual resource error reports and performance statistics from the virtualization infrastructure management module and performs further processing. The MEC application lifecycle management submodule manages the MEC application lifecycle and notifies the MEC orchestrator of MEC application lifecycle-related events.

[0051] The Virtualization Infrastructure Management module is responsible for the following functions: allocating, managing, and releasing virtualization resources such as computing, storage, and networking resources of the virtualization infrastructure; preparing the virtualization infrastructure for running MEC application image files, including configuring the infrastructure, receiving and storing MEC application image files; collecting and reporting performance and fault information of the virtualization infrastructure; and selectively supporting the migration of MEC applications between the MEC system and external cloud environments.

[0052] For shared edge MEC nodes, rate limiting needs to be applied individually to different users within the same 5G private network to ensure that the services of different enterprise users do not interfere with each other. Therefore, rate limiting schemes implemented independently for different 5G private network users not only need to meet the requirements of high bandwidth and low latency for those users, but also need to meet the requirements of easy deployment, easy maintenance, independent operation, and no impact on other private network users.

[0053] In related technologies, application flow control schemes for users of different 5G private networks on shared MEC nodes require three-layer detection for each service packet. After determining which user the packet belongs to, a specific thread performs statistics and rate limiting, or multiple service threads implement rate limiting through locking. This results in significant system performance consumption and increased processing latency. As the number of users and service types on the 5G private network on the MEC increases, the performance consumption caused by rate limiting will increase exponentially, and the processing latency will further increase, severely impacting the user experience of all users on the MEC.

[0054] In view of this, embodiments of this application provide a message transmission method, the method comprising: obtaining a message to be transmitted from a target terminal device; the source Internet Protocol (IP) address of the message to be transmitted is the IP address of the target terminal device, or the destination IP address of the message to be transmitted is the IP address of the target terminal device; transmitting the message to be transmitted based on a target transmission rate; the target transmission rate is the transmission rate of the bandwidth of the target DN interface of the message to be transmitted; the bandwidth of the target DN interface is the same as the bandwidth of the target terminal device.

[0055] The methods provided in the embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0056] It should be noted that the network system described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network systems and the emergence of other network systems, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0057] Figure 2 The diagram shown is a structural schematic of a message transmission system 10 provided in an embodiment of this application. Figure 2 As shown, the message transmission system 10 may include a public network 11 and a private network 12.

[0058] The public network 11 and the private network 12 are connected. For example, they can be connected wirelessly or via a wired connection.

[0059] In this embodiment of the application, the public network 11 includes: a public network SMF network element, a public network UPF network element, and the Internet. The public network SMF network element and the public network UPF network element are connected via an N4 interface. The public network UPF network element and the Internet are connected via an N6 interface.

[0060] The private network 12 involved in the embodiments of this application may include an edge UPF, a shared MEC, a first terminal (i.e., user 1's terminal) and a second terminal (i.e., user 2's terminal). The bandwidth of the first terminal is different from that of the second terminal.

[0061] The edge UPF is configured with N6 sub-interfaces N6-1 and N6-2. A first data network name DNN1 and a second data network name DNN2 are created on the edge UPF. The first terminal is configured to belong to DNN1, and the second terminal to belong to DNN2.

[0062] The shared MEC is configured with a first sub-interface (DN1) for the first terminal and a second sub-interface (DN2) for the second terminal. The first sub-interface is used to receive uplink data from the first terminal. The second sub-interface is used to receive uplink data from the second terminal.

[0063] The edge UPF connects to the public SMF via interface N4. The edge UPF connects to the public UPF via interface N9. The edge UPF connects to the base station via interface N3. The edge UPF connects to user 1 sub-interface DN1 of the shared MEC via sub-interface N6-1. The edge UPF connects to user 2 sub-interface DN2 of the shared MEC via sub-interface N6-2.

[0064] The bandwidth of user 1 sub-interface DN1 is the same as that of the first terminal. The bandwidth of user 2 sub-interface DN2 is the same as that of the second terminal.

[0065] Figure 2 This is just an example framework diagram. Figure 2 The names of the various devices included are unrestricted, and except for Figure 2 In addition to the functional nodes shown, other nodes may also be included, but this application embodiment does not limit this.

[0066] In practical implementation, Figure 2 Each device in the process can be adopted Figure 3 The shown composition structure, or including Figure 3 The components shown. Figure 3 This is a schematic diagram of the structure of a message transmission device 200 provided in an embodiment of this application. The message transmission device 200 can be a network device, or it can be a chip or system-on-a-chip within a network device. Figure 3 As shown, the message transmission device 200 includes a processor 201, a communication interface 202, and a communication line 203.

[0067] Furthermore, the message transmission device 200 may also include a memory 204. The processor 201, memory 204, and communication interface 202 can be connected via a communication line 203.

[0068] The processor 201 can be a CPU, a general-purpose processor, a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller, a programmable logic device (PLD), or any combination thereof. The processor 201 can also be other devices with processing capabilities, such as circuits, devices, or software modules, without limitation.

[0069] Communication interface 202 is used to communicate with other devices or other communication networks. Communication interface 202 can be a module, circuit, communication interface, or any device capable of enabling communication.

[0070] Communication line 203 is used to transmit information between the components included in message transmission device 200.

[0071] Memory 204 is used to store instructions. These instructions can be computer programs.

[0072] The memory 204 can be a read-only memory (ROM) or other type of static storage device that can store static information and / or instructions; it can also be a random access memory (RAM) or other type of dynamic storage device that can store information and / or instructions; it can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, etc., without limitation.

[0073] It should be noted that the memory 204 can exist independently of the processor 201 or can be integrated with the processor 201. The memory 204 can be used to store instructions, program code, or some data, etc. The memory 204 can be located inside or outside the message transmission device 200, without limitation. The processor 201 is used to execute the instructions stored in the memory 204 to implement the message transmission method provided in the following embodiments of this application.

[0074] In one example, processor 201 may include one or more CPUs, for example, Figure 3 CPU0 and CPU1 in the CPU.

[0075] As an optional implementation, the message transmission device 200 includes multiple processors, for example, besides Figure 3 In addition to processor 201, it may also include processor 205.

[0076] It should be pointed out that, Figure 3 The composition shown does not constitute a basis for this. Figure 2 The limitations of each device in the process, except Figure 3 In addition to the components shown, Figure 2 The various devices in can include compared to Figure 3 More or fewer components, or combinations of certain components, or different arrangements of components.

[0077] In this embodiment of the application, the chip system may be composed of chips or may include chips and other discrete devices.

[0078] Furthermore, the actions, terms, etc., involved in the various embodiments of this application can be referenced interchangeably without limitation. The message names or parameter names in the messages between the various devices in the embodiments of this application are merely examples, and other names may be used in specific implementations without limitation.

[0079] To facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with essentially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0080] It should be noted that, in this application, the terms "exemplary" or "for example" are used to indicate that something is being described as an example, illustration, or illustration. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0081] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0082] The following is combined with Figure 2 The message transmission system shown describes the message transmission method provided in the embodiments of this application.

[0083] Figure 4 This application provides a message transmission method that can be applied to multi-access edge computing (MEC) nodes, and can also be applied to devices in MEC nodes, such as chips.

[0084] This application uses an example of application to an MEC node for illustration, such as... Figure 4 As shown, the method includes the following steps S301-S302:

[0085] S301. Obtain the message to be transmitted from the target terminal device.

[0086] In this context, the source IP address of the message to be transmitted is the IP address of the target terminal device, or the destination IP address of the message to be transmitted is the IP address of the target terminal device. The message to be transmitted can be an uplink message or a downlink message.

[0087] Combination Figure 2 The target terminal device can be either a first terminal or a second terminal. For example, if the message to be transmitted is transmitted through user 1 sub-interface DN1, the target terminal device is the first terminal. If the message to be transmitted is transmitted through user 2 sub-interface DN2, the target terminal device is the second terminal.

[0088] The structure of the message to be transmitted may include: message header, command / response field, data field, and checksum.

[0089] The message header contains key information such as message type, length, and identifier, indicating the nature and content of the message. The command / response field identifies whether the message is a command or response message, instructing the receiving device to perform the corresponding operation or send a response. The data field includes the actual data content, such as configuration parameters, status information, and control commands. The checksum is used to ensure the integrity and correctness of the message.

[0090] As one possible implementation, when the message to be transmitted is an uplink message, the MEC node can obtain the message to be transmitted from the target terminal device based on the target DN interface.

[0091] In one example, combining Figure 2 When the message to be transmitted is an uplink message and the target terminal is the first terminal, the target DN interface is User 1 sub-interface DN1. The MEC node can obtain the message to be transmitted from the target terminal device based on User 1 sub-interface DN1.

[0092] In another example, combined Figure 2 When the message to be transmitted is an uplink message and the target terminal device is a second terminal, the target DN interface is User 2 sub-interface DN2. The MEC node can obtain the message to be transmitted from the target terminal device based on User 2 sub-interface DN2.

[0093] As another possible implementation, when the message to be transmitted is a downlink message, the MEC node can obtain the message to be transmitted from the target terminal device based on the associated service processing unit worker.

[0094] In one example, when the message to be transmitted is a downlink message and the target terminal device is the first terminal, the associated service processing unit worker is worker1. The MEC node can obtain the message to be transmitted from the target terminal device based on worker1.

[0095] In another example, when the message to be transmitted is a downlink message and the target terminal device is a second terminal, the associated service processing unit worker is worker2. The MEC node can obtain the message to be transmitted from the target terminal device through service processing unit worker2.

[0096] S302. Transmit the message to be transmitted based on the target transmission rate.

[0097] The target transmission rate is the transmission rate of the bandwidth of the target DN interface of the message to be transmitted; the bandwidth of the target DN interface is the same as the bandwidth of the target terminal device.

[0098] MEC nodes are pre-configured with multiple DN interfaces. Different DN interfaces are used to transmit service messages from different terminal devices. For example, different DN interfaces can be used to receive service messages from different terminal devices. Alternatively, different DN interfaces can be used to send service messages to different terminal devices.

[0099] For example, combining Figure 2 The DN1 interface is used to receive service messages from the first terminal and to send service messages to the first terminal. The DN2 interface is used to receive service messages from the second terminal and to send service messages to the second terminal.

[0100] As one possible implementation, when the message to be transmitted is an uplink message, the MEC node can transmit the message based on the uplink bandwidth transmission rate of the target DN interface.

[0101] In one example, if the uplink bandwidth of the DN1 interface is 100Mbps, the downlink bandwidth of the DN1 interface is 500Mbps. The uplink bandwidth of the DN2 interface is 50Mbps, and the downlink bandwidth of the DN1 interface is 200Mbps. Combined with... Figure 2 When the target DN interface is DN1, the MEC node can transmit packets at 100 Mbps. When the target DN interface is DN2, the MEC node can transmit packets at 50 Mbps.

[0102] As another possible implementation, when the message to be transmitted is a downlink message, the MEC node can transmit the message based on the downlink bandwidth transmission rate of the target DN interface.

[0103] In one example, if the uplink bandwidth of the DN1 interface is 100Mbps, the downlink bandwidth of the DN1 interface is 500Mbps. The uplink bandwidth of the DN2 interface is 50Mbps, and the downlink bandwidth of the DN1 interface is 200Mbps. Combined with... Figure 2 When the target DN interface is DN1, the MEC node can transmit the message to be transmitted at 500 Mbps. When the target DN interface is DN2, the MEC node can transmit the message to be transmitted at 200 Mbps.

[0104] Based on the technical solution provided in this application, the message to be transmitted from the target terminal device is obtained and transmitted based on the target transmission rate. Since the target transmission rate is the transmission rate of the bandwidth of the target DN interface of the message to be transmitted, the message to be transmitted is transmitted using the transmission rate of the target DN interface bandwidth. Because the bandwidth of the target DN interface is the same as that of the target terminal device, there is no need to parse the message to be transmitted to obtain the user's bandwidth information. This allows for rate limiting of messages from different terminals, reducing message transmission latency and network computing resources.

[0105] In one possible embodiment, if the message to be transmitted is an uplink message, after obtaining the message to be transmitted from the target terminal device, the message transmission method of this application may include the following S401-S402.

[0106] S401. Determine the DN interface from which the message to be transmitted is acquired as the target DN interface.

[0107] In one example, combining Figure 2 When the DN interface for the message to be transmitted is DN1, the MEC node will determine DN1 as the target DN interface. When the DN interface for the message to be transmitted is DN2, the MEC node will determine DN2 as the target DN interface.

[0108] It should be noted that the target DN interface is connected to the target N6 interface; the target N6 interface is the N6 interface associated with the target terminal device in the edge UPF network element.

[0109] In one example, the target DN interface can be connected to the target N6 interface via the target virtual LAN VLAN; the VLAN identifier of the target DN interface is the same as the VLAN identifier of the target N6 interface.

[0110] For example, combining Figure 2 When the target DN interface is DN1 and the VLAN of DN1 is VLAN3, the VLAN identifier can be VLAN3. The edge UPF node can be configured with the N6-1 sub-interface to connect to the DN1 interface via VLAN3.

[0111] For example, combining Figure 2 When the target DN interface is DN2 and the VLAN of DN2 is VLAN4, the VLAN identifier can be VLAN4. The UPF node can be configured to connect the N6-2 sub-interface to the DN2 interface via VLAN4.

[0112] The edge UPF node can direct the next hop of the service route for the first terminal to the IP address of the DN1 interface, and direct the next hop of the service route for the second terminal to the IP address of the DN2 interface.

[0113] The target N6 interface is determined by the edge UPF network element based on the IP address of the target terminal device and the first mapping relationship. The first mapping relationship includes the correspondence between different IP addresses and different N6 interface identifiers; the IP address of the target terminal device is determined by the edge UPF network element after performing session matching on the packet to be transmitted.

[0114] Session matching can determine that session information may include the IP address of the target terminal device and the Data Network Name (DNN).

[0115] In some embodiments, the edge UPF node can also create an N3 interface. The edge UPF node can configure the Virtual Routing Forwarding (VRF) of the N3 interface to the target VRF value; and configure the Virtual Local Area Network (VLAN) of the target N3 sub-interface to the target VLAN value.

[0116] After the edge UPF node creates the target private network, it first configures the value of the N3 virtual routing domain (N3-VRF) of the target private network to the target VRF value, then establishes the base station route between the N3 interface and the target private network, and then assigns the Internet Protocol (IP) of the N3 interface to the IP address corresponding to the N3 interface for the user.

[0117] Among them, the edge UPF node can assign the IP address of the N3 interface to the user when the target private network user goes online.

[0118] In one example, the steps to establish routing between the N3 interface and the target private network's base station include: binding the N3 interface to the target Virtual Private Network (VPN) on the switch, binding the first VLAN to the target VPN, and configuring the target VPN to route to the base station of the target private network. At this point, packets sent from the N3 interface will carry a tag of the target VLAN. The switch will assign the packet to the target VPN and then forward it to the base station of the target private network according to the routing.

[0119] S402. Determine that the target DN interface and the target N6 interface are associated interfaces.

[0120] Among them, the target N6 interface is the N6 interface for edge UPF network elements to send messages to be transmitted.

[0121] It should be noted that the target data network name (DNN) is associated with the target DN interface and the target N6 interface; the target DNN is the DNN configured for the target terminal device.

[0122] In one possible embodiment, if the message to be transmitted is a downlink message, after obtaining the message to be transmitted from the target terminal device, the message transmission method of this application may include the following S501-S502.

[0123] S501. Parse the DN interface identifier carried in the message to be transmitted.

[0124] As one possible implementation, MEC nodes can use a pre-defined parsing tool to parse the DN interface identifier carried in the message to be transmitted.

[0125] S502. Based on the DN interface identifier carried in the message to be transmitted, determine the target DN interface from multiple preset DN interfaces.

[0126] Among them, each of the multiple preset DN interfaces in MEC has a different DN interface identifier.

[0127] As one possible implementation, the MEC node can identify the target DN interface as the preset DN interface among multiple preset DN interfaces that has the same DN interface identifier as the DN interface carried by the message to be transmitted.

[0128] Furthermore, the MEC node can determine the corresponding target N6 interface based on the target DN interface, and transmit the message to be transmitted based on the target DN interface and the target N6 interface.

[0129] In one possible embodiment, in order to transmit a message to be transmitted based on a target transmission rate, the message transmission method of this application may include the following steps S601-S602.

[0130] S601. Determine whether the required bandwidth of the message to be transmitted is less than or equal to the bandwidth of the target DN interface.

[0131] The required bandwidth can be either uplink or downlink bandwidth.

[0132] As one possible implementation, the MEC node stores the bandwidth information of the target DN interface. The MEC node can determine whether the required bandwidth of the message to be transmitted is less than or equal to the bandwidth of the target DN interface based on the stored bandwidth information of the target DN interface.

[0133] In one example, when the message to be transmitted is a downlink message, the required bandwidth is the downlink required bandwidth. The MEC node can determine that the required bandwidth of the message to be transmitted is greater than the bandwidth of the target DN interface if the downlink required bandwidth of the message to be transmitted is greater than the downlink bandwidth of the target DN interface. Conversely, it can determine that the required bandwidth of the message to be transmitted is less than or equal to the bandwidth of the target DN interface if the downlink required bandwidth of the message to be transmitted is less than or equal to the downlink bandwidth of the target DN interface.

[0134] In another example, when the message to be transmitted is an uplink message, the required bandwidth is the uplink required bandwidth. The MEC node can determine that the required bandwidth of the message to be transmitted is greater than the bandwidth of the target DN interface if the uplink required bandwidth of the message to be transmitted is greater than the uplink bandwidth of the target DN interface. Conversely, it can determine that the required bandwidth of the message to be transmitted is less than or equal to the bandwidth of the target DN interface if the uplink required bandwidth of the message to be transmitted is less than or equal to the uplink bandwidth of the target DN interface.

[0135] S602. When the required bandwidth is less than or equal to the bandwidth of the target DN interface, transmit the message to be transmitted based on the target transmission rate.

[0136] The specific process of this step can be found in S302, and will not be elaborated here.

[0137] In some embodiments, if the required bandwidth is greater than the bandwidth of the target DN interface, the MEC node may discard the message to be transmitted.

[0138] It is understandable that discarding packets to be transmitted when the required bandwidth is greater than the bandwidth of the target DN interface can avoid network congestion and ensure stable network operation.

[0139] The various solutions in the above embodiments of this application can be combined without contradiction.

[0140] This application embodiment can divide the message transmission device into functional modules or functional units according to the above method examples. For example, each function can be divided into its own functional modules or functional units, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or in software functional modules or functional units. The module or unit division in this application embodiment is illustrative and represents only one logical functional division; other division methods may be used in actual implementation.

[0141] When dividing each function into modules according to its corresponding function. Figure 5 A schematic diagram of a message transmission device 700 is shown. The message transmission device can be a message transmission device or a chip applied in a message transmission device. The message transmission device 700 can be used to perform the functions of the message transmission device involved in the above embodiments. Figure 5The message transmission device 700 shown may include: an acquisition unit 701 and a processing unit 702; the acquisition unit 701 is used to acquire the message to be transmitted from the target terminal device; the source Internet Protocol IP address or destination IP address of the message to be transmitted is the IP address of the target terminal device; the processing unit 702 is used to transmit the message to be transmitted based on the target transmission rate; the target transmission rate is the transmission rate of the bandwidth of the target DN interface of the message to be transmitted; the bandwidth of the target DN interface is the same as the bandwidth of the target terminal device.

[0142] Optionally, the device further includes a determining unit 703; if the message to be transmitted is an uplink message, after obtaining the message to be transmitted from the target terminal device, the determining unit 703 is used to determine the DN interface that obtained the message to be transmitted as the target DN interface; determine that the target DN interface and the target N6 interface are associated interfaces; the target N6 interface is the N6 interface of the edge UPF network element that sends the message to be transmitted.

[0143] Optionally, the target DN interface is connected to the target N6 interface via a target virtual LAN VLAN; the VLAN identifier of the target DN interface is the same as that of the target N6 interface.

[0144] Optionally, the target N6 interface is determined by the edge UPF network element based on the IP address of the target terminal device and the first mapping relationship; the first mapping relationship includes the correspondence between different IP addresses and different N6 interface identifiers; the IP address of the target terminal device is determined by the edge UPF network element after performing session matching on the packet to be transmitted.

[0145] Optionally, the target data network name (DNN) is associated with the target DN interface and the target N6 interface; the target DNN is the DNN configured for the target terminal device.

[0146] Optionally, if the message to be transmitted is a downlink message, after obtaining the message to be transmitted from the target terminal device, the processing unit 702 is further configured to parse the DN interface identifier carried in the message to be transmitted; the determining unit 703 is further configured to determine the target DN interface from multiple preset DN interfaces based on the DN interface identifier carried in the message to be transmitted.

[0147] Optionally, the processing unit 702 is specifically used to: determine whether the required bandwidth of the message to be transmitted is less than or equal to the bandwidth of the target DN interface; and transmit the message to be transmitted based on the target transmission rate if the required bandwidth is less than or equal to the bandwidth of the target DN interface.

[0148] Optionally, the processing unit 702 is also configured to discard the message to be transmitted if the required bandwidth is greater than the bandwidth of the target DN interface.

[0149] This application also provides a computer-readable storage medium. All or part of the processes in the above method embodiments can be implemented by a computer program instructing related hardware. This program can be stored in the computer-readable storage medium, and when executed, it can include the processes of the above method embodiments. The computer-readable storage medium can be an internal storage unit of the message transmission device (including a data sender and / or a data receiver) of any of the foregoing embodiments, such as the hard disk or memory of the message transmission device. The computer-readable storage medium can also be an external storage device of the terminal device, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the terminal device. Further, the computer-readable storage medium can include both the internal storage unit of the message transmission device and an external storage device. The computer-readable storage medium is used to store the computer program and other programs and data required by the message transmission device. The computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0150] It should be noted that the terms "first" and "second," etc., in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0151] It should be understood that in this application, "at least one (item)" means one or more, "more than one" means two or more, "at least two (items)" means two or three or more, and "and / or" is used to describe the relationship between related objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0152] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0153] 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 modules or 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 apparatus, or some features may be ignored or not executed. Furthermore, the mutual 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.

[0154] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0155] 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 as a software functional unit.

[0156] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the 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, ROM, RAM, magnetic disks, or optical disks.

[0157] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A message transmission method, characterized in that, The method, applied to multi-access edge computing (MEC) nodes, includes: Obtain the message to be transmitted from the target terminal device; the source Internet Protocol IP address or the destination IP address of the message to be transmitted is the IP address of the target terminal device; If the message to be transmitted is an uplink message, the DN interface that receives the message to be transmitted will be determined as the target DN interface; The target DN interface and the target N6 interface are determined to be associated interfaces; the target N6 interface is the N6 interface through which the edge UPF network element sends the message to be transmitted; the target N6 interface is determined by the edge UPF network element based on the IP address of the target terminal device and a first mapping relationship; the first mapping relationship includes the correspondence between different IP addresses and different N6 interface identifiers; The message to be transmitted is transmitted based on a target transmission rate; the target transmission rate is the transmission rate of the bandwidth of the target DN interface of the message to be transmitted; the bandwidth of the target DN interface is the same as the bandwidth of the target terminal device.

2. The method according to claim 1, characterized in that, The target DN interface is connected to the target N6 interface via a target virtual LAN (VLAN); the VLAN identifier of the target DN interface is the same as that of the target N6 interface.

3. The method according to claim 1, characterized in that, The IP address of the target terminal device is determined by the edge UPF network element after performing session matching on the message to be transmitted.

4. The method according to claim 1, characterized in that, The target data network name (DNN) is associated with the target DN interface and the target N6 interface; the target DNN is the DNN configured for the target terminal device.

5. The method according to claim 1, characterized in that, If the message to be transmitted is a downlink message, after obtaining the message to be transmitted from the target terminal device, the method further includes: Parse the DN interface identifier carried in the message to be transmitted; Based on the DN interface identifier carried in the message to be transmitted, the target DN interface is determined from a plurality of preset DN interfaces.

6. The method according to claim 5, characterized in that, If the message to be transmitted is a downlink message, after obtaining the message to be transmitted from the target terminal device, the method further includes: The corresponding target N6 interface is determined based on the target DN interface; The message to be transmitted is transmitted based on the target DN interface and the target N6 interface.

7. The method according to any one of claims 1-6, characterized in that, The transmission of the message to be transmitted based on the target transmission rate includes: Determine whether the required bandwidth of the message to be transmitted is less than or equal to the bandwidth of the target DN interface; If the required bandwidth is less than or equal to the bandwidth of the target DN interface, the message to be transmitted is transmitted based on the target transmission rate.

8. The method according to claim 7, characterized in that, The method further includes: If the required bandwidth is greater than the bandwidth of the target DN interface, the message to be transmitted is discarded.

9. A message transmission device, characterized in that, The device, applied to multi-access edge computing (MEC) nodes, includes: an acquisition unit and a processing unit; The acquisition unit is used to acquire the message to be transmitted from the target terminal device; the source Internet Protocol IP address or the destination IP address of the message to be transmitted is the IP address of the target terminal device. The processing unit is configured to determine the DN interface receiving the message to be transmitted as the target DN interface if the message to be transmitted is an uplink message. The processing unit is configured to determine that the target DN interface and the target N6 interface are associated interfaces; the target N6 interface is the N6 interface through which the edge UPF network element sends the message to be transmitted; the target N6 interface is determined by the edge UPF network element based on the IP address of the target terminal device and a first mapping relationship; the first mapping relationship includes the correspondence between different IP addresses and different N6 interface identifiers; The processing unit is configured to transmit the message to be transmitted based on a target transmission rate; the target transmission rate is the transmission rate of the bandwidth of the target DN interface of the message to be transmitted; the bandwidth of the target DN interface is the same as the bandwidth of the target terminal device.

10. A computer-readable storage medium, characterized in that, The readable storage medium stores instructions that, when executed, implement the method as described in any one of claims 1-8.

11. A message transmission device, characterized in that, An application to a multi-access edge computing (MEC) node includes: a processor, a memory, and a communication interface; wherein the communication interface is used for the message transmission device to communicate with other devices or networks; the memory is used to store one or more programs, the one or more programs including computer-executable instructions, and when the message transmission device is running, the processor executes the computer-executable instructions stored in the memory to cause the message transmission device to perform the method of any one of claims 1-8.

Images