Communication control device and communication control method

Abstract

To appropriately control retry of signal transmission to a mobile communication terminal.SOLUTION: A UECF 10 being a communication control device includes: an acquisition unit 11 that acquires control information including type information indicating the type of a UE 100, which is a mobile communication terminal to be controlled; and a transmission unit 12 that transmits to the UE 100 to be controlled a signal that performs control according to the control information acquired by the acquisition unit 11 and controls retry of signal transmission to a mobile communication network N.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a communication control device and a communication control method. [Background technology]

[0002] Cause is a signal (information set in a signal) transmitted from a mobile communication network to UE (User Equipment), which is a mobile communication terminal (mobile device) (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2015-115767 Summary of the Invention [Problem to be solved by the invention]

[0004] Cause is a signal that controls retry of signal transmission from the UE to the mobile communication network. When the mobile communication network recovers from a failure, congestion occurs if the UE transmits a large number of signals (for example, location registration requests or PDU (Packet Data Unit) session establishment requests). In such cases, to prevent congestion, the mobile communication network transmits a Cause to the UE to suppress retry of signal transmission.

[0005] All causes are defined by standard specifications. Also, all causes sent to UEs for each use case are mapped. However, interpretations of standard specifications may differ depending on the UE manufacturer, and the behavior of UEs receiving a cause may differ depending on the UE model. Therefore, for example, among UEs receiving the same cause, some may retry signal transmission, while others may retry frequently. If these retries become too frequent, congestion occurs in nodes such as the Access and Mobility management Function (AMF) of the mobile communication network. Furthermore, if no retry requests are made, user operations such as rebooting the UE are required to restore communication after troubleshooting.

[0006] Furthermore, for example, when a temporary network error such as congestion occurs, one Cause prevents UEs from retrying for a while, causing them to retry after a random number of seconds. However, in reality, depending on the model, there are UEs that simultaneously retry signal transmission after a fixed time instead of a random number, and UEs that never retry signal transmission again. As such, in the past, the behavior of UEs that received a Cause was not necessarily what the mobile communication network expected. This type of UE behavior is very inconvenient for the mobile communication network.

[0007] The present invention has been made in view of the above, and has as its object to provide a communication control device and a communication control method that can appropriately control retries of signal transmission to a mobile communication terminal. [Means for solving the problem]

[0008] In order to achieve the above-mentioned object, the communication control device of the present invention comprises an acquisition unit that acquires control information including type information indicating the type of the mobile communication terminal to be controlled, and a transmission unit that transmits to the mobile communication terminal to be controlled a signal that performs control according to the control information acquired by the acquisition unit, the signal controlling retries of signal transmission to the mobile communication network.

[0009] According to the communication control device of the present invention, a signal for controlling retry of signal transmission is transmitted to the mobile communication terminal according to the type of the mobile communication terminal to be controlled. Therefore, according to the communication control device of the present invention, it is possible to appropriately control retry of signal transmission to the mobile communication terminal.

[0010] Incidentally, the present invention can be described not only as an invention of a communication control device as described above, but also as an invention of a communication control method as described below. These are essentially the same inventions, with similar actions and effects, but in different categories.

[0011] That is, the communication control method of the present invention includes an acquisition step in which the communication control device acquires control information including type information indicating the type of the mobile communication terminal to be controlled, and a transmission step in which the communication control device transmits to the mobile communication terminal to be controlled a signal that performs control in accordance with the control information acquired in the acquisition step and controls retries of signal transmission to the mobile communication network. [Effects of the Invention]

[0012] According to the present invention, it is possible to appropriately control retries of signal transmission to a mobile communication terminal. [Brief explanation of the drawings]

[0013] [Figure 1] 1 is a diagram illustrating a configuration of a UE Control Function (UECF), which is a communication control device according to an embodiment of the present invention, and a configuration of a mobile communication system including the UECF. [Figure 2] This is an example of information used in UECF. [Figure 3] 1 is a flowchart showing a communication control method which is a process executed by a UECF which is a communication control device according to an embodiment of the present invention. [Figure 4] 1 is a diagram illustrating a hardware configuration of a UECF (a physical server or the like in which the UECF is realized) which is a communication control device according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0014] Hereinafter, a communication control device and a communication control method according to an embodiment of the present invention will be described in detail with reference to the drawings. In the description of the drawings, the same elements are given the same reference numerals and duplicated explanations will be omitted.

