JP2016021624A - Terminal detection method for information processor, information processor, and information processing system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To identify whether or not each terminal is a terminal which transmits an intensively generated resource setting request on the basis of the reception status of a user packet to be transmitted from each terminal.SOLUTION: In a terminal detection method of an information processor connected to a network for receiving a resource setting request to be transmitted from each terminal in which a resource for packet transmission is unset to set the resource, and for relaying a packet to be transmitted from each terminal, the information processor determines whether or not the packet transmitted from each terminal has been received after the lapse of a predetermined time from the previous reception time, and stores, in a storage device, the number of the packets received after the lapse of the predetermined time and the identifier of each terminal of the transmission source of the packet received after the lapse of the predetermined time at each time zone by using the result of determination.SELECTED DRAWING: Figure 10

Description

  The present disclosure relates to a terminal detection method for an information processing device, an information processing device, and an information processing system.

  In a Long Term Evolution (LTE) network formed by a radio network and a core network, when a terminal (called User Equipment: UE) communicates, a session for communicating with the other party over the radio network and the core network Is established. If there is no communication for a certain period after the session is established (user packets are not transferred), the resources of the radio network and core network allocated for the session are released.

  If resources are released when the terminal resumes communication (transmits a user packet), the terminal transmits a resource reset request message to the terminal signal processing device in the core network. Upon receiving the resource reset request, the terminal signal processing apparatus sends a resource reset request to the packet relay apparatus that relays the user packet of the terminal. The packet relay device performs resource reconfiguration (reassignment). As a result, the terminal can transmit a user packet.

  By the way, some applications installed in the terminal automatically transmit user packets at a certain time (fixed time). If the resource for transmitting the user packet is released at the regular time, the terminal sends a resource reset request to the terminal signal processing device as described above.

  When the number of terminals in which the application is installed is not small, as shown in FIG. 12, a plurality of terminals simultaneously transmit resource reset requests, and the plurality of resource reset requests are concentrated on the terminal signal processing apparatus. It can happen to arrive. Due to such concentration of resource resetting requests, the load related to the resource resetting processing in the terminal signal processing device and the packet relay device increases in a burst manner, which may cause congestion of the processing.

  Processing for avoiding the burst load increase and congestion as described above is performed. For example, the time at which resource reset requests are intensively generated and the terminal that transmits the resource reset request are grasped by burst monitoring on the C plane. The device on the core network side calls each terminal and urges transmission of a resource resetting request before the certain time comes. Each terminal is called with the timing shifted. In this way, the timing at which resource reset requests arrive at the terminal signal processing device is distributed, and the number of resource reset requests that arrive at the certain time is reduced.

JP 2000-354065 A JP 2003-009229 A

The implementation of the above call processing has the following problems. Among the terminals that have been determined to be called on the core network side, there may be included terminals in which the operation stop of the application is set or applications that have been deleted. Since such a terminal does not transmit a resource reset request even at a certain time, it is not necessary to perform the above calling process.

  However, in the monitoring of the C plane, the concentration of resource reset requests is avoided by executing the calling process, so it has been impossible to determine whether the calling process is actually necessary for each terminal.

  An object of the present disclosure is to provide a technique that enables detection of a terminal that transmits a resource setting request that is intensively generated by each terminal based on reception status of user packets transmitted from each terminal.

The present disclosure accepts a resource setting request transmitted from each terminal for which no packet transmission resource is set, performs resource setting, and then processes information connected to a network that relays a packet transmitted from each terminal. A terminal detection method for a device,
The information processing apparatus is
Determining whether a packet transmitted from each terminal is received after a predetermined time from the previous reception time;
Using the determination result, the number of packets received after elapse of the predetermined time and the identifier of each terminal of the transmission source of the packet received after elapse of the predetermined time are stored in a storage device for each time period. This is a terminal detection method for an information processing apparatus.

  According to the present disclosure, it is possible to detect whether each terminal is a terminal that transmits resource setting requests that are generated intensively based on the reception status of user packets transmitted from each terminal.

1 shows a configuration example of a network system according to an embodiment. 2 shows a hardware configuration example of the S-GW shown in FIG. FIG. 3 is a diagram schematically illustrating an operation performed by the S-GW when the CPU executes a program. FIG. 4 is a diagram schematically showing an operation based on each process of the CPU shown in FIG. FIG. 5 is a flowchart illustrating an example of the no-communication monitoring process executed by the CPU. FIG. 6 is a flowchart illustrating an example of burst suppression control processing executed by the CPU. FIG. 7 is a diagram illustrating a data structure example of the user ID table. FIG. 8 is a diagram illustrating a data structure example of the burst management DB. FIG. 9 is a diagram illustrating a data structure example of the user behavior management DB. FIG. 10 is a sequence diagram illustrating an operation example 1 in the embodiment. FIG. 11 is a sequence diagram illustrating an operation example 1 in the embodiment. FIG. 12 is an explanatory diagram of related technology.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. The configuration of the embodiment is an exemplification, and the present invention is not limited to the configuration of the embodiment.

