CN112333830B - A business processing method and device - Google Patents

Abstract

The embodiment of the invention discloses a service processing method and equipment, and relates to the technical field of communication. The access problem of public network service and private network service of the same operator can be reasonably solved under the condition that the shared base station has limited resources. The method is applied to the access network equipment for configuring two paths of carriers for each of a plurality of operators. The method comprises the following steps: and determining the network type of each service to be accessed in at least one service to be accessed of the target carrier. And then, determining the priority parameters of the pseudo-access service according to the acquired priority level and RRC data of the pseudo-access service and the RRC data of other pseudo-access services of the same network type under the same carrier as the pseudo-access service in at least one pseudo-access service. And determining to access the target service to the target carrier under the condition that the RRC data of the target service determined in at least one of the to-be-accessed services based on the priority parameter of each to-be-accessed service meets the preset condition for indicating that the target service is the non-superfluous service.

Description

A business processing method and device

Technical Field

The embodiments of the present invention relate to the field of communication technology, and in particular to a service processing method and device.

Background Art

The fifth-generation mobile communication technology (5th-generation, 5G) network provides a variety of slicing modes that can meet the needs of both consumers (customer to customer, 2C) and enterprises (business to business, 2B).

The transceiver equipment (such as access network equipment) in the 5G network is usually a multi-antenna device, such as a 64-bit transmitter and receiver (TR) device, which results in extremely high network construction costs. Therefore, operators began to seek a way for multiple operators to jointly build and share base stations, and use the access network equipment of the jointly built shared base stations to allocate different carriers to different operators. The carriers simultaneously carry the 2B (which can be understood as private network) services and 2C (which can be understood as public network) services of the corresponding operators. Therefore, how the access network equipment of the jointly built shared base station can reasonably access the private network services and public network services of the same operator under limited resources has become an urgent problem to be solved.

Summary of the invention

The present invention provides a service processing method and device, which can reasonably solve the access problem of public network services and private network services of the same operator under the condition of limited resources of a shared base station.

In order to achieve the above object, the present invention adopts the following technical scheme:

In the first aspect, a service processing method is provided, which is applied to an access network device, wherein the access network device configures a carrier for each network category service of each operator, and each carrier is used to carry a network category service of an operator; the network categories include at least public network category and private network category, the network type of the public network category is a public network, and the network type of the private network category is multiple private networks, and the method includes: determining the network type of each service to be accessed in at least one service to be accessed. Obtain the radio resource control (RRC) data and priority level of each service to be accessed; wherein the RRC data includes: the number of service RRC connections, and the number of service RRC connections with data transmission. Determine the priority parameters of the service to be accessed based on the priority level of the service to be accessed, the RRC data of the service to be accessed, and the RRC data of other services to be accessed that are of the same network type under the same carrier as the service to be accessed in at least one service to be accessed. When the RRC data of the target service meets the preset conditions, it is determined to access the target carrier to the target service; the target service is determined in at least one service to be accessed based on the priority parameters of each service to be accessed under the same carrier; the target carrier is the carrier corresponding to the network type to which the target service belongs; the preset conditions are used to indicate that the target service is a non-overflow service.

Based on the above method, in the present technical scheme, for the case where an access network device (shared base station) configures different carriers for services of different network categories of each operator, the embodiment of the present invention first determines the network type of each service to be accessed in at least one service to be accessed. According to the priority level of each service to be accessed, each service to be accessed and the RRC data of other services to be accessed that are of the same network type under the same carrier as the service to be accessed in at least one service to be accessed, the priority parameters of each service to be accessed are determined, and the target service is determined in at least one service to be accessed according to the priority parameters. Then, when it is determined that the RRC data of the target service meets the preset conditions for indicating whether the target service is a super flow service, the target service is connected to the carrier corresponding to the network type to which it belongs. In order to realize that the access network equipment of the shared base station after co-construction can reasonably access the private network services and public network services of the same operator under the condition of limited resources.

In a second aspect, an access network device is provided, wherein the access network device configures a carrier for each network category service of each operator, and each carrier is used to carry a network category service of an operator; the network category includes at least a public network category and a private network category, the network type of the public network category is a public network, and the network type of the private network category includes multiple private networks, and the device includes:

The processing unit is used to determine the network type of each service to be accessed in at least one service to be accessed.

The acquisition unit is used to acquire the RRC data of each service to be accessed, wherein the RRC data includes the number of RRC connections of the service radio resource control service and the number of RRC connections of the service with data transmission.

A processing unit is used to determine the priority parameters of the service to be accessed based on the priority level of the service to be accessed obtained by the acquisition unit, the RRC data of the service to be accessed, and the RRC data of other services to be accessed that are of the same network type and under the same carrier as the service to be accessed in at least one service to be accessed.

The processing unit is also used to determine that the target service is connected to the target carrier when the RRC data of the target service meets the preset conditions; the target service is determined in at least one service to be connected based on the priority parameters of each service to be connected under the same carrier; the target carrier is the carrier corresponding to the network type to which the target service belongs; the preset conditions are used to indicate that the target service is a non-overflow service.

It can be understood that the access network device provided above is used to execute the method corresponding to the first aspect provided above. Therefore, the beneficial effects that can be achieved can refer to the method corresponding to the first aspect above and the beneficial effects of the corresponding scheme in the specific implementation method below, and will not be repeated here.

In a third aspect, an access network device is provided, wherein the structure of the access network device includes a processor, and the processor is used to execute program instructions so that the access network device executes the method of the first aspect.

According to a fourth aspect, a computer-readable storage medium is provided, wherein a computer program code is stored in the computer-readable storage medium. When the computer program code runs on an access network device, the access network device executes the method according to the first aspect.

In a fifth aspect, a computer program product is provided, which stores the above-mentioned computer software instructions. When the computer software instructions are executed on an access network device, the access network device executes a program of the method of the first aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

FIG1 is a schematic diagram of the structure of a communication system to which a service processing method provided by an embodiment of the present invention is applied;

FIG2 is a schematic diagram of a system architecture to which another service processing method provided by an embodiment of the present invention is applied;

