MOBILE COMMUNICATION SYSTEM, DETECTION SERVER, CONTROL APPARATUS, MOBILE COMMUNICATION APPARATUS, NETWORK OPTIMIZING METHOD, AND NON-TRANSITORY COMPUTER READABLE MEDIUM HAVING PROGRAM STORED THEREON

• US 20180084444A1
• Filed: 11/30/2017
• Published: 03/22/2018
• Est. Priority Date: 01/16/2012
• Status: Active Grant

• Current Assignee: NEC Corporation
• Original Assignee: NEC Corporation
• Inventors: IWAI, Takanori
• Granted Patent: US 10,382,982 B2
• Time in Patent Office: Days
• CPC Class Codes: G08G 1/0112 from the vehicle, e.g. floating car data [FCD]
• CPC Class Codes: H04B 7/26 at least one of which is mobile
• CPC Class Codes: H04W 24/02 Arrangements for optimising operational condition
• CPC Class Codes: H04W 40/005 Routing actions in the presence of nodes in sleep or doze mode
• CPC Class Codes: H04W 64/00 Locating users or terminals or network equipment for network management purposes, e.g. mobility management
• CPC Class Codes: H04W 76/10 Connection setup

Abstract

An object of the present invention is to provide a mobile communication system, a detection server, a control apparatus, a mobile communication apparatus, a network optimizing method, and a program which can execute optimization of network processing based on a change of use characteristics. A mobile communication system according to the present invention includes: a detection server that detects a characteristics change of a mobile communication apparatus based on an event notice transmitted from the mobile communication apparatus; and a control apparatus that determines control contents related to the mobile communication apparatus based on the characteristics change of the mobile communication apparatus detected by the detection server, and sets the determined control contents to a processing node that executes data transfer processing between the mobile communication apparatus and another mobile communication apparatus or control processing related to the data transfer processing.

Claims

1-19. -19. (canceled).

20. A server comprising:

a memory storing instructions; and

one or more processors configured to execute the instructions to send a first parameter indicating a communication pattern of a user equipment (UE) to a service entity which is connected to the server via an Application Programming Interface (API).

21. The server according to claim 20,

wherein the first parameter indicates at least one of:

a communication interval; and

whether the UE is stationary or mobile.

22. The server according to claim 20,

wherein the one or more processors are further configured to execute the instructions to send the first parameter when an application server is aware that the UE has started or stopped moving.

23. The server according to claim 20,

wherein a second parameter which is based on the first parameter is transmitted from the service entity, and

the second parameter is received by a mobility management entity.

24. The server according to claim 23,

wherein a third parameter, which is an information of a state transition of a UE, is derived by the mobility management entity using the second parameter.

25. The server according to claim 23,

wherein a third parameter, which is an information related to an idle period of a UE, is derived by the mobility management entity using the second parameter.

26. The server according to claim 23,

wherein a third parameter, derived by the mobility management entity using the second parameter, is provided to a radio base station by the mobility management entity.

27. A service entity comprising:

a memory storing instructions; and

one or more processors configured to execute the instructions to receive a first parameter indicating a communication pattern of a user equipment (UE) from a server which is connected to the service entity via an Application Programming Interface (API).

28. The service entity according to claim 27,

wherein the first parameter indicates at least one of:

a communication interval; and

whether the UE is stationary or mobile.

29. The service entity according to claim 27,

wherein the first parameter is sent when an application server is aware that the UE has started or stopped moving.

30. The service entity according to claim 27,

wherein the one or more processors are further configured to execute the instructions to send a second parameter which is based on the first parameter, and the second parameter is received by a mobility management entity.

31. The service entity according to claim 30,

wherein a third parameter, which is an information of a state transition of a UE, is derived by the mobility management entity using the second parameter.

32. The server according to claim 30,

wherein a third parameter, which is an information related to an idle period of a UE, is derived by the mobility management entity using the second parameter.

33. The service entity according to claim 30,

wherein a third parameter, derived by the mobility management entity using the second parameter, is provided to a radio base station by the mobility management entity.

34. A mobility management entity comprising:

a memory storing instructions; and

one or more processors configured to execute the instructions to receive a second parameter which is based on a first parameter indicating a communication pattern of a user equipment (UE), the second parameter sent from a service entity,

wherein the first parameter is sent to the service entity from a server which is connected to the service entity via an Application Programming Interface (API).

35. The mobility management entity according to claim 34,

wherein the first parameter indicates at least one of:

a communication interval; and

whether the UE is stationary or mobile.

36. The mobility management entity according to claim 34,

wherein the first parameter is sent when an application server is aware that the UE has started or stopped moving.

37. The mobility management entity according to claim 34,

wherein the one or more processors are further configured to execute the instructions to derive a third parameter, which is an information of a state transition of a UE, using the second parameter.

38. The mobility management entity according to claim 34,

wherein the one or more processors are further configured to execute the instructions to derive a third parameter, an information related to an idle period of a UE, using the second parameter.

39. The mobility management entity according to claim 34,

wherein the one or more processors are further configured to execute the instructions to:

derive a third parameter using the second parameter, and

provide the third parameter to a radio base station.

40. A radio base station comprising:

a memory storing instructions; and

one or more processors configured to execute the instructions to receive a third parameter from a mobility management entity, the third parameter derived by the mobility management entity using a second parameter which is based on a first parameter indicating a communication pattern of a user equipment (UE), the second parameter sent from a service entity,

wherein the first parameter is sent to the service entity from a server which is connected to the service entity via an Application Programming Interface (API).

41. A user equipment (UE) comprising:

a memory storing instructions; and

one or more processors configured to execute the instructions to communicate with a server, wherein a first parameter indicating a communication pattern of the UE is sent from the server to a service entity which is connected to the server via an Application Programming Interface (API).