Uplink data control method, apparatus and device, and storage medium

Abstract

Disclosed in the present application are an uplink data control method, apparatus and device, and a storage medium. The method comprises: receiving uplink data sent by a terminal; determining, by means of a preset offloading rule, a data network access identifier corresponding to the uplink data; on the basis of the data network access identifier, determining a virtual local area network corresponding to the uplink data; when the uplink data corresponds to a public-network virtual local area network, sending the uplink data to a public network or a public-network user plane function network element device by means of the public-network virtual local area network; and when the uplink data corresponds to a local virtual local area network, sending the uplink data to an internal network by means of the local virtual local area network.

Description

Uplink data control method, device, equipment and storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This disclosure is based on and claims the priority of Chinese patent application with application number 202311599550.5 and application date of November 27, 2023. The entire content of this Chinese patent application is incorporated herein by reference into this disclosure. Technical Field

[0003] The present application relates to the field of mobile communication technology, and in particular to a method, apparatus, device and storage medium for uplink data control. Background Art

[0004] Mobile network operators have long demanded customized data destinations. For example, some service providers are gradually deploying their own servers down-market, hoping to reduce circuitous routes and improve the customer experience. Some enterprises also seek customized management of their mobile networks to achieve higher security and more guaranteed bandwidth.

[0005] With the development of 5G technology, the uplink classifier (ULCL) user plane function (UPF) distinguishes local services, such as those used within an enterprise or downlink services deployed by a service provider, from normal services through traffic diversion. These services are then delivered to the central network or local network via the primary or secondary anchor UPF, respectively. However, current solutions rely on the ULCL UPF for traffic diversion, and therefore only support traffic diversion within the ULCL UPF coverage area. Traffic diversion is unavailable if the user roams outside the ULCL UPF coverage area.

[0006] Summary of the Invention

[0007] In view of one or more of the above-mentioned problems, the present application provides a method, apparatus, device and storage medium for uplink data control, which can realize the diversion of uplink traffic by a single user plane functional network element device and expand the diversion range.

[0008] In a first aspect, an embodiment of the present application provides a method for uplink data control, which is performed by a user plane functional network element device, including:

[0009] Receive uplink data sent by the terminal;

[0010] Determining a data network access identifier corresponding to the uplink data by a preset diversion rule;

[0011] Determining, based on the data network access identifier, a virtual local area network corresponding to the uplink data;

[0012] In the case where the uplink data corresponds to a public network virtual local area network, sending the uplink data to a public network or a public network user plane functional network element device through the public network virtual local area network;

[0013] In a case where the uplink data corresponds to a local virtual local area network, the uplink data is sent to the internal network via the local virtual local area network.

[0014] In some possible implementations, the method further includes:

[0015] Get the configuration information corresponding to the virtual LAN;

[0016] Searching for a preset location of the configuration information to obtain a corresponding data network access identifier;

[0017] The corresponding relationship between the data network access identifier and the virtual local area network is stored.

[0018] In some possible implementations, the method further includes:

[0019] Sending a virtual user plane function identifier corresponding to the internal network to the session management function device;

[0020] Receive the diversion rule sent by the session management function device based on the virtual user plane function identifier, and use the diversion rule as the preset diversion rule.

[0021] In some possible implementations, the method further includes:

[0022] receiving a charging policy sent by the session management function device;

[0023] According to the billing policy, obtaining billing information of the terminal, the billing information including data traffic and / or connection duration of the terminal, and a corresponding usage report rule identifier;

[0024] The charging information is sent to the session management function device, so that the session management function device performs charging based on the charging information.

[0025] In a second aspect, an embodiment of the present application provides another method for uplink data control, which is performed by a session management function device and includes:

[0026] Obtain device information of the terminal's main user plane functional network element devices;

[0027] In the case where the primary user plane functional network element device is a public network user plane functional network element device, issuing a diversion rule to the target user plane functional network element device, so that the target user plane functional network element device sends uplink data corresponding to the public network virtual local area network to the primary user plane functional network element device;

[0028] When the main user plane functional network element device is a private network user plane functional network element device, a diversion rule is issued to the target user plane functional network element device so that the target user plane functional network element device sends the uplink data corresponding to the public network virtual LAN to the public network.

[0029] In some possible implementations, the method further includes:

[0030] Sending charging policies to user plane functional network element devices;

[0031] Receiving billing information sent by the user plane functional network element device, the billing information including the data traffic and / or connection duration of the terminal and the corresponding usage reporting rule identifier;

[0032] Generate a call bill according to the gateway information corresponding to the usage report rule identifier and the data traffic and / or connection duration of the terminal;

[0033] The call record is sent to the billing service platform for billing.

[0034] In some possible implementations, the method further includes:

[0035] Obtaining location information of the terminal;

[0036] When the terminal moves to a preset designated range of the internal network, a diversion rule is sent to a target user plane functional network element device so that the target user plane functional network element device can send uplink data generated by the terminal to the internal network.

[0037] In a third aspect, an embodiment of the present application provides an apparatus for uplink data control, the apparatus comprising:

[0038] A receiving module, used for receiving uplink data sent by the terminal;

[0039] A processing module, configured to determine a data network access identifier corresponding to the uplink data according to a preset diversion rule;

[0040] a determination module, configured to determine, based on the data network access identifier, the virtual local area network corresponding to the uplink data;

[0041] A sending module, configured to send the uplink data to a public network or a public network user plane function network element device through the public network virtual local area network when the uplink data corresponds to a public network virtual local area network;

[0042] The sending module is further configured to send the uplink data to the internal network via the local virtual local area network when the uplink data corresponds to the local virtual local area network.

[0043] In a fourth aspect, an embodiment of the present application provides a device for uplink data control, comprising: a processor, and a memory storing computer program instructions; the processor reads and executes the computer program instructions to implement the uplink data control method as described above.

[0044] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the method for uplink data control as described above is implemented.

