JP7317921B2 - Core network equipment - Google Patents

Description

The present invention relates to core network equipment, mobile communication systems, and data communication systems.

In recent years, the scale of software installed in vehicles has expanded, and the volume of data obtained from onboard sensors has also increased. In addition, there is an increasing number of opportunities for downloading software updates and uploading in-vehicle sensor data between a vehicle and a server via mobile communication, for example.

As a technique for efficiently downloading data to a vehicle, for example, Patent Document 1 discloses that when the ignition switch is turned off by the user of the vehicle within a preset time, the vehicle is updated from the server to the vehicle. It is disclosed that information is provided.

JP-A-2004-228698

However, the technique described in Patent Literature 1 does not disclose means for appropriately providing update information when information update requests from a large number of vehicles converge on the server at the same time and congestion occurs.

In order to solve the above problems, a core network device according to one aspect of the present invention is a core network device connected to a server and a plurality of base stations, wherein the cell congestion status of each base station and the a determination unit that determines whether or not data communication between the mobile unit and the server is possible based on the serving cell of the mobile unit using a result of machine learning or the like; and a notification unit that notifies the server of the determination result of the determination unit. And prepare.

1 shows the configuration of a mobile communication system according to one aspect of the present invention; 1 shows the configuration of a core network device of a mobile communication system according to one aspect of the present invention; 2 is a block diagram of the network configuration of the mobile communication system of FIG. 1, showing the relationship between one mobile unit, core network devices, and external servers; FIG. 4 is a diagram showing the block diagram of FIG. 3 in comparison with the processing flow of the mobile communication system; FIG. 4 shows a modification of the configuration of the core network device of the mobile communication system according to one aspect of the present invention; 1 shows an example of a queuing list held and managed in a core network device of a mobile communication system according to one aspect of the present invention; 7 shows an example of prioritization of the queuing list T(2) of FIG. 6; FIG. 7 shows the calculated priority score of each moving object in the queuing list T(2) of FIG. A list T(4) that associates each device type with a coefficient corresponding to the remaining battery level is shown. A data communication priority list T(5) obtained by calculating the priority score of each mobile object in the queuing list T(2) of FIG. 6 using the score of the list T(4) of FIG. 9 is shown. 1 shows a mobile communication system according to another aspect of the present invention; FIG. 10 shows a table T(7) in which “possibly connected cars” used in a mobile communication system according to another aspect of the present invention are associated with cell IDs; FIG. FIG. 4 is a block diagram showing a schematic configuration of a mobile communication system according to another aspect of the present invention; FIG. 4 is a block diagram showing a schematic configuration of a mobile communication system according to another aspect of the present invention; FIG. 4 is a block diagram showing a schematic configuration of a mobile communication system according to another aspect of the present invention; FIG. 4 is a block diagram showing a schematic configuration of a mobile communication system according to another aspect of the present invention; FIG. 4 is a block diagram showing a schematic configuration of a mobile communication system according to another aspect of the present invention; FIG. 4 is a block diagram showing a schematic configuration of a mobile communication system according to another aspect of the present invention; FIG. 4 is a block diagram showing a schematic configuration of a mobile communication system according to another aspect of the present invention; 1 is a block diagram showing a schematic configuration of a data communication system according to one embodiment of the present invention; FIG.

[Embodiment 1]
A mobile communication system according to an embodiment of the present invention will be described below with reference to FIGS. 1 to 19. FIG.

<Mobile communication system>
The mobile communication system 1 shown in FIG. 1 may include a mobile unit 100 , an external server 200 (server), and a core network device 300 .

In this embodiment, a plurality of base stations 400 may be scattered over a wide area, and the cells 500 attached to each base station 400 may enable communication with mobile units 100 over a wide area. However, for example, when a large number of mobile units 100 are located in one cell 500 and communicate with the base station 400 of that cell 500, the communication load increases and congestion occurs. If it becomes a congestion state, the communication may be interrupted or the communication speed may be slowed down. When the amount of communication data is large and communication time is required, or when the data size of communication data is large and communication load is imposed, communication under such congestion conditions is inappropriate.

Therefore, in the mobile communication system 1, in order to solve such a problem, the core network device 300 connects the mobile unit 100 and the external server 200 based on the congestion status of each cell 500 and the cell in which the mobile unit 100 is located. and a notification unit 35 (FIG. 2) for notifying the external server 200 of the determination result of the determination unit 33 . Core network device 300 can notify external server 200 of whether or not data communication between mobile unit 100 and external server 200 is possible based on the congestion status of each cell and the cell in which the mobile unit is located. As a result, the mobile communication system 1 can perform stable communication without interruption even when the mobile object 100 runs in an automatic driving car or the like regardless of the time zone and performs large-capacity data communication. can provide services.

Further, by the core network device 300 grasping the congestion state of each cell 500, for example, when each mobile unit 100 grasps the congestion state of surrounding cells, and when each base station 400 grasps the congestion state of the cell belonging to itself Core network device 300 can perform appropriate processing based on information on cells in a wider range than when grasping the situation.

In addition, from a different point of view, the external server 200 communicates with the mobile object 100 via the core network device 300 according to the present embodiment, thereby reducing congestion that could not be obtained from the conventional core network device 300. It is possible to acquire information on whether or not data communication with the mobile unit 100 is possible based on the situation. Thereby, the external server 200 can perform data communication at appropriate timing.

In the following, a mode for realizing large-capacity data communication without delay will be described below, but this mode is applicable not only to large-capacity data communication but also to data communication in general. can be done. In addition, although a configuration for performing BDT (Background Data Transfer) as data communication will be described below, the present embodiment is not limited to this, and a configuration for performing data communication of another method may be employed.

Each configuration of the mobile communication system 1 will be described below.

(Moving body 100)
The mobile unit 100 may be a terminal (UE: User Equipment) capable of communicating with the external server 200 via the base station 400 . In this example, an in-vehicle terminal mounted on a vehicle will be described as an example of the mobile object 100, but the mobile object 100 is not limited to this, and may be a device such as a tablet or a smartphone that can be separated from the vehicle.

The mobile unit 100 can communicate with the base station 400 of the cell in which it is located, and as shown in FIG. Transfer (so-called handover), stop communication with the base station 400 of the serving cell (X mark between the mobile unit 100a and the base station 400 in FIG. 1), and the base station of the other cell 400 may be initiated. In this way, the mobile unit 100 can continue communication by switching the base station to be used for communication when the serving cell is switched.

Mobile object 100 may notify external server 200 of a data communication request via base station 400 when data communication is necessary. At this time, the data communication request may include information regarding the data size of data to be communicated, the degree of urgency of data communication, and the moving speed (running speed) of mobile object 100 . The data communication request preferably includes location information of the mobile unit 100 in addition to these pieces of information, but is not limited to this.

The core network device 300 may determine whether or not the mobile unit 100 is capable of data communication. Specifically, the core network device 300 may determine whether or not data communication is possible, and notify the determination result directly to the mobile object 100 via the external server 200 or not via the external server 200 .

