Message transmission method and device, related equipment and storage medium

Abstract

The invention discloses a message transmission method and device, a base station, core network equipment and a storage medium. The method comprises the following steps: a base station receives a data packet; a first message is generated by using the received data packet, the first message comprises first information and user information, and the first information is used for uniquely identifying a first radio remote unit (RRU) of the base station; and sending the first message.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to a method and apparatus for packet transmission, related devices, and a storage medium. Background Art

[0002] Deploying a femtocell indoors can not only enhance the indoor signal coverage of the home, ensure the network quality of home users, but also improve the network quality of surrounding non-home users. To attract more users to deploy femtocells, a reward policy can be set; specifically, rewards are provided to the users of the femtocell according to the traffic of non-home users absorbed by a femtocell.

[0003] However, how to implement the statistics of the traffic of non-home users absorbed by a femtocell is an urgent problem to be solved currently. Summary of the Invention

[0004] To solve the related technical problems, embodiments of this application provide a method and apparatus for packet transmission, a base station, a core network device, and a storage medium.

[0005] The technical solution of the embodiments of this application is implemented as follows:

[0006] Embodiments of this application provide a method for packet transmission, which is applied to a base station and includes:

[0007] Receiving a data packet;

[0008] Generating a first packet using the received data packet, where the first packet includes first information and user information, and the first information is used to uniquely identify a first remote radio unit (RRU) of the base station;

[0009] Sending out the first packet.

[0010] In the above solution, the first information includes:

[0011] Second information, where the second information includes device information of the first RRU;

[0012] Third information, where the third information is used to identify the cell corresponding to the base station.

[0013] In the above solution, the first information is set in the header of the first packet.

[0014] Embodiments of this application also provide a method for packet transmission, which is applied to a core network device and includes:

[0015] Receiving a first packet, where the first packet includes first information and user information, and the first information is used to uniquely identify a first RRU of a base station;

[0016] Using the user information included in the first message, determine that the user account corresponding to the first message is the first type of account corresponding to the first RRU;

[0017] Account the traffic generated by the first message to the second type of account corresponding to the first RRU.

[0018] In the above solution, the first information includes:

[0019] Second information, where the second information includes the device information of the RRU;

[0020] Third information, where the third information is used to identify the cell corresponding to the base station.

[0021] In the above solution, the first information is set in the message header of the first message.

[0022] In the above solution, the method further includes:

[0023] Using the first information and the fourth information, determine the second type of account corresponding to the first RRU, where the fourth information includes the user account information corresponding to at least one RRU, and the user account information corresponding to each RRU is at least associated with the second type of account corresponding to the RRU.

[0024] In the above solution, the method further includes:

[0025] For each RRU, generate the user account information corresponding to the RRU by using the information uniquely identifying the RRU and the primary user information included in the message associated with the RRU;

[0026] Using the user account information corresponding to each RRU, determine the fourth information.

[0027] In the above solution, the method further includes:

[0028] For each RRU, receive the registration information sent by the first user account associated with the RRU, where the registration information includes at least one user information associated with the RRU;

[0029] Using the received registration information, determine at least one first type of account corresponding to the RRU.

[0030] An embodiment of the present application further provides a message transmission device, including:

[0031] A first receiving unit, configured to receive a data packet;

[0032] A generating unit, configured to generate a first message by using the received data packet, where the first message includes first information and user information, and the first information is used to uniquely identify the first RRU of the base station;

[0033] A sending unit, configured to send the first message.

[0034] An embodiment of the present application further provides a message transmission device, including:

[0035] A second receiving unit, configured to receive a first message, where the first message includes first information and user information, and the first information is used to uniquely identify a first RRU of a base station;

[0036] A determining unit, configured to use the user information included in the first message to determine that the user account corresponding to the first message is a first type of account corresponding to the first RRU;

[0037] A statistical unit, configured to count the traffic generated by the first message into a second type of account corresponding to the first RRU.

[0038] An embodiment of the present application further provides a base station, including:

[0039] A first communication interface, configured to receive a data packet; send a first message;

[0040] A first processor, configured to generate the first message by using the received data packet, where the first message includes first information and user information, and the first information is used to uniquely identify the first RRU of the base station.

[0041] An embodiment of the present application further provides a core network device, including:

[0042] A second communication interface, configured to receive a first message, where the first message includes first information and user information, and the first information is used to uniquely identify a first RRU of a base station;

[0043] A second processor, configured to use the user information included in the first message to determine that the user account corresponding to the first message is a first type of account corresponding to the first RRU; and count the traffic generated by the first message into a second type of account corresponding to the first RRU.

[0044] An embodiment of the present application further provides a base station, including: a first processor and a first memory for storing a computer program capable of running on the processor,

[0045] wherein, when the first processor is configured to run the computer program, it executes the steps of any of the above methods on the base station side.

[0046] An embodiment of the present application further provides a core network device, including: a second processor and a second memory for storing a computer program capable of running on the processor,

[0047] Wherein, when the second processor is used to run the computer program, it executes the steps of any of the above methods on the core network device side.

[0048] An embodiment of the present application further provides a storage medium, on which a computer program is stored. When the computer program is executed by a processor, it implements the steps of any of the above methods on the base station side, or implements the steps of any of the above methods on the core network device side.

[0049] For the packet transmission method, device, related equipment, and storage medium provided by the embodiments of the present application, the base station receives a data packet; generates a first packet using the received data packet, where the first packet includes first information and user information, and the first information is used to uniquely identify the first RRU of the base station; sends out the first packet; the core network device receives the first packet, and uses the user information included in the first packet to determine that the user account corresponding to the first packet is the first type of account corresponding to the first RRU; and records the traffic generated by the first packet into the second type of account corresponding to the first RRU. In the solution provided by the embodiments of the present application, the base station adds user information and the identification information of the RRU of the base station to the packet sent to the core network device, so that the core network device can use the user information in the received packet to determine whether the user account of the first packet is the first type of account (which can also be understood as an account of a non-family user). When the user account corresponding to the packet is the first type of account, the core network device can record the traffic generated by the packet into the corresponding second type of account (which can also be understood as the main user account of the RRU corresponding to the packet). In this way, the core network can determine the traffic of non-family users absorbed by each RRU according to the traffic statistics of each second type of account, and then implement a reward policy for the corresponding second type of account according to the absorbed traffic value. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1 It is a schematic structural diagram of an extended home base station;