[0045] The implementation method of the present application links and stores the correspondence between the data network access identifier and the virtual local area network in the virtual local area network configuration information, so that the corresponding virtual local area network can be directly determined by the data network access identifier in the future, thereby speeding up the processing speed.

[0046] The implementation manner of the present application obtains the diversion rules by sending the virtual user plane function identifier corresponding to the internal network to the session management function device, thereby ensuring the timeliness and accuracy of the preset diversion rules.

[0047] The implementation method of the present application performs billing based on billing-related information such as terminal data traffic and connection duration according to the billing policy of the session management function device, which can realize different billing based on different service categories and improve the flexibility of billing.

[0048] The implementation method of the present application implements the diversion of uplink traffic by a single user plane functional network element device by issuing different diversion rules to different user plane functional network element devices, allowing the corresponding user plane functional network element devices to divert different traffic.

[0049] The implementation method of the present application sends a billing policy to the user plane functional network element device, and then receives the user's billing information obtained by the user plane functional network element device. Based on the billing information, the corresponding call bill is generated and billing is performed through the billing service platform. This can achieve different billing based on different service categories, thereby improving billing flexibility.

[0050] The embodiment of the present application determines whether the terminal is within the preset service range based on the terminal's location, and then decides whether to divert the terminal's traffic. The location of devices that can access the intranet can be restricted according to actual needs, thereby increasing data security.

[0051] The method, apparatus, device and storage medium for uplink data control of the implementation mode of the present application pre-sets the preset diversion rules and the corresponding virtual local area network in the user plane functional network element device. When receiving the uplink data sent by the receiving terminal, the data network access identifier corresponding to the uplink data is determined according to the preset diversion rules, and then the data network access identifier is used to accurately determine whether the uplink data should be sent to the public network or the internal network, and the uplink data is sent to the corresponding network through the corresponding virtual local area network, and the virtual local area network is used to isolate the data of different networks. The diversion of uplink traffic by a single user plane functional network element device is realized, and there is no need to rely on the ULCL UPF. By updating the software of the existing network element device, the uplink data diversion is no longer limited to the coverage range of the ULCL UPF. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] The present application can be better understood from the following description of specific embodiments of the present application in conjunction with the accompanying drawings, in which:

[0053] Other features, objects and advantages of the present application will become more apparent by reading the following detailed description of non-limiting embodiments with reference to the accompanying drawings, in which the same or similar reference numerals represent the same or similar features.

[0054] FIG1 is a schematic diagram of the network configuration of the technical solution of this application;

[0055] FIG2 is a schematic flow chart of a method for uplink data control provided by an embodiment of the present application;

[0056] FIG3 is a schematic flow chart of a method for uplink data control provided by another embodiment of the present application;

[0057] FIG4 is a schematic diagram of the UPF deployment logic in an embodiment of the present application;

[0058] FIG5 is a schematic diagram of a billing method according to an embodiment of the present application;

[0059] FIG6 is a schematic structural diagram of an uplink data control apparatus provided by another embodiment of the present application;

[0060] FIG7 is a schematic diagram of the hardware structure of uplink data control provided in an embodiment of the present application. DETAILED DESCRIPTION

[0061] The features and exemplary embodiments of various aspects of the present application will be described in detail below. In the detailed description below, many specific details are proposed to provide a comprehensive understanding of the application. However, it will be apparent to those skilled in the art that the application can be implemented without the need for some of these specific details. The following description of the embodiments is merely to provide a better understanding of the application by illustrating the examples of the present application. The application is by no means limited to any specific configuration and algorithm proposed below, but covers any modification, replacement and improvement of elements, parts and algorithms without departing from the spirit of the application. In the accompanying drawings and the following description, known structures and technologies are not shown to avoid causing unnecessary ambiguity to the application.

[0062] It should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or device comprising the element.

[0063] Primary anchor point UPF: The UPF that allocates an IP address to a user terminal when the user terminal activates a protocol data unit session. During the user terminal session, it serves as the anchor point for the protocol data unit session.

[0064] ULCL UPF: UPF that implements uplink classification, which is inserted into the user session by the Session Management Function (SMF) when traffic diversion is activated.

[0065] Auxiliary anchor UPF: When traffic diversion is activated, the UPF is inserted simultaneously with the ULCL UPF. It is connected to the local network through the N6 interface and is responsible for processing traffic on the local network.

[0066] Mobile network operators have long demanded customized data destinations. For example, some service providers are gradually deploying their own servers down-market, hoping to reduce circuitous routes and improve the customer experience. Some enterprises also seek customized management of their mobile networks to achieve higher security and more guaranteed bandwidth.

[0067] At present, with the development of 5G technology. Through diversion, the uplink classifier (ULCL) user plane function (UPF) distinguishes local services, such as services used within the enterprise, or sinking services deployed by service providers, from normal services, and delivers them to the central network or local network through the main anchor point UPF or the auxiliary anchor point UPF respectively. However, the current solution relies on ULCL UPF for diversion, so it only supports diversion within the coverage of ULCL UPF. If the user roams out of the coverage of ULCL UPF, diversion cannot be performed. Moreover, when the operator provides the on-site UPF to the local network, it is also necessary to expand the local city's bearer network bandwidth, which increases the operation and maintenance and construction costs.

[0068] The inventors have studied the above-mentioned issues and discovered that currently, achieving uplink data offloading requires the coordinated operation of three types of UPFs. Furthermore, because offloading relies on ULCL UPFs, offloading services are limited by the coverage of the ULCL UPFs and cannot be rolled out. Dedicated deployment of a large number of ULCL UPFs is also prohibitively expensive. This problem could be resolved by enabling all existing UPFs to support offloading through software updates. Specifically, by dividing virtual local area networks (VLANs) within each UPF, traffic data from the public network and local network could be separated. Offloading rules could then be set within the UPFs, allowing different traffic data to pass through different VLANs. This allows a single UPF to perform both offloading and the routing of different traffic flows. Specifically, referring to Figure 1, after updating all existing ULCL UPFs and auxiliary UPFs, as well as some primary UPFs, the UPFs in the communication system are primarily divided into two categories: private network or intranet UPFs used for offloading, and public network UPFs used only for complex public network traffic data. User traffic can be diverted through the intranet UPF. At the same time, since public network traffic is generally much larger than intranet traffic, the pressure on the intranet UPF can be reduced by having the intranet UPF forward the public network traffic to the public network UPF.