(external server 200)
The external server 200 is provided separately from the core network device 300, for example, outside the core network device 300, communicates with the mobile object 100 via the core network device 300, and receives data sent from the mobile object 100. You can The external server 200 also communicates with the core network device 300 , notifies the core network device 300 of information about the mobile unit 100 , and can receive various signals from the core network device 300 . Examples of the external server 200 include, but are not limited to, a general-purpose cloud server, an on-premise server, and the like.

When external server 200 receives a data communication request from mobile unit 100, in addition to the information included in the data communication request, external server 200 sends the received identification ID of mobile unit 100 (hereinafter referred to as mobile unit ID) to the core network device. 300 may be notified.

(Core network device 300)
The core network device 300 may be a device implementing core network functions of the mobile communication system 1 . The core network device 300 may be composed of one server, or may be composed of a plurality of servers. The core network device 300 may include a core functional unit 310 and a CPF (Control Plane Function) 320 . The core network device 300 may further include an NF (Network Function) section (for example, a UPF (User Plane Function) section, not shown) other than the CPF 320 . The core function unit 310 may be a function unit that mediates between the CPF 320 or other NF units and the external server 200 . The core function unit 310 may also include a data communication control unit 311 that functions as an application function (AF) for bulk data communication (BDT). The CPF 320 may be a control unit for the core network device 300 as a whole.

Details of the core function unit 310 will be described with reference to FIG. FIG. 2 is a block diagram showing the configuration of the core network device 300 centering on the configuration of the core function unit 310. As shown in FIG.

The core function unit 310 may include a data communication control unit 311, a serving cell identification unit 312, and a conversion unit 313 (in-range cell identification unit).

Based on the mobile ID from the external server 200, the serving cell identification unit 312 may identify the cell in which the mobile 100 is serving. As a result, even if the mobile unit 100 cannot acquire its own location, it is possible to identify the serving cell. Information on the specified serving cell may be notified to data communication control section 311 .

Data communication control unit 311 may include movement identification unit 30 , determination unit 33 , notification unit 35 , and timer setting unit 37 .

The movement identifying section 30 may include a time identifying section 31 and a range identifying section 32 .

Based on the serving cell information received from serving cell identifying unit 312 and the data communication request from external server 200, time identifying unit 31 determines the time required for data communication based on the data size and data communication throughput. (estimated required time) may be specified.

The range identification unit 32 may calculate an estimated movement range within which the moving object 100 can move within the identified estimated required time.

The conversion unit 313 may identify all cells (in-range cells) included in the estimated movement range identified by the range identification unit 32 . Specifically, the conversion unit 313 may identify the cell ID of the cell (in-range cell) corresponding to the position from the position information of the estimated movement range identified by the range identification unit 32 .

A detection unit 321 included in the CPF 320 may obtain information about the congestion status of cells from each base station 400 (FIG. 1) and detect whether each cell is a congested cell. A congested cell is a cell that is in a congested state, and is congested due to reasons such as the presence of multiple mobile units. The initiation of communication refers to being in an inappropriate state. The detection unit 321 may be configured including, for example, a commercial or non-commercial KPI measurement function. Detecting unit 321 is an index related to radio resources used in each base station 400 (for example, the number of PRBs (Physical Resource Blocks) allocated for each UL/DL, the usage rate, throughput, the number of connected users of each terminal, etc.). It may be determined that the cell of the base station 400 is congested when each index exceeds a certain threshold (for example, 80% of the theoretical maximum value of each index). Alternatively, when the throughput of IP packet data from each base station 400 exceeds a certain value in UPF, it may be determined that the base station (group) 400 is congested.

The determining unit 33 uses the cell IDs of the cells within the range and the information indicating the congestion status of each cell notified from the detection unit 321 to determine whether the cells within the range are in a congested state, and determines whether data communication is possible. You can judge. In the example shown in FIG. 1, the mobile unit 100b tried to connect to an adjacent handover destination cell (ID5 in the figure) when a handover occurred, but since the cell was congested, the mobile unit 100b was not connected to that cell. It shows that it does not (x mark in the figure). Further, the determination unit 33 may determine whether data communication with the external server 200 is possible or not for the same mobile unit 100 multiple times. At this time, the timer setting unit 37 may set a backoff timer value, which is the time until the next determination by the determination unit 33 . The notification unit 35 may notify the external server 200 of the determination result of the determination unit 33 and the backoff timer value set by the timer setting unit 37 .

Mobile unit 100 notified of data communication permission from external server 200 starts data communication with external server 200 . At this time, the mobile unit 100 performs data communication with the external server 200 for the time determined by the backoff timer value, and immediately before the time elapses, notifies the external server 200 of the data communication request again. On the other hand, mobile unit 100 notified by external server 200 that data communication is not permitted does not perform data communication with external server 200 . In this case, the mobile unit 100 notifies the external server 200 of the data communication request again immediately after the time determined by the backoff timer value has passed.

According to the configuration of the mobile communication system described above, it is possible to configure an external server to be notified of whether or not data communication is possible based on the congestion state of the cells within the estimated movement range of the mobile body. Therefore, when large-capacity data communication is required, the external server can know the timing at which data communication is not interrupted during movement and large-capacity data communication can be stably realized. Furthermore, since the mobile unit can also know the timing by being notified of the timing from the external server, it is possible to avoid sending excessive data communication requests to the external server.

(processing flow)
The flow of data communication availability determination processing in the mobile communication system of the present embodiment will be described with reference to FIGS. 3 and 4. FIG. FIG. 3 is a block diagram of the network configuration of the mobile communication system in FIG. 1, looking at the relationship between one mobile unit, core network devices, and external servers. FIG. 4 is a diagram showing the block diagram of FIG. 3 in comparison with the flow of data communication permission/inhibition determination processing.

First, when the mobile 100 starts communicating with a cell of a certain base station, the CPF 320 may make the mobile 100 camp on the cell (S1 in FIG. 4).