In the following embodiments, bursts occurring on or possibly occurring on the C plane (control plane) side by analyzing the behavior (packet reception status) on the U plane (user plane) side in the network. A network system capable of estimating a load and performing processing for burst suppression will be described.
<Example of network system configuration>
FIG. 1 is a diagram illustrating a configuration example of a network system according to the embodiment. In FIG. 1, the network system illustrates an LTE network system. The LTE network includes the Evolved Universal Terrestrial Radio Network (eUTRAN) of the wireless network 1 and the core network 2.
Evolved Packet Core (also called EPC: SAE (System Architecture Evolution)).

  The wireless network 1 is formed by wireless base stations (base stations: called eNodeB (eNB)) 3. The base station 3 is wirelessly connected to the terminal 4 through a random access procedure with the wireless terminal (terminal: UE) 4.

  The core network 2 includes a Mobility Management Entity (MME) 5 that handles the C plane, a serving gateway (S-GW) 6 that handles user packets, and a packet data network gateway (P-GW) 7. Further, in the core network 2, an access management device 9 that executes a burst suppression process described later is disposed and connected to the S-GW 6. A user packet is an example of a “packet”.

  The MME 5 is a C-plane access gateway that handles network control. The MME 5 is a terminal signal processing device that communicates with the terminal 4 via the base station 3, and performs call control (call establishment and call disconnection) of the terminal 4. The MME 5 also performs sequence control and handover control, position management when the terminal 4 is on standby (position registration of the wireless terminal), call (paging) when the base station 3 is received, authentication of the terminal 4 (NAS (Non Access Stratum) )) Etc. The MME 5 is an example of a “device that controls resource settings”.

  The S-GW 6 is a gateway (packet relay device) that relays user packets, and performs processing for connecting LTE user data to a 2G (for example, GSM) or 3G (W-CDMA) system. The S-GW 6 is an example of an “information processing device”.

The P-GW 6 is a gateway for the packet data network (PDN) 8 and is a gateway for connecting user packets to an external network (Internet or intranet) connected to the PDN 8. The P-GW 6 performs charging data collection, quality of service (QoS) control, packet filtering, and the like.

The terminal 4 is an information processing apparatus (communication device) having a wireless communication function, such as a smartphone or a tablet terminal. The terminal 4 performs wireless connection (Radio Resource Connection (RRC) connection) with the base station 3 and exchanges control signals (C-plane communication) with the base station 3 and the MME 5.

  Specifically, the terminal 4 wirelessly connected to the base station 3 performs a process for registering the terminal 4 in the LTE network, called an attach procedure. The attach procedure is performed on the C plane. The terminal 4 sends a control signal called an attach request signal to the MME 5 via the base station 3. When the MME 5 receives the attach request, the MME 5 authenticates the terminal 4. Further, the MME 5 registers the location of the terminal 4 with respect to a Home Subscriber Server (HSS: subscriber server, not shown).