FIG3 is a schematic diagram of the structure of an access network device provided by an embodiment of the present invention;

FIG4 is a flow chart of a service processing method according to an embodiment of the present invention;

FIG5 is a second flow chart of a service processing method provided by an embodiment of the present invention;

FIG6 is a third flow chart of a service processing method provided by an embodiment of the present invention;

FIG7 is a schematic diagram of a structure of an access network device according to an embodiment of the present invention;

FIG8 is a second schematic diagram of the structure of an access network device provided by an embodiment of the present invention;

FIG. 9 is a schematic diagram of the structure of a computer program product of a business processing method provided by an embodiment of the present invention.

DETAILED DESCRIPTION

The technical solutions in the embodiments of the present invention will be described clearly and completely below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all the embodiments.

It should be noted that, in the embodiments of the present invention, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present invention should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

It should also be noted that in the embodiments of the present invention, "of", "corresponding, relevant" and "corresponding" can sometimes be used interchangeably. It should be pointed out that when the distinction between them is not emphasized, the meanings they intend to express are consistent.

In the embodiments of the present application, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of the present application, unless otherwise specified, "plurality" means two or more.

The transceiver equipment (such as access network equipment) in the 5G network is usually a multi-antenna device, such as a 64-bit transmitter and receiver (TR) device, which results in extremely high network construction costs. Therefore, operators began to seek a way for multiple operators to jointly build and share base stations, and use the access network equipment of the jointly built shared base stations to allocate different carriers to different operators. The carriers simultaneously carry the 2B (which can be understood as private network) services and 2C (which can be understood as public network) services of the corresponding operators. Therefore, how the access network equipment of the jointly built shared base station can reasonably access the private network services and public network services of the same operator under limited resources has become an urgent problem to be solved.

In view of the above problems, the embodiment of the present application provides a service processing method, which can reasonably access the private network service and public network service of the same operator based on the number of users under the condition of limited resources. The method is applied to the communication system shown in Figure 1, which may include: terminal 01, access network device 02 and at least one core network device 03 (03-1, 03-2, 03-3 and 03-4), each core network device 03 corresponds to an operator core network (private network core network (supporting 2B service) or public network core network (supporting 2C service)); illustratively, as shown in Figure 1, 03-1 can correspond to the public network core network of operator 1, 03-2 can correspond to the private network core network of operator 1, 03-3 can correspond to the public network core network of operator B, and 03-4 can correspond to the private network core network of operator B. After the terminal 01 access network device 02 is connected to the access network device, it can access the public network core network or private network core network of the corresponding operator through different core network devices 03. Of course, in practice, there can be only one core network device 03, which can complete the functions of the above-mentioned multiple core network devices.

It should be noted that in this application, an operator core network corresponds to one public network and multiple private networks. Public network services (2C services) refer to all services in a public network, and private network services (2B services) refer to all services in a private network.

Exemplarily, as shown in FIG2 , the functional modules in the core network device 03 may include a service distribution demand collection module 031, a service dependency analysis module 032, a key concurrent user number customization module 033, and a differentiated carrier user number customization module 034. The service distribution demand collection module 031 may collect RRC data of a private network service or a public network service of a corresponding operator of the access network device 02 (e.g., a base station) to which it is connected.

The service dependency analysis module 032 can cooperate with the service dependency analysis module 032 in other core network devices corresponding to the access network device 02 connected thereto, and use the RRC data obtained by the corresponding service distribution demand collection module 031 to obtain the service dependency degree of the scenario on the large number of connections, and clarify that such scenarios use resource scheduling and load balancing based on the number of service RRC connections. Of course, if all core networks correspond to the same core network device, the service dependency analysis module included therein independently completes the above calculation process. The specific algorithm is as follows:

H＝∑∑H _i

Where _Hi is the number of busy hours on the i-th day.

In addition, the hours dominated by business RRC connections:

(如30％)；

(e.g. 30%);

(如30％)。

(e.g. 30%).

The key concurrent user number customization module 033 is used to provide recommended agreed RRC data for the public networks and private networks of different operators by analyzing the maximum RRC data (including the number of service RRC connections and the number of service RRC connections with data transmission) and the average RRC data (including the number of service RRC connections and the number of service RRC connections with data transmission) obtained by the service distribution demand collection module 031.

The differentiated carrier user number customization module 034 clarifies the agreed number of users for each carrier through the demand for the number of users in the proposed deployment area, and the demand for the number of users in the proposed deployment area is calculated by the aforementioned key traffic customization module. For example, taking the case where the access network equipment only carries public network and private network services, and each operator is configured with a private network carrier and a public network carrier, the preset traffic (preset unit traffic) of a certain operator's public network carrier and private network carrier in unit time is calculated by the following formula:

RRC ^PU _NTi =RRC ^PU _Yi ;

Among them, RRC ^PU _NTi represents the agreed service RRC connection number of public network carrier i; RRC ^PU _Yi represents the service RRC connection number of public network users per TTI agreed under the carrier pair i-th public network; the specific calculation method of RRC ^PU _Yi will be described in detail below.

RDT ^PU _NTi =RDT ^PU _Yi ;

Among them, RDT ^PU _NTi represents the number of RRC connections with data transmission agreed for public network carrier i; RDT ^PU _Yi represents the number of RRC connections with data transmission agreed for public network users per TTI under the carrier pair i-th public network; the specific calculation method of RDT ^PU _Yi will be described in detail below.

RCC ^Pr _NTk =RCC ^Pr _Yki ;

Among them, RCC ^Pr _NTk represents the agreed service RRC connection number of private network carrier k; RDT ^Pr _Yki represents the service RRC connection number of public network users per TTI agreed under k carrier for j private networks.

RDT ^Pr _NTk =RDT ^Pr _Yki ;

Among them, RDT ^PU _NTi represents the number of RRC connections with data transmission services agreed for public network carrier i; RCC ^PU _Yi represents the number of RRC connections with data transmission services agreed for public network users per TTI under k carrier for j private networks.

Exemplarily, as shown in FIG. 2 , the access network device 02 includes a network parameter collection module 021 , a service assurance parameter collection module 022 , a priority parameter calculation module 023 , and a user access and resource allocation module 024 .