Further, the detection unit 321 (NWDAF) may autonomously notify the data communication control unit 311 of information indicating the congestion status of each cell (S1# in FIG. 4).

The detector 321 may generate information indicating the congestion status of each cell. Information indicating the congestion status of each cell is, for example, a table T(1) in which cell IDs and congestion statuses shown in FIG. 2 are associated with each other. In the table T(1) shown in FIG. 2, the cell 500 (FIG. 1) with the cell ID "ID1" is in a congested state, and the cells 500 with the cell IDs "ID2" and "ID3" are in a congested state. indicates no The information indicating the congestion status of each cell, which is notified from the detection unit 321 to the determination unit 33, does not have to be in the form of a table, and the format is not limited as long as it includes the cell ID and the congestion status.

The detection unit 321 may autonomously notify the data communication control unit 311 of information indicating the congestion status of each cell. In one example, the detection unit 321 may notify the data communication control unit 311 of information indicating the congestion status of each cell periodically (for example, at the timing of updating the KPI measurement result (about 15 minutes at the latest)). The timing notified from the detection unit 321 to the data communication control unit 311 and the determination timing by the determination unit 33 of the data communication control unit 311 may be asynchronous.

Next, a data communication request from the mobile device 100 is transmitted to the external server 200 (S2 in FIG. 4). Serving cell identification unit 312 and data communication control unit 311 may be notified (S2# in FIG. 4). Based on the mobile unit ID included in the data communication request, serving cell identification unit 312 may identify the cell in which mobile unit 100 is located, and notify data communication control unit 311 of it.

Next, based on the serving cell information notified from serving cell identifying unit 312 and the data communication request from external server 200, time specifying unit 31 of data communication control unit 311 determines the data size and data communication , and the estimated required time may be determined from the throughput of .

In one example, a statistical fixed value may be set as the data communication throughput. As another example, a statistical value (for example, an average value, etc.) of the same time period in the past predetermined period (for example, the past 1 to 20 days) in the serving cell may be used as the data communication throughput. Note that different parameters (eg, uplink throughput, downlink throughput) may be used for download and upload. Also, the estimated required time is obtained by performing machine learning in a learning unit (not shown) in the core network device 300 using the data size, throughput, time actually required for communication, etc. in the past data communication as teacher data. It may be specified based on the results.

Then, the range identification unit 32 may calculate an estimated movement range in which the moving object 100 can travel within the identified estimated required time (S3 in FIG. 4). The range specifying unit 32 determines the radius R (for example, the unit is meters (m)) using the estimated required time specified by the time specifying unit 31 and the traveling speed information of the mobile object 100, and determines the range of the radius R. This is assumed to be the estimated moving range of the moving object 100 . Here, if the running speed is different, the radius R will be a different value. Note that the value of the radius R may be reduced when the moving body 100 is stopped, for example, in parking or in a traffic jam. For example, if the cell in which the mobile object 100 is located is the same as that used in the previous data communication availability determination process, the range identification unit 32 determines that the mobile object 100 is stationary, and reduces the value of the radius R. may

Also, if the data size can be divided, the data size for each upload can be reduced, and the upload (or download) time is shortened, so the radius R can be narrowed down. The range identification unit 32 may divide the data size based on the data communication request from the external server 200, and when the determination unit 33 determines that data communication is not possible in the previous data communication availability determination process, Data size may be divided.

Alternatively, the data communication control unit 311 may calculate the data size that can be communicated and notify the external server 200 or the mobile unit 100 of the data size. Data communication control unit 311 calculates the allowable length of time during which data communication is possible (or the start time and end time when communication is possible), and sends the length of time (or start time and end time) to external server 200 or mobile object 100. may notify you.

Alternatively, if the position information can be acquired from the moving body 100, the range specifying unit 32 may set the estimated movement range within a radius R from the position (point). On the other hand, if the location information cannot be acquired from the mobile unit 100, the location of the mobile unit within the serving cell cannot be determined.

Next, the conversion unit 313 may convert the estimated moving range into a cell ID (S4 in FIG. 4).

Next, the determination unit 33 may determine whether or not data communication is possible using the cell ID converted by the conversion unit 313 and the information indicating the congestion status of each cell notified from the detection unit 321 (FIG. 4). S5).

As an example, the determination unit 33 first determines whether or not the serving cell is congested based on the information indicating the congestion status of each cell, and if the serving cell is congested, the data It may be determined that communication is impossible. In this case, since it can be determined that data communication is impossible regardless of the result of calculation of the estimated moving range by the range identifying unit 32, it may be possible to determine that data communication is impossible by omitting S3 and S4 in FIG. When the determination unit 33 does not permit data communication, the timer setting unit 37 sets a backoff timer value according to the moving speed of the mobile unit 100 that is not permitted. For example, the timer setting unit 37 may set a value obtained by dividing a predetermined distance by the moving speed of the moving body 100 as the backoff timer value. Although the predetermined distance is not particularly limited, it can be 100 m to 10 km. The backoff timer value is a value that indicates the time until data communication availability determination processing is performed again.

Note that the timer setting unit 37 may set the backoff timer value based on a reference different from the moving speed of the moving body 100 . For example, the timer setting unit 37 may set the backoff timer value to a time period (for example, midnight of the next day) according to the service to which the mobile unit 100 is subscribed.

On the other hand, when the serving cell is not congested, the determination unit 33 may determine that data communication is possible. When the determination unit 33 permits data communication, the timer setting unit 37 may set the backoff timer value based on (i) or (ii) below.

(i) The timer setting unit 37, if there is a congested cell in the cell existing within the estimated movement range, (a) determines the nearest Based on the distance to the cell edge of the congested cell at the position and (b) the moving speed, the shortest required time to reach the cell edge of the congested cell at the closest position was calculated and calculated. The shortest required time may be used as a backoff timer value. As a result, data communication can be realized without re-determining whether or not data communication is possible while the possibility of the mobile unit 100 entering a congested cell is low.

(ii) The timer setting unit 37 may set a value obtained by subtracting a predetermined value from the time required for data communication (estimated required time) as the backoff timer value if there is no congested cell within the estimated movement range. Thereby, the timer setting unit 37 can designate the execution timing of the re-determination process in consideration of the possibility that the traveling speed increases and the moving body 100 exits out of the estimated movement range. Note that the backoff timer value may be a fixed value, or may be set according to the moving speed of the moving body 100 .

When data communication is permitted as a result of determination by the determination unit 33, the data communication control unit 311 notifies the CPF 320 of an instruction signal for establishing a BDT PDU session (S6 in FIG. 4), and establishes a BDT PDU session. you can build. Further, the data communication control unit 311 may notify the determination result to the external server 200 (S7 in FIG. 4), and the external server 200 may notify the moving body 100 of the notified determination result. At this time, if data communication is permitted, data communication (BDT communication) may be performed between mobile device 100 and external server 200 using the established BDT PDU session. Further, the determination unit 33 may manage the communication permission time and notify the external server of the communication permission and the communication permission time. In this case, the determination unit 33 may instruct the CPF 320 to end the PDU session and notify the external server 200 of the end of the communication after the allowed time has passed.

Even if data communication is not permitted as a result of the determination by the determination unit 33, the determination result is notified to the mobile unit 100 from the external server 200 after being notified to the external server 200 (S7 in FIG. 4). you can In this case, the backoff timer value set by the timer setting unit 37 may also be notified from the external server 200 to the moving object 100 .

Mobile unit 100 notified of data communication permission from external server 200 may wait for the establishment of a PDU session from core network device 300 side, and may start data communication with external server 200 after the session is established. At this time, the mobile unit 100 may perform data communication with the external server 200 for a period of time determined by the backoff timer value, and immediately before the time elapses, notify the external server 200 of the data communication request again. In the case of data communication permission, the cell ID of the estimated movement range through which mobile unit 100 passes may be recorded in the database of conversion unit 313 . When the data communication is completed, the data communication control section 311 of the core network device 300 is notified of the completion of the data communication from the mobile unit 100 via the external server 200. In response, the data communication control section 311 may notify the mobile unit 100 via the external server 200 of a confirmation notification that the notification has been received.

On the other hand, mobile unit 100 notified by external server 200 that data communication is not permitted does not perform data communication with external server 200 . In this case, the mobile unit 100 notifies the external server 200 of the data communication request again immediately after the time determined by the backoff timer value has passed. By setting the back-off timer value, data transmission can be retried at an appropriate timing without the unfavorable continuation of a state in which data communication is not permitted.

According to the processing flow described above, highly reliable data communication (BDT communication) can be realized based on information as to whether or not a congested cell exists within the estimated moving range of the moving object.

[Modification 1]
The determining unit 33 may determine whether data communication is possible or not by using the cell congestion status of each base station according to whether the data communication is upload or download. In this case, the determination unit 33 may identify whether the data communication request from the mobile unit 100 is an upload request or a download request. In the case of this example, the determination unit 33 may store in advance a list indicating cells that are in a congested state for upload and a list that indicates cells that are in a congested state for download. Then, the determination unit 33 may determine based on the presence or absence of congested cells using a list according to the identification result.

According to the present example, whether or not data communication is possible is determined individually for upload and download. That is, even if uploading is congested, if download is available, the data communication request for download can be permitted.

[Modification 2]
When mobile unit 100 notifies external server 200 of a data communication request, information on the data size of data to be communicated, the degree of urgency of data communication, and the moving speed (running speed) of mobile unit 100 is notified. It doesn't have to be. If these pieces of information are not notified from the mobile unit 100, the values corresponding to these pieces of information may be notified to the core network device 300 using predetermined values determined in advance by the external server 200. FIG. According to this example, even if information about the data size of data to be communicated, the degree of urgency of data communication, and the moving speed (running speed) of the mobile unit 100 is not provided from the mobile unit 100, data based on the congestion status Whether or not communication is possible can be realized in the same manner as in the above-described embodiment.

[Modification 3]
In the above-described embodiment, the serving cell identification unit 312 identifies the serving cell ID of the mobile unit 100, but the serving cell identification unit 312 is omitted in order to allow the serving cell ID of the mobile unit 100 to be identified. You may

That is, in this example, as shown in FIG. 5, the mobile unit 100 may be configured to notify the information of the serving cell to the external server 200 via the base station 400 .

In this way, the mobile unit 100 may be equipped with a serving cell identification unit that identifies the serving cell ID. Furthermore, during handover, if the mobile unit 100 can acquire the information of the cell ID of the handover destination cell, communication can be stopped if the handover destination is a congested cell.

[Modification 4]
Specification of the estimated moving range by the range specifying unit 32 can be narrowed down to the minimum necessary range as the information obtained from the moving object increases. If the range can be narrowed down, the number of cells to be checked for congestion is reduced, the possibility of hitting a congested cell is also reduced, and data communication can be performed for a longer period of time. For example, if the traveling direction of the vehicle is known, the range of the radius R can be narrowed down from the range of 360 degrees around the moving body 100 to the range of 180 degrees (semicircular shape). In another example, if it is known that a moving body (vehicle) is traveling on a highway, it is possible to limit the cells to those on the highway. can determine the direction of travel. As another example, if information on the moving route of the car is known, it is possible to limit the cells to those on the route. As a specific example of this case, in the case of an autonomous vehicle, the cells can be limited based on the information of the operational design domain based on the Operational Design Domain.

As yet another aspect, the radius R may be a predetermined fixed value. As a result, the estimated movement range can be determined with a certain degree of accuracy without obtaining information such as vehicle speed from the moving object 100 .

[Modification 5]
The detection unit 321 receives an inquiry from the determination unit 33 every time the determination unit 33 obtains a cell ID from the conversion unit 313, and every time it receives an inquiry, the detection unit 321 notifies the determination unit 33 of the congestion status of the cell with the cell ID. may be Even in this mode, the detection unit 321 can provide the determination unit 33 with information indicating the congestion status of each cell.

[Modification 6]
Instead of the above-described mode, the detection unit 321 prepares future predictions of each KPI of the relevant cell ID for each hour and day of the week from past statistical information, The congestion status of each cell may be returned in response to the ID and timestamp input. Even in this mode, the detection unit 321 can provide the determination unit 33 with information indicating the congestion status of each cell.

[Modification 7]
Instead of the above aspect, the determination unit 33 uses the information indicating the congestion state of the cell generated by the detection unit 321, and does not permit data communication when the cell includes even one congested cell. On the other hand, data communication may be permitted when no congested cells are included. In this case, the aforementioned backoff timer value may not be calculated either. According to this example, it is possible to quickly determine whether or not data communication is possible based on the presence or absence of congested cells.

In this example, the backoff timer value is set to a fixed value (for example, a minute), and when data communication is permitted by the determination unit 33, data communication is allowed for the period of the backoff timer value. be able to. On the other hand, if the determination unit 33 determines that data communication is not permitted, the external server 200 may be notified of the data communication request again after the backoff timer value has elapsed.

[Modification 8]
In the above-described embodiment, after the determination unit 33 permits data communication and the mobile object 100 starts data communication, when the mobile object 100 connects to a cell outside the estimated movement range specified by the range specifying unit 32, implements the above-described data communication enable/disable determination processing after the backoff timer value has elapsed based on the remaining data for which transmission has not been completed among the data being communicated, and the determination unit 33 determines whether data communication is possible. You can decide whether to accept it or not.

[Embodiment 2]
Other embodiments of the invention are described below. For convenience of description, members having the same functions as those of the members described in the above embodiments are denoted by the same reference numerals, and description thereof will not be repeated.

In the first embodiment described above, the criterion for determining whether or not the determination unit 33 permits data communication is the presence or absence of a congested cell within the estimated movement range. However, one aspect of the present invention is not limited to this. For example, in addition to the presence or absence of congested cells, the determination may be based on the number of mobile units performing data communication (in particular, large-capacity data communication) in cells within the estimated movement range.

In the present embodiment, the determination unit 33 permits data communication to M units of mobile units when there is a congested cell that is congested in a predetermined physical area centered on the mobile units, if there is no congested cell in the predetermined physical area, permitting the data communication to N mobile units;
M and N have the following relationship:
N > M
may be configured so that

The predetermined physical area range here can be defined as, for example, a radius Rkm centered on the moving body. As an example, Rkm may be 100m to 10km.

As for the relationship between M and N, M can be 1 and N can be 100, for example. In addition, if the moving object is a vehicle, N<10000 and M<1000 for a physical area of 1 km ² . These are just examples, and N and M may be set as appropriate. It is sufficient if the number of mobile units permitted to perform data communication is larger when there is no congested cell that is being used.

The number of mobile units currently permitted for data communication can be managed by the management server in association with each congested cell and a predetermined geographical area. The number of units may be counted up, for example, when data communication (large-capacity data communication) is permitted for a certain mobile unit. Conversely, when the period of permitted data communication expires, or when the management server receives a message indicating the completion of data communication from a mobile unit for which data communication is permitted, the number of mobile units may be counted down.

[Embodiment 3]
Other embodiments of the invention are described below. For convenience of description, members having the same functions as those of the members described in the above embodiments are denoted by the same reference numerals, and description thereof will not be repeated.

In this embodiment, a mobile unit for which data communication is not permitted in response to a data communication request and a mobile unit for which data communication is to be temporarily suspended are stored and stored as a queuing list on the core network device side. At a predetermined timing, the core network device may request the external server to download data from mobile units in the list. Specifically, the queuing list is held and managed in data communication control section 311 . FIG. 6 shows an example of the queuing list.

The queuing list T(2) in FIG. 6 includes, for each mobile unit, information on the serving cell, information on the attributes of the mobile unit, information on recommended time periods for data communication, information on the priority of data communication, and , information on the number of times data communication has not been permitted (number of retries) may be included.

When the determination unit 33 determines that data communication is not permitted, the data communication control unit 311 may add the information of the determination target mobile to the queuing list T(2).

When the data communication control unit 311 shown in FIG. 2 receives a data communication request from the mobile unit 100 listed in the queuing list T(2), the movement identification unit 30 identifies the estimated required time and the estimated movement range. , identification of the cell ID by conversion unit 313, detection by detection unit 321, and determination by determination unit 33 are not performed, and a notification of disapproval of data communication may be sent to mobile unit 100 as a notification of acceptance completion of the data communication request. .

Then, the data communication control unit 311 may notify the data communication permission according to the "data communication priority order" of the queuing list T(2). In this example, the implementation timing can be set according to the network load of the core network device 300 and the number of queuing devices. Extend the processing interval of For example, if 100 moving bodies are listed in the queuing table, it is determined to be once per second, and if 1000 vehicles are listed, it is determined to be 10 seconds. Note that the mobile unit that has received data communication disapproval notifies the external server 200 of the data communication request and starts again. At that time, the backoff timer value is not used.

As a specific example, an example of prioritization of the queuing list T(2) is shown in FIG. As in the score table 1000 shown in FIG. 7, the score for each element may be determined in advance. FIG. 8 shows the calculation of the priority score of each moving object in the queuing list T(2) of FIG. 6 using this score. As in table T(3) shown in FIG. 8, the higher the priority score, the higher the priority.

Note that different queuing lists may be used depending on whether the data communication is upload or download.

In the aspect using the queuing list T(2) described above, when the determination unit 33 determines whether or not to permit data communication, the determination result obtained by the determination unit 33 of the first embodiment is received, and data communication is performed. If it is permissible, a notification permitting data communication may be transmitted to mobile units having a higher data communication priority at the aforementioned implementation timing.

According to the mobile communication system of the present embodiment, data communication (especially large-capacity data communication) can be stably realized according to the data communication priority.

[Modification 1]
The data communication control unit 311 also adds the information of the mobile unit to the queuing list T(2) when the mobile unit with the subscriber information "late night" flag requests data communication during the daytime. good too. The subscriber information "late night zone" flag is managed for each mobile unit, and can be given to a user who preferentially communicates in the late night zone. Granting of this "late night zone" can be reflected in the price plans of mobiles (e.g. mobile devices), and mobiles to which "late nights zone" is granted are billing plans for mobiles that do not have "late night zone". can be set cheaper than

[Modification 2]
Wearable terminals (mobiles) that operate with a small capacity battery are relatively affected by battery consumption due to data communication. Therefore, as shown in the queuing list T(2) in FIG. 6, the remaining battery level may be listed together with the type of mobile object.

In this modification, in addition to the score list shown in FIG. 7, a list T (4 ) may be included. Note that the "interruption" of the score means that data communication is interrupted because there is not enough remaining capacity for data communication. FIG. 10 shows a data communication priority list T(5) obtained by calculating the priority score of each mobile object in the queuing list T(2) of FIG. 6 using the score of the list T(4) of FIG. . As shown in FIG. 10, the higher the priority score, the higher the priority.

According to aspects of the present embodiment and modifications, it is possible to perform priority control according to the attribute of a moving object. In other words, if the mobile object for which data communication is not permitted is a "high priority" vehicle, the retry right can be given earlier than the "middle priority" vehicle.

In addition, it is also possible to grasp the congestion situation depending on the time zone, and allow vehicles with low priority to communicate during the time zone (off-season) when the network is not busy. As an example, the detection unit 321 may accumulate congestion conditions in all time slots during the day and night, and perform machine learning using this as teacher data to estimate the time slots when the network is free. Such a time period may be late at night or early in the morning, for example. When a vehicle to which the "off-season flag" is given as a vehicle attribute receives a data communication request during a period other than the off-season, the data communication control unit 311 causes the determination unit 33 to perform queuing without making a determination. let me

Further, by storing the number of times data communication is determined to be disallowed and the disallowed cell ID, subsequent retry control can be changed and retry control can be advanced. Examples of changing the retry control include narrowing the radius R (determining that the vehicle is parked or stopped) if the same congested cell is disallowed many times, or changing the time period.

[Embodiment 4]
Other embodiments of the invention are described below. For convenience of description, members having the same functions as those of the members described in the above embodiments are denoted by the same reference numerals, and description thereof will not be repeated.

In this embodiment, in the mobile communication system 1 shown in FIG. 11, it is assumed that there are data communication requests from a plurality of mobile units 100a, 100b, and 100c. Data communication control unit 311 of core network device 300 records the cell IDs of all cells included in the estimated moving range of each of mobile units 100a, 100b, and 100c (the recording table is shown in table T(6) in FIG. 11). .

Also, in the present embodiment, 1 may be added to "Possibly connected cars" for all cells within the estimated moving range. "Possibly connected cars" can be set such that when there are more than a certain threshold of M cells, no more cars are accepted. In other words, when the cell is included in the estimated range of movement of the subsequent moving object, the determining unit 33 may determine that data communication is not possible. FIG. 12 shows a table T(7) that associates "possibly connected cars" with cell IDs. As shown in table T(7) in FIG. 12, the cell with cell ID "1" has "Possibly connected cars" of 1, that is, the threshold for the number of mobile units that can be connected to the cell with cell ID "1" is 1. Therefore, based on the table T(6) in FIG. 11, the moving object that includes the cell with the cell ID “1” within the estimated moving range is one with the moving object ID “1”, and the cell ID that satisfies the threshold is A cell with "1" is regarded as a congested cell, and if another mobile that subsequently requests data communication includes a cell with a cell ID of "1" within its estimated range of movement, the other mobile's data communication is permitted. may not.

Note that when the data communication is completed, 1 may be subtracted from "Possibly connected cars" for the cells included in the estimated moving range of the mobile.

As described above, according to the present embodiment, the determination unit 33 determines in advance that the certain mobile body performs data communication within the cells regarding all the cells included in the estimated moving range of the certain mobile body. In addition, a threshold for the number of mobile units with which data communication is possible is set in all of the cells, and data communication by new mobile units in the area is not permitted in cells where the threshold has been reached. As a result, it is possible to provide a mobile communication system capable of appropriately coping with a plurality of mobile units and performing stable data communication.

[Embodiment 5]
Other embodiments of the invention are described below. For convenience of description, members having the same functions as those of the members described in the above embodiments are denoted by the same reference numerals, and description thereof will not be repeated.

In the above-described embodiment, a data communication request from a mobile unit is used as a trigger to determine whether or not data communication is possible. On the other hand, in the present embodiment, the core network device takes the lead in determining whether or not data communication is possible without requiring the trigger, and notifying it to the mobile unit.

FIG. 13 is a block diagram showing a schematic configuration of the mobile communication system 1A of this embodiment. In the data communication control unit 311A of the core network device 300A shown in FIG. 13, there are mobile units for which data communication is not permitted, mobile units for which data communication is to be temporarily suspended, and the priority of these mobile units. An associated queuing list T(8) may be maintained and managed.

The data communication control unit 311A may transmit a data communication permission notification via the external server 200 to mobile units with high priority based on the retained queuing list T(8) (( i)). In the queuing list T(8) of FIG. 13, data communication is permitted to the mobile unit 100 with the mobile unit ID “200” and the priority level “1” regardless of whether or not there is a data communication request from the mobile unit 100 concerned. A notification may be sent ((ii) in FIG. 13). The mobile unit 100 that has received the data communication permission notification may notify the data communication control unit 311A of the core network device 300A of the data communication request via the external server 200 ((iii) in FIG. 13). The data communication control unit 311 may start data communication between the external server 200 and the mobile unit 100 in response to receiving this notification.

An aspect of the present embodiment is, for example, using a time period when the load on the core network device is relatively light, and the like, under the leadership of the core network device 300. Allows body data communication. As a result, it is possible to construct a highly reliable mobile communication system without missing data to be communicated.

[Embodiment 6]
Other embodiments of the invention are described below. For convenience of description, members having the same functions as those of the members described in the above embodiments are denoted by the same reference numerals, and description thereof will not be repeated.

This embodiment is similar to the fifth embodiment described above, and is performed at the initiative of the core network device. Specifically, in the present embodiment, it is possible to inquire whether or not data communication is necessary for a mobile object existing in a specific cell.

FIG. 14 is a block diagram showing a schematic configuration of the mobile communication system 1B of this embodiment. The data communication control unit 311B shown in FIG. 14 may hold and manage a table T(9) in which whether or not the communication load is low is associated with the cell ID. Further, the data communication control unit 311B may hold and manage a table T(10) in which mobile units located in a low-load cell are associated with the cell ID of the low-load cell. .

Table T(9) may be created by CPF 320 (low load area identification unit) of FIG. 1 of core network device 300 . Specifically, since the detector 321 constantly monitors the load in each cell, the CPF 320 acquires the current load of each cell from the detector 321 and compares it with a predetermined threshold to obtain A cell ID of a cell that is lightly loaded may be identified. The CPF 320 (low load area identification unit) identifies an area where the cell load state is low in a wide range, and identifies the cell ID of the cell corresponding to that area. A wide range can be, for example, 100 m to 100 km around the serving cell, but is not limited to this. The CPF 320 creates a table T3 by listing the identified cell IDs.

Table T(10) is created by data communication control section 311B. Specifically, the determination unit 33B of the data communication control unit 311B acquires the table T3, identifies the low-load cell ID, and identifies the mobile unit 100 located within the cell of that cell ID.
The data communication control unit 311B may use the table T(10) to identify mobile units that are located in a cell with a low load. In the example of FIG. 14, the mobile with mobile ID "100" is located in the cell with cell ID "1", the mobile with mobile ID "200" is located in the cell with cell ID "2", It may be specified that the mobile with mobile ID "300" is located in the cell with cell ID "3".

Next, data communication control unit 311B transmits a signal inquiring whether data communication is necessary to each of the mobile units with mobile unit IDs "100", "200" and "300" via external server 200. Good ((i) and (ii) in FIG. 14).

Each of the mobile units with mobile unit IDs "100", "200", and "300" receives the signal and, if data communication is necessary, sends a data communication request to the core network device 300 via the external server 200. The communication control unit 311 may be notified ((iii) in FIG. 14). Data communication control section 311 may start data communication between external server 200 and mobile unit 100 in response to this notification.

According to the aspect of the present embodiment, the core network device 300 can take the lead in confirming whether or not data communication is necessary with respect to a moving object, by effectively utilizing a time zone or the like when the load on the core network device is relatively light. As a result, the server load can be distributed, and a mobile communication system that realizes stable communication can be constructed by avoiding the problem of data communication caused by an excessive server load.

[Embodiment 7]
Other embodiments of the invention are described below. For convenience of description, members having the same functions as those of the members described in the above embodiments are denoted by the same reference numerals, and description thereof will not be repeated.

In the first embodiment described above, as shown in FIG. 2, the core network device 300 holds the table T(1) (information indicating the congestion status of each cell) in which the congestion status of cells is associated with the cell ID. and may be managed. On the other hand, this embodiment shows an example of a mode in which both the core network device 300 and the mobile unit 100C hold the list.

FIG. 15 shows an overview of the mobile communication system 1C of this embodiment. In the mobile communication system 1C shown in FIG. 15, the data communication control unit 311C receives the notification of the data communication request from the mobile unit 100C and specifies the estimated required time and the estimated moving range in the same manner as in the first embodiment. Then, based on the table T(1) obtained from the detector 321, it may be determined whether to permit or not to permit data communication.

Next, in the step of notifying the determination result to the mobile unit 100C via the external server 200, in the present embodiment, the data communication control unit 311C controls the determination result, the PDU session number for data communication, and the detection unit Table T(1) obtained from 321 may be notified to the moving object 100C.

The mobile unit 100C that has received the notification may wait for the period of the backoff timer value, as in the case of the first embodiment, if the determination result indicates non-permission.

On the other hand, if the obtained determination result indicates permission, the mobile unit 100C performs data communication based on the obtained PDU session number for data communication using the PDU session for data communication corresponding to the number. can be started.

In this embodiment, since the mobile unit 100C acquires the table T(1), it is possible for the mobile unit 100C to check whether the cell in which it is located is a congested cell. Therefore, as shown in FIG. 16, when the mobile unit 100C is handed over to an adjacent cell, the mobile unit 100C can autonomously confirm (determine) whether or not the adjacent cell is a congested cell in the confirmation unit 101. .

Specifically, as shown in (a) in FIG. 16, when receiving a handover command notification from CPF 320 of core network device 300, mobile unit 100C performs handover based on table T(1). The confirmation unit 101 may determine whether the service cell is a congested cell. Then, if the cell is not a congested cell, data communication may be continued in the serving cell to which the handover has been made. On the other hand, if the serving cell to which handover is made is a congested cell, the mobile unit 100C may notify the core network device 300 of the PDU session release ((b) in FIG. 16). This interrupts data communication. After the suspension, when another cell is handed over, if the confirmation unit 101 determines that the cell is not a congested cell, the core network device 300 is requested to resume the PDU session, and the suspended data communication is resumed. It can be restarted in a cell.

Further, if the mobile object 100C has the table T(1) as in the present embodiment, when the mobile object 100C connects to a cell outside the estimated movement range after starting data communication in the first embodiment, the cell is a congested cell or not can be confirmed on the mobile unit 100C side (confirmation unit 101). At this time, if the connected cell is not in the table T(1), the data communication is interrupted, and the remaining data for which communication has not been completed is processed for the data communication request from the mobile unit described in the first embodiment. can be executed.

It should be noted that mobile unit 100C is preferably configured to receive notification of table T(1) from data communication control unit 311C periodically or under specific conditions. As a result, the mobile unit 100C side can hold the table T(1) reflecting the timely congestion status.

[Modification]
Even in the aspect of limiting the number of devices for data communication in the fourth embodiment described above, the mobile device can determine whether or not communication is possible based on the list held by the mobile device as in the present embodiment.

FIG. 17 shows the mobile communication system 1D of this example. Note that FIG. 17 emphasizes portions that are different from the mobile communication system of FIG. 11 of the fourth embodiment. Also in the mobile communication system of this example, the determination result by the determination unit 33 of the core network device 300, the PDU session number for data communication, and the table T(1) obtained from the detection unit 321 as in this embodiment. may be notified to the mobile object 100 .

The mobile unit 100 that has received the notification may wait for the period of the backoff timer value if the determination result indicates non-permission.

On the other hand, if the obtained determination result indicates permission, the mobile unit 100 performs data communication based on the obtained PDU session number for data communication using the PDU session for data communication corresponding to the number. to start. When the data communication is completed, 1 is subtracted from "Possibly connected cars" for the cell used for communication based on the table T(1) held by the mobile unit 100C.

[Embodiment 8]
Other embodiments of the invention are described below. For convenience of description, members having the same functions as those of the members described in the above embodiments are denoted by the same reference numerals, and description thereof will not be repeated.

In the first embodiment described above, the core network device 300 (FIG. 2) holds and manages a list in which cell congestion states are associated with cell IDs. On the other hand, in the present embodiment, an example of a mode in which the mobile object 100D holds the list is shown.

FIG. 18 shows an overview of the mobile communication system of this embodiment. In the present embodiment, the function of the determination unit 33 in the first embodiment is performed by the moving object 100D. In other words, the moving body 100D may have a determining section 133 having the same function as the determining section 33 in the first embodiment.

In the data communication control unit 311D, upon receipt of the data communication request from the moving object 100, the estimated required time and the estimated moving range may be specified as in the first embodiment. Further, the data communication control unit 311D may generate a table T(1) limited to cells included in the estimated movement range from the table T(1) provided by the detection unit 321. ) may be notified to the moving object 100</b>D via the external server 200 . In the mobile unit 100D that has acquired the table T(1), the determination unit 133 uses the table T(1) to determine whether the serving cell is a congested cell. you can start.