[0015] FIG. 1 shows a UECF10, which is a communication control device according to this embodiment. The UECF10 is a device (system, node) that controls communications in a mobile communication network N. The mobile communication network N is a communication network that provides mobile communication functions to a UE100, which is a mobile communication terminal (mobile device). The mobile communication network N according to this embodiment is, for example, a 5G mobile communication network. However, the mobile communication network N does not need to be a 5G mobile communication network, and may be any mobile communication network within a framework that complies with this embodiment.

[0016] The UE 100 is a device having a function of connecting to a mobile communication network N and performing mobile communication. The UE 100 is, for example, a mobile phone or a smartphone used by a user. The UE 100 may be a conventional one.

[0017] The mobile communication network N includes a plurality of functional elements (network function units) called NFs (Network Functions), which provide mobile communication functions to the UE 100. The mobile communication network N includes network resources (network infrastructure), which are physical networks including links (e.g., lines or transmission paths between devices) and nodes (e.g., the devices themselves) of network devices. The NFs are implemented on a physical server, which is one of the resources, or on a dedicated network device (e.g., a router or a switch).

[0018] The NFs include the AMF 20 and SMF (Session Management Function) 30 shown in FIG. 1. The AMF 20 is an NF that has the function of managing the location of the UE 100 and performing communication path setting processing. The SMF 30 is an NF that has a session management function. The mobile communication network N may include NFs other than those included in a conventional mobile communication network. Each NF in the mobile communication network N has the same function as each NF in a conventional mobile communication network. The mobile communication network N may be realized in the same way as a conventional mobile communication network, except for the one according to this embodiment described later. Note that some NFs such as the AMF 20 and SMF 30 have the function described below in addition to the conventional function.

[0019] The UECF10, which is a communication control device according to this embodiment, is an NF included in the core network of the mobile communication network N. The UECF10 is an NF that is not included in conventional mobile communication networks. The UECF10 is an NF that is provided in the mobile communication network N to realize functions according to this embodiment that are not conventional. The UECF10 can transmit and receive information to and from other NFs, such as the AMF20 and SMF30, in the mobile communication network N. The UECF10 controls the Cause transmitted from the mobile communication network N to the UE100. The Cause is a signal (information set in the signal) that controls retries of signal transmission from the UE100 to the mobile communication network N.

[0020] When a signal is transmitted from the UE 100 to the mobile communication network N, if there is an abnormality in the signal from the UE 100 or in the mobile communication network N, the Cause is transmitted from the mobile communication network N to the UE 100 as an abnormality response (Reject response). For example, the Cause suppresses signal transmission from the UE 100 to the mobile communication network N. The Cause includes information indicating the content of control. The content of control is, for example, at least one of whether a retry is possible and the time interval between retries. This prevents congestion from occurring in the mobile communication network N, for example, as described above.

[0021] In a conventional mobile communication network, a Cause is transmitted to a UE in the following cases, for example: A signal related to a PDU session (PDU session esta) is transmitted from the UE to the mobile communication network. The transmitted signal is received by the AMF. The AMF checks contract information related to the UE with other NFs in the mobile communication network. If the result shows that the UE signal cannot be processed, the AMF transmits a Cause to the UE in response to the signal related to the PDU session. Furthermore, the AMF makes a session management request related to the UE to the SMF. If the session management request related to the UE is not accepted by the SMF, the AMF transmits a Cause to the UE in response to the signal related to the PDU session. The above Cause is a 5GSM (session management) Cause.

[0022] Alternatively, a Cause is also sent to the UE in the following cases: A location registration request signal is sent from the UE to the mobile communication network. The AMF checks the contract information related to the UE with other NFs in the mobile communication network. If the result is that the UE signal cannot be processed, the AMF sends a Cause to the UE as a response to the signal related to the PDU session. The above Cause is a 5GMM (mobility management) Cause. In the above example, the sender of the Cause was the AMF, but depending on the Cause, the sender may be an NF other than the Cause, for example, an SMF. In this way, a Cause can be sent from multiple locations.

[0023] Conventionally, Causes sent to UEs are uniform and defined by standard specifications, regardless of the UE model. The Causes defined in the standard specifications are vague, and as mentioned above, the behavior of conventional Causes (including the control content) varies depending on the UE model. For example, even if a Cause sent to a UE is expected to cause the UE to retransmit a signal to the mobile communication network after a few minutes, some UEs will retransmit within a few minutes, some will retransmit immediately, and some will not retransmit at all. For UEs that do not retransmit, user operation such as restarting the power or turning on / off airplane mode is required.