Among them, the network parameter collection module 021 can collect frequency information, data network name (data network name, DNN) information and public and private network identification for subsequent distinction between the operator's private network and public network. The data that needs to be recorded in this module is shown in Table 1 below:

Table 1

Business Logo Frequency information DNN Public and private network logo 1 A — PU 2 B — PU 3 A 1 Pr 4 A i Pr 5 B 1 Pr n B j Pr

The service guarantee parameter collection module 022 needs to extract parameters related to service characteristics, such as 5QI, service RRC connection number, service arrival time of service RRC connection number with data transmission, and service demand duration information, which will be used for the calculation of priority parameters. The content that needs to be recorded in this module is shown in Table 2 below:

Table 2

The priority parameter calculation module 023 calculates the priority parameters of the service based on the service assurance parameter collection module 022, and accesses the service through the priority parameters. First, it is necessary to analyze the 5QI to obtain the priority level. 5QI is a scalar used to index a 5G QoS feature. TS23.501 Table 5.7.4-1 has a standardized 5QI mapping relationship. This patent applies the priority level (PrLi) in 5QI for subsequent calculations. The smaller the priority level, the higher the priority parameter. The following Table 3 shows the 5G Qos characteristics related to 5QI.

Table 3

In addition, Table 4 below gives the mapping of the third generation partnership project (3GPP), i.e., standard 5QI to 5G Qos characteristics.

Table 4

Exemplarily, taking the 5G communication network as an example, as shown in FIG3 , the actual device in the access network device 02 may include a radio frequency unit and a baseband processing unit. The radio frequency unit is connected to the baseband processing unit via a common public radio interface (CPRI (eCRPI)), and the public network core network (5GC1) of operator 1, the public network core network (5GC2) of operator B, the private network core network (5GC3) of operator 1, and the private network core network (5GC4) of operator B are all connected to the baseband processing unit of the access network device 2 via an NG interface.

The 5G baseband processing unit includes a control plane (CP) and a user plane (UP). The control plane contains an identification module for the private core network and public core network of different operators (specifically, it can be judged by PLMN (public land mobile network), APN (access point name), DNN (Data network name), etc.), so as to distinguish the public core network and private core network under different operators. The above-mentioned real-time traffic monitoring module 021, traffic identification module 022, and network load balancing module 023 can also be set in the CP.

The 5G radio frequency unit includes an antenna unit, a switch, and a transceiver. The transceiver includes a digital up conversion (DUC), a digital to analog converter (DAC), a transmit antenna (TX), a receive antenna (RX), an analog to digital converter (ADC), and a digital down conversion (DDC).

In a specific implementation, taking the network categories including public network and private network as an example, in the technical solution provided by the present invention, the access network device 02 configures two carriers for each of the multiple operators respectively, and the two carriers include a public network carrier and a private network carrier, wherein the public network carrier provides support for the services corresponding to the public network of an operator, and the private network carrier provides support for the services corresponding to all private networks of an operator. Each carrier includes an uplink carrier and a downlink carrier, and the communication link corresponding to the uplink carrier is composed of the antenna unit, switch, RX, ADC, DDC, and 5G baseband processing unit in Figure 3, and the communication link corresponding to the downlink carrier is composed of the antenna unit, switch, TX, DAC, DUC, and 5G baseband processing unit in Figure 3. When the user terminals corresponding to operator 1 and operator 2 initiate private network services or public network services, they transmit relevant data through the communication link corresponding to the uplink carrier and the communication link corresponding to the downlink carrier.

For example, as shown in Figure 3, when two operators (operator 1 and operator B) are connected to the access network device 02, the user terminal of operator 1 can transmit through the first carrier when initiating related services of the private network; the user terminal of operator 1 can transmit through the second carrier when initiating related services of the private network; the user terminal of operator B can transmit through the third carrier when initiating related services of the public network; the user terminal of operator B can transmit through the fourth carrier when initiating related services of the private network. Among them, the first carrier includes a first transceiver (DUC1, DAC1, TX1, DDC1, ADC1, RX1), a first combiner, a switch and an antenna unit; the second carrier includes a second transceiver (DUC2, DAC2, TX2, DDC2, ADC2, RX2), a second combiner, a switch and an antenna unit; the third carrier includes a third transceiver (DUC3, DAC3, TX3, DDC3, ADC3, RX3), a first combiner, a switch and an antenna unit; the fourth carrier includes a fourth transceiver (DUC4, DAC4, TX4, DDC4, ADC4, RX4), a second combiner, a switch and an antenna unit.

In the embodiment of the present application, the access network device 02 can be a global system for mobile communication (GSM), an access network device (base transceiver station, BTS) in code division multiple access (CDMA), an access network device (node B, NB) in wideband code division multiple access (WCDMA), an access network device (evolved Node B, eNB) in long term evolution (LTE), an eNB in the internet of things (IoT) or narrowband internet of things (NB-IoT), an access network device in a future 5G mobile communication network or a future evolved public land mobile network (PLMN), and the embodiment of the present invention does not impose any restrictions on this.

Exemplarily, the terminal 01 in the embodiment of the present application may have different names, such as user equipment (UE), access terminal, terminal unit, terminal station, mobile station, mobile station, remote station, remote terminal, mobile device, wireless communication device, vehicle user equipment, terminal agent or terminal device, etc. It may specifically be a mobile phone, tablet computer, desktop, laptop, handheld computer, notebook computer, ultra-mobile personal computer (UMPC), netbook, as well as cellular phone, personal digital assistant (PDA), augmented reality (AR)\virtual reality (VR) equipment and other equipment that can communicate with the base station, and the embodiment of the present application does not impose any special restrictions on the specific form of the terminal.

In the following, in conjunction with the communication system shown in FIG. 1 , taking the access network device 02 as a base station as an example, the service processing method provided by the embodiment of the present invention is introduced.

As shown in FIG4 , the service processing method provided by the embodiment of the present invention is applied to a base station. The base station configures a carrier for each network category service of each operator, and each carrier is used to carry a network category service of an operator; the network category includes at least a public network category and a private network category, the network type of the public network category is a public network, and the network type of the private network category includes multiple private networks. The following is described with the base station as the execution subject. The method includes:

S11. The base station determines a network type of each service to be accessed in at least one service to be accessed.

Optionally, determining whether the intended access service is a public network or a private network is mainly determined based on the public or private network identifier of the intended access service. When the intended access service is a private network, the specific private network to which the intended access service belongs is determined based on the DNN.

Exemplarily, the specific private network for the service to be accessed may be determined in the following manner.

Exemplarily, in combination with the communication system of Figure 1, the access network device 02 is taken as a base station, and the core network device 03 supports at least one operator core network of a preset operator as an example for explanation. The specific implementation process is: the operator core network can be a dedicated network core network (also called a private network) or the operator core network can be a public network core network.

Specifically, the core network identifier includes any one of a public network identifier and a private network identifier, each public network core network corresponds to a public network identifier, and each private network core network corresponds to a private network identifier. Specifically, the first network type is different from the second network type. Exemplarily, the first network type is a public network, and the second network type is a private network.

When the base station obtains the terminal identifier and the core network identifier corresponding to the terminal identifier from the core network device, the base station needs to determine the service type and operator identifier of the terminal corresponding to the terminal identifier based on the terminal identifier. Then, the base station determines the network type of the terminal based on the operator identifier and the core network identifier.

S12: The base station obtains the radio resource control RRC data and priority level of each service to be accessed.

The RRC data includes: the number of service RRC connections and the number of service RRC connections with data transmission.

Optionally, the base station obtains network data of each service to be accessed in each operator in the current unit time.

For example, in order to ensure timely processing of the access request of the user terminal based on the service RRC connection number and the service RRC connection number with data transmission, the unit time here can be one second. Of course, under the actual technical conditions, it can also be a smaller unit time, which is not specifically limited here.

For example, in practice, S12 may be executed by the aforementioned service assurance parameter collection module, and the data collected is recorded as shown in Table 5 below:

Table 5

Among them, YY represents the year, MM represents the month, DD represents the day of the month MM, and HH:SS represents hours, minutes and seconds.

S13. The base station determines the priority parameters of the service to be accessed according to the priority level of the service to be accessed, the RRC data of the service to be accessed, and the RRC data of other services to be accessed that are of the same network type and under the same carrier as the service to be accessed in at least one service to be accessed.

Optionally, obtain the service quality identifier (5G service quality identity document, 5QI) information of the fifth generation mobile communication technology of the service to be accessed, and determine the priority level based on the 5QI information.

It should be noted that when calculating the priority parameters of one of the intended access services, it is necessary to first determine a target intended access service (i.e., the intended access service in S13) among at least one intended access service. Then, determine the RRC data of all intended access services (including the target intended access service) in the same network type (such as carrier A private network 1) under the same carrier as the target intended access service, and determine the maximum number of service RRC connections and the maximum number of service RRC connections with data transmission in the RRC data, and then determine the priority parameters based on the maximum number of service RRC connections, the maximum number of service RRC connections with data transmission, the RRC data of the target intended access service, and the priority level of the target intended access service.

Exemplarily, the priority parameters may be determined based on the following formula according to the parameters mentioned in S13, specifically:

Among them, Pa _i represents the priority parameter of the target intended access service i; RRC _i represents the number of service RRC connections of the target intended access service i; RDT _i represents the number of service RRC connections for data transmission of the target intended access service i, RRC ₁ , RRC ₂ ..., RRC _N represent the number of service RRC connections of all intended access services (here are N intended access services, N≥1) belonging to the same carrier and the same network type as RRC _i ; RDT ₁ , RDT ₂ ..., RDT _N represent the number of service RRC connections with data transmission of all intended access services of the same carrier and the same network type as RRC _i ; PrL _i represents the priority level of the target intended access service i.

As shown in the following Table 6, when the network type is a public network, a correspondence between the operator, the public network, the intended access service and the priority parameters is illustrated.

Table 6

As shown in Table 7 below, when the network type is a private network (private network i and private network j), a correspondence method between the operator, the private network, the intended access service and the priority parameters is illustrated.

Table 7

S14. When the RRC data of the target service meets a preset condition, the base station determines to connect the target service to the target carrier.

Among them, the target service is determined in at least one service to be accessed based on the priority parameters of each service to be accessed under the same carrier; the target carrier is the carrier corresponding to the network type to which the target service belongs; and the preset condition is used to indicate that the target service is a non-overflow service.

Further, when the RRC data of the target service does not meet the preset condition, the base station determines to prohibit the target service from accessing the target carrier.

Exemplarily, the priority parameters of each service to be accessed can first be arranged in a preset order. The preset order can be from high to low or from low to high. For example, the service to be accessed that is ranked first (e.g., arranged in order from large to small, and the largest priority parameter is selected) among the priority parameters of all services to be accessed under the target carrier is selected as the target service, and a preset condition judgment is performed to determine whether the target carrier can be accessed. When the target service is judged, the target service is removed from the process of this service access, and the next target service is selected from the remaining services to be accessed in the above manner for preset condition judgment to determine whether the target carrier can be accessed.

Specifically, the preset conditions include: if when the target service is accessed, the total number of service RRC connections of the current access service in the target carrier is less than or equal to the first threshold, and the total number of service RRC connections of the current access service under the same carrier and the same network type as the target service is less than or equal to the second threshold, and the total number of service RRC connections with data transmission for the current access service in the target carrier is less than or equal to the third threshold, and the number of service RRC connections with data transmission for the current access service under the same carrier and the same network type as the target service is less than or equal to the fourth threshold.

The embodiment of the present application can more accurately determine the target service access to the target carrier based on the priority parameters by setting the preset conditions for the RRC data of the intended access service and the accessed service under the carrier, thereby bringing a better experience to the user.

Furthermore, when the target service meets the preset conditions, the target service is accessed according to 5QI and subsequent service judgment is performed, otherwise, access to the target service is prohibited.

Optionally, assuming that the target carrier is carrier A, carrier A corresponds to the services of the public network of carrier 1, and the public network includes target service a, the base station can determine whether the RRC data of target service a meets the preset conditions according to the following method. Including:

且

且∑RRC^now _{运营商1公网}≤RRC^PU _A；且∑RDT^now _{运营商1公网}≤RDT^PU _A。

and

And ∑RRC ^now _{operator 1 public network} ≤RRC ^PU _A ; and ∑RDT ^now _{operator 1 public network} ≤RDT ^PU _A .

Among them, RRC ^A _a represents the number of RRC connections of service a connected in carrier A; the value range of a is 1 to n; n is a positive integer. RDT ^A _a represents the number of RRC connections with data transmission of service a connected in carrier A; RRC ^now _{operator 1 public network} represents the number of RRC connections of services connected in operator 1's public network; RDT ^now _{operator 1 public network} represents the number of RRC connections with data transmission of services connected in operator 1's public network.

The first threshold is 90%×RRC ^A _{carrier limit} , wherein RRC ^A _{carrier limit} represents the limit value of the number of service RRC connections of carrier A. 90% is the first preset threshold value, and of course it can also be other first preset threshold values, and the first preset threshold value is not limited here.

The second threshold is 90%×RDT ^A _{carrier limit} ; RDT ^A _{carrier limit} indicates the limit value of the number of RRC connections with data transmission of carrier A. 90% is the second preset threshold value, and of course it can also be other second preset threshold values, and no limitation is made to the second preset threshold value here.

The third threshold is RRC ^PU _A ; RRC ^PU _A represents the number of RRC connections of public network users per TTI agreed under carrier A; TTI represents a unit time, which can be seconds, minutes or hours; there is no limitation on the length of the unit time. RRC ^PU _A is obtained by calculating according to the following formula:

Among them, PU represents the public network; RRC ^PU _MAX is the maximum number of business RRC connections per hour of the public network; RRC ^PU _mean is the average number of business RRC connections per hour of the public network.

The fourth threshold is RDT ^PU _A ; RDT ^PU _A represents the number of service RRC connections of public network users per TTI agreed under carrier A; wherein RDT ^PU _A is obtained by calculating according to the following formula:

Among them, RDT ^PU _MAX is the maximum number of RRC connections with data transmission per hour of the public network; RDT ^PU _mean is the average number of RRC connections with data transmission per hour of the public network.

Optionally, it is assumed that the target carrier is carrier A, and carrier A corresponds to the private network class service of carrier 1, and the private network class includes private network i; private network i corresponds to target service a, and the base station can determine whether the RRC data of target service a meets the preset conditions according to the following method. Including:

且

且∑RRC^now _{载波A专网i}≤RCC^Pr _Ai；且∑RDT^now _{载波A专网i}≤RDT^Pr _Ai。

and

And ∑RRC ^now _{carrier A private network i} ≤RCC ^Pr _Ai ; and ∑RDT ^now _{carrier A private network i} ≤RDT ^Pr _Ai .

Among them, RRC ^A _a represents the number of RRC connections of service a connected in carrier A; the value range of a is 1 to n; n is a positive integer. RDT ^A _a represents the number of RRC connections with data transmission of service a connected in carrier A; RRC ^now _{carrier A private network i} represents the number of RRC connections of services connected in private network i of carrier A; RDT ^now _{carrier A private network i} represents the number of RRC connections with data transmission of services connected in private network i of carrier A.

The first threshold and the second threshold refer to the description in the previous optional section and will not be repeated here.

The third threshold is RCC ^Pr _Ai ; RCC ^Pr _Ai represents the number of RRC connections of the service of the private network i user per TTI agreed under carrier A; TTI represents the unit time, which can be seconds, minutes or hours; there is no limitation on the length of the unit time. Among them, RCC ^Pr _Ai is calculated according to the following formula:

Among them, Pr represents private network i; RRC ^Pr _MAX is the maximum number of business RRC connections per hour for private network i; RRC ^Pr _mean is the average number of business RRC connections per hour for private network i.

The fourth threshold is RDT ^Pr _Ai ; RDT ^Pr _Ai represents the number of service RRC connections of private network i user per second agreed under carrier A; wherein, RDT ^Pr _Ai is calculated and obtained according to the following formula:

Among them, RDT ^Pr _MAX is the maximum number of RRC connections with data transmission per hour for the private network i; RDT ^Pr _mean is the average number of RRC connections with data transmission per hour for the private network i.

It should be noted that the connected services involved in the preset conditions include the above-mentioned target services.

Based on the above method, when the access network equipment of the existing shared base station carries the services of multiple operators, after allocating a carrier to an operator, the carrier carries all public network services and private network services of the corresponding operator. In the context of the carrier carrying all public network services and private network services of the corresponding operator, the embodiment of the present invention first determines the network type of each intended access service in at least one intended access service in the target carrier. According to the priority level of each intended access service, each intended access service and the RRC data of other intended access services of the same network type under the same carrier as the intended access service in at least one intended access service, the priority parameters of each intended access service are determined, and the target service is determined in at least one intended access service according to the priority parameters. Then, when it is determined that the RRC data of the target service meets the preset conditions for indicating whether the target service is a super flow service, the target service is connected to the above-mentioned target carrier. In this way, the access network equipment of the shared base station after co-construction can reasonably access the private network services and public network services of the same operator under the condition of limited resources.

In one implementation, referring to FIG. 5 , before S11, the following steps are further included:

S1. The base station obtains frequency information and data network name DNN information of at least one service to be accessed.

Exemplarily, the frequency point information and DNN information can be obtained by the aforementioned network parameter acquisition module. The specific frequency point information example can be referred to as shown in Table 1, which will not be repeated here.

It should be noted that the frequency point information is actually the number of fixed frequencies. The frequency interval is 200khz. In this way, according to the frequency interval of 200khz, 890mhz, 890.2mhz, 890.4mhz, 890.6mhz, 890.8mhz, 891mhz...915mhz are divided into 125 wireless frequency bands, and each frequency band is numbered from 1, 2, 3, 4...125.

S2. The base station determines the carrier to which the service to be accessed belongs based on the frequency information.

Exemplarily, the frequency information may be extracted from the broadcast signaling MIB of the service to be accessed.