In this embodiment, since the mobile unit 100D acquires the table T(1), the mobile unit 100 can confirm whether the cell in which it is located is a congested cell. Therefore, as shown in FIG. 19, when the mobile unit 100 is handed over to an adjacent cell, the mobile unit 100 can autonomously determine whether the adjacent cell is a congested cell.

Specifically, as shown in (a) of FIG. 19 , when the moving object 100 receives a handover command notification from the CPF 320 of the core network device 300, the determining unit 133 determines that the serving cell to which the handover is performed is , is included in table T(1). As a result, if it is included in the table T(1), it is possible to autonomously determine whether or not the handed-over serving cell is a congested cell. Then, if the cell is not a congested cell, data communication may be continued in the serving cell to which the handover has been made. On the other hand, if the serving cell to which handover is made is a congested cell, the mobile unit 100 may notify the core network device 300 of the PDU session release ((b) in FIG. 19). This interrupts data communication. After the suspension, when another cell is handed over, if it is determined that the cell is not a congested cell, the core network device 300 is requested to resume the PDU session, and the suspended data communication is resumed in the cell. you can

Update data of the congestion information may be transmitted to the moving body 100 at the timing when the congestion information of the cell is updated from the detection unit 321 to the notification unit 35 .

[Embodiment 9]
Other embodiments of the invention are described below. For convenience of description, members having the same functions as those of the members described in the above embodiments are denoted by the same reference numerals, and description thereof will not be repeated.