[0069] Specifically, an embodiment of the method for uplink data control of the present application is proposed, and reference may be made to FIG2 . In this embodiment, the method is applied to a user plane functional network element device, and the method includes the following steps S201 to S205 .

[0070] Step S201: receiving uplink data sent by a terminal.

[0071] A terminal can be a device connected to the network, such as a smartphone, computer, or sensor device.

[0072] Uplink data is data transmitted from a terminal device or user end to a server or network center. In network communications, uplink data is often used to upload files, send requests, or convey user actions. For example, uplink data is sent when a user terminal sends an email or uploads a file.

[0073] In a specific implementation, after establishing a connection with a terminal device, the transmission request sent by the terminal device is received. The transmission request usually includes the destination address and other necessary header information. Then, the uplink data packet of the terminal device is received. The data can be in the form of text, files, images, audio, etc.

[0074] Step S202: Determine the data network access identifier corresponding to the uplink data through a preset diversion rule.

[0075] Preset routing rules can be used to distribute data to different processing paths or targets according to specific rules during data transmission or processing. These rules are used to determine how to divert input data to appropriate processing systems, services, or resources.

[0076] The data network access identifier can be the access identifier of the data network. Each network has a unique identifier that distinguishes different networks or subnetworks. This name is typically used to identify and manage network resources, making it easier for users or systems to access and configure them. This identifier can be the Data Network Name (DNN). In 5G networks, the DNN is equivalent to the Access Point Name (APN) in 4G.

[0077] In practice, the user plane functional network element device pre-stores a set of traffic diversion rules that can be categorized based on various criteria. For example, diversion rules can be formulated based on the data's source address, destination address, transmission protocol, data content type, and data volume. Upon receiving uplink data, these rules are used to determine the corresponding data network access identifier.

[0078] Step S203: Based on the data network access identifier, determine the virtual local area network corresponding to the uplink data.

[0079] A Virtual Local Area Network (VLAN) is a technology that logically divides LAN members into different groups based on specific criteria. VLANs can be used to create multiple logically independent LANs on a single physical network infrastructure, allowing different devices to be divided into different virtual networks, even if they are connected to the same network device.

[0080] In practice, user-plane functional network elements are pre-configured with virtual local area networks (VLANs), and each VLAN is assigned a unique VLAN ID. These VLAN IDs are typically numeric and uniquely identify each VLAN. Each data network access ID is associated with one or more specific VLAN IDs. When uplink data arrives at a network device, the device identifies the VLAN to which the data corresponds based on pre-configured VLAN IDs and association rules. This may involve inspecting the VLAN tag in the packet or determining the VLAN to which the data belongs based on port and device configuration.

[0081] Step S204: When the uplink data corresponds to a public network virtual local area network, the uplink data is sent to a public network or a public network user plane functional network element device through the public network virtual local area network.

[0082] A public VLAN is a virtual local area network that sends data to a public network, namely the Internet.

[0083] Public network user plane function network elements are devices deployed on the public Internet to provide network connectivity and services. They are typically located within the service provider's network and handle data traffic and network functions for public network users.

[0084] In a specific implementation, VLAN tagging is required for specific uplink data traffic. VLAN tagging is a technology used to identify and separate different virtual local area networks (VLANs) within a network. It adds a VLAN tag to the packet header to indicate the VLAN to which the packet belongs. If the uplink data corresponds to a public VLAN, the data is sent to the public network or a public network user plane functional network element.

[0085] Step S205: When the uplink data corresponds to a local virtual local area network, the uplink data is sent to the internal network via the local virtual local area network.

[0086] A local virtual LAN can be a virtual LAN that sends data to a local network, that is, a LAN built by the user himself.

[0087] In a specific implementation, by configuring the virtual local area network, the corresponding uplink data is sent to the internal network through the virtual local area network.

[0088] The embodiments of the present application pre-set pre-configured traffic diversion rules and configure corresponding virtual local area networks (VLANs) in user plane functional network element devices. Upon receiving uplink data from a receiving terminal, the pre-configured traffic diversion rules determine whether the uplink data should be sent to a public network or an internal network, and then the uplink data is sent to the corresponding network via the virtual local area network. This enables uplink traffic diversion by a single user plane functional network element device, eliminating the need for reliance on the ULCL UPF. Software updates to existing network element devices can eliminate the need for uplink data diversion to be limited to the coverage area of ​​the ULCL UPF.

[0089] In some implementations, before determining the data network access identifier corresponding to the uplink data using a preset diversion rule, the method further includes:

[0090] Get the configuration information corresponding to the virtual local area network.

[0091] In a specific implementation, corresponding network management software and scripts can be used to query and obtain the configuration information corresponding to the virtual local area network.

[0092] The preset location of the configuration information is searched to obtain the corresponding data network access identifier.

[0093] In a specific implementation, the found configuration information is searched for fields or columns related to data network access, and the obtained data network access identifier is recorded.

[0094] The corresponding relationship between the data network access identifier and the virtual local area network is stored.

[0095] In a specific implementation, storing the corresponding relationship between the data network access identifier and the virtual local area network can be achieved by configuring a configuration file or establishing a corresponding database.

[0096] The implementation method of the present application links and stores the correspondence between the data network access identifier and the virtual local area network in the virtual local area network configuration information, so that the corresponding virtual local area network can be directly determined by the data network access identifier in the future, thereby speeding up the processing speed.