In addition, the carrier can be determined according to the frequency information; since one carrier corresponds to one in the embodiment of the present application, therefore, the operator is determined according to the frequency information; such as:

S3. When the first carrier corresponds to a public network type, the base station determines all the intended access services corresponding to the first carrier as intended access services belonging to the same carrier and the same network type.

The first carrier is any one of multiple carriers configured by the access network device.

S4. When the second carrier corresponds to a private network class, the base station determines the intended access services with the same DNN information among the intended access services corresponding to the second carrier as intended access services belonging to the same carrier and the same network type.

The second carrier is any one of multiple carriers configured by the access network device.

In this implementation, the specific carrier of the intended access service is determined based on the frequency information, and then at least one intended access service of the target carrier is determined from all the intended access services in multiple carriers, so as to provide a basis for the carrier to carry the public network and private network of the operator.

In one implementation, in order to more accurately obtain the priority parameter, referring to FIG. 6 , S13 specifically includes:

S131. The base station obtains time data of each service to be accessed.

The time data includes at least one of the service arrival time of the intended access service, the start time of the previous scheduling moment, and the service duration.

It should be noted that the previous scheduling time of the service to be accessed specifically refers to a time that is adjacent to the current scheduling time corresponding to the scheduling of the service to be accessed, and is adjacent to the current scheduling time.

S132. The base station determines the priority parameters of the intended access service based on the RRC data of other intended access services of the same network type under the same carrier as the intended access service in at least one intended access service, the priority level of the intended access service, the RRC data of the intended access service, and the time data of the intended access service.

Exemplarily, when determining the priority parameters of the service to be accessed, it can be determined based on the RRC data of other services to be accessed that are of the same network type under the same carrier as the service to be accessed in at least one service to be accessed, the priority level of the service to be accessed, the RRC data of the service to be accessed, and the time data of the service to be accessed; wherein the time data of the service to be accessed may include one or more of the service arrival time of the service to be accessed, the start time of the previous scheduling moment, and the service duration; below, the priority parameters are calculated using the example that the time data of the service to be accessed includes the service arrival time of the service to be accessed, the start time of the previous scheduling moment, and the service duration.

Specifically, the priority parameter can be calculated according to the following formula:

Among them, Pa _i represents the priority parameter of the target intended access service i; RRC _i represents the number of service RRC connections of the target intended access service i; RDT _i represents the number of service RRC connections for data transmission of the target intended access service i; RRC ₁ , RRC ₂ ..., RRC _N represent the number of service RRC connections for all intended access services (here are N intended access services, N≥1) belonging to the same carrier and the same network type as RRC _i ; RDT ₁ , RDT ₂ ..., RDT _N represent the number of service RRC connections with data transmission for all intended access services belonging to the same carrier and the same network type as RRC _i ; Time _i represents the service arrival time of the target intended access service i; TTI _pre is the time from the previous scheduling moment; Last represents the service duration of the intended access service. _{PrL i} represents the priority level of the target intended access service i.

Furthermore, in the above formula, any one or more items in the time data can be removed to calculate the priority parameter. For example, the service duration of the intended access service in the time data is removed; the priority parameter can be calculated according to the following formula:

Exemplarily, priority parameters of all services to be accessed in carrier A are merged and sorted in a preset manner. The sorting result is shown in Table 8.

Table 8

In this implementation, the accuracy of calculating the priority parameters of the intended access service is improved by adding the time data of the intended access service on the basis of the RRC data of other intended access services of the same network type under the same carrier as the intended access service in at least one intended access service, the priority level of the intended access service, and the RRC data of the intended access service. In addition, in actual applications, the requirements for the acquisition of time data and the accuracy of priority parameters are improved by selecting one or more parameters in the time data, such as the service arrival time of the intended access service, the start time of the previous scheduling moment of the intended access service, and the service duration of the intended access service, to improve the flexibility of calculating the priority parameters.

The embodiment of the present invention can divide the access network device 02 into functional modules according to the above method embodiment. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present invention is schematic and is only a logical function division. There may be other division methods in actual implementation.

As shown in FIG7 , it is a schematic diagram of the structure of an access network device 02 provided in an embodiment of the present invention. The access network device 02 configures one carrier for each network category service of each operator, and each carrier is used to carry a network category service of one operator; the network category includes at least a public network category and a private network category, the network type of the public network category is a public network, and the network type of the private network category includes multiple private networks. The access network device 02 specifically includes an acquisition unit 701 and a processing unit 702.

Specifically, the processing unit 702 is configured to determine a network type of each service to be accessed in at least one service to be accessed.

The acquisition unit 701 is used to acquire the RRC data and priority level of each service to be accessed, wherein the RRC data includes the number of service radio resource control service RRC connections and the number of service RRC connections with data transmission.

The processing unit 702 is used to determine the priority parameters of the service to be accessed based on the priority level of the service to be accessed obtained by the acquisition unit 701, the RRC data of the service to be accessed, and the RRC data of other services to be accessed that are of the same network type and under the same carrier as the service to be accessed in at least one service to be accessed.

Processing unit 702 is also used to determine that the target service is connected to the target carrier when the RRC data of the target service meets the preset conditions; the target service is determined in at least one service to be connected based on the priority parameters of each service to be connected under the same carrier; the target carrier is the carrier corresponding to the network type to which the target service belongs; the preset conditions are used to indicate that the target service is a non-overflow service.

Optionally, the acquisition unit 701 is further used to obtain frequency information and data network name DNN information of at least one service to be accessed.

The processing unit 702 is used to determine the carrier to which the service to be accessed belongs according to the frequency information acquired by the acquisition unit 701.

The processing unit 702 is further configured to determine all intended access services corresponding to the first carrier as intended access services belonging to the same carrier and the same network type when the first carrier corresponds to a public network type; the first carrier is any one of the multiple carriers configured for the access network device.

The processing unit 702 is also used to, when the second carrier corresponds to a private network class, determine the intended access services with the same DNN information among the intended access services corresponding to the second carrier as intended access services belonging to the same network type of the same carrier; the second carrier is any one of the multiple carriers configured for the access network device.