In the above-described third embodiment, data communication propriety determination is performed using the queuing list T(2) (FIG. 6). In relation to this, the present embodiment relates to data communication with a vehicle (moving body) that is powered by a battery such as an electric vehicle. Such a vehicle cannot run if the battery runs out. Therefore, it is necessary to consider the remaining amount of the battery even in data communication that consumes the battery. Therefore, an example of a mode in which data communication is controlled in consideration of the remaining battery level of the vehicle will be shown.

Specifically, the mobile communication system of the present embodiment monitors whether the remaining battery level of a vehicle (mobile body) falls below a predetermined threshold. As a general rule, list them on a queuing list so that data communication is not permitted.

On the other hand, considering the urgency of data communication, when it becomes necessary to transmit data of high urgency, the data communication priority included in the queuing list T(2) (FIG. 6) is raised. As a result, it is possible to prepare conditions that facilitate data communication, and it is possible to retrieve emergency data from the vehicle before the battery runs out.

For data with a low degree of urgency, queuing is continued and data communication is put on hold until the remaining battery level recovers to a certain amount, that is, until the low battery level state is resolved. As a result, it is possible to avoid further battery consumption due to executing data communication of data with a low degree of urgency.

[Embodiment 10]
The present invention also includes a data communication system comprising a mobile and a server for data communication with the mobile. A data communication system according to an embodiment of the present invention will be described below with reference to FIG.