[0051] Figure 2 It is a schematic flowchart of a packet transmission method according to an embodiment of the present application;

[0052] Figure 3 It is a schematic flowchart of another packet transmission method according to an embodiment of the present application;

[0053] Figure 4 It is a schematic data structure diagram of user account information according to an embodiment of the present application;

[0054] Figure 5 It is a schematic flowchart of the core network device for traffic statistics according to an embodiment of the present application;

[0055] Figure 6Schematic flowchart of a core network device for traffic statistics of packets sent by a femtocell in an application example of this application;

[0056] Figure 7 Schematic structural diagram of a packet transmission device according to an embodiment of this application;

[0057] Figure 8 Schematic structural diagram of another packet transmission device according to an embodiment of this application;

[0058] Figure 9 Schematic structural diagram of a base station according to an embodiment of this application;

[0059] Figure 10 Schematic structural diagram of a core network device according to an embodiment of this application;

[0060] Figure 11 Schematic structural diagram of a packet transmission system according to an embodiment of this application. Detailed implementation manners

[0061] The present application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0062] Deploying a fifth-generation mobile communication technology (5G) femtocell (also referred to as a home small cell or home base station) indoors can not only enhance the indoor 5G signal coverage of this home, but also improve the 5G network quality of surrounding homes.

[0063] In actual application, the femtocell can be deployed in an extended architecture, such as Figure 1 As shown, the femtocell with an extended architecture (or referred to as an extended femtocell) includes: an indoor baseband processing unit (BBU, Building Baseband Unit) and at least one RRU deployed in different homes. The BBU and the RRU are connected through an optical link terminal (OLT, Optical Link Terminal) and at least one optical network unit (ONU, Optical Network Unit) deployed in different homes. The OLT and multiple ONUs are connected through a passive optical splitter. Among them, in the femtocell with an extended architecture, the wireless devices connected to the RRU in this home include the wireless devices of the users in this home and the wireless devices of non-users in this home. The RRU and the wired devices (such as routers) of the users in this home are connected to the ONU in this home. The ONUs in multiple homes are connected to the OLT through a passive optical splitter. The OLT is connected to the BBU, and the BBU is connected to the core network. In this way, the packets generated by the wireless devices of non-users in this home can pass through the RRU in this home, the ONU in this home, the OLT, and the BBU in sequence, and finally be transmitted to the core network.