[0024] Alternatively, even if a Cause transmitted to a UE expects the UE to prohibit retransmission of a signal to a mobile communication network for a certain period of time, some UEs may prohibit retransmission and others may immediately retransmit the signal. In this case, immediate retransmission of a signal from the UE may, for example, hinder recovery from a problem. As described above, in the past, the behavior of a UE in response to a Cause did not match the behavior expected by the mobile communication network, causing inconvenience to the mobile communication network. This embodiment is intended to solve the above problem.

[0025] Next, a description will be given of the functions of the UECF 10, which is a communication control device according to this embodiment. As shown in FIG.

[0026] The acquisition unit 11 is a functional unit that acquires control information including type information indicating the type of the mobile communication terminal to be controlled. The acquisition unit 11 may also acquire control information including contract information related to the contract of the mobile communication terminal to be controlled. The acquisition unit 11 acquires the control information, for example, as follows.

[0027] In a conventional mobile communication network, the AMF 20, SMF 30, and the like, which are NFs that can be the source of a Cause, make an inquiry to the UECF 10 about the Cause when there is an opportunity to send a Cause to the UE 100.

[0028] For example, in the following cases, the AMF 20 and SMF 30 etc. make a query about the cause to the UECF 10. The UE 100 transmits a location registration request signal to the mobile communication network N, and the AMF 20 receives the signal. Upon receiving the signal, the AMF 20 selects a UDM (Unified Data Management). If the AMF 20 fails to select a UDM, it uses this as an opportunity to send a cause to the UE 100 and makes a query about the cause to the UECF 10. Alternatively, if congestion occurs in the AMF 20 upon receiving the signal, it uses this as an opportunity to send a cause to the UE 100 and makes a query about the cause to the UECF 10.

[0029] The UE 100 transmits a service request signal (Service Request) to the mobile communication network N, and the SMF 30 receives a corresponding signal (Nsmf_PDU session_UpdateSMCContext Request). Upon receiving this signal, the SMF 30 selects a UPF (User Plane Function). If the SMF 30 fails to connect to the selected UPF, it uses this as an opportunity to send a Cause to the UE 100 and queries the UECF 10 about the Cause.

[0030] The inquiry about the Cause to the UECF 10 includes type information indicating the type of the UE 100 to which the Cause is to be transmitted. The type information is, for example, a Permanent Equipment Identifier (PEI) or an International Mobile Equipment Identifier (IMEI), which is an identifier for identifying the UE 100. The identification information is included in a signal transmitted from the UE 100, and the AMF 20, the SMF 30, etc. include the identification information in the inquiry about the Cause. Note that the identification information may be information other than the above, as long as it indicates the type of the UE 100 to be controlled.

[0031] Furthermore, the inquiry about the Cause to the UECF 10 may include information indicating the cause of the above-mentioned trigger, i.e., the cause for controlling the retry. The information indicating the cause for controlling the retry is, for example, information indicating the event that triggered the transmission of the Cause to the UE 100 (information indicating the use case for transmitting the Cause). This information may be information for determining the Cause that is conventionally transmitted to the UE.

[0032] The acquisition unit 11 receives a Cause inquiry from the AMF 20, the SMF 30, etc. The acquisition unit 11 acquires information included in the received Cause inquiry as control information.

[0033] The acquiring unit 11 may also acquire contract information related to the contract of the UE 100 to be controlled as the control information. The contract information used as the control information is information used to control the transmission of Cause. The contract information is associated with the UE 100 in advance and stored in the mobile communication network N (UDM, etc.). The contract information may be new information not used in conventional mobile communication networks, or may be information used in conventional mobile communication networks.

[0034] For example, the acquisition unit 11 acquires contract information that is stored in the mobile communication network N in advance in association with the UE 100 indicated by the identifier included in the inquiry of Cause.

[0035] The acquisition unit 11 may acquire information other than the above as control information as long as the information is used to control the transmission of Cause. The acquisition unit 11 may also acquire the control information by a method other than the above. The acquisition unit 11 outputs the acquired control information to the transmission unit 12.

[0036] The transmitter 12 is a functional unit that transmits to the mobile communication terminal to be controlled a signal that performs control according to the control information acquired by the acquirer 11 and controls retries of signal transmission to the mobile communication network N. The transmitter 12 may determine a signal to be transmitted to the mobile communication terminal to be controlled based on a model generated by machine learning. The transmitter 12 may also transmit a signal according to the cause for controlling the retry. For example, the transmitter 12 transmits the above signal, Cause, to the mobile communication terminal UE 100 to be controlled, as follows:

[0037] The transmitter 12 receives the control information from the acquirer 11. The transmitter 12 determines the Cause (content of control to be included in the Cause) to be transmitted to the UE 100 from the received control information based on a criterion stored in advance, and transmits the Cause to the UE 100.

[0038] The transmitter 12 stores the error message table shown in Fig. 2 as the above-mentioned standard. The error message table associates a PEI (IMEI) bitmap, a model name, and a cause for each use case. The PEI (IMEI) bitmap is a PEI (IMEI) in bitmap format. The model name is the model name of the UE 100 indicated by the corresponding PEI (IMEI). The cause for each use case is a cause transmitted to the UE 100. The cause for each use case is set according to the model of the UE 100, i.e., the model name.

[0039] A Cause associated with a combination of a model name (i.e., PEI (IMEI)) and a use case is a Cause that causes the UE 100 of that model name to behave in a desired manner with respect to retrying signal transmission in that use case. For example, compared to Causes defined in standard specifications, the Cause is a Cause that specifically defines the behavior of the UE 100.

[0040] The transmitter 12 determines, in the error message table, a Cause associated with the combination of the type information (PEI (IMEI)) included in the input control information and the use case indicated by the control information, as a Cause to be transmitted to the UE 100. If the type information (PEI (IMEI)) included in the input control information is not included in the error message table, the transmitter 12 determines a preset default Cause as a Cause to be transmitted to the UE 100. The default Cause may also be for each use case.

[0041] In addition, when the acquisition unit 11 is configured to acquire control information other than the above (for example, contract information), the candidate causes to be transmitted to the UE 100 are associated with combinations that further include the control information other than the above, and the transmission unit 12 determines the cause associated with the input combination of control information as the cause to be transmitted to the UE 100.

[0042] Furthermore, the transmitting unit 12 may store in advance a model generated by machine learning as the above-mentioned criterion, and determine a Cause to be transmitted to the UE 100 based on the model. In this case, the transmitting unit 12 inputs the input control information or information based on the control information into the model, and determines a Cause to be transmitted to the UE 100. For example, the model is obtained by machine learning using type information, response time, and the like, so that the behavior of the UE 100 is optimized for each use case. Specifically, in creating an error message table, a model name may be determined from the IMEI of the UE that performed communication, and a model may be generated by learning the results of the reaction of the model (e.g., after how many minutes a retry was performed, or no retry was performed), and the reaction for each model and cause may be automatically updated.

[0043] Furthermore, the determination of the Cause to be transmitted to the UE 100 by the transmitter 12 may be performed by a method other than the above, as long as the determination is based on the control information input from the acquirer 11.

[0044] The transmission unit 12 transmits the determined Cause to the UE 100. For example, the transmission unit 12 transmits the Cause to the UE 100 via the AMF 20, the SMF 30, or the like, which are the sources of the Cause inquiry. Furthermore, the transmission unit 12 may transmit the Cause to the UE 100 by a method other than the above.

[0045] The UE 100, which is the destination of the Cause, receives the Cause transmitted from the transmitter 12 and is controlled by the Cause to retry transmitting a signal to the mobile communication network N. The above is the function of the UECF 10 according to this embodiment.

[0046] Next, a communication control method, which is a process executed by the UECF10, which is a communication control device according to this embodiment (an operation method performed by the UECF10), will be described using the flowchart in Fig. 3. This process is conventionally performed when an opportunity to send a Cause to the UE100 is detected by the AMF20, SMF30, or the like, which are NFs that can be the source of a Cause, and an inquiry about the Cause is made to the UECF10.

[0047] The UECF 10 receives the inquiry about the Cause. When the inquiry about the Cause is received, the acquisition unit 11 acquires control information (S01, acquisition step). The control information includes type information indicating the type of the UE 100 to be controlled. The control information may also include information other than the type information, such as contract information related to the contract of the UE 100.

[0048] Next, the transmitter 12 determines a Cause to be transmitted to the UE 100 from the control information as follows: First, it is determined whether or not type information (PEI (IMEI)) included in the control information is included in the error message table (S02, transmission step). If it is determined that the type information is included in the error message table (YES in S02), the Cause corresponding to the control information in the error message table is determined as the Cause to be transmitted to the UE 100 (S03, transmission step). If it is determined that the type information is not included in the error message table (NO in S02), the default Cause is determined as the Cause to be transmitted to the UE 100 (S04, transmission step). Once the Cause to be transmitted to the UE 100 has been determined (S03, S04), the determined Cause is transmitted from the transmitter 12 to the UE 100 (S05, transmission step). The UE 100, which is the destination of the Cause, receives the Cause transmitted from the transmitter 12 and controls retry of signal transmission to the mobile communication network N according to the Cause. The above is the communication control method according to this embodiment.