[0097] In some implementations, before receiving uplink data sent by the terminal, the method further includes:

[0098] The virtual user plane function identifier corresponding to the internal network is sent to the session management function device.

[0099] Session management devices are network devices used to manage and control network sessions. They are responsible for tracking, monitoring, and maintaining sessions established with different users or terminal devices in the network. Specifically, session management devices are devices in mobile communication systems that run session management functions.

[0100] In a specific implementation, a virtual user plane function identifier corresponding to the internal network is sent to the session management function device. For example, a preset protocol can be used to transmit the virtual user plane function identifier, and it is ensured that the session management device can correctly parse and understand these protocols.

[0101] Receive the diversion rule sent by the session management function device based on the virtual user plane function identifier, and use the diversion rule as the preset diversion rule.

[0102] In specific implementations, the system communicates with the session management device to request traffic diversion rules based on the virtual user plane function identifier (VUPF). After receiving the diversion rules returned from the session management device, the system parses and processes them and then applies them as pre-set diversion rules. This means that sessions and traffic will be diverted based on these rules.

[0103] The implementation manner of the present application obtains the diversion rules by sending the virtual user plane function identifier corresponding to the internal network to the session management function device, thereby ensuring the timeliness and accuracy of the preset diversion rules.

[0104] In some implementations, after sending the virtual user plane function identifier corresponding to the internal network to the session management function device, the method further includes:

[0105] Receive the charging policy sent by the session management function device.

[0106] Billing policies can be the rules and principles governing pricing and charging for communications services. Examples include usage-based billing and monthly or annual subscriptions. For example, a telecom operator offers a mobile phone plan where users pay a fixed monthly fee for a certain amount of talk time and data usage.

[0107] In a specific implementation, it is necessary to establish a communication connection with the session management function device, communicate with the session management function device, and send a specific query request to the device to request the current charging policy setting.

[0108] According to the charging policy, the charging information of the terminal is obtained, where the charging information includes the data traffic and / or connection duration of the terminal, and a corresponding usage report rule identifier.

[0109] Billing information can be data or information related to the use and charging of services. It includes records of user consumption, rate calculations, payment information, and other billing-related data.

[0110] A usage reporting rule identifier is an identifier assigned to a user terminal in the corresponding Usage Reporting Rules (URR). For example, a telecom operator may need to collect and report customer usage data for communication services, such as call duration, text message volume, and data usage. These reports can be used to optimize network resource allocation.

[0111] In specific implementations, it is necessary to collect billing-related information such as the terminal's data traffic and connection duration. This may involve monitoring the data transmission status of the network interface, recording the timestamps of user operations, or other data related to data network usage. The collected billing information is then processed according to pre-defined billing policies. Billing policies may be differentiated based on different usage reporting rule identifiers. For example, some rule identifiers may require billing based on data traffic, while others may require billing based on connection duration. When processing billing information, it is necessary to associate the terminal's data traffic and connection duration with the corresponding usage reporting rule identifier.

[0112] The charging information is sent to the session management function device, so that the session management function device performs charging based on the charging information.

[0113] In a specific implementation, after generating the billing information, a communication connection is established with the session management function device. The generated billing information is sent to the session management function device via a communication channel. Once the session management function device receives the billing information, it performs appropriate billing processing based on the received information. This may involve verifying the validity of the billing information, charging according to preset billing rules, and updating the user's billing status.

[0114] The embodiment of the present application performs billing based on billing-related information such as terminal data traffic and connection duration according to the billing policy of the session management function device, which can realize different billing based on different service categories and improve billing flexibility.

[0115] Based on the above embodiment, another embodiment of the method for uplink data control of the present application is proposed. This method is applied to a session management function device. As shown in FIG3 , the method includes steps S301 to S303 .

[0116] Step S301: Acquire device information of the main user plane function network element device of the terminal.

[0117] Primary user plane function network elements are network devices that directly interact with end users and provide primary functions and services. They are typically located at the edge of the network, providing end users with various services such as connectivity, communication, and data transmission.

[0118] In a specific implementation, a network scan may be performed to discover the primary user plane functional network element device connected to the terminal device, and then obtain device information of the primary user plane functional network element device of the terminal.

[0119] Step S302: When the main user plane functional network element device is a public network user plane functional network element device, a diversion rule is issued to the target user plane functional network element device so that the target user plane functional network element device sends the uplink data corresponding to the public network virtual LAN to the main user plane functional network element device.

[0120] The target user plane functional network element device may be a user plane functional network element device that is newly added in addition to the main user plane functional network element device in order to complete traffic distribution or load sharing.

[0121] In specific implementations, it is necessary to identify and determine the target user plane functional network element device. This can be achieved through the device's IP address, MAC address, or other unique identifier. For example, the software may maintain a device list that contains all available target user plane functional network element devices and their related information. Based on demand, a diversion rule is generated to instruct the target user plane functional network element device to send the uplink data corresponding to the public network virtual LAN to the primary user plane functional network element device. Through the connection established with the target user plane functional network element device, a configuration command is sent to the target user plane functional network element device, and the generated diversion rule is sent to the target user plane functional network element device.

[0122] Step S303: When the main user plane functional network element device is a private network user plane functional network element device, a diversion rule is issued to the target user plane functional network element device so that the target user plane functional network element device sends the uplink data corresponding to the public network virtual LAN to the public network.

[0123] In a specific implementation, the target user plane functional network element device is determined. Traffic diversion rules are then generated for the target user plane functional network element device. These rules may include conditions such as the source IP address, destination IP address, and port number, as well as configuration information indicating that data should be sent to the public network. A configuration command is sent to the target user plane functional network element device via a connection established with the target user plane functional network element device, and the generated traffic diversion rules are distributed to the target user plane functional network element device.

[0124] The implementation method of the present application implements the diversion of uplink traffic by a single user plane functional network element device by issuing different diversion rules to different user plane functional network element devices, allowing the corresponding user plane functional network element devices to divert different traffic.