[0064] To attract more users to deploy home base stations, a reward policy can be set. Specifically, according to the traffic of non-home users absorbed by a home base station (which can also be understood as the traffic corresponding to the packets transmitted by non-home users through the RRU in this home), rewards are provided to the users of the home base station (i.e., this home's users).

[0065] In the related art, when the core network counts user traffic, it identifies the user information of the packets and monitors, counts, and classifies the data in the packets to achieve traffic statistics, and finally records each user information and the corresponding traffic.

[0066] However, the current traffic statistics solution only records user information and traffic counts, and cannot count the traffic of non-home users attracted by home base stations (referred to as base stations in the following description), making it difficult to implement the reward policy.

[0067] Based on this, in various embodiments of the present application, the base station adds user information and the identification information of the RRU of the base station to the packets sent to the core network device, enabling the core network device to use the user information in the received packets to determine whether the user account of the first packet is a first type of account (which can also be understood as the account of a non-home user or a non-whitelist account). When the user account corresponding to the packet is a first type of account, the core network device can count the traffic generated by the packet into the corresponding second type of account (which can also be understood as the main user account of the RRU corresponding to the packet). In this way, the core network can determine the traffic of non-home users absorbed by each RRU according to the traffic counted for each second type of account, and then implement the reward policy for the corresponding second type of account according to the absorbed traffic value.

[0068] An embodiment of the present application provides a packet transmission method, which is applied to a base station, as Figure 2 shown, the method includes:

[0069] Step 201: Receive a data packet;

[0070] Step 202: Generate a first packet using the received data packet, where the first packet includes first information and user information, and the first information is used to uniquely identify the first RRU of the base station;

[0071] Step 203: Send out the first packet.

[0072] Here, in actual application, the base station can be referred to as a home base station, such as a gNB; specifically, it can be any base station using an extended architecture and including at least one RRU, and the specific implementation of the base station in the embodiments of the present application is not limited.

[0073] In actual application, a cell may contain multiple Remote Radio Units (RRUs). To count the traffic generated by non-household users absorbed by each RRU, the household users (also referred to as in-house users) and non-household users (also referred to as absorbed users or sharing users) can be distinguished by setting up a whitelist.

[0074] Specifically, for each RRU, the device of the primary user account associated with the RRU can send registration information (which can also be understood as whitelist registration) to the core network device. The registration information contains whitelist user information. Correspondingly, the core network device can generate a whitelist corresponding to the RRU by using the registration information sent by the device of the primary user account, and then can determine whether the user corresponding to each packet is a household user (which can also be understood as a whitelist user) or a non-household user (which can also be understood as a non-whitelist user) according to the whitelist. Here, the whitelist includes the user information of all whitelist users associated with the RRU. Among them, the device of the primary user account can send the registration information to the core network device through the base station.

[0075] That is to say, in one embodiment, the method may further include:

[0076] For each RRU, receive the registration information sent by the first user account associated with the RRU, where the registration information contains at least one user information associated with the RRU;

[0077] Send the registration information.

[0078] Here, in actual application, the first user account may specifically be the primary user account, and may also be referred to as the main account, user primary account, etc. The embodiments of the present application do not make any limitations in this regard.

[0079] In actual application, the at least one user information associated with the RRU may specifically include the mobile phone numbers of the whitelist users associated with the RRU, or may be any user information that can be used to identify the whitelist users. The embodiments of the present application do not make any limitations on the specific implementation of the user information.

[0080] In actual application, the specific implementation of the registration information may include a short message in a preset format, or may be any other information format that can be recognized by the core network device. The embodiments of the present application do not make any limitations on the specific implementation of the registration information.

[0081] It should be noted that after the first user account sends registration information to the core network device, the device of the first user account may first send a message to the core network device through this RRU, so that the core network device can determine the association relationship between this RRU and the first user account, that is, based on the information uniquely identifying the RRU contained in the message corresponding to the first user account, determine which RRU the registration information sent by the device of the first user account corresponds to.

[0082] In practical applications, when the base station executes the message transmission function after booting up, the first RRU receives the data packet sent by the terminal. After the first RRU receives the data packet sent by the terminal, it transfers the received data packet to the BBU of the base station, and the BBU performs transmission-related processing on the data packet at the data link layer (also known as layer 2 (L2, Layer 2)) and the network layer (also known as layer 3 (L3, Layer 3)) to generate a first message and send the first message; wherein, the message header of the first message is scalable and can carry content other than the data content.

[0083] Based on this, in an embodiment, the first information is set in the message header of the first message.

[0084] Here, in practical applications, a cell may include multiple RRUs. In order to be able to uniquely identify the RRU corresponding to the first message through the first information, for each cell, different RRUs can be distinguished by the RRU identifier (such as the device information of the RRU). However, different cells can use the same RRU identifier to identify the RRUs within their respective cells, that is, there is a situation of RRU identifier reuse. Exemplarily, for cell 1 and cell 2, cell 1 includes 2 RRUs, which are identified by {RRU_1, RRU_2}, and cell 2 includes 3 RRUs, which are identified by {RRU_1, RRU_2, RRU_3}; when the data packet corresponding to the first message is received by RRU_1 in cell 1, it is necessary to combine the cell identifier (such as {cell 1, RRU_1}) to uniquely identify the RRU corresponding to the first message.

[0085] Based on this, in an embodiment, the first information may include:

[0086] Second information, the second information includes the device information of the first RRU; Exemplarily, the second information may include the device number of the first RRU (such as the RRU ID of the first device);

[0087] Third information, the third information is used to identify the cell corresponding to the base station; Exemplarily, the third information may include a cell identifier (such as a cell ID (which can be expressed in English as Cell local ID)) and a base station identifier (such as a base station ID).

[0088] Exemplarily, after the BBU of the base station performs L2 and L3 transmission-related processing on the data packet, a General Packet Radio Service Tunneling Protocol (GTP) message (i.e., the first message) is generated. As shown in Table 1, a new type of extended header (which can also be referred to as a new extended packet header) can be added to the message header of the generated GTP message, and the first information is set in the new extended packet header.

[0089]

[0090] Table 1

[0091] The new extended packet header includes: a NextExtensionHeaderType field and an ExtensionHeaderLength field. Through the gNB ID, Cell local ID, and RRU_ID information, the RRU (i.e., the first RRU) corresponding to the GTP message can be uniquely identified.

[0092] In actual application, in step 203, the base station may send the first message to the core network device through the N3 interface. The specific sending method of the first message in the embodiments of the present application is not limited.

[0093] Correspondingly, the embodiments of the present application also provide a message transmission method applied to a core network device. As Figure 3 shown, the method includes:

[0094] Step 301: Receive a first message, where the first message includes first information and user information, and the first information is used to uniquely identify the first RRU of the base station;

[0095] Step 302: Use the user information included in the first message to determine that the user account corresponding to the first message is the first type of account corresponding to the first RRU;

[0096] Step 303: Account the traffic generated by the first message into the second type of account corresponding to the first RRU.

[0097] Here, in actual application, the first type of account may specifically be a non-household user account (which can also be understood as a non-whitelist user account), and the second type of account may specifically be the main user account. For an RRU, the core network device can count the traffic generated by the first type of account corresponding to the RRU into the second type of account corresponding to the RRU, so as to realize the statistics of the traffic generated by non-household users through the RRU (which can also be understood as absorbing traffic), and then can provide rewards for the second type of account corresponding to the RRU according to the counted traffic.

[0098] In actual application, the user plane function (UPF) in the core network can receive the first message, and then transfer the first message to the policy control function (PCF) in the core network. The PCF executes steps 302 to 303 to complete the traffic statistics. Of course, the above steps can also be executed by other functions in the core network. The embodiments of the present application do not limit this.

[0099] In actual application, before the core network device executes step 302, it is necessary to determine the first type of account corresponding to each RRU, so that after receiving the first message, it determines the first RRU according to the first information in the first message, and then uses the user information included in the first message to determine whether the corresponding user account is the first type of account corresponding to the first RRU.

[0100] Based on this, in an embodiment, the method may further include:

[0101] For each RRU, receive the registration information sent by the first user account associated with the RRU, where the registration information includes at least one user information associated with the RRU;

[0102] Use the received registration information to determine the first type of account corresponding to the RRU.

[0103] Here, in actual application, the first user account may specifically be the main user account (i.e., the second type of account), and can also be called the main account, user main account, etc. The embodiments of the present application do not limit this.

[0104] In actual application, the core network device can use the received registration information to determine the user accounts corresponding to at least one user information included in the registration information as user accounts that do not need to be traffic - counted (which can also be understood as whitelist accounts or home accounts of this family). This process can also be referred to as generating the whitelist corresponding to the RRU. In this way, the core network device can determine all user accounts that are not related to the registration information (i.e., non - whitelist accounts or non - home accounts of this family) as the first - type accounts that need to be traffic - counted. Furthermore, when receiving the first message, it can be determined whether the user account corresponding to the first message is a first - type account for the RRU corresponding to the first message.

[0105] In actual application, when the home users corresponding to the RRU change, the device of the first user account associated with the RRU can also send updated registration information to the core network device. Correspondingly, the core network device can use the updated registration information to update the user accounts that do not need to be traffic - counted corresponding to the RRU (which can also be understood as updating the whitelist), so as to update the first - type accounts corresponding to the RRU.

[0106] When transmitting messages using the RRU, the device of the first user account can first send a message to the core network device through the RRU, so that the core network device can determine the association relationship between the RRU and the first user account, that is, based on the information uniquely identifying the RRU included in the message corresponding to the first user account, determine which RRU the registration information sent by the device of the first user account corresponds to.

[0107] In actual application, the core network device determines the corresponding first - type accounts for each RRU, that is, the first - type accounts are associated with the RRU. The first - type accounts can be specifically characterized by all whitelist accounts under the corresponding RRU. That is, all user accounts that do not belong to the whitelist accounts are first - type accounts. Among them, the whitelist accounts are related to the registration information, and the whitelist accounts at least include the primary user account (i.e., the second - type account). In this case, in step 302, it is determined that the user account corresponding to the first message is the first - type account corresponding to the first RRU by the whitelist method, which can also be understood as determining that the user corresponding to the first message does not belong to the whitelist users corresponding to the first RRU.

[0108] In actual application, in step 303, the traffic generated by the first message is counted into the second - type account corresponding to the first RRU. The second - type account can also be understood as the primary user account for traffic - counting corresponding to the first message.

[0109] In practical applications, in order to implement accounting the traffic generated by the packets of the first type of account under the second type of account corresponding to the corresponding RRU, the core network device also needs to determine, for each received packet (i.e., the first packet), which RRU (i.e., the first RRU) the packet corresponds to, and determine whether the user account corresponding to the packet is the first type of account corresponding to the RRU (i.e., the first RRU). When the user account corresponding to the packet is the first type of account corresponding to the RRU, before accounting the traffic generated by the packet under the second type of account corresponding to the RRU, it is necessary to first determine the second type of account corresponding to the RRU.

[0110] In practical applications, since the RRU and the second type of account are in one-to-one correspondence, the core network device can establish a correspondence relationship between the RRU and the second type of account. In this way, the core network device only needs to use the first information included in the received packet (i.e., the first packet) to determine the RRU (i.e., the first RRU) corresponding to the packet, and then can uniquely determine the second type of account corresponding to the packet by using the correspondence relationship between the determined RRU and the second type of account.

[0111] Based on this, in one embodiment, the method may further include:

[0112] Using the first information and the fourth information to determine the second type of account corresponding to the first RRU, where the fourth information includes user account information corresponding to at least one RRU, and the user account information corresponding to each RRU is at least associated with the second type of account corresponding to the RRU.

[0113] In practical applications, the fourth information represents the correspondence relationship between each RRU and the user account information for packet transmission using the RRU. Among them, the user account information for packet transmission using the RRU at least includes the user account information of the second type of account corresponding to the RRU. That is to say, the fourth information represents the correspondence relationship between the RRU and the second type of account.

[0114] Exemplarily, as shown in Table 2, the user account information may specifically include the following data: gNB_ID, Cell_ID, RRU_ID, UE_ID, Type, where gNB_ID represents the base station identifier, Cell_ID represents the cell identifier, RRU_ID represents the device number of the RRU, and a RRU can be uniquely identified by the gNB_ID, Cell_ID, and RRU_ID; UE_ID represents user information, and Type represents the user account type. Among them, the second type of account (which can also be understood as the main user account) may correspond to a value of "1" for Type, and the non-second type of account (which can also be understood as the non-main user account) may correspond to a value of "0" for Type.

[0115] gNB_ID Cell_ID RRU_ID UE_ID TYPE

[0116] Table 2

[0117] In actual application, the core network device can record the user information in the packets associated with each RRU, and then generate the user account information corresponding to the RRU.

[0118] Specifically, in one embodiment, the method may further include:

[0119] For each RRU, use the information uniquely identifying the RRU and the user information included in the packet associated with the RRU to generate the user account information corresponding to the RRU;

[0120] Use the user account information corresponding to each RRU to determine the fourth information.

[0121] As Figure 4 shown, the user account information of one RRU corresponds to at least one user account (specifically, it can be represented by UE_ID), and the gNB_ID, Cell_ID, and RRU_ID corresponding to each user account in the user account information are the same. At the same time, for one RRU, it can be determined that the second type of account for traffic statistics corresponding to the RRU will definitely transmit packets through the RRU. That is to say, the user account information corresponding to each RRU generated at least includes the user account information of the second type of account corresponding to the RRU (that is, Figure 4 the user account information with TYPE value of 1 in

[0122] In actual application, when the core network device generates the user account information corresponding to each RRU, it can determine the second type of account corresponding to the RRU through the registration information corresponding to the RRU, that is, determine the value of TYPE.

[0123] Specifically, the device of the first user account that sends the registration information can first send a packet to the core network device through the RRU, so that the core network device can determine the second type of account corresponding to the RRU, that is, based on the information uniquely identifying the RRU included in the packet corresponding to the first user account, determine the RRU corresponding to the registration information, and use the first user account as the second type of account corresponding to the RRU.

[0124] In actual application, after the core network device receives a packet associated with an RRU, it can use the user information contained in the packet to determine the user information corresponding to the packet (i.e., UE_ID); use the information capable of identifying the RRU contained in the packet to determine the RRU corresponding to the packet (i.e., gNB_ID, Cell_ID, RRU_ID); use the identification information carried in the packet and / or the registration information corresponding to the RRU to determine whether the user account corresponding to the packet is a second type of account (i.e., TYPE), so as to generate the user account information corresponding to the packet. The specific implementation may include: when the determined combination of (gNB_ID, Cell_ID, RRU_ID, UE_ID, Type) is not recorded under the RRU, record (which can also be understood as storing or updating) the determined combination of (gNB_ID, Cell_ID, RRU_ID, UE_ID, Type) in the user account information under the RRU.

[0125] In actual application, after the core network device determines the fourth information, when receiving the first packet, it can determine the first information and user information corresponding to the first packet, use the first information to determine the first RRU, and determine the user account information corresponding to the first RRU in the fourth information, and then use the user account information corresponding to the first RRU to determine the second type of account corresponding to the first RRU.

[0126] In actual application, after step 303, the core network device can also determine the reward for each second type of account according to the traffic under each second type of account statistically counted within a preset time period, in combination with the reward policy, to implement the reward policy. The preset time period may be a reward cycle set according to a specific reward policy, such as one month, one quarter, etc., and the embodiments of the present application do not limit this.

[0127] The embodiments of the present application also provide a packet transmission method, as Figure 5 shown, this method includes:

[0128] Step 501: The base station receives a data packet;

[0129] Step 502: The base station generates a first packet using the received data packet. The first packet contains first information and user information, and the first information is used to uniquely identify the first RRU of the base station;

[0130] Step 503: The base station sends out the first packet;

[0131] Step 504: The core network device receives the first packet;

[0132] Step 505: The core network device determines that the user account corresponding to the first message is the first type of account corresponding to the first RRU by using the user information included in the first message;

[0133] Step 506: The core network device accounts the traffic generated by the first message into the second type of account corresponding to the first RRU.

[0134] Here, it should be noted that: The specific processing procedures of the base station and the core network device have been described in detail above, and will not be elaborated here.

[0135] In the message transmission method provided by the embodiment of the present application, the base station receives a data packet; generates a first message by using the received data packet, where the first message includes first information and user information, and the first information is used to uniquely identify the first RRU of the base station; sends out the first message; the core network device receives the first message, and determines that the user account corresponding to the first message is the first type of account corresponding to the first RRU by using the user information included in the first message; accounts the traffic generated by the first message into the second type of account corresponding to the first RRU. In the solution provided by the embodiment of the present application, the base station adds user information and the identification information of the RRU of the base station to the message sent to the core network device, so that the core network device can use the user information in the received message to determine whether the user account of the first message is the first type of account (which can also be understood as an account of a non-family user). When the user account corresponding to the message is the first type of account, the core network device can account the traffic generated by the message into the corresponding second type of account (which can also be understood as the main user account of the RRU corresponding to the message). In this way, the core network can determine the traffic of non-family users absorbed by each RRU according to the traffic statistics of each second type of account, and then implement a reward policy for the corresponding second type of account according to the absorbed traffic value.

[0136] The following further describes the present application in detail with application examples.

[0137] As Figure 6 shown, in this application example, the process of the core network device performing traffic statistics on the messages sent by the home base station includes the following steps:

[0138] Step 601: The core network device registers a whitelist for each RRU;

[0139] Specifically, the core network device receives the registration information sent by the main user account of each RRU, where the registration information includes the user information of the home user (i.e., the whitelist user); the core network device can generate a corresponding whitelist for each RRU by using the received registration information.

[0140] Exemplarily, the main user account can send a text message in a special format to the core network device to achieve the white list registration of all home users. The content of the text message can include the mobile phone numbers of all home users (i.e., home user information).

[0141] Here, it should be noted that the core network device can set the user account that sends the registration information as the main user account, and the white list contains at least the main user account. The main user account can be the user account of the user who handles the home base station service among the home users, and / or the user account targeted by the reward policy.

[0142] In actual application, the core network device generates a corresponding white list for each RRU, that is, the white list is associated with the RRU. The white list can contain the user information (such as UE ID) of all white list users under the corresponding RRU. Among them, the user information contains at least the user information corresponding to the main user account (which can also be called the main user information). At the same time, the white list also contains the user account types (TYPE) of all white list users, and the user account types can include the main user account and non-main user accounts.

[0143] In actual application, the user accounts in the white list (i.e., the user accounts of home users) and the non-white list user accounts (i.e., the user accounts of non-home users) within the coverage area of the home base station can both achieve 5G network connection through the home base station deployed in this home. Among them, the non-white list user accounts do not identify the specific home base station providing 5G network services (that is, do not perform white list registration) and are unaware of the home base station providing 5G network services.

[0144] In actual application, when the home users corresponding to the RRU change, the main user account associated with the RRU can send updated registration information to the core network device, and the core network device can use the updated registration information to update the white list of the RRU.

[0145] Step 602: The core network device establishes user account information for each RRU;

[0146] In actual application, in order to achieve accounting for the traffic generated by non-white list users (i.e., the above first type of accounts) under the main user account (i.e., the above second type of accounts) corresponding to the RRU, the core network device also needs to determine whether the user of the received packet belongs to a white list user for each received packet, and then determine the main user account corresponding to the packet for the packets that do not belong to white list users.

[0147] Since one RRU corresponds to only one primary user account, a corresponding relationship can be established between the RRU and the primary user account, enabling the core network device to uniquely determine the primary user account corresponding to the message by using the determined RRU and the corresponding relationship based on only the message received to determine the RRU corresponding to the message.

[0148] Meanwhile, the core network device may not be able to directly obtain the corresponding relationship between the registration information and the RRU from the registration information sent by the primary user account, and thus may not be able to determine which RRU the whitelist generated using the registration information corresponds to.

[0149] To be able to determine which specific RRU the generated whitelist corresponds to, the core network device can establish a corresponding relationship between each generated whitelist and the RRU. In this way, after determining the RRU corresponding to the first message, the core network device can use the corresponding relationship between the whitelist and the RRU to determine the whitelist corresponding to the first message.

[0150] In practical applications, the core network device can generate user account information for each RRU and use the user account information to determine the corresponding relationship between the RRU and the primary user account and the corresponding relationship between the whitelist and the RRU.

[0151] Specifically, the core network device can receive the message sent by the primary user account. The message sent by the primary user account contains the identification information of the RRU (specifically including gNB_ID, Cell_ID, RRU_ID) and the primary user information (specifically including UE_ID), and generate user account information using the identification information of the RRU and the primary user information.

[0152] Exemplarily, before performing traffic statistics for each RRU, the core network device first determines whether the user sending the message is a primary account user (specifically, it can include determining whether the UE_ID is the UE_ID corresponding to the whitelist). When the user sending the message is a primary account user, record the gNB_ID, Cell_ID, and RRU_ID in the message. Use the recorded gNB_ID, Cell_ID, and RRU_ID and the UE_ID and TYPE included in the whitelist to establish the user account information for each RRU as shown in Figure 4 the following.

[0153] Step 603: The femto base station adds user information and the identification information of the RRU of the femto base station (i.e., the above-mentioned first information) to the message (i.e., the above-mentioned first message) sent to the core network device;

[0154] In actual application, the home base station receives data packets, generates a message using the received data packets, adds user information and the identification information of the RRU of the home base station to the message, and sends the message to the core network device.

[0155] Exemplarily, an RRU in the home base station receives a data packet containing user data sent by a user, and transfers the RRU_ID for identifying the RRU and the data packet to the BBU side in the home base station. After performing relevant L2 and L3 processing on the data packet, when generating a GTP message, an extended packet header (i.e., the identification information of the RRU) is added to the message header of the GTP message. The RRU_ID (i.e., the above-mentioned second information) is included in the extended packet header. At the same time, the Cell_ID for identifying the cell (i.e., the above-mentioned third information) and the gNB_ID for identifying the home base station are added. The RRU can be uniquely identified by the RRU_ID, Cell_ID, and gNB_ID. At the same time, the UE_ID (such as the mobile phone number of the user sending the access information) is also included in the GTP message. After generating the GTP message, the home base station sends the GTP message to the core network device through the N3 interface.

[0156] Step 604: The core network device receives the message sent by the home base station, and uses the whitelist to determine whether the user of the message is a whitelist user.

[0157] In actual application, the core network device can use the user information included in the message to determine whether the user of the message belongs to or does not belong to the whitelist user.

[0158] Specifically, the core network device can match the user information included in the message in the whitelist. When there is no matching item, it is determined that the user of the message does not belong to the whitelist user; when there is a matching item, it is determined that the user of the message belongs to the whitelist user.

[0159] In actual application, when it is determined that the user of the message belongs to the whitelist user, that is, the user of the message is a home user. At this time, the message does not belong to the object of traffic statistics, and the core network device does not perform subsequent steps; when it is determined that the user of the first message does not belong to the whitelist user, that is, the user of the first message is a non-home user, the core network device can count the traffic generated by the message into the main user account associated with the RRU corresponding to the message, so as to realize the statistics of the traffic of non-home users.

[0160] Step 605: When the user of the message does not belong to the whitelist user, the core network device uses the message and the user account information to determine the main user account for traffic statistics corresponding to the message.

[0161] When the user of the message belongs to a whitelist user, the core network device does not process the message;

[0162] Specifically, the core network device can use the identification information of the RRU of the femtocell included in the message, combined with the user account information, to determine the main user account for traffic statistics corresponding to the message, and the user account information includes the corresponding relationship between the RRU and the main user account.

[0163] In practical applications, the UPF in the core network device can receive the message sent by the femtocell and transfer the message sent by the femtocell to the PCF in the core network, and the PCF executes steps 604-605 to complete the traffic statistics.

[0164] Step 606: The core network device records the traffic generated by the message into the main user account for traffic statistics corresponding to the message.

[0165] In the application example of this application, the femtocell adds user information and the identification information of the RRU of the femtocell to the message sent to the core network device, so that the core network device can use the user information in the received message to determine whether the user of the first message belongs to a whitelist user. When the user corresponding to the message does not belong to a whitelist user, the core network device can determine the main user account information of the RRU corresponding to the message according to the information in the message and the user account information under the RRU, and record the traffic generated by the message into the corresponding main user account. In this way, the core network can realize the statistics of the traffic of non-home users (i.e., non-whitelist users) absorbed by each RRU according to the traffic corresponding to each RRU main user account, so as to implement an incentive policy for the corresponding main user account according to the statistical traffic value.

[0166] To implement the solution on the base station side in the embodiments of this application, the embodiments of this application also provide a message transmission device, as Figure 7 shown, set on the base station, including:

[0167] A first receiving unit 701, configured to receive a data packet;

[0168] A generating unit 702, configured to generate a first message by using the received data packet, where the first message includes first information and user information, and the first information is used to uniquely identify the first RRU of the base station;

[0169] A sending unit 703, configured to send out the first message.

[0170] Wherein, in one embodiment, the generating unit 702 is further configured to set the first information in the message header of the first message.

[0171] Here, it should be noted that the function of the first receiving unit 701 is equivalent to the function of the RRU in the base station in the application example; the functions of the generating unit 702 and the transmitting unit 703 are equivalent to the functions of the BBU in the base station in the application example.

[0172] In actual application, the first receiving unit 701 and the transmitting unit 703 can be implemented by the communication interface in the message transmission device; the generating unit 702 can be implemented by the processor in the message transmission device.

[0173] To implement the solution on the core network device side in the embodiments of the present application, the embodiments of the present application further provide a message transmission device, which is disposed on the core network device, as Figure 8 shown, including:

[0174] A second receiving unit 801, configured to receive a first message, where the first message includes first information and user information, and the first information is used to uniquely identify a first RRU of a base station;

[0175] A determining unit 802, configured to use the user information included in the first message to determine that the user account corresponding to the first message is the first type of account corresponding to the first RRU;

[0176] A statistical unit 803, configured to count the traffic generated by the first message into the second type of account corresponding to the first RRU.

[0177] Wherein, in one embodiment, the determining unit 802 is further configured to:

[0178] Use the first information and the fourth information to determine the second type of account corresponding to the first RRU, where the fourth information includes user account information corresponding to at least one RRU, and the user account information corresponding to each RRU is at least associated with the second type of account corresponding to the RRU.

[0179] In one embodiment, the message transmission device further includes:

[0180] A generating unit, configured to, for each RRU, use the information uniquely identifying the RRU and the user information included in the message associated with the RRU to generate user account information corresponding to the RRU;

[0181] The determining unit 802 is configured to use the user account information corresponding to each RRU to determine the fourth information.

[0182] In one embodiment, the determining unit 802 is further configured to:

[0183] For each RRU, receive the registration information sent by the first user account associated with the RRU, where the registration information includes at least one user information associated with the RRU; use the received registration information to determine the first type of account corresponding to the RRU.

[0184] In practical applications, the determining unit 802, the statistical unit 803, and the generating unit can be implemented by a processor in the message transmission device; the second receiving unit 801 can be implemented by a communication interface in the message transmission device.

[0185] It should be noted that: when the message transmission device provided in the above embodiment performs message transmission, only the division of the above program units is used for illustration. In practical applications, the above processing can be allocated to different program units according to needs, that is, the internal structure of the device is divided into different program units to complete all or part of the above-described processing. In addition, the message transmission device provided in the above embodiment and the embodiment of the message transmission method belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.

[0186] Based on the hardware implementation of the above program modules, and in order to implement the method on the base station side of the embodiments of the present application, the embodiments of the present application further provide a base station, as Figure 9 shown, the base station 900 includes:

[0187] A first communication interface 901 capable of performing information interaction with a core network device;

[0188] A first processor 902, connected to the first communication interface 901 to implement information interaction with a core network device, and used to execute the method provided by one or more technical solutions on the base station side when running a computer program; the computer program is stored on a first memory 903.

[0189] Specifically, the first communication interface 901 is used to receive data packets;

[0190] The first processor 902 is used to generate a first message using the received data packet, where the first message includes first information and user information, and the first information is used to uniquely identify the first RRU of the base station;

[0191] The first communication interface 901 is further used to send out the first message.

[0192] Wherein, in one embodiment, the first processor 902 is further used to set the first information in the message header of the first message.

[0193] It should be noted that: the specific processing processes of the first processor 902 and the first communication interface 901 can be understood with reference to the above method.

[0194] Of course, in practical applications, each component in the base station 900 is coupled together through the bus system 904. It can be understood that the bus system 904 is used to implement the connection and communication between these components. In addition to the data bus, the bus system 904 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clear illustration, in Figure 10 the various buses are all labeled as the bus system 904.

[0195] The first memory 903 in the embodiment of the present application is used to store various types of data to support the operation of the base station 900. Examples of these data include: any computer program for operating on the base station 900.

[0196] The method disclosed in the embodiment of the present application described above can be applied to the first processor 902 or implemented by the first processor 902. The first processor 902 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit in the hardware of the first processor 902 or instructions in software form. The above-mentioned first processor 902 may be a general-purpose processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The first processor 902 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiment of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. Combining the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as being executed and completed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, and this storage medium is located in the first memory 903. The first processor 902 reads the information in the first memory 903 and combines its hardware to complete the steps of the foregoing method.

[0197] In an exemplary embodiment, the base station 900 may be implemented by one or more application specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general purpose processors, controllers, microcontroller units (MCUs), microprocessors, or other electronic components for performing the foregoing methods.

[0198] Based on the hardware implementation of the foregoing program modules and for implementing the method on the core network device side in the embodiments of the present application, the embodiments of the present application further provide a core network device, as Figure 10 shown. The core network device 1000 includes:

[0199] A second communication interface 1001 capable of interacting with the base station for information;

[0200] A second processor 1002 connected to the second communication interface 1001 to implement information interaction with the base station. When running a computer program, the second processor 1002 is used to execute the method provided by one or more technical solutions on the core network device side; the computer program is stored on a second memory 1003.

[0201] Specifically, the second communication interface 1001 is configured to receive a first message, where the first message includes first information and user information, and the first information is used to uniquely identify a first RRU of the base station;

[0202] The second processor 1002 is configured to use the user information included in the first message to determine that the user account corresponding to the first message is a first type of account corresponding to the first RRU;

[0203] Account the traffic generated by the first message into a second type of user account corresponding to the first RRU.

[0204] In an embodiment, the second processor 1002 is further configured to:

[0205] Use the first information and fourth information to determine a second type of account corresponding to the first RRU, where the fourth information includes user account information corresponding to at least one RRU, and the user account information corresponding to each RRU is at least associated with the second type of account corresponding to the RRU.

[0206] In one embodiment, the second processor 1002 is further configured to:

[0207] For each RRU, generate user account information corresponding to the RRU by using the information uniquely identifying the RRU and the user information included in the packet associated with the RRU;

[0208] Determine the fourth information by using the user account information corresponding to each RRU.

[0209] In one embodiment, the second processor 1002 is further configured to:

[0210] For each RRU, receive registration information sent by a first user account associated with the RRU, where the registration information includes at least one user information associated with the RRU;

[0211] Determine a first type of account corresponding to the RRU by using the received registration information.

[0212] It should be noted that: The specific processing procedures of the second processor 1002 and the second communication interface 1001 can be understood with reference to the above method.

[0213] Of course, in actual application, each component in the core network device 1000 is coupled together through the bus system 1004. It can be understood that the bus system 1004 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1004 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clear description, in Figure 11 all kinds of buses are labeled as the bus system 1004.

[0214] The second memory 1003 in the embodiments of the present application is used to store various types of data to support the operation of the core network device 1000. Examples of these data include: any computer program for operating on the core network device 1000.

[0215] The method disclosed in the embodiments of the present application can be applied to or implemented by the second processor 1002. The second processor 1002 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in the second processor 1002 or the instructions in the form of software. The above-mentioned second processor 1002 may be a general-purpose processor, DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The second processor 1002 can implement or execute each method, step, and logic block diagram disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. Combining the steps of the method disclosed in the embodiments of the present application, it can be directly embodied as being executed and completed by the hardware decoding processor, or executed and completed by the combination of the hardware and software modules in the decoding processor. The software module may be located in the storage medium, and this storage medium is located in the second memory 1003. The second processor 1002 reads the information in the second memory 1003 and combines its hardware to complete the steps of the foregoing method.

[0216] In an exemplary embodiment, the core network device 1000 can be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, Microprocessors, or other electronic components for executing the foregoing method.

[0217] It can be understood that the memories (the first memory 903 and the second memory 1003) in the embodiments of the present application can be volatile memories or non-volatile memories, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM, Read Only Memory), a programmable read-only memory (PROM, Programmable Read-Only Memory), an erasable programmable read-only memory (EPROM, Erasable Programmable Read-Only Memory), an electrically erasable programmable read-only memory (EEPROM, Electrically Erasable Programmable Read-Only Memory), a ferromagnetic random access memory (FRAM, ferromagnetic random access memory), a flash memory (Flash Memory), a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM, Compact Disc Read-Only Memory); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM, Random Access Memory), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as a static random access memory (SRAM, Static Random Access Memory), a synchronous static random access memory (SSRAM, Synchronous Static Random Access Memory), a dynamic random access memory (DRAM, Dynamic Random Access Memory), a synchronous dynamic random access memory (SDRAM, Synchronous Dynamic Random Access Memory), a double data rate synchronous dynamic random access memory (DDR SDRAM, Double Data Rate Synchronous Dynamic Random Access Memory), an enhanced synchronous dynamic random access memory (ESDRAM, Enhanced Synchronous Dynamic Random Access Memory), a synchronous link dynamic random access memory (SLDRAM, SyncLink Dynamic Random Access Memory), and a direct rambus random access memory (DRRAM, Direct Rambus Random Access Memory).The memories described in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0218] To implement the method provided by the embodiments of the present application, the embodiments of the present application further provide a message transmission system, as Figure 11 shown, the system includes: a base station 1101 and a core network device 1102.