[0049] According to the present embodiment, in accordance with the type of the UE 100 to be controlled, a Cause, which is a signal for controlling retry of signal transmission, is transmitted to the UE 100. This makes it possible to control the UE 100 so as to exhibit a targeted behavior regarding retry of signal transmission in accordance with the type of the UE 100 to be controlled.

[0050] For example, when it is desired to make the UE 100 perform a retry operation after a random period of time, even if the UE 100 is of a type that does not perform a retry for a cause defined in the standard specifications, the present embodiment can make the UE 100 perform a retry. This contributes to the communication quality on the user side. Alternatively, when a retry operation is not immediately required during congestion or the like, but an increase in requests would have an adverse effect, it is possible to stop the retries of the UE 100 of a type that immediately performs a retry for a certain period of time. This contributes to communication recovery. In the present embodiment, the UE 100 may be the same as a conventional UE, and therefore there is no need to add new functions to the UE 100 that has already been sold. In this way, according to the present embodiment, it is possible to appropriately control the retry of signal transmission to the UE 100.

[0051] Furthermore, as in the above-described embodiment, the control information may also include contract information related to the contract of the UE 100 to be controlled. According to this configuration, it is possible to perform retry control of signal transmission to the UE 100 in accordance with the contract of the UE 100. However, the contract information related to the contract of the UE 100 does not necessarily need to be used.

[0052] Furthermore, as in the above-described embodiment, a cause to be transmitted to the UE 100 to be controlled may be determined based on a model generated by machine learning. This configuration makes it possible to more appropriately control the retry of signal transmission to the UE 100. However, the above-described model does not necessarily have to be used to determine a cause to be transmitted to the UE 100 to be controlled.

[0053] Furthermore, as in the above-described embodiment, a cause for controlling a retry, that is, a cause according to a use case, may be transmitted to the UE 100. According to this configuration, it is possible to perform retry control of signal transmission to the UE 100 according to the cause for controlling a retry. However, the cause for controlling a retry does not necessarily have to be used.

[0054] In the above-described embodiment, the communication control device was the UECF 10, which is not included in conventional mobile communication networks. According to this configuration, even if there are multiple nodes in the mobile communication network N that detect an opportunity to send a Cause to the UE 100, such as the AMF 20 and the SMF 30, the control according to this embodiment can be performed by newly providing one node, the UECF 10, in the mobile communication network N.

[0055] However, the communication control device does not need to be the UECF10, and may be another node included in the mobile communication network N. For example, the communication control device may be a node, such as an AMF or an SMF, that detects an opportunity to send a Cause to the UE100 and transmits the Cause to the UE100. In this case, the AMF, SMF, etc., which are nodes that transmit the Cause, may each have the function of the UECF10 described above. In this case, information indicating a criterion for determining a Cause to be transmitted to the UE100 (for example, the error message table shown in FIG. 2) may be stored in a node such as the UECF, and the AMF, SMF, etc., which are nodes that transmit the Cause, may acquire the information indicating the criterion at a point in time before transmitting the Cause (for example, after receiving a signal requesting location registration or after receiving a signal corresponding to a service request). Furthermore, some of the functions included in the UECF10 may be included in the AMF, SMF, etc.

[0056] In addition, in this embodiment, the signal sent to UE100 to control the retry of signal transmission to the mobile communication network N is a Cause, but the signal may be other than a Cause as long as it is meaningful for the same control as in this embodiment.

[0057] The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or multiple devices with software.

[0058] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocation, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0059] For example, the UECF10 (or a physical server or the like in which the UECF10 is implemented) according to an embodiment of the present disclosure may function as a computer that performs processing of the method of the present disclosure. FIG. 4 is a diagram illustrating an example of a hardware configuration of the UECF10 (or a physical server or the like in which the UECF10 is implemented) according to an embodiment of the present disclosure. The above-described UECF10 (or a physical server or the like in which the UECF10 is implemented) may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like. In addition, other components of the mobile communication network N and the hardware configuration of the UE100 may also be as described herein.

[0060] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of UECF10 (or a physical server on which it is implemented) may be configured to include one or more of the devices shown in the figure, or may be configured to exclude some of the devices.