Optionally, the acquisition unit 701 is specifically used to obtain time data of each service to be accessed; wherein the time data includes at least one of the service arrival time of the service to be accessed, the start time of the previous scheduling moment, and the service duration.

The processing unit 702 is used to determine the priority parameters of the intended access service based on the RRC data of other intended access services of the same network type under the same carrier as the intended access service in at least one intended access service obtained by the acquisition unit 701, the priority level of the intended access service, the RRC data of the intended access service, and the time data of the intended access service.

Optionally, the preset conditions include: if when the target service is accessed, the total number of service RRC connections of the current access service in the target carrier is less than or equal to a first threshold, and the total number of service RRC connections of the current access service of the same network type under the same carrier as the target service is less than or equal to a second threshold, and the total number of service RRC connections with data transmission of the current access service in the target carrier is less than or equal to a third threshold, and the number of service RRC connections with data transmission of the current access service of the same network type under the same carrier as the target service is less than or equal to a fourth threshold.

Optionally, the acquisition unit 701 is specifically used to obtain service quality identification 5QI information of the fifth generation mobile communication technology of the intended access service.

The processing unit 702 is used to determine the priority level according to the 5QI information obtained by the obtaining unit 701.

Of course, the access network device 02 provided in the embodiment of the present invention includes but is not limited to the above modules, for example, the access network device 02 may also include a sending unit 703 and a storage unit 704. The sending unit 703 may be used to send relevant data in the access network device 02 to other devices to implement data interaction with other devices. The storage unit 704 may be used to store the program code of the access network device 02, and may also be used to store data generated by the access network device 02 during operation, such as data in a write request, etc.

Here, the system architecture and business scenarios described in the embodiments of the present invention are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

FIG8 is a schematic diagram of the structure of an access network device 02 provided in an embodiment of the present invention. As shown in FIG8 , the access network device 02 may include: at least one processor 51 , a memory 52 , a communication interface 53 and a communication bus 54 .

The following is a detailed introduction to the various components of the access network device 02 in conjunction with FIG8 :

The processor 51 is the control center of the access network device 02, and may be a processor or a general term for multiple processing elements. For example, the processor 51 is a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiment of the present invention, such as one or more DSPs, or one or more field programmable gate arrays (FPGAs).

In a specific implementation, as an embodiment, the processor 51 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG8. Also, as an embodiment, the access network device 02 may include multiple processors, such as the processor 51 and the processor 55 shown in FIG8. Each of these processors may be a single-core processor (Single-CPU) or a multi-core processor (Multi-CPU). The processor here may refer to one or more devices, circuits, and/or processing cores for processing data (such as computer program instructions).

The memory 52 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 52 may exist independently and be connected to the processor 51 via a communication bus 54. The memory 52 may also be integrated with the processor 51.

In a specific implementation, the memory 52 is used to store the data in the present invention and execute the software program of the present invention. The processor 51 can execute various functions of the access network device 02 by running or executing the software program stored in the memory 52 and calling the data stored in the memory 52.

The communication interface 53 uses any transceiver-like device for communicating with other devices or communication networks, such as a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), a terminal, a cloud, etc. The communication interface 53 may include a receiving unit to implement a receiving function, and a sending unit to implement a sending function.

The communication bus 54 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, FIG8 only uses one thick line, but does not mean that there is only one bus or one type of bus.

As an example, in combination with Figure 7, the function implemented by the acquisition unit 701 in the access network device 02 is the same as the function of the communication interface 53 in Figure 8, the function implemented by the processing unit 702 is the same as the function of the processor 51 in Figure 8, and the function implemented by the storage unit 704 is the same as the function of the memory 52 in Figure 8.

Another embodiment of the present invention further provides a computer-readable storage medium, in which instructions are stored. When the instructions are executed on a computer, the computer executes the method shown in the above method embodiment.

In some embodiments, the disclosed methods may be implemented as computer program instructions encoded in a machine-readable format on a computer-readable storage medium or on other non-transitory media or articles of manufacture.

FIG9 schematically shows a conceptual partial view of a computer program product provided by an embodiment of the present invention, wherein the computer program product includes a computer program for executing a computer process on a computing device.

In one embodiment, the computer program product is provided using a signal bearing medium 410. The signal bearing medium 410 may include one or more program instructions that, when executed by one or more processors, may provide the functionality or portions of functionality described above with respect to FIG. 4 . Thus, for example, with reference to the embodiment shown in FIG. 4 , one or more features of S11-S14 may be undertaken by one or more instructions associated with the signal bearing medium 410. In addition, the program instructions in FIG. 9 also describe example instructions.

In some examples, signal bearing medium 410 may include computer readable medium 411, such as, but not limited to, a hard drive, a compact disk (CD), a digital video disk (DVD), a digital tape, a memory, a read-only memory (ROM), or a random access memory (RAM), and the like.

In some implementations, signal bearing medium 410 may include computer recordable medium 412 such as, but not limited to, memory, read/write (R/W) CD, R/W DVD, and the like.

In some implementations, signal bearing medium 410 may include communication medium 413 such as, but not limited to, digital and/or analog communication media (eg, fiber optic cables, waveguides, wired communication links, wireless communication links, etc.).

The signal bearing medium 410 may be communicated by a wireless form of communication medium 413 (eg, a wireless communication medium complying with the IEEE 802.41 standard or other transmission protocols). The one or more program instructions may be, for example, computer executable instructions or logic implemented instructions.

In some examples, a write data device such as described with respect to FIG. 4 may be configured to provide various operations, functions, or actions in response to one or more program instructions via computer-readable medium 411 , computer-recordable medium 412 , and/or communication medium 413 .

Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

In the several embodiments provided by the present invention, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present invention is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, ROM, RAM, disk or optical disk and other media that can store program codes.

The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any changes or substitutions within the technical scope disclosed by the present invention should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims (8)