[0219] Here, it should be noted that: the specific processing procedures of the base station 1101 and the core network device 1102 have been described in detail above and will not be elaborated here.

[0220] In an exemplary embodiment, the embodiments of the present application further provide a storage medium, namely a computer storage medium, specifically a computer-readable storage medium. For example, it includes a first memory 903 storing a computer program, and the above computer program can be executed by a first processor 902 of the base station 900 to complete the steps of the foregoing method on the base station side. Another example is a second memory 1003 storing a computer program, and the above computer program can be executed by a second processor 1002 of the core network device 1000 to complete the steps of the foregoing method on the core network device side. The computer-readable storage medium can be ROM, PROM, EPROM, EEPROM, FRAM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM; the magnetic surface memory can be disk memory or tape memory.

[0221] It should be noted that: "first", "second", etc. are used to distinguish similar objects and do not necessarily need to describe a specific order or sequence.

[0222] In addition, the technical solutions described in the embodiments of the present application can be arbitrarily combined without conflict.

[0223] The above is only a preferred embodiment of the present application and is not used to limit the protection scope of the present application.

Claims

1. A message transmission method, characterized in that, applied to a base station, comprising: Receiving a data packet; Generating a first message using the received data packet, the first message including first information and user information, the first information being used to uniquely identify a first radio remote unit (RRU) of the base station; Sending out the first message.