Subsequently, the MME 5 sends a control signal called a bearer (user packet path) setting request signal to the S-GW 6. The S-GW 6 performs bearer setting between the S-GW 6 and the P-GW 7 in accordance with the bearer setting request signal. When the bearer setting is performed, the MME 5 sends a control signal called a radio bearer setting request (attach acceptance) signal to the terminal 4 via the base station 3.

  At this time, a radio bearer is set between the terminal 4 and the base station 3. Thereafter, the terminal 4 sends an attach completion signal to the MME 5 via the base station 3. Then, the MME 5 gives a control signal for bearer update to the S-GW 6, and the S-GW 6 sets a radio bearer between the S-GW 6 and the base station 3.

  In this way, a bearer passing through terminal 4 to base station 3 to S-GW 6 to P-GW 7 is set, and a user packet transmitted from terminal 4 reaches P-GW 7 through the bearer and reaches PDN 8. Sent. In the bearer setting, resources of the wireless network 1 and the core network 2 are used. That is, resource settings are made.

  A user packet (for example, an IP packet) is transferred between the terminal 4 and the base station 3 using a protocol called Packet Data Convergence Protocol (PDCP). On the other hand, a tunnel (GTP-U path) using a protocol called General Packet Radio Service Tunneling Protocol for User Plane (GTP-U) is generated between the base station 3 and the S-GW 6. -Transferred to S-GW 6 through U path.

  When a certain period of time has elapsed since the terminal 4 has not transmitted user packets, the radio bearer between the terminal 4 and the base station 3 and the radio bearer between the base station 3 and the S-GW 4 are released. By releasing the radio bearer, the resources used for setting the radio bearer are released. The released resources can be used for other purposes. For this reason, efficient use of radio resources is achieved.

  Thereafter, when the radio bearer is released when the terminal 4 starts transmitting the user packet, the terminal 4 sends a control signal (hereinafter referred to as “service request”) to the MME 5 for a service request (corresponding to a resource reset request). Send). The MME 5 sends a radio bearer setting request signal to the S-GW 6. Thereby, the radio bearer from the terminal 4 to the S-GW 6 is reset, and the terminal 4 can transmit the user packet. The service request is an example of a “resource setting request”.

  FIG. 1 shows a plurality (n (n is a natural number)) of terminals 4 (terminals # 1 to #n). For example, it is assumed that an application program that transmits a user packet is installed in each of the plurality of terminals 4 at a fixed time (fixed time) every day. Under this assumption, when the radio bearer is released in each of the terminals # 1 to #n at the scheduled time, each of the terminals # 1 to #n transmits a service request (resource reset request) to the MME 5 at the same time. To do.

In this case, a burst of load (burst load) is generated in the MME 5 that sends service requests to the S-GW 6 and the S-GW 6 that sets the radio bearer according to the radio bearer setting signal. , Processing can be congested. Hereinafter, the S-GW 6 that detects (identifies) the terminal 4 that needs to be controlled in the C plane in order to avoid the burst load as described above will be described.
<S-GW hardware configuration example>
FIG. 2 shows a hardware configuration example of an information processing apparatus (computer) that can be used as the S-GW 6. As a hardware configuration of the S-GW 6, a hardware architecture provided in a general-purpose computer such as a personal computer (PC) or a workstation (WS) or a dedicated computer such as a server machine can be applied.

In FIG. 2, an S-GW (information processing apparatus) 6 includes a communication interface (communication I / F) 11 and a central processing unit (CPU) 1 connected via a bus B (internal communication path).
2, a main memory (MM: main storage device) 13, and a hardware disk drive (HDD) 14.

  The communication I / F 11 accommodates a physical line (physical link) connected to the P-GW 7, the MME 5, and the base station 3. For example, a network interface card (NIC) or a LAN (private branch exchange network) card can be applied to the communication I / F 11. The communication I / F 11 is an example of a “communication device”.

  The MM 13 includes a random access memory (RAM) that is an example of a volatile recording medium, and a read only memory (ROM) that is an example of a nonvolatile recording medium. The RAM in the MM 13 is used as a work area for the CPU 11.

  The HDD 14 is an example of an auxiliary storage device. The ROM and the HDD 14 in the MM 13 store a plurality of computer programs including an operating system (OS) and various application programs, and data used when each program is executed.

The MM 13 and the HDD 14 are examples of “storage device”, “storage medium”, and “storage unit”. As the non-volatile storage medium or auxiliary storage device, at least one of an electrically erasable programmable ROM (EEPROM), a flash memory, a solid state drive (SSD), and the like can be used.

  The CPU 12 loads a program stored (installed) in the HDD 14 or ROM into the RAM and executes it. As a result, the S-GW 8 performs processing related to the C plane such as bearer setting (GTP-U path setting, etc.), processing related to transfer of user packets (U plane), and burst of the C plane described below. A process of detecting (identifying) the terminal 4 that causes the load is executed. The CPU 12 is an example of a “processor”, “control device”, and “control unit”. The CPU 12 is an example of a “determination unit” or “storage processing unit”.

Note that part or all of the processing executed by the CPU 12 can be implemented by hardware logic. As a mechanism for executing hardware logic, for example, an integrated circuit (IC, LSI, Application Specific Integrated Circuit (ASIC))
Can be applied. Alternatively, a programmable logic device (PLD, for example, Field Programmable Gate Array (FPGA)) can be applied.

  FIG. 3 is a diagram schematically illustrating an operation performed by the S-GW 6 when the CPU 12 executes a program. FIG. 4 is a diagram schematically showing an operation based on each process of the CPU shown in FIG. FIG. 5 is a flowchart illustrating an example of the non-communication monitoring process 24 executed by the CPU 12. FIG. 6 is a flowchart illustrating an example of the burst suppression control process 31 executed by the CPU 12.

  In FIG. 3, the CPU 12 performs a U plane process 20 and a C plane process 30. In the U plane process 20, a packet reception process 21, a transfer process 22, a packet transmission process 23, a no-communication monitoring process 24, and a timer management 25 are executed. A user ID table 26 used in the no-communication monitoring process 24 is stored in the MM 13 or the HDD 14.

  On the other hand, in the C plane process 30, a burst suppression control process 31 is executed. Further, a burst management DB 32 and a user behavior management DB 33 are stored in the MM 13 or the HDD 14 as a database (DB) for storing information related to the C plane processing 30.

  In FIG. 4, in a packet reception process 21, a reception process for a user packet transmitted from the base station 3 and received by the communication I / F 11 is executed. In the transfer process 22, the transfer destination of the user packet is determined. In the transfer process 22, a reception notification regarding the received user packet is given to the no-communication monitoring process (FIG. 4).

The reception notification includes TEID-U (Tunnel Endpoint Identifier for User Plane: GTP-U path identifier) set in the user packet. In the packet transmission process 23,
Processing for transmitting a user packet directed to the transfer destination from the communication I / F 11 is executed. A plurality of cylinders shown in FIG. 4 indicate user packet transfer paths.

  In the no-communication monitoring process 24, no-communication monitoring using a timer managed by the timer management 25 is performed. The timer management 25 manages a plurality of timers prepared for each GTP-U path (terminal 4). Each timer is associated with TEID-U.

  When the expiration of the timer is notified from the timer management 25 in the no-communication monitoring process 24, the S-GW 6 performs a radio bearer release process for the corresponding terminal 4. Thereby, the radio bearer between the S-GW 6 and the terminal 4 is released.

  In addition, when the no-communication monitoring process 24 receives the user packet reception notification from the transfer process 25 (FIG. 5, 01), the timer management 25 resets the timer corresponding to the TEID-U included in the reception notification. Instruct. The timer management 25 resets the timer according to the reset instruction, and returns the time measured by the timer (elapsed time at the reset) to the no-communication monitoring process 24.

  The no-communication monitoring process 24 that has received the time measurement determines whether or not the time measurement (elapsed time) is equal to or greater than a predetermined threshold (predetermined value) (FIG. 5, 02). If the measured time is less than or equal to the threshold (02, NO), the process returns to 01. On the other hand, if the timekeeping time is equal to or greater than the threshold (02, YES), the no-communication monitoring process 24 performs an update process of the burst management DB 32 (FIG. 5, 03).

  The predetermined threshold takes into account the time when the terminal 4 transmits a resource reset request to the MME 5 for user packet transmission, and after the resource (radio bearer) reset, the user packet is transmitted and received by the S-GW 6. Is set. When the timekeeping time is equal to or greater than the threshold, there is a high possibility that the terminal 4 has transmitted a user packet after the resource resetting described above.

  In the update process (FIG. 5, 03) of the burst management DB 32, the following process is executed. That is, the no-communication monitoring process 24 refers to the user ID table 26 and obtains the user ID (identifier of the terminal 4) corresponding to TEID-U.

  FIG. 7 is a diagram illustrating a data structure example of the user ID table 26 (table 26). In FIG. 4, the table 26 is formed of a plurality of entries that store pairs of TEID-U and International Mobile Subscriber Identity (IMSI).

  The IMSI used as the user ID (terminal identifier) is a unique identifier of the terminal 4 (user). The IMSI is sent from the terminal 4 to the MME 5 when registering the location of the terminal 4. For example, when setting the GTP-U path for each terminal 4, the S-GW 6 receives the IMSI corresponding to each terminal 4 from the MME 5, and associates each IMSI with the set GTP-U path in the table 26. Store. Thereby, the table 26 can be generated.

In this embodiment, since the terminal 4 is managed by IMSI in the C plane, IMSI is used as the user ID. The user packet relayed by the S-GW 6 is a packet in which an encrypted IP packet is encapsulated by the TEID-U. For this reason, the S-GW 6 may not be able to obtain the packet source IP address. Furthermore, it is also considered that the TEID-U can be changed for the same terminal 4 whereas the IMSI is an identifier that is unchanged for the terminal 4. However, as long as the user ID is an identifier that can uniquely identify the terminal 4, an identifier other than the IMSI can be used.

  The no-communication monitoring process 24 detects, as an event, reception of a user packet of the terminal 4 whose timed time is equal to or greater than a threshold, that is, the time length from the previous reception to the current reception is equal to or greater than the threshold. The no-communication monitoring process 24 registers the occurrence of the event and the user ID related to the event in the burst management DB 32.

  FIG. 8 is a diagram illustrating a data structure example of the burst management DB 32. In FIG. 8, the burst management DB 32 is configured to store the number of event occurrences (number of events) occurring in each time zone (time) for each time zone of unit time (1 minute in the example of FIG. 8). Has been. Further, the burst management DB 32 stores a list (user list) of terminals 4 (IMSI) that transmitted user packets that triggered the occurrence of events in association with the number of events. The unit time length (the length of the time zone) can be set as appropriate. By adjusting the unit time length, fluctuations and delays in user packets can be absorbed.

  When an event occurs, the no-communication monitoring process 24 refers to the burst management DB 32, increments the number of events corresponding to the time zone to which the reception time of the packet related to the event belongs, and sets the IMSI corresponding to the event to the user list. Register with.

  Returning to FIG. 4, for example, the burst suppression control process 31 is periodically started to perform the following process. The burst suppression control process 31 is performed asynchronously with the no-communication monitoring process 24. However, the burst suppression control process 31 may be executed so that both are synchronized. The burst suppression control process 31 reads the burst management DB 32 (FIGS. 6 and 11).

  Next, the burst suppression control process 31 determines whether or not there is a time zone during which a bursty user packet is received (FIGS. 6 and 12). This determination is made based on whether the number of events exceeds the threshold value prepared in advance (for example, stored in the HDD 14) with respect to the number of events in each time zone. If there is no time slot in which the number of events exceeds the threshold in the 12 processes (12, NO), the burst suppression control process 31 ends. On the other hand, if there is a time slot in which the number of events exceeds the threshold (12, YES), the process proceeds to 13.

  The processes after 13 are performed for each time period in which the number of events found in the 12 processes exceeds the threshold. 13, the burst suppression control process 31 performs a behavior analysis on each user ID (terminal 4) registered in the user list associated with the time zone in which the number of events exceeds the threshold (FIGS. 6 and 13). The behavior analysis is performed by acquiring the behavior information of the corresponding user ID in the user behavior management DB 33.

  FIG. 9 is a diagram illustrating an exemplary data structure of the user behavior management DB 33. In FIG. 9, the user behavior management DB 33 stores information (behavior information) indicating the reception status (behavior) of packets within a predetermined period for each user ID. The user ID is an IMSI (user ID) registered in the user list of the burst management DB 32 (of the terminal 4 involved in the occurrence of burst reception). The behavior information stores information indicating the behavior of the terminal 4 having the corresponding user ID (IMSI) in a predetermined period (within several days in FIG. 9).

  The behavior information is created by the CPU 12 (for example, the no-communication monitoring process 24) as follows. When the CPU 12 registers a user ID (IMSI) in the burst management DB 32, the CPU 12 creates an entry related to the user ID. The CPU 12 stores the time zone to which the user ID belongs in the burst management DB 32 as behavior information in the created entry. Such time zone storage is performed for a predetermined period for each user ID.

  When the behavior information of a certain user ID indicates daily user packet reception (time zone) and the time zone satisfies the condition that these time zones are completely coincident or within the range that is recognized as coincidence, the terminal 4 It can be seen that user packets received by the S-GW 6 are transmitted every day. That is, with respect to the terminal 4, it can be determined that the regular user packet transmission is continuously performed. Therefore, it can be estimated that the terminal 4 transmits a resource reset request (service request) that causes a burst load on the C plane almost at a fixed time.

  It should be noted that “every day” in the above condition may be “almost every day”. In this way, it is possible to determine continuity even in the case where the user packet is not transmitted for only one day among several days. In the above case, the terminal 4 is powered off for one day, and the regular user packet transmission is not performed only on that day, or the user packet is not transmitted on a certain day of the week (for example, Sunday) depending on the application specifications. Cases are considered.

  When the above conditions are not satisfied, the terminal 4 can determine that the scheduled user packet transmission is not continuously performed. For example, regarding time zone information accumulated as behavior information, a determination element without continuity such as a time zone that is not aligned for a predetermined number of days or a time zone that is disjoint (no regularity) is proactive. It may be judged. The reception time of the user packet may be used instead of the time zone.

  In the example illustrated in FIG. 9, an example in which determination results (with the continuity of regular user packet transmission and without continuity) determined using the above-described “time zone” information for several days are stored as behavior information. Is shown. As described above, information such as “time zone” used for continuity determination may be accumulated as the behavior information, and the presence / absence of continuity may be determined in 13 processes. Alternatively, as shown in FIG. 9, information indicating the determination result may be stored in advance as behavior information, and in the 13 analysis processes, the presence or absence of continuity may be determined by referring to the behavior information. In this case, the determination result is updated at an appropriate timing.

  Returning to FIG. 4 (FIG. 6), the burst suppression control process 31 determines whether or not there is continuity for all user IDs registered in the user list in the 13 analysis processes. By this determination, the plurality of user IDs registered in the user list are classified into two groups. One is a group (first group) of terminals 4 having continuity of regular user packet transmission, and the other is a group of terminals 4 (second group) having no continuity of regular user packet transmission. is there. In other words, it is possible to identify whether the user ID (terminal 4) belongs to the first group or the second group by the 13 analysis processes. The terminals 4 belonging to the first group are detected as the terminals 4 that cause the concentration of resource resetting requests.

  The burst suppression control process 31 determines to execute the burst suppression process 34 for each terminal 4 having the user ID belonging to the first group, and causes the access management apparatus 9 to start the burst suppression process (FIGS. 6 and 14).

The access management apparatus 9 is an information processing apparatus having a hardware configuration similar to the hardware architecture shown in FIG. The access management device 9 communicates with the S-GW 6 and obtains an activation instruction (burst suppression instruction) for the burst suppression process 34. The burst suppression instruction includes information on the first group and the second group (information indicating the IMSI belonging to each group), and information indicating a time zone of occurrence of burst reception of user packets.

  FIG. 10 is a sequence diagram showing an operation example 1 related to the burst suppression process 34. As a premise of the operation example of FIG. 10, each terminal # 1 to #n has an environment in which a resource reconfiguration request is transmitted to the MME 5 all at once in order to transmit user packets on a regular basis (<1> to FIG. 10). <6>). The burst suppression process 34 is an example of a “predetermined process”.

  As a result of the burst suppression control process 31, the S-GW 6 sends a burst suppression instruction (including time zone information and information on the first group and the second group) to the access management apparatus 9 (<7> in FIG. 10). At this time, it is assumed that the information of the first group includes the IMSIs of the terminals # 1 to #n, and there is no IMSI belonging to the second group.

  The access management device 9 wirelessly transmits to each terminal # 1 to #n in order to distribute the arrival times of resource reset requests from the terminals # 1 to #n that are predicted to arrive in the time zone during which burst suppression is instructed. A bearer resetting instruction is sent to the MME 5 (FIG. 10 <8> to <10>). The reset instruction includes the IMSI of each of the terminals # 1 to #n and the time zone information.

The MME 5 makes a terminal call to each of the terminals # 1 to #n based on the IMSI of each of the terminals # 1 to #n and prompts transmission of a resource reset request (service request) (FIG. 10 <11>, <1
2>, <16>, <17>, <21>, <22>). In response to the call, each terminal # 1 to #n transmits a resource reset request (FIG. 10 <13>, <14>, <18>, <19>, <23>, <24>).

  The MME 5 receives the resource reconfiguration request and transmits a radio bearer setting request signal to the S-GW 6, and the S-GW 6 performs reconfiguration of the radio bearer regarding each terminal # 1 to #n (<15> in FIG. 10). , <20>, <24>).

  When calling, the MME 5 sends a call signal to each terminal # 1 to #n with a predetermined interval so that the resource reset request from each terminal # 1 to #n reaches the MME 5 in a distributed manner. At this time, the MME 5 starts the call to the first terminal # 1 among the terminals # 1 to #n at a timing later than the time that is backed by the timer expiration time from the time zone (time) included in the reset instruction. To do. This is to prevent the radio bearer set by the resetting from being released when the timer expires before the scheduled time.

  When the activation time of the application in each terminal # 1 to #n is reached (<26> in FIG. 10), the application generates a user packet to be transmitted. At this time, radio bearers from the terminals # 1 to #n to the S-GW 6 are already set. Therefore, each terminal # 1 to #n transmits a user packet without transmitting a resource reset request (<27> in FIG. 10).

  The burst suppression control process 31 is executed periodically or periodically. However, the burst suppression control process 31 can be started at an appropriate timing in response to a manual operation or a trigger generated by a predetermined algorithm. When the access management apparatus 9 receives a burst suppression instruction from the S-GW 6, the access management apparatus 9 creates a list of IMSIs (radio bearer reconfiguration target list) in the information of the first group included in the instruction, and the MM or HDD Is stored in a storage device such as Then, the access management device 9 sends an instruction to set the radio bearer for the IMSI in the list to the MME 5 at an appropriate timing before the time period included in the burst suppression instruction.

  FIG. 11 is a sequence diagram illustrating an operation example 2 according to the burst suppression process 34. An operation example 2 shown in FIG. 11 shows an operation example after the operation example 1. As a premise of the operation example 2, among the terminals # 1 to #n (n = 3 in FIG. 11), the terminals # 1 and # 2 maintain an environment for transmitting user packets on a regular basis by an application. (FIG. 10 <1> to <4>). On the other hand, the terminal #n (terminal # 3) is in a state in which it does not perform regular user packet transmission due to any one of application deletion, application specification change, or application setting change (FIG. 11). (See dashed arrow).

  The S-GW 6 identifies that the terminals # 1 and # 2 belong to the first group as a result of the execution of the burst suppression control process 31. On the other hand, the behavior information of the terminal #n indicates that there is no continuity of the regular user packet transmission due to the deletion of the application. For this reason, the terminal #n is identified as the terminal 4 belonging to the second group.