1. A service processing method, applied to an access network device, wherein the access network device configures a carrier for each network category service of each operator, and each carrier is used to carry a network category service of an operator; the network category includes at least a public network category and a private network category, the network type of the public network category is a public network, and the network type of the private network category includes multiple private networks, and is characterized by comprising: Determine a network type of each service to be accessed in at least one service to be accessed; Acquire the radio resource control RRC data and priority level of each service to be accessed; wherein the RRC data includes: the number of service RRC connections and the number of service RRC connections with data transmission; Determine the priority parameter of the service to be accessed according to the priority level of the service to be accessed, the RRC data of the service to be accessed, and the RRC data of other services to be accessed that are of the same network type under the same carrier as the service to be accessed in the at least one service to be accessed; When the RRC data of the target service meets a preset condition, determining to access the target service to a target carrier; the target service is determined in the at least one service to be accessed based on a priority parameter of each service to be accessed under the same carrier; the target carrier is a carrier corresponding to a network type to which the target service belongs; and the preset condition is used to indicate that the target service is a non-superflow service; The determining, according to the priority level of the intended access service, the RRC data of the intended access service, and the RRC data of other intended access services of the same network type under the same carrier as the intended access service in the at least one intended access service, the priority parameter of the intended access service comprises: Acquire the time data of each service to be accessed; wherein the time data includes at least one of the service arrival time of the service to be accessed, the start time of the previous scheduling moment, and the service duration; Determine the priority parameter of the intended access service based on the RRC data of other intended access services of the same network type under the same carrier as the intended access service in the at least one intended access service, the priority level of the intended access service, the RRC data of the intended access service, and the time data of the intended access service; The preset conditions include: If, when the target service is accessed, the total number of service RRC connections of the current access service in the target carrier is less than or equal to the first threshold, and the total number of service RRC connections of the current access service of the same network type under the same carrier as the target service is less than or equal to the second threshold, and the total number of service RRC connections with data transmission of the current access service in the target carrier is less than or equal to the third threshold, and the number of service RRC connections with data transmission of the current access service of the same network type under the same carrier as the target service is less than or equal to the fourth threshold. 2. The service processing method according to claim 1, characterized in that when the network category of the service to be accessed only includes the public network category and the private network category, before determining the network type of each service to be accessed in at least one service to be accessed, it also includes: Obtaining frequency information and data network name DNN information of at least one service to be accessed; Determine the carrier to which the service to be accessed belongs according to the frequency point information; When the first carrier corresponds to the public network class, all the intended access services corresponding to the first carrier are determined as intended access services belonging to the same carrier and the same network type; the first carrier is any one of the multiple carriers configured by the access network device; When the second carrier corresponds to the private network class, the intended access services with the same DNN information among the intended access services corresponding to the second carrier are determined as intended access services belonging to the same network type of the same carrier; the second carrier is any one of the multiple carriers configured for the access network device. 3. The service processing method according to claim 1, characterized in that it comprises: Acquire the service quality identifier 5QI information of the fifth generation mobile communication technology of the service to be accessed, and determine the priority level according to the 5QI information. 4. An access network device, wherein the access network device configures one carrier for each network category service of each operator, and each carrier is used to carry a network category service of one operator; the network category includes at least a public network category and a private network category, the network type of the public network category is a public network, and the network type of the private network category includes multiple private networks, characterized in that: A processing unit, configured to determine a network type of each service to be accessed in at least one service to be accessed; An acquisition unit, configured to acquire RRC data and a priority level of each service to be accessed, wherein the RRC data includes a number of service radio resource control service RRC connections and a number of service RRC connections with data transmission; The processing unit is used to determine the priority parameter of the intended access service according to the priority level of the intended access service acquired by the acquisition unit, the RRC data of the intended access service, and the RRC data of other intended access services of the same network type under the same carrier as the intended access service in the at least one intended access service; The processing unit is further used to determine that the target service is connected to the target carrier when the RRC data of the target service meets the preset condition; the target service is determined in the at least one service to be connected based on the priority parameter of each service to be connected under the same carrier; the target carrier is a carrier corresponding to the network type to which the target service belongs; the preset condition is used to indicate that the target service is a non-superflow service; The acquisition unit is specifically used to acquire the time data of each service to be accessed; wherein the time data includes at least one of the service arrival time of the service to be accessed, the start time of the previous scheduling moment, and the service duration; The processing unit is used to determine the priority parameter of the intended access service based on the RRC data of other intended access services of the same network type under the same carrier as the intended access service in the at least one intended access service acquired by the acquisition unit, the priority level of the intended access service, the RRC data of the intended access service, and the time data of the intended access service; The preset conditions include: If, when the target service is accessed, the total number of service RRC connections of the current access service in the target carrier is less than or equal to the first threshold, and the total number of service RRC connections of the current access service of the same network type under the same carrier as the target service is less than or equal to the second threshold, and the total number of service RRC connections with data transmission of the current access service in the target carrier is less than or equal to the third threshold, and the number of service RRC connections with data transmission of the current access service of the same network type under the same carrier as the target service is less than or equal to the fourth threshold. 5. The access network device according to claim 4, characterized in that: The acquisition unit is further used to acquire the frequency point information and data network name DNN information of the at least one service to be accessed; The processing unit is used to determine the carrier to which the intended access service belongs according to the frequency information acquired by the acquisition unit; The processing unit is further configured to, when the first carrier corresponds to the public network class, determine all intended access services corresponding to the first carrier as intended access services belonging to the same carrier and the same network type; the first carrier is any one of the multiple carriers configured by the access network device; The processing unit is also used to, when the second carrier corresponds to the private network class, determine the intended access services with the same DNN information among the intended access services corresponding to the second carrier as intended access services belonging to the same network type of the same carrier; the second carrier is any one of the multiple carriers configured for the access network device. 6. The access network device according to claim 4, characterized in that it comprises: The acquisition unit is specifically used to acquire the service quality identifier 5QI information of the fifth generation mobile communication technology of the intended access service; The processing unit is used to determine the priority level according to the 5QI information acquired by the acquisition unit. 7. An access network device, characterized in that the structure of the access network device includes a processor, and the processor is used to execute program instructions so that the access network device executes the service processing method according to any one of claims 1-3. 8. A computer-readable storage medium, characterized in that the computer-readable storage medium stores computer program code, and when the computer program code runs on an access network device, the access network device executes the service processing method according to any one of claims 1 to 3.

Images