FIG. 20 is a block diagram showing a schematic configuration of a data communication system according to this embodiment. As shown in FIG. 20, a data communication system 600 includes a mobile unit 100, a server 200' that performs data communication via the mobile unit 100, a base station 400, and a core network device 300. The server 200' , a communication unit 210 (receiving unit) for receiving from the core network device 300 the availability of the data communication based on the cell congestion status of the plurality of base stations 400 and the cell in which the mobile unit 100 is located.

Note that the server 200′ in FIG. 20 has functions equivalent to those of the external server 200 described in the above-described embodiment. For example, in the external server 200 shown in FIG. The communication unit 210 in FIG. 20 receives the result.

The communication unit 210 is configured to receive the data communication request notified from the mobile unit 100 in the above-described embodiment, and is configured to notify the mobile unit 100 of the determination result as to whether or not data communication is possible.

Furthermore, the server 200 ′ includes a main control section 220 that controls the communication section 210 .

The mobile unit 100 is also similar to the mobile unit 100 described in the above embodiments, and includes a communication unit 140 that transmits data communication requests to the communication unit 210 of the server 200'. The communication unit 140 receives the determination result of whether or not data communication is possible, notified from the communication unit 210 of the external server 200 .

Further, the mobile body 100 includes a main control section 150 that controls the communication section 140 .