In response to the result of the burst suppression control process 31, the S-GW 6 sends a burst suppression instruction (including time zone information and information on the first group and the second group) to the access management apparatus 9 (<7> in FIG. 11). . At this time, the first group information includes the IMSIs of the terminals # 1 and # 2, and the second group information includes the IMSI of the terminal #n.

  When the access management apparatus 9 receives the burst suppression instruction and finds the information of the second group in the instruction, the access management apparatus 9 searches the radio bearer reconfiguration target list for the IMSI that is the same as the IMSI in the information of the second group. When the same IMSI is found in the radio bearer reconfiguration target list, the access management device 9 deletes the IMSI from the radio bearer reconfiguration target list. As a result, the access management device 9 excludes the terminal #n from the terminals 4 to which the radio bearer reconfiguration instruction is sent to the MME 5 (<8> in FIG. 11).

The access management device 9 sends a radio bearer reconfiguration instruction for the terminals # 1 and # 2 to the MME 5 (FIG. 10 <9>, <10>). The MME 5 performs a terminal call for each of the terminals # 1 and # 2, and prompts transmission of a resource reset request (service request) (FIG. 10 <11>, <12>, <16>, <17>). In contrast, no call is made to terminal #n (FIG. 11 <2
1>).

Each terminal # 1, # 2 transmits a resource reset request (FIG. 10 <13>, <14>, <1
8>, <19>, <23>, <24>). In response to the resource reset request, MME 5
The radio bearer setting request signal is transmitted to the GW 6, and the S-GW 6 reconfigures the radio bearers related to the terminals # 1 and # 2 (<15> and <20> in FIG. 10).