[0125] In some implementations, after obtaining device information of a primary user plane function network element device of the terminal, the method further includes:

[0126] Send the charging policy to the user plane functional network element device.

[0127] In a specific implementation, a charging policy is pre-configured, including information such as charging rules, rates, and billing cycles. These policies can be customized based on service requirements and device characteristics. The configured charging policy is converted into a format recognizable by the user plane functional network element device, typically using configuration commands supported by the device. The converted charging policy is then sent to the user plane functional network element device via a connection established with the device.

[0128] Receive the billing information sent by the user plane functional network element device, where the billing information includes the data traffic and / or connection duration of the terminal and the corresponding usage report rule identifier.

[0129] In a specific implementation, a connection is established with a user plane functional network element device via a selected communication protocol to receive billing information. The billing information sent by the user plane functional network element device is then received. This information may be real-time events pushed by the device, responses to periodic polling queries, or data provided by other means.

[0130] Generate a call bill based on the gateway information corresponding to the usage report rule identifier and the data traffic and / or connection duration of the terminal.

[0131] A call record (CDR) is a file data file transmitted within a communication system, recording every original communication record. This includes information such as the serial number, user ID, calling number, called number, start time, end time, call duration, internet traffic, and call nature. It is also known as a Call Detail Record (CDR). Call records can be categorized as voice, SMS, and data service records. A CDR is generated whenever a user uses a service.

[0132] In a specific implementation, a specific call record can be generated according to a predefined call record format based on the obtained gateway information, terminal data traffic and / or connection duration. The call record contains a detailed record of billing information, usually including terminal identification, start and end time, data traffic, connection duration, rate, fee, etc. In the process of generating the call record, the obtained gateway information, terminal data traffic and / or connection duration need to be filled into the corresponding call record fields. This may involve operations such as string concatenation, data format conversion, and unit conversion. The generated call record can be saved to a database, file system, or other data storage medium, and the call record data can be persisted for subsequent query, statistics, and bill generation.

[0133] The call record is sent to the billing service platform for billing.

[0134] A billing service platform is a software platform that provides billing management and bill generation capabilities to support billing requirements in various business scenarios. It centrally manages and processes billing-related information, such as resource usage, rate settings, bill generation, and payment.

[0135] In practice, a network connection must first be established with the billing service platform to transmit call record data and receive billing results. Before sending the call record data to the billing service platform, the data must be formatted to meet the platform's interface requirements. After formatting, the data is sent to the billing service platform via the established connection. This can be accomplished by sending HTTP requests, TCP packets, or other methods.

[0136] The implementation method of the present application sends a billing policy to the user plane functional network element device, and then receives the user's billing information obtained by the user plane functional network element device. Based on the billing information, the corresponding call bill is generated and billing is performed through the billing service platform. This can achieve different billing based on different service categories, thereby improving billing flexibility.

[0137] In some implementations, after obtaining device information of a primary user plane function network element device of the terminal, the method further includes:

[0138] Acquire the location information of the terminal.

[0139] In specific implementations, positioning services typically include GPS, Wi-Fi, Bluetooth, and mobile network base stations. You can choose the appropriate positioning method based on your needs. Generally speaking, the terminal's location information is determined directly through a mobile network base station.

[0140] When the terminal moves to a preset designated range of the internal network, a diversion rule is sent to a target user plane functional network element device so that the target user plane functional network element device can send uplink data generated by the terminal to the internal network.

[0141] In the specific implementation, the terminal's location information is monitored in real time, and based on the terminal's location information, it is determined whether it has moved into the preset designated range of the internal network. Once the terminal moves into the preset designated range of the internal network, the corresponding diversion rules are issued to the target user plane functional network element device through the established connection.

[0142] The embodiment of the present application determines whether the terminal is within the preset service range based on the terminal's location, and then decides whether to divert the terminal's traffic. The location of devices that can access the intranet can be restricted according to actual needs, thereby increasing data security.

[0143] As an implementation of the present application, in this embodiment, a virtual UPF instance can be configured in a session management function (SMF) device, and a binding relationship between the virtual UPF instance and a data network access identifier (DNAI) can be configured. This allows the session management function device to treat a single UPF as multiple UPFs, even if the UPF can actually perform the functions of multiple UPFs. This reduces modifications to the session management function device and facilitates solution implementation and deployment.

[0144] In the UPF, add a primary anchor VPN, which is also a public network VPN; add a primary anchor address pool; and add the primary anchor local policy and charging control (PCC) rules. At the same time, add a secondary anchor VPN based on DNAI configuration; add a secondary anchor address pool for publishing routes; add ULCL diversion rule configuration, which mainly includes L34, DNS domain name, etc.; and add secondary anchor local configuration. The improved UPF implements the functions of the primary anchor UPF, secondary anchor UPF, and ULCL UPF. This three-in-one UPF can communicate with the private network in the user campus through the N6 dedicated line using the Generic Routing Encapsulation (GRE) tunnel protocol.

[0145] Through new construction or retrofitting and upgrading existing mainstream solutions, there are two types of UPFs: the original, unmodified primary anchor point UPF, which serves as the UPF for the external network, namely the Internet; and the improved three-in-one UPF. The two private network UPFs simultaneously facilitate both external and internal network traffic. The three-in-one UPF can serve as the primary anchor point for external network services and also as both the primary and secondary anchor point for campus users. This UPF supports the ULCL three-in-one function (i.e., one UPF supports primary, secondary, and ULCL functions).

[0146] During implementation, when campus users have not entered the edge UPF 5G tracking area, that is, the preset diversion service area, the private network UPF and the external network UPF will serve as the main anchor points for campus contracted users and ordinary users, and the load will be shared between the private network UPF and the external network UPF.