According to the data communication system 600 of the present embodiment, data communication is performed between the server and the mobile object based on the determination result of whether or not data communication is possible based on the congestion state of the cells within the estimated movement range of the mobile object. be able to. Therefore, when large-capacity data communication is required, it is possible to realize a data communication system that stably realizes large-capacity data communication without interrupting data communication during movement. Furthermore, since the mobile unit can also know the timing by being notified of the timing from the external server, it is possible to prevent excessive data communication requests from being sent to the server.

[Additional notes]
The present invention is not limited to the embodiments and modifications described above, but can be modified in various ways within the scope of the claims, and can be obtained by appropriately combining technical means disclosed in different embodiments. Any embodiment is also included in the technical scope of the present invention.

〔summary〕
A core network device according to an aspect of the present invention is a core network device connected to a server and a plurality of base stations, wherein the above A determination unit that determines whether or not data communication between the mobile unit and the server is possible, and a notification unit that notifies the server of a determination result of the determination unit.

A mobile communication system according to an aspect of the present invention includes a core network device having the above configuration, the server, and the mobile unit.

Further, a data communication system according to an aspect of the present invention is a data communication system comprising: a mobile body; and a server that performs data communication via the mobile body, a base station, and a core network device, The server includes a receiving unit that receives from the core network device the permission/prohibition of the data communication based on the cell congestion status of the plurality of base stations and the cell in which the mobile unit is located.