<Effects of Embodiment>
According to the embodiment described above, the burst management DB 32 is generated by the no-communication monitoring process 24 of the CPU 12. That is, the burst management DB 32 stores the number of events and the user list for each time zone (time) (FIG. 5, 03). The number of events indicates “the number of received (user) packets transmitted from each terminal 4 after the elapse of a predetermined time (number of received (user) packets)”.

  As described above, the reception of such a packet is performed after each terminal 4 whose IMSI is registered in the user list transmits a resource reset request for transmitting the user packet, and after the resource is reset, the user packet Is likely to have sent. Therefore, the number of events corresponding to each time can be used as an estimated value of the number of transmission (occurrence) of C-plane resource reset request.

Further, in the burst suppression control process 31 of the CPU 12, a time zone (time) in which the number of events exceeds the threshold is extracted (FIGS. 6 and 12). Since the burst time user packet is received in the U plane, it can be estimated that the resource reset request has occurred intensively in the C plane. Then, the terminal 4 whose IMSI is registered in the user list can be detected as the terminal 4 that causes the concentration of resource resetting requests in the C plane.

  Further, the CPU 12 uses the user behavior management DB 33 to determine whether or not the user (terminal 4) is performing a regular packet transmission from the behavior information (packet reception status), and determines the terminal 4 as the first group and the first group. It can be divided into two groups. The terminals 4 belonging to the first group are identified as the terminals 4 that are performing regular packet transmission. Such a terminal has a high possibility of performing a regular packet transmission in the future, and is determined as a target of the burst suppression process 34 (predetermined process).

  As a result, as shown in operation example 1, the transmission timing of the resource reset request of each terminal 4 belonging to the first group is adjusted, so that a bursty load increase occurs and the processing is congested. It can be avoided (suppressed). As described above, according to the process 13 in FIG. 6, the identification (detection) accuracy of the terminal 4 that requires the burst suppression process 34 can be improved as compared with the case where the process is not performed.

  Further, according to the process 13, since the terminal 4 that does not require the burst suppression process 34 can be detected (identified), it is possible to determine whether or not the burst suppression process 34 for each terminal 4 needs to be performed.

  Terminals 4 belonging to the second group can be identified as terminals 4 that are not performing regular packet transmission. Such a terminal 4 has a high possibility of being received in the said time slot | zone as a result of transmitting resource packet accidentally and transmitting a user packet. In other words, since it is unlikely that scheduled packet transmission will be performed in the future, it is excluded from the target of the burst suppression process 34. As a result, as shown in the operation example 2, it is possible to avoid useless terminal calls and radio bearer resetting and to effectively use resources.