[0147] When a campus user enters the edge UPF 5G tracking area, the private network UPF acts as the campus user's ULCL UPF + secondary anchor UPF. If the private network UPF previously served as the campus user's primary anchor, the private network UPF now serves as a three-in-one UPF, allowing the campus user to access both local campus services and internet services on this private network UPF. If the external network UPF previously served as the campus user's primary anchor, the private network 2 UPF now serves as a two-in-one UPF (ULCL UPF + secondary anchor UPF), allowing the campus user to access both local campus services and internet services on the original external network UPF. The private network UPF requires dedicated lines to connect to the campus intranet. In scenarios where the private network UPF serves as a two-in-one UPF and the external network UPF serves as the primary anchor UPF, the private network UPF must connect to the N9 interface connected to the other external network UPFs to communicate with the external network UPF via this N9 interface.

[0148] Users in different campuses are distinguished through DNAI to solve the problem of overlapping server addresses in different campuses. In the case of overlapping user IP addresses under the external network UPF, the private network UPF detects user IP address overlap and needs to shut down the user session.

[0149] As shown in Figure 4, UPF1, UPF2, UPF3, and UPF4 serve as the primary anchor points for the common data network name (DNN), connected to the Internet via the N6 egress and deployed in a load-sharing manner. UPF1 and UPF2 also serve as ULCL and secondary anchor points, with the N6 egress added to the campus network, deployed in a primary-backup manner.

[0150] During actual user usage, if the user terminal has selected UPF1 or UPF2 as the primary anchor point, the SMF will prioritize the primary anchor point UPF1 or UPF2 as the user's three-in-one UPF when inserting the ULCL and secondary anchor point for the user. If the user terminal has selected UPF3 or UPF4 as the primary anchor point, the SMF will prioritize UPF1 and UPF2 as the user's two-in-one UPF based on the configuration.

[0151] The general-purpose DNN on the three-in-one UPF has two N6 egresses: one external N6, connecting to the Internet; the other, the enterprise N6, connecting to the enterprise campus's internal LAN. The same user terminal also has two N6 egresses: public network services are sent to the Internet via the external VPN, while campus services are sent to the campus' internal LAN via the internal VPN. The internal VPN is configured on the three-in-one UPF based on DNAI to distinguish it from the external VPN.

[0152] When configuring the corresponding address pool for the extranet VPN on the UPF, you only need to configure the user terminal address segment of the primary anchor point of the UPF. When configuring the downlink route of the user terminal for the intranet VPN on the UPF, the configuration is the same as that of the UPF two-in-one secondary anchor point UPF.

[0153] In addition, the Policy Control Function (PCF) platform issues corresponding PCCs to the three-in-one UPF and the external network UPF. For the three-in-one UPF, both the external network PCC and the internal network PCC are issued, while for the external network UPF, only the external network PCC is issued. This allows for separate billing of external and internal network traffic.

[0154] The specific billing method is shown in Figure 5. Since a virtual UPF is set up for the three-in-one UPF on the SMF, the three-in-one UPF appears as two UPFs on the SMF. This virtual UPF corresponds to a UPF ID and its corresponding DNAI. This UPF ID will be reported to the Charging Function (CHF) platform and the Business & Operation Support System (BOSS). Among them, BOSS needs to support multiple UPF IDs in the billing request for a session, and the authorized quota for each different network will be replied separately in the response message.

[0155] First, SMF issues the ULCL diversion strategy and the extranet and intranet service billing strategy to the three-in-one UPF. The three-in-one UPF charges the data flow of the extranet service rules according to the extranet billing strategy issued by SMF, and supports content billing based on service identification. The corresponding billing traffic and duration statistics of the three-in-one UPF, as well as the corresponding usage reporting rules (URR), are reported to SMF. For private network services in the campus, the three-in-one UPF charges the locally diverted service flows according to the intranet billing strategy issued by SMF.

[0156] The technical implementation method of the UPF three-in-one function provided in this application can support the diversion and billing of external and internal network traffic access for users outside the coverage area of ​​ULCL UPF. It can also reduce the investment cost of operators in the shared UPF scenario in prefecture-level cities to a certain extent.

[0157] Based on the uplink data control method provided in the above embodiment, the present application also provides a specific implementation of an uplink data control device. Please refer to the following embodiment.

[0158] First, referring to FIG6 , an apparatus 600 for uplink data control provided in an embodiment of the present application includes the following modules:

[0159] The receiving module 601 is configured to receive uplink data sent by a terminal.

[0160] The processing module 602 is configured to determine the data network access identifier corresponding to the uplink data according to a preset diversion rule.

[0161] The determination module 603 is configured to determine the virtual local area network corresponding to the uplink data based on the data network access identifier.

[0162] The sending module 604 is configured to send the uplink data to a public network or a public network user plane functional network element device via the public network virtual local area network when the uplink data corresponds to a public network virtual local area network.

[0163] The sending module 604 is further configured to send the uplink data to the internal network via the local virtual local area network when the uplink data corresponds to the local virtual local area network.

[0164] The embodiments of the present application pre-set pre-configured traffic diversion rules and configure corresponding virtual local area networks (VLANs) in user plane functional network element devices. Upon receiving uplink data from a receiving terminal, the pre-configured traffic diversion rules determine whether the uplink data should be sent to a public network or an internal network, and then the uplink data is sent to the corresponding network via the virtual local area network. This enables uplink traffic diversion by a single user plane functional network element device, eliminating the need for reliance on the ULCL UPF. Software updates to existing network element devices can eliminate the need for uplink data diversion to be limited to the coverage area of ​​the ULCL UPF.

[0165] As an implementation of the present application, the uplink data control apparatus 600 may further include the following modules:

[0166] The acquisition module is used to obtain the configuration information corresponding to the virtual local area network.

[0167] The search module is used to search for a preset location of the configuration information and obtain a corresponding data network access identifier.

[0168] The storage module is used to store the corresponding relationship between the data network access identifier and the virtual local area network.