1, 1A, 1B, 1C, 1D mobile communication system 30 movement identification unit 31 time identification unit 32 range identification unit 33, 33B, 133 determination unit 35 notification unit 37 timer setting unit 100, 100a, 100b, 100c, 100C, 100D Mobile object 101 Confirmation unit 200 External server (server)
200' server 210 communication unit (receiving unit)
300, 300A core network device 310 core function units 311, 311A, 311B, 311C, 311D data communication control unit 312 serving cell identification unit 313 conversion unit (in-range cell identification unit)
320 CPF
321 detector 400 base station 500 cell 600 data communication system

Claims (14)

A core network device connected to a server and a plurality of base stations,
a determination unit that determines whether or not data communication between the mobile unit and the server is possible based on the cell congestion status of each base station and the cell in which the mobile unit is located;
a notification unit that notifies the server of the determination result of the determination unit ;
a range identification unit that identifies an estimated movement range in which the mobile object is estimated to move within the time required for the data communication;
an in-range cell identifying unit that identifies cells existing within the estimated movement range;
a detection unit for detecting whether there is a congested congested cell and acquiring the congestion status of the cell of each base station;
with
The determination unit uses the cell identified by the in-range cell identification unit and the congestion status of the cell of each base station acquired by the detection unit, and uses the cell identified by the in-range cell identification unit to determine the Determining whether the data communication of the mobile object is possible,
Core network equipment. The determination unit determines whether or not data communication with the server is possible for the same mobile object a plurality of times,
Further comprising a timer setting unit that sets a backoff timer value that is the time until the next determination by the determination unit,
The core network device according to claim 1. A core network device connected to a server and a plurality of base stations,
a determination unit that determines whether or not data communication between the mobile unit and the server is possible based on the cell congestion status of each base station and the cell in which the mobile unit is located;
a notification unit that notifies the server of the determination result of the determination unit;
with
A range identification unit that identifies an estimated movement range in which the mobile object is estimated to move within the time required for the data communication.
further comprising
The determination unit determines whether or not data communication with the server is possible for the same mobile object a plurality of times,
A timer setting unit that sets a backoff timer value that is the time until the next determination by the determination unit
further prepared,
When the determination unit permits the data communication and there is a congested cell in the cell existing within the estimated movement range,
The timer setting unit determines the moving speed of the moving object and the distance from the cell edge of the serving cell or the position of the moving object in the serving cell to the cell edge of the congested cell at the closest position. Based on this, calculate the shortest required time to reach the cell edge of the congested cell at the closest position, and set the calculated shortest required time as the backoff timer value,
The notification unit notifies the server of the backoff timer value set by the timer setting unit.
Core network equipment. A core network device connected to a server and a plurality of base stations,
a determination unit that determines whether or not data communication between the mobile unit and the server is possible based on the cell congestion status of each base station and the cell in which the mobile unit is located;
a notification unit that notifies the server of the determination result of the determination unit;
with
A range identification unit that identifies an estimated movement range in which the mobile object is estimated to move within the time required for the data communication.
further comprising
The determination unit determines whether or not data communication with the server is possible for the same mobile object a plurality of times,
A timer setting unit that sets a backoff timer value that is the time until the next determination by the determination unit
further prepared,
When the determination unit permits the data communication and there is no congested cell in the cells existing within the estimated movement range,
The timer setting unit sets a value obtained by subtracting a predetermined value from the required time as the backoff timer value,
The notification unit notifies the server of the backoff timer value set by the timer setting unit.
Core network equipment. A core network device connected to a server and a plurality of base stations,
a determination unit that determines whether or not data communication between the mobile unit and the server is possible based on the cell congestion status of each base station and the cell in which the mobile unit is located;
a notification unit that notifies the server of the determination result of the determination unit;
with
A range identification unit that identifies an estimated movement range in which the mobile object is estimated to move within the time required for the data communication.
further comprising
The determination unit determines whether or not data communication with the server is possible for the same mobile object a plurality of times,
A timer setting unit that sets a backoff timer value that is the time until the next determination by the determination unit
further prepared,
the timer setting unit, when the determination unit does not permit the data communication, sets the back-off timer value according to the moving speed of the unpermitted mobile body;
The notification unit notifies the server of the backoff timer value,
Core network equipment. With respect to the mobile body that the determination unit permits the data communication and has started the data communication, after the back-off timer value has elapsed, the remaining data of the data that is being communicated and the communication of which has not been completed. , the determination unit determines again whether data communication of the mobile unit is possible;
A core network device according to any one of claims 2 to 5. The determination unit does not permit the data communication when at least one of the cells identified by the serving cell and the in-range cell identification unit is a congested cell,
The core network device according to claim 1. The determination unit determines whether the data communication is possible or not, using a cell congestion status of each base station according to whether the data communication is upload or download.
The core network device according to claim 1. A core network device connected to a server and a plurality of base stations,
a determination unit that determines whether or not data communication between the mobile unit and the server is possible based on the cell congestion status of each base station and the cell in which the mobile unit is located;
a notification unit that notifies the server of the determination result of the determination unit;
with
The determination unit permits the data communication to M mobile units when there is a congested cell congested in a predetermined physical area centered on the mobile unit, and the predetermined permitting the data communication to N mobile units when no congestion cells exist in the physical area;
M and N have the following relationship:
N > M
holds,
Core network equipment. A core network device connected to a server and a plurality of base stations,
a determination unit that determines whether or not data communication between the mobile unit and the server is possible based on the cell congestion status of each base station and the cell in which the mobile unit is located;
a notification unit that notifies the server of the determination result of the determination unit;
with
The cell congestion status of each base station includes a queuing list indicating mobile units whose permission or denial of data communication is to be temporarily suspended,
The queuing list includes, for each mobile unit, information on a serving cell, information on the attributes of the mobile unit, information on recommended time periods for data communication, information on the priority of data communication, and information on the priority of data communication. contains information about the number of times not allowed,
Core network equipment. The determining unit, when there are a plurality of mobiles in one of the serving cells, selects the data of a mobile having a higher priority for data communication among the plurality of mobiles based on the queuing list. permitting communication and not permitting said data communication of said low-priority mobile;
The core network device according to claim 10. the moving body comprises a battery,
the priority of the data communication is determined based on at least the type of the mobile object and a score according to the remaining battery level;
The core network device according to claim 11. With respect to all cells included in the estimated movement range of a certain mobile, the determination unit predetermines that the certain mobile will perform data communication within the cells, Set a threshold for the number of mobile units that can communicate, and do not allow data communication for new mobile units that have reached the threshold.
The core network device according to claim 1. further comprising a low load area identifying unit that identifies an area where cells with a communication load of a predetermined value or less are clustered over a predetermined range,
The determination unit determines that data communication is possible for a mobile station located in a cell in the area identified by the low load area identification unit.
The core network device according to claim 1.

Images