2. The method according to claim 1, characterized in that, the first information includes: second information, the second information including device information of the first RRU; third information, the third information being used to identify the cell corresponding to the base station.

3. The method according to claim 1 or 2, characterized in that, the first information is set in the message header of the first message.

4. A message transmission method, characterized in that, applied to a core network device, comprising: Receiving a first message, the first message including first information and user information, the first information being used to uniquely identify a first RRU of a base station; Using the user information included in the first message to determine that the user account corresponding to the first message is a first type of account corresponding to the first RRU; Counting the traffic generated by the first message into a second type of account corresponding to the first RRU.

5. The method according to claim 4, characterized in that, the first information includes: second information, the second information including device information of the RRU; third information, the third information being used to identify the cell corresponding to the base station.

6. The method according to claim 4, characterized in that, the first information is set in the message header of the first message.

7. The method according to any one of claims 4 to 6, characterized in that, the method further includes: Using the first information and fourth information to determine a second type of account corresponding to the first RRU, the fourth information including user account information corresponding to at least one RRU, and the user account information corresponding to each RRU being at least associated with the second type of account corresponding to the RRU.

8. The method according to claim 7, characterized in that, the method further includes: For each RRU, generating user account information corresponding to the RRU by using the information uniquely identifying the RRU and user information included in the message associated with the RRU; Using the user account information corresponding to each RRU to determine the fourth information.