[0169] The implementation method of the present application links and stores the correspondence between the data network access identifier and the virtual local area network in the virtual local area network configuration information, so that the corresponding virtual local area network can be directly determined by the data network access identifier in the future, thereby speeding up the processing speed.

[0170] As an implementation of the present application, the sending module 604 is further configured to send a virtual user plane function identifier corresponding to the internal network to the session management function device.

[0171] The receiving module 601 is further configured to receive a diversion rule sent by the session management function device based on the virtual user plane function identifier, and use the diversion rule as a preset diversion rule.

[0172] The implementation manner of the present application obtains the diversion rules by sending the virtual user plane function identifier corresponding to the internal network to the session management function device, thereby ensuring the timeliness and accuracy of the preset diversion rules.

[0173] As an implementation of the present application, the receiving module 601 is further configured to receive a charging policy sent by the session management function device.

[0174] The acquisition module is further configured to acquire terminal billing information according to the billing policy, wherein the billing information includes data traffic and / or connection duration of the terminal, and a corresponding usage report rule identifier.

[0175] The sending module 604 is further configured to send the billing information to the session management function device, so that the session management function device performs billing based on the billing information.

[0176] The implementation method of the present application performs billing based on billing-related information such as terminal data traffic and connection duration according to the billing policy of the session management function device, which can realize different billing based on different service categories and improve the flexibility of billing.

[0177] The embodiment of the present application also provides another device for uplink data control, including:

[0178] The acquisition module is used to obtain the device information of the main user plane function network element device of the terminal. The uplink data control device 600 may also include the following modules:

[0179] The sending module is used to send diversion rules to the target user plane functional network element device when the main user plane functional network element device is a public network user plane functional network element device, so that the target user plane functional network element device can send the uplink data corresponding to the public network virtual LAN to the main user plane functional network element device.

[0180] The sending module is also used to send diversion rules to the target user plane function network element device when the main user plane function network element device is a private network user plane function network element device, so that the target user plane function network element device can send the uplink data corresponding to the public network virtual LAN to the public network.

[0181] The implementation method of the present application implements the diversion of uplink traffic by a single user plane functional network element device by issuing different diversion rules to different user plane functional network element devices, allowing the corresponding user plane functional network element devices to divert different traffic.

[0182] As an implementation of the present application, the uplink data control device further includes:

[0183] The sending module is used to send the charging policy to the user plane functional network element device.

[0184] The receiving module is used to receive the billing information sent by the user plane functional network element device, where the billing information includes the data traffic and / or connection duration of the terminal and the corresponding usage report rule identifier.

[0185] The processing module is used to generate a call record according to the gateway information corresponding to the usage report rule identifier and the data traffic and / or connection duration of the terminal.

[0186] The sending module is also used to send the call record to the billing service platform for billing.

[0187] The implementation method of the present application sends a billing policy to the user plane functional network element device, and then receives the user's billing information obtained by the user plane functional network element device. Based on the billing information, the corresponding call bill is generated and billing is performed through the billing service platform. This can achieve different billing based on different service categories, thereby improving billing flexibility.

[0188] As an implementation method of the present application, the acquisition module is further used to obtain the location information of the terminal.

[0189] The sending module is also used to send diversion rules to the target user plane functional network element device when the terminal moves to a preset specified range of the internal network, so that the target user plane functional network element device can send the uplink data generated by the terminal to the internal network.

[0190] The embodiment of the present application determines whether the terminal is within the preset service range based on the terminal's location, and then decides whether to divert the terminal's traffic. The location of devices that can access the intranet can be restricted according to actual needs, thereby increasing data security.

[0191] The apparatus of the above-mentioned embodiment of the present application can implement the method of uplink data control as described above and achieve the corresponding effect, which will not be described in detail here.

[0192] FIG7 shows a schematic diagram of the hardware structure of an uplink data control device provided in an embodiment of the present application.

[0193] The device for uplink data control may include a processor 701 and a memory 702 storing computer program instructions.

[0194] Specifically, the processor 701 may include a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.

[0195] The memory 702 may include a large capacity memory for data or instructions. By way of example and not limitation, the memory 702 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive, or a combination of two or more of these. Where appropriate, the memory 702 may include removable or non-removable (or fixed) media. Where appropriate, the memory 702 may be inside or outside the integrated gateway disaster recovery device. In a specific embodiment, the memory 702 is a non-volatile solid-state memory.

[0196] The memory may include a read-only memory (ROM), a random access memory (RAM), a magnetic disk storage medium device, an optical storage medium device, a flash memory device, an electrical, optical or other physical / tangible memory storage device. Therefore, generally, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., a memory device) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method for uplink data control according to any one embodiment of the present disclosure.

[0197] The processor 701 implements any one of the uplink data control methods in the above embodiments by reading and executing computer program instructions stored in the memory 702 .

[0198] In one example, the uplink data control device may further include a communication interface 703 and a bus 710. As shown in FIG7, the processor 701, the memory 702, and the communication interface 703 are connected via the bus 710 and communicate with each other.

[0199] The communication interface 703 is mainly used to implement communication between various modules, devices, units and / or equipment in the embodiments of the present application.

[0200] Bus 710 includes hardware, software or both, and the parts of online data flow metering equipment are coupled to each other. For example, but not limitation, bus can include accelerated graphics port (AGP) or other graphics bus, enhanced industry standard architecture (EISA) bus, front side bus (FSB), hypertransport (HT) interconnection, industry standard architecture (ISA) bus, infinite bandwidth interconnection, low pin count (LPC) bus, memory bus, micro channel architecture (MCA) bus, peripheral component interconnection (PCI) bus, PCI-Express (PCI-X) bus, serial advanced technology attachment (SATA) bus, video electronics standard association local (VLB) bus or other suitable bus or two or more of these combinations. In appropriate cases, bus 710 can include one or more buses. Although the present application embodiment describes and shows specific bus, the application considers any suitable bus or interconnection.