As described above, in the present embodiment, the terminal 4 that causes the concentration of resource resetting requests (burst load occurrence) in the C plane is detected based on the U plane behavior (user packet reception status). be able to. For this reason, it is not necessary to monitor the resource reconfiguration request in the C plane as described in the related art, and the above-described effects can be obtained.
<Modification>
In the present embodiment, an example in which the S-GW 6 that is a user packet relay device is an “information processing device” has been described. Instead, the table 26, the burst management DB 32, and the user behavior management DB 33 are stored in a storage device of a computer that can communicate with the S-GW 6 (for example, the access management device 9 or a separate server device). The no-communication monitoring process 24, the timer management 25, and the burst suppression control process 31 may be executed using a packet reception notification received from the S-GW 6. That is, the “information processing apparatus” is not limited to the relay apparatus (S-GW 6), and may be a monitoring server that monitors the reception status of user packets in the S-GW 6.

  Further, instead of the configuration described in the present embodiment, the stored contents of the burst management DB 32 may be displayed on a predetermined display device. In this case, a person who refers to the stored contents identifies the terminal 4 in which the burst suppression processing 34 is preferably performed by grasping the time zone (time) of occurrence of the burst and referring to the user list (IMSI). Can do. In this case, the burst suppression control process 31 is optional.

  In the present embodiment, user behavior analysis (FIGS. 6 and 13) is performed, but this may be optional. That is, the burst suppression process 34 can be executed for all terminals 4 registered in the user list at the time (time period) set as the burst time period. The configurations shown in the above embodiments can be combined as appropriate.