9. The method according to any one of claims 4 to 6, characterized in that, the method further includes: For each RRU, receiving registration information sent by a first user account associated with the RRU, the registration information including at least one user information associated with the RRU; Using the received registration information to determine a first type of account corresponding to the RRU.

10. A message transmission device, characterized in that, comprising: A first receiving unit for receiving a data packet; A generating unit for generating a first message by using the received data packet, the first message including first information and user information, the first information being used to uniquely identify a first RRU of a base station; A sending unit for sending out the first message.

11. A message transmission device, characterized in that, comprising: A second receiving unit, configured to receive a first message, where the first message includes first information and user information, and the first information is used to uniquely identify a first RRU of a base station; A determining unit, configured to use the user information included in the first message to determine that the user account corresponding to the first message is a first type of account corresponding to the first RRU; A statistical unit, configured to count the traffic generated by the first message into a second type of account corresponding to the first RRU.

12. A base station, characterized in that, it includes: A first communication interface, configured to receive a data packet; and send out a first message; A first processor, configured to generate the first message by using the received data packet, where the first message includes first information and user information, and the first information is used to uniquely identify the first RRU of the base station.

13. A core network device, characterized in that, it includes: A second communication interface, configured to receive a first message, where the first message includes first information and user information, and the first information is used to uniquely identify a first RRU of a base station; A second processor, configured to use the user information included in the first message to determine that the user account corresponding to the first message is a first type of account corresponding to the first RRU; and count the traffic generated by the first message into a second type of account corresponding to the first RRU.

14. A base station, characterized in that, it includes: A first processor and a first memory for storing a computer program capable of running on the processor, wherein, when the first processor is used to run the computer program, it executes the steps of the method according to any one of claims 1 to 3.

15. A core network device, characterized in that, it includes: A second processor and a second memory for storing a computer program capable of running on the processor, wherein, when the second processor is used to run the computer program, it executes the steps of the method according to any one of claims 4 to 9.

16. A storage medium, on which a computer program is stored, characterized in that, when the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 3, or implements the steps of the method according to any one of claims 4 to 9.

Images