[0201] In addition, in conjunction with the uplink data control method in the above embodiment, the present application embodiment can provide a computer storage medium for implementation. The computer storage medium stores computer program instructions; when the computer program instructions are executed by a processor, any of the uplink data control methods in the above embodiment is implemented.

[0202] However, it should be understood that the present application is not limited to the specific configurations and processes described above and shown in the figures. Furthermore, for the sake of brevity, a detailed description of known methods and techniques is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present application is not limited to the specific steps described and shown. Those skilled in the art may make various changes, modifications, and additions, or change the order of the steps after understanding the spirit of the present application.

[0203] The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of the present application are programs or code segments that are used to perform the required tasks. The program or code segment can be stored in a machine-readable medium, or transmitted on a transmission medium or a communication link by a data signal carried in a carrier wave. "Machine-readable medium" can include any medium that can store or transmit information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROMs, flash memories, erasable ROMs (EROMs), floppy disks, CD-ROMs, optical disks, hard disks, optical fiber media, radio frequency (RF) links, etc. The code segment can be downloaded via a computer network such as the Internet, an intranet, etc.

[0204] The present application can be implemented in other specific forms without departing from its spirit and essential characteristics. For example, the algorithm described in the specific embodiment can be modified, and the system architecture does not depart from the basic spirit of the present application. Therefore, the current embodiment is considered to be exemplary and not restrictive in all aspects, and the scope of the present application is defined by the appended claims rather than the above description, and all changes that fall within the scope of the meaning and equivalents of the claims are thereby included within the scope of the present application.

[0205] Those skilled in the art should understand that the above embodiments are exemplary rather than restrictive. Different technical features appearing in different embodiments can be combined to achieve beneficial effects. Based on a study of the drawings, the specification and the claims, those skilled in the art should be able to understand and implement other variations of the disclosed embodiments. In the claims, the term "comprising" does not exclude other devices or steps; the indefinite article "a" does not exclude a plurality; the terms "target" and "second" are used to identify names rather than to indicate any specific order. Any figure marks in the claims should not be understood as limiting the scope of protection. The functions of multiple parts appearing in the claims can be implemented by a separate hardware or software module. The fact that certain technical features appear in different dependent claims does not mean that these technical features cannot be combined to achieve beneficial effects.

Claims

1. A method for uplink data control, performed by a user plane functional network element device, the method comprising: Receiving uplink data sent by the terminal; Determine the data network access identifier corresponding to the uplink data by a preset diversion rule; Based on the data network access identifier, determining the virtual local area network corresponding to the uplink data; In the case where the uplink data corresponds to a public network virtual local area network, sending the uplink data to a public network or a public network user plane functional network element device through the public network virtual local area network; In the case that the uplink data corresponds to a local virtual local area network, the uplink data is sent to the internal network through the local virtual local area network.

2. The method for uplink data control according to claim 1, wherein: The method further comprises: Get the configuration information corresponding to the virtual LAN; Finding the preset location of the configuration information to obtain the corresponding data network access identifier; The corresponding relationship between the data network access identifier and the virtual local area network is stored.

3. The method for uplink data control according to claim 1, wherein: The method further comprises: Sending a virtual user plane function identifier corresponding to the internal network to the session management function device; The diversion rule sent by the session management function device based on the virtual user plane function identifier is received, and the diversion rule is used as a preset diversion rule.

4. The method for uplink data control according to claim 3, wherein: The method further comprises: Receiving a charging policy sent by the session management function device; According to the charging policy, obtaining charging information of the terminal, the charging information including data flow and / or connection duration of the terminal, and a corresponding usage report rule identifier; The charging information is sent to the session management function device, so that the session management function device performs charging based on the charging information.

5. A method for uplink data control, performed by a session management function device, the method comprising: Obtain device information of the terminal's main user plane functional network element devices; In the case where the primary user plane functional network element device is a public network user plane functional network element device, issuing a diversion rule to the target user plane functional network element device so that the target user plane functional network element device sends uplink data corresponding to the public network virtual local area network to the primary user plane functional network element device; When the main user plane functional network element device is a private network user plane functional network element device, a diversion rule is issued to the target user plane functional network element device so that the target user plane functional network element device sends the uplink data corresponding to the public network virtual LAN to the public network.

6. The method for uplink data control according to claim 5, wherein: The method further comprises: Sending charging policies to user plane functional network element devices; Receiving charging information sent by the user plane functional network element device, the charging information including data traffic and / or connection duration of the terminal and a corresponding usage report rule identifier; Generate a call record according to the gateway information corresponding to the usage report rule identifier and the data traffic and / or connection duration of the terminal; The call record is sent to the billing service platform for billing.

7. The method for uplink data control according to claim 5, wherein: The method further comprises: Acquiring location information of the terminal; When the terminal moves to a preset designated range of the internal network, a diversion rule is sent to a target user plane functional network element device so that the target user plane functional network element device can send the uplink data generated by the terminal to the internal network.

8. An uplink data control device, comprising: A receiving module, used for receiving uplink data sent by the terminal; A processing module, used to determine a data network access identifier corresponding to the uplink data according to a preset diversion rule; A determination module, configured to determine, based on the data network access identifier, the virtual local area network corresponding to the uplink data; A sending module, configured to send the uplink data to a public network or a public network user plane function network element device through the public network virtual local area network when the uplink data corresponds to a public network virtual local area network; The sending module is further used to send the uplink data to the internal network through the local virtual local area network when the uplink data corresponds to the local virtual local area network.

9. A device for uplink data control, comprising: a processor, and a memory storing computer program instructions; The processor reads and executes the computer program instructions to implement the method for uplink data control as described in any one of claims 1-7.

10. A computer-readable storage medium having computer program instructions stored thereon, wherein the computer program instructions, when executed by a processor, implement the method for uplink data control according to any one of claims 1 to 7.

Images