3. Base station (radio base station)
4 ... Terminal (wireless terminal)
5 ... MME
6 ... S-GW
12 ... CPU
13 ... Main memory

Claims (7)

Detection of information processing equipment connected to a network that accepts a resource setting request sent from each terminal for which no packet transmission resource is set, sets the resource, and then relays the packet sent from each terminal A method,
The information processing apparatus is
Determining whether a packet transmitted from each terminal is received after a predetermined time from the previous reception time;
Using the determination result, the number of packets received after elapse of the predetermined time and the identifier of each terminal of the transmission source of the packet received after elapse of the predetermined time are stored in a storage device for each time period. Information processing apparatus terminal detection method. The information processing apparatus is
Each terminal having an identifier stored in association with a time zone in which the number of packets received after the predetermined time elapses is greater than or equal to a threshold value transmits the resource setting request for transmission of the packet received in the time zone The terminal detection method for an information processing apparatus according to claim 1, further comprising identifying the terminal as a terminal to perform. The information processing apparatus is
A packet reception status within a predetermined period of each terminal having an identifier stored in association with a time zone in which the number of packets received after the predetermined time has passed is greater than or equal to a threshold;
Further comprising identifying, among the terminals, a terminal indicating continuity of packet transmission when the reception status is fixed as a terminal that transmits the resource setting request for transmission of a packet received in the time period. The terminal detection method of the information processing apparatus according to claim 1 or 2. The information processing apparatus is
Deciding to perform processing for adjusting the timing of transmitting the resource setting request to each terminal identified as the terminal transmitting the resource setting request for transmitting packets received in the time period The terminal detection method of the information processing apparatus according to claim 3. The information processing apparatus is
The method further includes determining to exclude from the process of adjusting the timing of transmitting the resource setting request to a terminal whose reception status does not indicate continuity of packet transmission at a fixed time among the terminals. Item 5. A terminal detection method for an information processing apparatus according to Item 3 or 4. An information processing apparatus connected to a network that accepts a resource setting request transmitted from each terminal for which no packet transmission resource is set, sets a resource, and then relays a packet transmitted from each terminal. ,
A determination unit that determines whether a packet transmitted from each terminal is received after a predetermined time has elapsed since the previous reception time;
Using the determination result, the number of packets received after elapse of the predetermined time and the identifier of each terminal of the transmission source of the packet received after elapse of the predetermined time are stored in a storage device for each time period. A storage processing unit;
An information processing apparatus including: A device that accepts a resource setting request transmitted from each terminal for which no resource for packet transmission is set and controls the setting of the resource;
A relay device that relays a packet transmitted from each terminal after setting the resource,
The relay device is
A determination unit that determines whether a packet transmitted from each terminal is received after a predetermined time has elapsed since the previous reception time;
Using the determination result, the number of packets received after elapse of the predetermined time and the identifier of each terminal of the transmission source of the packet received after elapse of the predetermined time are stored in a storage device for each time period. A storage processing unit;
Information processing system including

Images