[0061] Each function in UECF10 is realized by loading specified software (programs) onto hardware such as processor 1001 and memory 1002, causing processor 1001 to perform calculations, control communication via communication device 1004, and control at least one of reading and writing data in memory 1002 and storage 1003.

[0062] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, each function in the UECF10 described above may be realized by the processor 1001.

[0063] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, each function in the UECF 10 may be implemented by a control program stored in the memory 1002 and running on the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

[0064] The memory 1002 is a computer-readable recording medium and may be configured by, for example, at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store an executable program (program code), a software module, etc. for implementing a method according to one embodiment of the present disclosure.

[0065] Storage 1003 is a computer-readable recording medium and may be, for example, at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray® disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The storage medium provided in UECF10 (or a physical server on which UECF10 is implemented, etc.) may be, for example, a database, a server, or other appropriate medium including at least one of memory 1002 and storage 1003.

[0066] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, each function of the UECF 10 described above may be realized by the communication device 1004.

[0067] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0068] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0069] Furthermore, UECF10 (or a physical server or the like in which it is implemented) may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be implemented by the hardware. For example, processor 1001 may be implemented using at least one of these pieces of hardware.

[0070] The notification of information is not limited to the aspects / embodiments described in the present disclosure and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, and broadcast information (Master Information Block (MIB) and System Information Block (SIB))), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0071] Each aspect / embodiment described in the present disclosure may be applied to at least one of systems using LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (New Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark), IEEE 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), or other appropriate systems, and next-generation systems extended based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.) may also be applied.

[0072] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0073] In the present disclosure, a specific operation described as being performed by a base station may be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and another network node other than the base station (for example, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (for example, an MME and an S-GW) may also be used.

[0074] Information etc. may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0075] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

[0076] The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0077] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

[0078] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0079] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0080] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0081] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0082] Note that terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0083] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0084] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0085] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0086] In this disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0087] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

[0088] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0089] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0090] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, or the mobile body itself. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0091] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, a user terminal in the present disclosure may also be read as a base station.

[0092] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0093] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0094] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0095] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0096] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0097] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0098] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0099] The communication control device and the communication control method according to the present disclosure have the following configuration. [1] An acquisition unit that acquires control information including type information indicating the type of a mobile communication terminal to be controlled; a transmitter that transmits to the mobile communication terminal to be controlled a signal that performs control according to the control information acquired by the acquirer, the signal controlling a retry of signal transmission to the mobile communication network; A communication control device comprising: [2] The communication control device according to [1], wherein the acquisition unit acquires control information including contract information relating to the contract of the mobile communication terminal to be controlled. [3] The communication control device according to [1] or [2], wherein the transmitting unit determines a signal to be transmitted to the mobile communication terminal to be controlled based on a model generated by machine learning. [4] The communication control device according to any one of [1] to [3], wherein the transmission unit transmits a signal according to a cause for controlling the retry. [5] An acquisition step in which the communication control device acquires control information including type information indicating the type of the mobile communication terminal to be controlled; a transmission step in which the communication control device transmits to the mobile communication terminal to be controlled a signal for performing control according to the control information acquired in the acquisition step, the signal controlling retry of signal transmission to the mobile communication network; A communication control method including: [Explanation of symbols]

[0100] 10...UECF, 11...acquisition unit, 12...transmission unit, 20...AMF, 30...SMF, N...mobile communication network, 100...UE, 1001...processor, 1002...memory, 1003...storage, 1004...communication device, 1005...input device, 1006...output device, 1007...bus.

Claims

1. an acquisition unit that acquires control information including type information indicating the type of a mobile communication terminal to be controlled; a transmitter that transmits to the mobile communication terminal to be controlled a signal that performs control according to the control information acquired by the acquirer, the signal controlling a retry of signal transmission to the mobile communication network; A communication control device comprising:

2. The communication control device according to claim 1 , wherein the acquisition unit acquires control information including contract information relating to a contract of the mobile communication terminal to be controlled.

3. The communication control device according to claim 1 , wherein the transmission unit determines a signal to be transmitted to the mobile communication terminal to be controlled based on a model generated by machine learning.

4. The communication control device according to claim 1 , wherein the transmission unit transmits a signal according to a cause for controlling the retry.

5. an acquisition step in which the communication control device acquires control information including type information indicating the type of the mobile communication terminal to be controlled; a transmission step in which the communication control device transmits to the mobile communication terminal to be controlled a signal for performing control according to the control information acquired in the acquisition step, the signal controlling retry of signal transmission to the mobile communication network; A communication control method including:

Images