SP310939WO00
1/54
Description
Title of Invention
COMMUNICATION DEVICE, COMMUNICATION CONTROL METHOD, AND
5 COMMUNICATION SYSTEM
Technical Field
[0001]
The present disclosure relates to a communication device, a communication
10 control method, and a communication system.
Background Art
[0002]
Recently, a form of communication referred to as machine-type
15 communication (MTC) communication or machine-to-machine (M2M)
communication in which a terminal device connected to a communication network
independently performs communication without involving human intervention has
been widely used. For example, a household gas meter is used as an MTC terminal
and the remaining amount of gas is periodically transmitted from the meter to a
20 server of a provider, so that the provider can recognize an amount of gas used in each
household without requiring an inspector to perform a meter reading operation. In
addition, the MTC communication, for example, can be used for various purposes
such as transmission of an inventory quantity from a vending machine, transmission
of the remaining amount of toner from a copier, transportation management in the
25 transportation industry, and monitoring for security. The use of the MTC
communication is also expected to expand in the fiiture.
[0003]
When the use of the MTC communication becomes widespread, the number
of terminals to be accommodated by a communication network significantly
30 increases. As a result, congestion of traffic within the communication network
occurs and a communication failure or deterioration of quality of service (QoS) is
SP310939WO00
2/54
likely to be problematic.
[0004]
The following Patent Literature 1 proposes technology for monitoring a
state of a communication node in a mobile communication network and changing a
5 forwarding path of a signal from a terminal when congestion or abnormality has been
detected.
Citation List
Patent Literature
10 [0005]
Patent Literature 1: JP2009-130657A
Summary of Invention
Technical Problem
15 [0006]
However, the technology disclosed in the above-described Patent Literature
1 is intended to reduce an influence of congestion when the congestion is already
occurring, and is not intended to avoid the occurrence of congestion itself
[0007]
20 Here, considering the above-described purposes of the MTC communication,
the MTC communication contains a risk of concentration of data transmission in a
specific time and a specific region. However, because the MTC communication is
usually systematically performed, the MTC communication is different from
communication from a terminal used by a human and it is sufficiently possible to
25 predict a risk of concentration of data transmission in the MTC communication. In
addition, the case in which a low delay is strictly necessary as in voice
communication, real-time streaming, and the like is comparatively less in the MTC
communication. Accordingly, it is estimated that it is possible to avoid or mitigate
the congestion of traffic in the MTC communication by systematically and smoothly
30 controlling a communication path of the MTC communication to a certain extent.
[0008]
SP310939WO00
3/54
It is desirable to provide a novel and improved mechanism capable of
avoiding or mitigating congestion of traffic in MTC communication.
Solution to Problem
5 [0009]
According to an embodiment of the present disclosure, there is provided a
communication device including a communication control unit that inserts, into a
destination field of a data packet, intermediate node designation information
designating an intermediate node different from a destination node of the data packet
10 on a path to the destination node, and a transmission unit that transmits the data
packet into which the intermediate node designation information is inserted.
[0010]
This communication device may be an MTC terminal, or a base station or
another communication node within a communication network that receives a data
15 packet transmitted from the MTC terminal. According to this configuration, the
data packet transmitted from the MTC terminal is routed through the intermediate
node without necessarily being transmitted along the shortest path to the destination
node of the data packet.
[0011]
20 The communication device may further include a reception unit that
receives the data packet transmitted from a terminal device or transmitted to the
terminal device. The communication control unit may insert the intermediate node
designation information into the destination field of the data packet when the
terminal device is a machine-type communication (MTC) terminal.
25 [0012]
The communication control unit may specify an intermediate node to be
designated for the data packet from a plurality of intermediate node candidates using
intermediate node data for specifying the intermediate node to be designated.
[0013]
30 The communication control unit may transcribe information described in the
destination field upon receipt of the data packet to another field.
SP310939WO00
4/54
[0014]
The communication control unit may add a flag indicating that the
destination field is changed to the data packet.
[0015]
5 The communication control unit may insert control information used for
enabling the intermediate node to identify the destination node of the data packet into
the data packet.
[0016]
The communication device may be one of a plurality of intermediate node
10 candidates.
[0017]
The communication device may be an MTC terminal that generates the data
packet.
[0018]
15 According to another embodiment of the present disclosure, there is
provided a communication control method including inserting, into a destination
field of a data packet, intermediate node designation information designating an
intermediate node different from a destination node of the data packet on a path to
the destination node, and transmitting the data packet into which the intermediate
20 node designation information is inserted.
[0019]
According to another embodiment of the present disclosure, there is
provided a communication device including a reception unit that receives a data
packet transmitted from a terminal device or transmitted to the terminal device,
25 wherein the communication device is designated in a destination field, a
communication control unit that identifies a destination node of the data packet from
information included in a field different from the destination field within the data
packet, and inserts destination node designation information designating the
identified destination node into the destination field, and a transmission unh that
30 transmits the data packet into which the destination node designation information is
inserted.
SP310939WO00
5/54
[0020]
The communication device may further include a storage unit that stores
destination node data in which control information within the data packet is
associated with the destination node of the data packet. The communication control
5 unit may identify the destination node of the data packet using the destination node
data.
[0021]
The control information may include information specifying a terminal
identifier (ID), a class, or a group of the terminal device, an application (AP) ID or a
10 class of an AP relating to the data packet, or a provider that provides the AP.
[0022]
The communication device may further include an information management
unit that acquires update data for updating the destination node data from an
information management server and updates the destination node data using the
15 acquired update data.
[0023]
The communication control unit may identify the destination node of the
data packet from information transcribed from the destination field to a field
different from the destination field.
20 [0024]
According to another embodiment of the present disclosure, there is
provided a communication control method for use in a communication device within
a communication network including a plurality of communication nodes, including
receiving a data packet transmitted from a terminal device or transmitted to the
25 terminal device, wherein the communication device is designated in a destination
field, identifying a destination node of the data packet from information included in a
field different from the destination field within the data packet, inserting destination
node designation information designating the identified destination node into the
destination field, and transmitting the data packet into which the destination node
30 designation information is inserted.
[0025]
SP310939WO00
6/54
According to another embodiment of the present disclosure, there is
provided a communication system including a first communication device including
a communication control unit that inserts, into a destination field of a data packet,
intermediate node designation information designating an intermediate node different
5 from a destination node of the data packet on a path to the destination node, and a
transmission unit that transmits the data packet into which the intermediate node
designation information is inserted, and a second communication device including a
reception unit that receives a data packet transmitted from a terminal device or
transmitted to the terminal device, wherein an own device is designated in a
10 destination field, a communication control unit that identifies a destination node of
the data packet from information included in a field different from the destination
field within the data packet, and inserts destination node designation information
designating the identified destination node into the destination field, and a
transmission unit that transmits the data packet into which the destination node
15 designation information is inserted. The second communication device may be a
candidate for the intermediate node.
[0026]
According to another embodiment of the present disclosure, there is
provided a communication device including a storage unit that stores destination
20 node data in which control information within a data packet transmitted from an
MTC terminal or transmitted to the MTC terminal is associated with a destination
node of the data packet, a management unit that manages an update of the destination
node data stored by the storage unit, and a transmission unit that transmits update
data relating to the destination node data to an intermediate node different from the
25 destination node on a path to the destination node of the data packet.
[0027]
The control information may include information specifying a terminal ID, a
class, or a group of an MTC terminal, an AP ID or a class of an AP relating to the
data packet, or a provider that provides the AP.
30
Advantageous Effects of Invention
SP310939WO00
7/54
[0028]
As described above, in accordance with the technology of the present
disclosure, congestion of traffic can be avoided or mitigated in MTC communication.
5 Brief Description of Drawings
[0029]
[Fig. 1] Fig. 1 is a schematic diagram illustrating an outline of a communication
system in accordance with a first embodiment.
[Fig. 2] Fig. 2 is a block diagram illustrating an example of a configuration of a
10 terminal device in accordance with the first embodiment.
[Fig. 3] Fig. 3 is an explanatory diagram illustrating an example of a packet format.
[Fig. 4] Fig. 4 is a flowchart illustrating an example of a flow of a data transmission
process in accordance with the first embodiment.
[Fig. 5] Fig. 5 is a block diagram illustrating an example of a configuration of a base
15 station in accordance with the first embodiment.
[Fig. 6] Fig. 6 is a flowchart illustrating an example of a flow of a control
information insertion process in accordance with the first embodiment.
[Fig. 7] Fig. 7 is a block diagram illustrating an example of a configuration of a
forwarding node in accordance with the first embodiment.
20 [Fig. 8A] Fig. 8A is an explanatory diagram illustrating a first example of forwarding
destination data.
[Fig. 8B] Fig. 8B is an explanatory diagram illustrating a second example of
forwarding destination data.
[Fig. 9] Fig. 9 is a flowchart illustrating an example of a data forwarding process in
25 accordance with the first embodiment.
[Fig. 10] Fig. 10 is a schematic diagram illustrating an outline of a communication
system in accordance with a second embodiment.
[Fig. 11] Fig. 11 is a block diagram illustrating an example of a configuration of a
terminal device in accordance with the second embodiment.
30 [Fig. 12] Fig. 12 is a flowchart illustrating an example of a flow of a data
transmission process in accordance with the second embodiment.
SP310939WO00
8/54
[Fig. 13] Fig. 13 is a block diagram illustrating an example of a configuration of a
base station in accordance with the second embodiment.
[Fig. 14A] Fig. 14A is an explanatory diagram illustrating a first example of
intermediate node data.
5 [Fig. 14B] Fig. 14B is an explanatory diagram illustrating a second example of
intermediate node data.
[Fig. 15A] Fig. 15A is an explanatory diagram illustrating a first example of a
destination field update process in accordance with the second embodiment.
[Fig. 15B] Fig. 15B is an explanatory diagram illustrating a second example of a
10 destination field update process in accordance with the second embodiment.
[Fig. 15C] Fig. 15C is an explanatory diagram illustrating a third example of a
destination field update process in accordance with the second embodiment.
[Fig. 15D] Fig. 15D is an explanatory diagram illustrating a fourth example of a
destination field update process in accordance with the second embodiment.
15 [Fig. 15E] Fig. 15E is an explanatory diagram illustrating a fifth example of a
destination field update process in accordance with the second embodiment.
[Fig. 16A] Fig. 16A is a flowchart illustrating an example of a flow of a data
forwarding process by the base station in accordance with the second embodiment.
[Fig. 16B] Fig. 16B is a flowchart illustrating another example of a flow of a data
20 forwarding process by the base station in accordance with the second embodiment.
[Fig. 17] Fig. 17 is a block diagram illustrating an example of a configuration of an
intermediate node in accordance with the second embodiment.
[Fig. 18] Fig. 18 is an explanatory diagram illustrating an example of destination
node data.
25 [Fig. 19A] Fig. 19A is a flowchart illustrating an example of a flow of a data
forwarding process by the intermediate node in accordance with the second
embodiment.
[Fig. 19B] Fig. 19B is a flowchart illustrating another example of a flow of a data
forwarding process by the intermediate node in accordance with the second
30 embodiment.
[Fig. 20] Fig. 20 is an explanatory diagram illustrating an example of a
SP310939WO00
9/54
communication path capable of being implemented in accordance with the second
embodiment.
[Fig. 21] Fig. 21 is a block diagram illustrating an example of a configuration of an
information management server in accordance with the second embodiment.
5 [Fig. 22] Fig. 22 is an explanatory diagram illustrating an example of update data.
[Fig. 23 A] Fig. 23A is a flowchart illustrating a first example of a flow of an update
data distribution process in accordance with the second embodiment.
[Fig. 23B] Fig. 23B is a flowchart illustrating a second example of a flow of an
update data distribution process in accordance with the second embodiment.
10 [Fig. 24] Fig. 24 is a flowchart illustrating an example of a flow of a destination node
data update process in accordance with the second embodiment.
Description of Embodiments
[0030]
15 Hereinafter, preferred embodiments of the present invention will be
described in detail with reference to the appended drawings. Note that, in this
specification and the drawings, elements that have substantially the same function
and structure are denoted with the same reference signs, and repeated explanation is
omitted.
20 [0031]
Hereinafter, "modes for carrying out the present invention" will be
described in the following order.
1. Description of First Embodiment
1-1. Outline of System
25 1-2. Terminal Device
1-3. Base Station
1.4. Forwarding Node
1.5. Summary of First Embodiment
1-6. Application Example
30 2. Description of Second Embodiment
2-1. Oufline of System
SP310939WO00
10/54
2-2. Terminal Device
2-3. Base Station
2-4. Intermediate Node
2-5. Example of Communication Path
5 2-6. Information Management Server
2-7. Management of Discontinuous Reception (DRX)
2-8. Summary of Second Embodiment
2-9. Application Example
[0032]
10 <1. Description of First Embodiment>
[1-1. Outline of System]
First, the first embodiment will be described using Figs. 1 to 9. Fig. 1 is a
schematic diagram illustrating an outline of a communication system 1 in accordance
with the first embodiment. Referring to Fig. 1, the communication system 1
15 includes a plurality of terminal devices 100a to lOOe, a plurality of base stations 120a
to 120d, a plurality of communication devices 140a to 140d, and a plurality of
application (AP) servers 190a to 190c. The plurality of communication devices
140a to 140d form a core network 10 in the communication system 1. The base
station 120d and the AP servers 190a and 190b are connected to a network 20.
20 [0033]
In this specification, when it is not necessary to distinguish the terminal
devices 100a to lOOe from one another, they are collectively referred to as a terminal
device 100. The same is also true for a base station 120 (120a to 120d), a
communication device 140 (140a to 140d), and an AP server 190 (190a to 190c).
25 [0034]
The terminal device 100 is a wireless communication device that operates as
an MTC terminal. Each terminal device 100 transmits and receives a radio signal to
and from the base station 120 that provides a wireless communication service to a
cell to which the terminal device 100 belongs. For example, the terminal device
30 100 generates AP data such as an amount of used gas or an inventory quantity of a
vending machine, and transmits a data packet including the generated AP data to the
SP310939WO00
11/54
base station 120. The data packet transmitted from the terminal device 100 to the
base station 120 is ultimately delivered to a desired AP server 190 via several
communication nodes.
[0035]
5 The base station 120, for example, is a communication node that provides
the wireless communication service within a cell extending around its own device
according to a cellular communication scheme represented by long term evolution
(LTE), LTE-Advanced, or the like. The base station 120, for example, receives a
data packet including the AP data generated by the terminal device 100, and forwards
10 the received data packet to the communication device 140 of the core network 10.
In addition, the base station 120 receives a data packet addressed to the terminal
device 100 forwarded via the core network 10, and forwards the received data packet
to the destination terminal device 100.
[0036]
15 In the example of FIG. 1, the base stations 120a to 120c are so-called
macrocell base stations directly connected to the core network 10. On the other
hand, the base station 120d is a femtocell base station (also referred to as home eNB
(HeNB) in LTE) connected to the core network 10 via the network 20. These base
stations 120 may also provide the wireless communication service to a general user
20 terminal as well as an MTC terminal like the terminal device 100.
[0037]
The communication device 140 is a communication node that forms the core
network 10. Each communication device 140, for example, may be a radio network
controller (RNC), a mobility management entity (MME), a home subscriber server
25 (HSS), a serving GPRS support node (SGSN), a gateway GPRS support node
(GGSN), or the like. In addition, each communication device 140, for example,
may be a network device such as a switch or router connected between the
communication nodes. The communication device 140, for example, receives a
data packet transmitted from the terminal device 100 or transmitted to the terminal
30 device 100, and sequentially forwards the received data packet so that the received
data packet is delivered to a destination AP server 190.
SP310939WO00
12/54
[0038]
Among the communication devices 140 illustrated in Fig. 1, for example,
the communication device 140d is the GGSN having a function of a so-called
gateway, and is located in a boundary between the core network 10 and the network
5 20. The network 20, for example, may be an Internet protocol (IP) network such as
the Internet, or may be a non-IP network such as an asynchronous transfer mode
(ATM) network.
[0039]
The AP server 190, for example, is a server device having an AP function
10 such as planning for charging of a gas fee or delivery of products for a vending
machine. A server device using AP data transmitted from the MTC terminal is also
referred to as an MTC server. The AP server 190 may be connected to the network
20 or may be located within the core network 10. In the example of Fig. 1, the AP
servers 190a and 190b are connected to the network 20, and the AP server 190c is
15 located within the core network 10. The AP server 190c may be implemented on
physically the same device as a communication node that forms the core network 10.
[0040]
The AP server 190, for example, ultimately receives a data packet
transmitted from the terminal device 100. The AP server 190 executes the AP
20 function as described in the above example by acquiring the AP data included in the
received data packet. In addition, the AP server 190 may provide a user with a user
interface for accepting an input of a setting relating to the MTC terminal. The
setting relating to the MTC terminal, for example, can include a setting relating to a
schedule of MTC communication between the AP server 190 and the terminal device
25 100.
[0041]
When there are a large number of MTC terminals in the communication
system 1 illustrated in Fig. 1, data packets transmitted from the MTC terminals are
likely to cause congestion on a communication path to the destination AP server 190.
30 In particular, when an AP necessary to collect periodic data is introduced, data
packets can be simultaneously transmitted from the terminal devices 100 in a specific
SP310939WO00
13/54
time or a specific region. However, because MTC communication is systematically
performed, congestion by the MTC communication can be avoided before the
congestion occurs. In addition, when the purpose of the MTC communication is
data collection, the data packet may not necessarily be delivered to the AP server 190
5 at a maximum rate. In this embodiment, the occurrence of congestion of traffic in
the MTC communication is avoided or mitigated by adopting a configuration of each
device described from the next section.
[0042]
In this specification, it should be noted that the term "communication node"
10 or "communication device" can be any of the terminal device 100, the base station
120, the communication device 140, and the AP server 190 illustrated in FIG. 1 when
no particular reference sign is attached.
[0043]
[1-2. Terminal Device]
15 (1) Configuration Example of Device
Fig. 2 is a block diagram illustrating an example of a configuration of the
terminal device 100 in accordance with this embodiment. Referring to Fig. 2, the
terminal device 100 includes an AP unit 102, a storage unit 104, a communication
control unit 110, a wireless transmission unit 112, and a wireless reception unit 114.
20 [0044]
The AP unit 102 generates AP data to be transmitted to the AP server 190,
and outputs the generated AP data to the communication control unit 110. The AP
data generated by the AP unit 102, for example, can include an arbitrary type of data
such as an amount of used gas, an inventory quantity of a vending machine, the
25 remaining amount of toner of a copier, or position data for transport management
according to a purpose of an AP. The generation of AP data, for example, may be
periodically performed at a preset time or frequency. Alternatively, the generation
of the AP data may be performed using a predetermined event (for example, a
decrease of more than a given quantity in an inventory quantity) as a trigger.
30 [0045]
The storage unit 104 stores programs and data for processing by the AP unit
SP310939WO00
14/54
102 and the communication control unit 110 using a storage medium such as a hard
disk or a semiconductor memory. In addition, the storage unit 104 stores data
serving as a base for the generation of the AP data by the AP unit 102. In addition,
the storage unit 104 pre-stores at least part of control information inserted into a data
5 packet as will be described later.
[0046]
When the AP data to be transmitted to the AP server 190 is input from the
AP unit 102, the communication control unit 110 generates a data packet including
the AP data. The communication control unit 110 causes the generated data packet
10 to be transmitted from the wireless transmission unit 112. In addition, when a data
packet is received by the wireless reception unit 114, the communication control unit
110 acquires AP data included in the data packet and outputs the acquired AP data to
the AP unit 102.
[0047]
15 The wireless transmission unit 112 and the wireless reception unit 114 have
an antenna and a radio frequency (RF) circuit. The wireless transmission unit 112
transmits a data packet generated by the communication control unit 110 as a radio
signal on an air interface to the base station 120. In addition, the wireless reception
unit 114 receives a data packet transmitted from the base station 120 as a radio signal
20 on the air interface, and outputs the received data packet to the communication
control unit 110.
[0048]
(2) Example of Packet Format
Fig. 3 is an explanatory diagram illustrating an example of a packet format
25 of a data packet transmitted by the terminal device 100 in this embodiment.
Referring to FIG. 3, the data packet in accordance with this embodiment includes a
header area HS and a data area DS. As illustrated in Fig. 3, the header area HS has
eight fields Fl to F8 in which control information is stored. The data area DS is an
area for storing the above-described AP data.
30 [0049]
In the destination field Fl of the header area HS, informafion designating a
SP310939WO00
15/54
destination node of the data packet is stored. The information stored in the
destination field Fl, for example, may be an Internet protocol (IP) address of the
destination node, a media access control (MAC) address, a host name, or another
unique identifier. When the terminal device 100 transmits AP data, the AP server
5 190 that provides a corresponding AP function becomes the destination node. In
addition, when the terminal device 100 receives a data packet, the terminal device
100 becomes the destination node.
[0050]
In the transmission source field F2, transmission source node information
10 designating a transmission source node of the data packet is stored. When the
terminal device 100 transmits AP data to the AP server 190, the terminal device 100
generating the AP data becomes the transmission source node.
[0051]
The application (AP) class field F3 and the AP identifier (ID) field F4 are
15 fields for storing an AP class and an AP ID, respectively. The AP class and the AP
ID are control information regarding an AP relating to a data packet. The AP class
is a class to which an individual AP belongs when APs have been classified into
several classes. For example, a QoS class classified according to QoS requirements
may be used as the AP class. The AP ID is an ID for uniquely identifying an
20 individual AP. Values of the AP class and the AP ID supported by each terminal
device 100 can be pre-stored by the storage unit 104.
[0052]
The terminal class field F5, the terminal group (Grp) field F6, and the
terminal ID field F7 are fields for storing a terminal class, a terminal group, and a
25 terminal ID. The terminal class, the terminal group, and the terminal ID are control
information regarding an MTC terminal. When MTC terminals have been
classified into several classes and groups, the terminal class and the terminal group
are a class and a group to which an individual terminal device belongs, respectively.
For example, according to 3'^'' Generation Partnership Project (3GPP) Technical
30 Specification (TS) 22.368, the MTC terminal can be classified as security equipment,
transportation-related equipment, payment equipment, health care equipment, remote
SP310939WO00
16/54
control equipment, measurement equipment, consumer equipment, and the like
according to its service field. In addition, for example, as in a vending machine or
point of sales (POS) equipment for the payment equipment, a power meter or a gas
meter for the measurement equipment, the MTC terminal can be classified in further
5 detail according to its purpose. The terminal class, for example, may be a class of
the MTC terminal corresponding to the service field or purpose. In addition, 3GPP
TS 22.368, for example, proposes allocation of MTC terminals to one or more
groups defined in terms of a QoS policy, a maximum bit rate, and the like. The
terminal group, for example, may be a group defined to manage the MTC terminals
10 based on the above-described group. Of course, the classification of the MTC
terminal according to another concept may be used. The terminal ID is an ID for
uniquely identifying an individual terminal device. Values of the terminal class, the
terminal group, and the terminal ID of each terminal device 100 can be pre-stored by
the storage unit 104.
15 [0053]
The provider ID field F8 is a field for storing a provider ID that uniquely
specifies a provider that provides an AP relating to a data packet transmitted by each
terminal device 100. In addition, the provider ID can also be pre-stored by the
storage unit 104.
20 [0054]
(3) Flow of Data Transmission Process
Fig. 4 is a flowchart illustrating an example of the flow of the data
transmission process by the terminal device 100 in accordance with this embodiment.
[0055]
25 Referring to Fig. 4, first, the AP unit 102 of the terminal device 100
generates AP data periodically or according to occurrence of a predetermined event
(step SI02). Next, the communication control unit 110 acquires control information
regarding an AP such as an AP class, an AP ID, or the like for the generated AP data
from the storage unit 104 (step SI04). In addition, the communication control unit
30 110 acquires control information such as a terminal class, a terminal group, a
terminal ID, and the like regarding an MTC terminal of the terminal device 100 from
SP310939WO00
17/54
the storage unit 104 (step SI06). Next, the communication control unit 110
generates a data packet having a paclcet format illustrated in Fig. 3 using the acquired
control information and the AP data (step SI08). Here, a destination of the
generated data packet, for example, can be designated by the AP unit 102 in
5 association with the AP data. The wireless transmission unit 112 transmits the data
packet generated by the communication control unit 110 to the base station 120 (step
SllO).
[0056]
Although an example in which the terminal device 100 inserts the control
10 information into the data packet has been described, another communication node
(for example, the base station 120, the communication device 140, or the like) may
insert the control information into the data packet instead of the terminal device 100.
A device that inserts the control information into the data packet may be a device (for
example, a relay station or the like capable of intervention between the terminal
15 device 100 and the base station 120) not illustrated in Fig. 1. In the next section, an
example in which the base station 120 inserts part of the control information into the
data packet will be described.
[0057]
[1-3. Base Station]
20 (1) Configuration Example of Device
Fig. 5 is a block diagram illustrating an example of a configuration of the
base station 120 in accordance with this embodiment. Referring to Fig. 5, the base
station 120 includes a wireless reception unit 122, a wireless transmission unit 124, a
transmission unit 126, a reception unit 128, a storage unit 130, and a communication
25 control unit 132.
[0058]
The wireless reception unit 122 and the wireless transmission unit 124 have
an antenna and an RF circuit for performing wireless communication among a
plurality of terminal devices 100. The wireless reception unit 122 receives a data
30 packet transmitted from the terminal device 100, and outputs the received data packet
to the communication control unit 132. In addition, when a data packet addressed
SP310939WO00
18/54
to the terminal device 100 is input from the communication control unit 132, the
wireless transmission unit 124 transmits the data packet to the terminal device 100.
[0059]
The transmission unit 126 and the reception unit 128 are communication
5 interfaces for enabling the base station 120 to perform communication with the
communication device 140 of the core network 10. When the data packet is input
from the communication control unit 132, the transmission unit 126 transmits the
data packet to the core network 10. When the data packet is received from the core
network 10, the reception unit 128 outputs the data packet to the communication
10 control unit 132.
[0060]
The storage unit 130 stores a program and data for processing by the
communication control unit 132 using a storage medium. In addition, the storage
unit 130 may pre-store part of the control information illustrated in Fig. 3 in
15 association with a terminal ID or address information of each terminal device 100.
[0061]
The communication control unit 132, for example, causes the base station
120 to operate as a base station for cellular communication according to standard
specs of LTE, LTE-A, or the like. In addition, in this embodiment, the
20 communication control unit 132 can insert the above-described control information
into the data packet transmitted from the terminal device 100 instead of the terminal
device 100. For example, when the data packet from the terminal device 100 is
input from the wireless reception unit 122, the communication control unit 132
acquires control information associated with a terminal ID or a transmission source
25 address described within the data packet from the storage unit 130. The
communication control unit 132 inserts the acquired control information into the data
packet.
[0062]
(2) Flow of Control Information Insertion Process
30 Fig. 6 is a flowchart illustrating an example of the flow of the control
information insertion process by the base station 120 in accordance with this
SP310939WO00
19/54
embodiment.
[0063]
Referring to Fig. 6, first, the wireless reception unit 122 of the base station
120 receives a data packet transmitted from the terminal device 100 (step SI22).
5 The wireless reception unit 122 outputs the received data packet to the
communication control unit 132. Next, the communication control unit 132
determines whether the received data packet is a packet for MTC communication
(step S124). The packet for the MTC communication includes both a packet for
which a transmission source is an MTC terminal and a packet for which an ultimate
10 destination is an MTC terminal. The communication control unit 132, for example,
can determine whether the data packet is a packet for MTC communication by
referring to a terminal group or a terminal class included in the data packet or
comparing a terminal ID included in the data packet with a pre-registered ID list.
Alternatively, the communication control unit 132, for example, may determine
15 whether the data packet is a packet for MTC communication by referring to an AP
class included in the data packet or comparing an AP ID included in the data packet
with a pre-registered ID list. Here, if the data packet is the packet for the MTC
communication, then the process of steps SI 26 and SI 28 is performed.
[0064]
20 When a device of the transmission source is the MTC terminal, the
communication control unit 132 inserts control information (the AP class, the AP ID,
and the like) regarding an AP into the data packet (step SI26). In addition, the
communication control unit 132 inserts control information (the terminal class, the
terminal group, or the like) regarding the MTC terminal into the data packet (step
25 S128).
[0065]
Next, the communication control unit 132 regenerates the data packet (step
SI30). The regenerated data packet is forwarded from the transmission unit 126 to
the core network 10 (step SI32).
30 [0066]
When the terminal device 100 inserts all control information to be used for a
SP310939WO00
20/54
data forwarding process by the communication device 140 (the forwarding node) into
the data packet as will be described next, the control information insertion process by
the base station 120 illustrated in FIG. 6 is omitted. In this case, like the data packet
transmitted from a normal user terminal, the data packet transmitted from the
5 terminal device 100 is forwarded by the base station 120 to the core network 10.
[0067]
[1-4. Forwarding Node]
(1) Configuration Example of Device
Fig. 7 is a block diagram illustrating an example of a configuration of the
10 communication device 140 in accordance with this embodiment. Referring to Fig.
7, the communication device 140 includes a reception unit 142, a transmission unit
144, a storage unit 150, and a communication control unit 152. .
[0068]
The reception unit 142 and the transmission unit 144 are communication
15 interfaces for enabling the communication device 140 to perform communication
with other communication devices. When a data packet is received from another
communication device, the reception unit 142 outputs the data packet to the
communication control unit 152. When a data packet is input from the
communication control unit 152, the transmission unit 144 transmits the data packet
20 to another communication device.
[0069]
The storage unit 150 stores a program and data for processing by the
communication control unit 152 using a storage medium. In addition, the storage
unit 150 stores forwarding destination data associated with classification based on
25 control information within a data packet and a forwarding destination node of the
data packet. An example of the forwarding destination data stored by the storage
unit 150 will be described later.
[0070]
When a device of a transmission source of the data packet received by the
30 reception unit 142 is an MTC terminal, the communication control unit 152 selects a
forwarding destination node of a data packet from a plurality of forwarding
SP310939WO00
21/54
destination node candidates so that traffic is distributed. More specifically, in this
embodiment, the communication control unit 152 selects the forwarding destination
node of the data paclcet based on control information within the data paclcet. For
example, the communication control unit 152 may classify the data packet according
5 to the control information within the data packet, and select the forwarding
destination node associated with the classification of the data packet in the
forwarding destination data stored by the storage unit 150 as the forwarding
destination node of the data packet. Alternatively, the communication control unit
152 may select the forwarding destination node of each data packet, for example, so
10 that forwarding destinations of data packets belonging to the same classification may
be distributed to a plurality of forwarding destination nodes. The selection of the
forwarding destination node by the communication control unit 152 is typically
performed regardless of a routing metric relating to a path to a destination node of
the data packet. That is, the communication device 140 in accordance with this
15 embodiment does not necessarily select a forwarding destination node in which a
metric such as the number of hops to the destination node or costs of a
communication path is minimized.
[0071]
Figs. 8A and 8B are explanatory diagrams each illustrating an example of
20 forwarding destination data available for selection of a forwarding destination node
by the communication device 140.
[0072]
Referring to Fig. 8A, forwarding destination data 151a is shown as a first
example. The forwarding destination data 151a has three data items of an "AP
25 class," a "terminal ID," and a "forwarding destination node." In the first example,
the communication control unit 152 classifies data packets into six categories
according to AP classes and terminal IDs included in control information within the
data packets. For example, when the AP class is "CI," the data packet is classified
into one of first to fourth categories according to two lower-order bits of the terminal
30 ID. The forwarding destination node of the data packet classified into the first
category (the two lower-order bits of the terminal ID = [00]) is a node Nl. The
SP310939WO00
22/54
forwarding destination node of the data packet classified into the second category
(the two lower-order bits of the terminal ID = [01]) is a node N2. The forwarding
destination node of the data packet classified into the third category (the two lowerorder
bits of the terminal ID = [10]) is a node N3. The forwarding destination node
5 of the data packet classified into the fourth category (the two lower-order bits of the
terminal ID = [11]) is a node N4. In addition, when the AP class is "C2," the data
packet is classified into a fifth category regardless of the terminal ID. The
forwarding destination node of the data packet classified into the fifth category is a
node N5. When the AP class is "C3," the data packet is classified into a sixth
10 category regardless of the terminal ID. The forwarding destination node of the data
packet classified into the sixth category is a node N6.
[0073]
The AP class "CI," for example, is a class in which a low delay is
recommended in relation to QoS (for example, an upper limit of an allowed delay is
15 designated). In this case, it is possible to avoid the occurrence of congestion and
reduce a risk of QoS violation by distributing the forwarding destination of the data
packet to a plurality of forwarding destination nodes according to a terminal ID as in
the first example. The communication control unit 152, for example, may distribute
the forwarding destination of the data packet of the AP class "CI" among the four
20 forwarding destination nodes Nl to N4 in a round-robin scheme or a random scheme
without using the terminal ID.
[0074]
In addition, in the first example, data packets of different AP classes are
forwarded to different forwarding destination nodes. For example, the nodes N5
25 and N6 may be nodes having throughput not higher than that of the nodes Nl to N4
or nodes having low-speed links. The congestion of traffic is less likely to be
caused by selecting a different forwarding destination node for every AP.
[0075]
Referring to Fig. 8B, forwarding destination data 151b is illustrated as the
30 second example. The forwarding destination data 15lb has two data items such as a
"terminal class" and a "forwarding destination node". In the second example, the
SP310939WO00
23/54
communication control unit 152 classifies data packets into four categories according
to terminal classes included in control information of the data packets. For example,
when the terminal class is "Tl", the data packet is classified into a first category, and
the node Nl serving as the forwarding destination node is selected. When the
5 terminal class is "T2", the data packet is classified into a second category, and the
node N2 serving as the forwarding destination node is selected. When the terminal
class is "T3", the data packet is classified into a third category, and the node N3
serving as the forwarding destination node is selected. When the terminal class is
"T4", the data packet is classified into a fourth category, and the node N4 serving as
10 the forwarding destination node is selected.
[0076]
In the second example, because data packets of different terminal classes are
forwarded to different forwarding destination nodes, forwarding destinations of data
packets are distributed between terminal classes. Thus, the possibility of congestion
15 of data packets is reduced. The communication control unit 152, for example, may
distribute forwarding destinations of data packets from the terminal devices 100 of
the same terminal class in the round-robin scheme or the random scheme among the
four forwarding destination nodes Nl to N4. In addition, a terminal group may be
used instead of the terminal class.
20 [0077]
All the communication devices 140 within the core network 10 may not
have a function serving as a forwarding destination node described here. In
addition, content of forwarding destination node data may differ for every
communication device 140 that functions as the forwarding destination node. That
25 is, a first forwarding destination node may have forwarding destination data
illustrated in Fig. 8A, while a second forwarding destination node may have
forwarding destination data illustrated in Fig. 8B. The forwarding destination node
data may be separately registered and updated in each forwarding destination node or
may be collectively managed and dynamically updated in an information
30 management server as described in the second embodiment.
[0078]
SP310939WO00
24/54
(2) Flow of Data Forwarding Process
Fig. 9 is a flowcliart illustrating an example of the data forwarding process
by the communication device 140 in accordance with this embodiment.
[0079]
5 Referring to Fig. 9, first, the reception unit 142 of the communication device
140 receives a data packet transmitted from the terminal device 100 (step SI42).
The reception unit 142 outputs the received data packet to the communication control
unit 152. Next, the communication control unit 152 determines whether the
received data packet is a packet for MTC communication (step S144). Here, if the
10 data packet is the packet for the MTC communication, the process proceeds to step
SI46. On the other hand, if the data packet is not the packet for the MTC
communication, the process proceeds to step SI 54.
[0080]
In step SI46, the communication control unit 152 acquires control
15 information included in a header area of the data packet (step SI46). Next, the
communication control unit 152 classifies the data packet into one of a plurality of
categories according to the acquired control information (step S148). Next, the
communication control unit 152 determines whether there is a forwarding destination
node corresponding to a category to which the data packet belongs in forwarding
20 destination node data stored in the storage unit 150 (step SI50). Here, when there is
a corresponding forwarding destination node in the forwarding destination node data,
the process proceeds to step SI52. On the other hand, when there is no
corresponding forwarding destination node in the forwarding destination node data,
the process proceeds to step SI54.
25 [0081]
In step SI52, the communication control unit 152 selects the forwarding
destination node associated with the category to which the data packet belongs in the
forwarding destination node data as the forwarding destination node of the data
packet (step SI52). On the other hand, in step SI54, the communication control
30 unit 152 selects a predetermined forwarding destination node as the forwarding
destination node of the data packet (step SI54). Here, the predetermined
SP310939WO00
25/54
forwarding destination node, for example, may be a forwarding destination node
fixedly defined in advance or may be a forwarding destination node dynamically
selected according to a routing metric.
[0082]
5 The transmission unit 144 forwards the data packet to the forwarding
destination node selected by the communication control unit 152 (step SI56).
[0083]
[1-5. Summary of First Embodiment]
The first embodiment has been described above using Figs. 1 to 9. In
10 accordance with this embodiment, when a data packet has been transmitted from an
MTC terminal, a forwarding destination node is selected from a plurality of
forwarding destination node candidates according to a forwarding node within a
communication network, and the data packet is forwarded to the selected forwarding
destination node. Thereby, it is possible to route traffic of MTC communication to
15 a plurality of routes and avoid or mitigate congestion. In addition, as a result, it is
possible to increase the number of MTC terminals capable of being accommodated
in a communication system.
[0084]
In addition, in accordance with this embodiment, a forwarding node selects
20 a forwarding destination node based on control information within a data packet.
This control information can be used to classify the data packet in terms of an AP
relating to MTC communication or a type of MTC terminal. According to this
configuration, it is possible to systematically distribute the data packet according to a
type of AP or a type of terminal. For example, it is also possible to distribute
25 forwarding destinations of data packets from the same type of APs or the same type
of terminals, which are likely to simultaneously transmit data, among a plurality of
forwarding destination nodes. Accordingly, it is possible to avoid the occurrence of
congestion by MTC communication in advance or effectively mitigate the congestion.
[0085]
30 In addition, it is possible to introduce a mechanism for the above-described
congestion avoidance without giving impact such as modification of a processing
SP310939WO00
26/54
logic to an existing device such as an MTC terminal or a base station normally using
information included in a data packet as control information.
[0086]
In addition, in accordance with this embodiment, the selection of the
5 forwarding destination node in the forwarding node can be performed regardless of a
routing metric relating to a path to a destination node. This is a concept focusing on
characteristics of MTC communication in which data may not necessarily be
delivered to a destination at a maximum rate in many cases as compared with
communication by a normal (human-used) user terminal. Accordingly, data packets
10 of MTC communication are not concentrated on a so-called "optimum"
communication path in terms of a routing metric. As a result, for example, a risk of
MTC communication interfering with non-MTC communication such as voice
communication or real-time streaming having high priority is reduced.
[0087]
15 [ 1 -6. Application Example]
In the first embodiment, an example in which a forwarding destination of a
data packet transmitted from an MTC terminal is mainly distributed among a
plurality of forwarding destination node candidates has been described. However, a
mechanism of selection of the above-described forwarding destination node is also
20 applicable to a data packet transmitted to the MTC terminal. For example, the
communication device 140 illustrated in Fig. 1 has additional forwarding destination
data describing a plurality of forwarding destination node candidates for a data
packet transmitted to the terminal device 100, and traffic is distributed based on
control information within the data packet and the additional forwarding destination
25 data, so that the forwarding destination node of the data packet transmitted to the
terminal device 100 may be selected from the plurality of forwarding destination
node candidates.
[0088]
<2. Description of Second Embodiment>
30 Next, the second embodiment will be described using Figs. 10 to 24. In
the first embodiment, a forwarding node distributes traffic of MTC communication
SP310939WO00
27/54
and hence concentration of traffic on a specific communication patli is prevented in
advance. In the second embodiment to be described in this section, the traffic of
MTC communication is guided to a path via an intermediate node to be described
later, and hence the concentration of traffic on a specific communication path is
5 ultimately prevented.
[0089]
[2-1. Outline of System]
Fig. 10 is a schematic diagram illustrating an outline of a communication
system 2 in accordance with the second embodiment. Referring to Fig. 10, the
10 communication system 2 includes a plurality of terminal devices 200a to 200d, a
plurality of base stations 220a to 220c, communication devices 140, 240a, and 240b
within the core network 10, an information management server 270, and a plurality
of AP servers 190a to 190c.
[0090]
15 Like the terminal device 100 of the first embodiment, the terminal device
200 is a wireless communication device that operates as an MTC terminal. Each
terminal device 200 transmits and receives a radio signal to and from the base station
220 that provides a wireless communication service to a cell to which the terminal
device 200 belongs. The terminal device 200, for example, generates AP data, and
20 transmits a data packet including the generated AP data to the base station 220. The
data packet transmitted from the terminal device 200 to the base station 220 is
ultimately delivered to a desired AP server 190 via several communication nodes.
However, in this embodiment, the terminal device 200 can designate information
designating a communication node different from a destination node, which is an
25 ultimate destination, in a destination field of the data packet. In this specification,
as described above, a communication node designated as a temporary destination
(not the ultimate destination) of the data packet transmitted from the MTC terminal is
referred to as an intermediate node.
[0091]
30 Like the base station 220 in accordance with the first embodiment, the base
station 220 is a communication node that provides a wireless communication service
SP310939WO00
28/54
within a cell extending around its own device, for example, according to a cellular
communication scheme represented by LTE, LTE-Advanced, or the like. The base
station 220, for example, receives a data packet including AP data generated by the
terminal device 200, and forwards the received data packet to a communication node
5 of the core network 10. However, in this embodiment, the base station 220 can
insert information designating an intermediate node into the destination field of the
forwarded data packet. In addition, the base station 220 receives the data packet
addressed to the terminal device 200 forwarded via the core network 10, and
forwards the received data packet to a destination terminal device 200.
10 [0092]
The communication device 240 is a communication node that is likely to be
designated as the intermediate node. Each communication device 240, for example,
may be an RNC, an MME, an HSS, an SGSN, a GGSN, or the like, or may be a
switch or a router that establishes a connection between communication nodes. The
15 communication device 240, for example, receives a data packet designated by its
own device in the destination field, identifies an appropriate destination node using
control information within the data packet, and forwards the data packet toward the
identified destination node.
[0093]
20 The information management server 270 is a communication device that
manages a master of the destination node data to be used when the intermediate node
identifies the destination node. In the example of Fig. 10, the information
management server 270 is connected to the network 20. However, the present
disclosure is not limited to this example, and the information management server 270,
25 for example, may be located in the core network 10. In addition, the information
management server 270 may be implemented on physically the same device as a
communication node that forms the core network 10. The information management
server 270 may manage a master of the forwarding destination data described in the
first embodiment in addition to the master of the destination node data.
30 [0094]
[2-2. Terminal Device]
SP310939WO00
29/54
(1) Configuration Example of Device
Fig. 11 is a block diagram illustrating an example of a configuration of the
terminal device 200 in accordance with this embodiment. Referring to Fig. 11, the
terminal device 200 includes an AP unit 102, a storage unit 204, a communication
5 control unit 210, a wireless transmission unit 112, and a wireless reception unit 114.
[0095]
The storage unit 204 stores programs and data for processing by the AP unit
102 and the communication control unit 210 using a storage medium. In addition,
like the storage unit 104 of the terminal device 100 in accordance with the first
10 embodiment, the storage unit 204 stores data serving as a base for generation of AP
data by the AP unit 102. In addition, the storage unit 204 pre-stores control
information inserted into a data packet. Further, in this embodiment, the storage
unit 204, for example, pre-stores intermediate node designation information
designating an intermediate node different from a destination node on a path to an
15 ultimate destination node of the data packet in association with an AP. The
intermediate node designation information, for example, may be an IP address, a
MAC address, a host name, or another unique ID of the intermediate node.
[0096]
When the AP data to be transmitted to the AP server 190 is input from the
20 AP unit 102, the communication control unit 210 generates a data packet including
the AP data. At this time, the communication control unit 210 can insert the
intermediate node designation information stored in association with an AP in the
storage unit 204 into the destination field of the data packet. The communication
control unit 210 causes the generated data packet to be transmitted from the wireless
25 transmission unit 112. In addition, when the data packet is received by the wireless
reception unit 114, the communication control unit 210 acquires the AP data included
in the data packet and outputs the acquired AP data to the AP unit 102.
[0097]
(2) Flow of Data Transmission Process
30 Fig. 12 is a flowchart illustrating an example of the flow of the data
transmission process by the terminal device 200 in accordance with this embodiment.
SP310939WO00
30/54
[0098]
Referring to Fig. 12, first, the AP unit 102 of the terminal device 200
generates AP data periodically or according to a predetermined event (step S202).
Next, the communication control unit 210 acquires control information regarding an
5 AP such as an AP class, an AP ID, or the like for the generated AP data from the
storage unit 204 (step S204). In addition, the communication control unit 210
acquires control information such as a terminal class, a terminal group, a terminal ID,
and the like regarding an MTC terminal of the terminal device 200 from the storage
unit 204 (step S206). Next, the communication control unit 210 acquires the
10 intermediate node designation information to be inserted into the destination field of
the data packet from the storage unit 204 (step S208). Next, the communication
control unit 210 generates a data packet including the acquired intermediate node
designation information and the control information in the header area and the data
area (step S210). The wireless transmission unit 112 transmits the data packet
15 generated by the communication control unit 210 to the base station 220 (step S212).
[0099]
Although an example in which the terminal device 200 inserts the control
information into the data packet has been described here, another communication
node (for example, the base station 220, the communication device 240, or the like)
20 may insert the control information into the data packet instead of the terminal device
200. In addition, as will be described next, instead of the terminal device 200, the
other communication node may insert the intermediate node designation information
into the destination field. A device that inserts the intermediate node designation
information into the destination field may be a device (for example, a relay station
25 capable of intervention between the terminal device 200 and the base station 220) not
illustrated in Fig. 10. In the next section, an example in which the base station 220
inserts part of the control information into the data packet will be described. In the
example of the next section, the terminal device 200 can insert the destination node
designation information designating the ultimate destination node into the destination
30 field as in a general data transmission process.
[0100]
SP310939WO00
31/54
[2-3. Base Station]
(1) Configuration Example of Device
Fig. 13 is a block diagram illustrating an example of a configuration of the
base station 220 in accordance with this embodiment. Referring to Fig. 13, the base
5 station 220 includes a wireless reception unit 122, a wireless transmission unit 124, a
transmission unit 126, a reception unit 128, a storage unit 230, and a communication
control unit 232.
[0101]
The storage unit 230 stores a program and data for processing by the
10 communication control unit 232 using a storage medium. In addition, the storage
unit 230 may pre-store at least part of the control information illustrated in Fig. 3 in
association with a terminal ID or address information of each terminal device 200.
In addition, in this embodiment, the storage unit 230 pre-stores intermediate node
data obtained by listing candidates for the intermediate node to be designated for the
15 data packet.
[0102]
Figs. 14A and 14B are explanatory diagrams each illustrating an example of
intermediate node data. Referring to Fig. 14A, intermediate node data 231a is
illustrated as the first example. The intermediate node data 231 a has two data items
20 such as an "AP class" and an "intermediate node." In this case, the intermediate
node data 231a is data defining an intermediate node to be designated for every AP
class of the data packet. On the other hand, referring to Fig. 14B, intermediate node
data 231b is illustrated as the second example. The intermediate node data 231b
has two data items such as a "terminal class" and an "intermediate node." In this
25 case, the intermediate node data 231b is data defining an intermediate node to be
designated for every terminal class of the data packet. The present disclosure is not
limited to these examples. The intermediate node data may be data defining an
intermediate node in association with arbitrary control information as illustrated in
Fig. 3.
30 [0103]
The communication control unit 232, for example, causes the base station
SP310939WO00
32/54
220 to operate as a base station for cellular communication according to standard
specs of LTE, LTE-A, or the like. In addition, in this embodiment, the
communication control unit 232 can insert intermediate node designation information
designating an intermediate node different from the ultimate destination node of the
5 data packet into the destination field of the data packet received by the wireless
reception unit 122. For example, when the data packet from the terminal device
200 is input from the wireless reception unit 122, the communication control unit
232 can specify an intermediate node associated with an AP class or a terminal class
described within the data packet using the above-described intermediate node data
10 stored by the storage unit 230. The communication control unit 232 inserts the
intermediate node designation information designating the specified intermediate
node into the destination field of the data packet. Here, a plurality of patterns of a
process of updating the destination field will be described later in detail in an
example. The communication control unit 232 may designate a different
15 intermediate node for every data packet, for example, in a round-robin scheme or a
random scheme, from a plurality of intermediate node candidates.
[0104]
In addition, the communication control unit 232 may insert control
information to be used for enabling the intermediate node to identify the ultimate
20 destination node of the data packet into the data packet transmitted from the terminal
device 200 instead of the terminal device 200. The control information to be used
for identifying the ultimate destination node, for example, can include at least one of
pieces of the control information described using Fig. 3.
[0105]
25 (2) Example of Destination Field Update Process
Figs. 15A to 15E are explanatory diagrams each illustrating an example of
the destination field update process by the communication control unit 232 in
accordance with this embodiment. In each drawing, content of destination fields
before and after the update by the communication control unit 232 is illustrated.
30 [0106]
In the first example illustrated in Fig. 15A, the communication control unit
SP310939WO00
33/54
232 simply overwrites information regarding the destination node inserted into the
destination field Fl of the data packet over the intermediate node designation
information (for example, an IP address, a host name, or the like of the intermediate
node). In this case, the destination field update process can be most easily
5 implemented.
[0107]
In the second example illustrated in Fig. 15B, the communication control
unit 232 overwrites information regarding the destination node inserted into the
destination field FI of the data packet over the intermediate node designation
10 information (Fib), and adds a flag indicating that the destination field Fl has been
changed to the data packet (Fla). In this case, the intermediate node receiving the
data packet after the update can know whether the destination field Fl has been
changed by referring to the flag. A position of the flag within the data packet may
be a position different from the position illustrated in Fig. 15B.
15 [0108]
In the third example illustrated in Fig. 15C, the destination field Fl is predivided
into a flag sub-field Fla and a node-information sub-field Fib. In this case,
for example, the terminal device 200 transmits a data packet in which the flag of the
sub-field Fla has been set to zero and information regarding the destination node has
20 been inserted into the sub-field Fib. The communication control unit 232 of the
base station 220 can update the flag of the sub-field Fla to 1, and overwrite the subfield
Fib over the intermediate node designation information. In this case, all
communication nodes receiving the data packet can know whether the destination
field Fl has been changed by referring to the flag sub-field Fla.
25 [0109]
In the fourth example illustrated in Fig. 15D, the communication control
unit 232 updates the flag to 1, inserts the intermediate node designation information
into the destination field Fl, and transcribes information described in the destination
field Fl upon receipt of the data packet to a reserved field F9. In this case, the
30 intermediate node receiving the data packet after the update can identify the ultimate
destination node by referring to information regarding the destination node described
SP310939WO00
34/54
in the reserved field F9.
[0110]
The fifth example illustrated in Fig. 15E is an example of the destination
field update process capable of being adopted when a plurality of intermediate nodes
5 are sequentially designated on the occasion of forwarding of one data packet. In
this case, first, the communication control unit 232 of the base station 220 inserts the
intermediate node designation information into the destination node field Fl, and
transcribes information designating the ultimate destination node (destination node 1)
to the reserved field F9. Next, the intermediate node receiving the data packet
10 inserts new intermediate node designation information into the destination field Fl,
and further transcribes original intermediate node designation information described
in the destination field Fl to the reserved field F9. At this time, instead of fiags of
two values indicating the presence and absence of the update, it is desirable to add
information indicating the number of updates to the data packet (increment the
15 number of updates). Thereby, the intermediate node receiving the data packet after
the update can easily know the number of pieces of node information transcribed to
the reserved field F9. In the fifth example, because the reserved field F9 represents
a history of designation of the intermediate node, it is possible to prevent a looped
communication path from being formed by designating one intermediate node a
20 plurality of times.
[0111]
(3) Flow of Data Forwarding Process
Figs. 16A and 16B are flowcharts each illustrating an example of the flow of
the data forwarding process by the base station 220 in accordance with this
25 embodiment.
[0112]
Fig. 16A illustrates an example of a flow including the destination field
update process illustrated in Figs. 15Ato 15C. In the example of Fig. 16A, first, the
wireless reception unit 122 of the base station 220 receives a data packet transmitted
30 from the terminal device 200 (step S222). The wireless reception unit 122 outputs
the received data packet to the communication control unit 232. Next, the
SP310939WO00
35/54
communication control unit 232 determines whether the received data packet is a
packet for MTC communication (step S224). Here, if the data packet is the packet
for the MTC communication, then the process of steps S226 to S232 is performed.
[0113]
5 When a device of a transmission source is an MTC terminal, the
communication control unit 232 specifies an intermediate node to be designated in
the destination field of the data packet using intermediate node data (step S226).
Next, the communication control unit 232 inserts the intermediate node designation
information designating the specified intermediate node into the destination field of
10 the data packet (step S230). Next, the communication control unit 232 sets a flag
(for example, Flag =1) indicating that the destination field has been changed in the
data packet (step S232).
[0114]
The data packet is forwarded from the transmission unit 126 to the core
15 network 10 (step S234).
[0115]
Fig. 16B illustrates an example of a flow including the destination field
update process illustrated in Figs. 15D and 15E. In the example of Fig. 16B, first,
the wireless reception unit 122 of the base station 220 receives a data packet
20 transmitted from the terminal device 200 (step S222). The wireless reception unit
122 outputs the received data packet to the communication control unit 232. Next,
the communication control unit 232 determines whether the received data packet is a
packet for MTC communication (step S224). Here, if the data packet is the packet
for the MTC communication, then the process of steps S226 to S233 is performed.
25 [0116]
When the device of the transmission source is the MTC terminal, the
communication control unit 232 specifies an intermediate node to be designated in
the destination field of the data packet using the intermediate node data (step S226).
Next, the communication control unit 232 transcribes information regarding the
30 destination node described in the destination field upon receipt of the data packet to
another field such as the reserved field (step S228). Next, the communication
SP310939WO00
36/54
control unit 232 inserts the intermediate node designation information designating
the specified intermediate node into the destination field of the data paclcet (step
S230). Next, the communication control unit 232 updates the flag (step S233).
[0117]
5 The data packet is forwarded from the transmission unit 126 to the core
network 10 (step S234).
[0118]
[2-4. Intermediate Node]
(1) Configuration Example of Device
10 Fig. 17 is a block diagram illustrating an example of a configuration of the
communication device 240 that operates as the intermediate node. Referring to Fig.
17, the communication device 240 includes a reception unit 142, a transmission unit
144, a storage unit 250, a communication control unit 252, and an information
management unit 254.
15 [0119]
The storage unit 250 stores programs and data for processing by the
communication control unit 252 and the information management unit 254 using a
storage medium. In addition, in this embodiment, the storage unit 250 may store
destination node data in which control information within the data packet is
20 associated with the destination node of the data packet as will be described later. In
addition, like the storage unit 150 of the communication device 140 in accordance
with the first embodiment, the storage unit 250 may store forwarding destination data
in which the control information within the data packet is associated with the
forwarding destination node of the data packet.
25 [0120]
The communication control unit 252 identifies an ultimate destination node
of the data packet from information included in a field different fi-om the destination
field when the reception unit 142 receives the data packet in which its own device is
designated in the destination field. More specifically, the communication control
30 unit 252, for example, can identify the ultimate destination node for every data
packet using destination node data in which the control information within the data
SP310939WO00
37/54
packet is associated with the destination node of the data packet.
[0121]
Fig. 18 is an explanatory diagram illustrating an example of destination
node data capable of being stored by the storage unit 250. Referring to Fig. 18, as
5 an example, destination node data 251 has four data items such as an "AP class," a
"terminal class," a "provider," and a "destination node." Among these, a
combination of the "AP class," the "terminal class," and the "provider" becomes an
identification key for identifying one destination node. For example, a data packet
in which the AP class is "CI," the terminal class is "T3," and the provider is "JOl"
10 corresponds to a destination node Dl. The data packet in which the AP class is
"CI," the terminal class is "T3," and the provider is "J02" corresponds to a
destination node D2 (description of the remaining records is omitted). Control
information available as the identification key for identifying the destination node is
not limited to this example. For example, an arbitrary item among the control
15 information illustrated in Fig. 3 (or other control information) may be used as the
identification key for identifying the destination node. In this embodiment, the
above-described destination node data can be managed in the information
management server 270 illustrated in Fig. 10 and shared between intermediate nodes.
[0122]
20 The communication control unit 252 can identify the destination node
corresponding to the control information within the data packet as the ultimate
destination node using the above-described destination node data. When a device
(for example, the above-described base station 220) designating the intermediate
node transcribes information regarding the destination node to the reserved field, the
25 communication control unit 252 can identify the ultimate destination node without
using the destination node data. In this case, the storage unit 250 may not store the
destination node data illustrated in Fig. 18.
[0123]
The communication control unit 252 inserts destination node designation
30 information designating the destination node identified as described above into the
destination field of the data packet. That is, the communication control unit 252
SP310939WO00
38/54
corrects information of the temporarily designated destination field to information of
the destination node at which the data paclcet should ultimately arrive. The
communication control unit 252 causes the transmission unit 144 to transmit a data
packet in which the ultimate destination node designation information is included in
5 the destination field.
[0124]
The communication control unit 252 may select a forwarding destination
node (the next hop) of the data packet from a plurality of forwarding destination
node candidates so that traflfic is distributed as in the forwarding node in accordance
10 with the first embodiment. In addition, by inserting intermediate node designation
information designating a separate intermediate node instead of the ultimate
destination node into the destination field, the communication control unit 252 may
further forward the data packet to the separate intermediate node.
[0125]
15 The information management unit 254 acquires update data for updating the
destination node data stored by the storage unit 250 from the information
management server 270, and updates the destination node data using the acquired
update data. The information management unit 254 may request the information
management server 270 to periodically distribute the update data at a constant
20 frequency. Alternatively, when the update data has been received from the
information management server 270, the information management unit 254 may
passively update the destination node data.
[0126]
(2) Flow of Data Forwarding Process
25 Figs. 19A and 19B are flowcharts each illustrating an example of a flow of a
data forwarding process by the communication device 240 in accordance with this
embodiment.
[0127]
Fig. 19A illustrates an example of a flow including a destination node
30 identification process using destination node data. In the example of Fig. 19A, first,
the reception unit 142 of the communication device 240 receives a data packet
SP310939WO00
39/54
transmitted from the terminal device 200 (step S242). The reception unit 142
outputs the received data packet to the communication control unit 252. Next, the
communication control unit 252 determines whether the received data packet is a
packet for MTC communication (step S244). Here, if the data packet is the packet
5 for the MTC communication, the process proceeds to step S246. On the other hand,
if the data packet is not the packet for the MTC communication, the process proceeds
to step S254.
[0128]
In step S246, the communication control unit 252 acquires control
10 information included in the header area of the data packet (step S246). Next, the
communication control unit 252, for example, identifies a forwarding destination
node corresponding to a combination of an AP class, a terminal class, and a provider
included in the acquired control information using destination node data (step S248).
The communication control unit 252 inserts destination node designation information
15 designating the identified destination node into the destination field of the data
packet (step S250). At this time, the communication control unit 252 updates a
value of the flag within the data packet if necessary.
[0129]
The transmission unit 144 forwards the data packet to the next hop (for
20 example, a forwarding destination node or a predetermined communication node
selected so that traffic is distributed) (step S254).
[0130]
Fig. 19B illustrates an example of a flow of a data forwarding process not
using destination node data. In the example of Fig. 19B, first, the reception unit
25 142 of the communication device 240 receives a data packet transmitted from the
terminal device 200 (step S242). The reception unit 142 outputs the received data
packet to the communication control unit 252. Next, the communication control
unit 252 determines whether the received data packet is a packet for MTC
communication (step S244). Here, if the data packet is the packet for the MTC
30 communication, the process proceeds to step S247. On the other hand, if the data
packet is not the packet for MTC communication, the process proceeds to step S254.
SP310939WO00
40/54
[0131]
In step S247, the communication control unit 252 determines whether the
destination field has been changed by referring to a flag within the data packet (step
S247). Here, when the destination field has been changed, the process proceeds to
5 step S249. On the other hand, when the destination field has not been changed, the
process proceeds to step S254.
[0132]
In step S249, the communication control unit 252 identifies a destination
node from information transcribed to the reserved field within the data packet (step
10 S249). The communication control unit 252 inserts destination node designation
information designating the identified destination node into the destination field of
the data packet (step S252). At this time, the communication control unit 252
updates a value of the flag within the data packet if necessary.
[0133]
15 The transmission unit 144 forwards the data packet to the next hop (for
example, a forwarding destination node or a predetermined communication node
selected so that traffic is distributed) (step S254).
[0134]
[2-5. Example of Communication Path]
20 Fig. 20 is an explanatory diagram illustrating the example of the
communication path capable of being implemented in accordance with this
embodiment. Referring to Fig. 20, as an example, three communication paths Rl,
R2, and R3 simplified between the terminal device 200, which is a transmission
source of MTC communication, and the AP server 190, which is a destination, are
25 illustrated. Control signaling, which is collaterally performed, such as an
acknowledgement (ACK) and a negative acknowledgement (NACK) is not
illustrated in the drawing. The communication path Rl is a shortest path (having an
optimum routing metric) between the terminal device 200 and the AP server 190.
On the other hand, the communication paths R2 and R3 are redundant paths that
30 bypass some links included in the communication path Rl.
[0135]
SP310939WO00
41/54
For example, when the terminal device 200 or the base station 220 has
designated an intermediate node Ml in the destination field of the data packet, the
data packet can reach the AP server 190 via the communication path R2. In
addition, for example, when the terminal device 200 or the base station 220 has
5 designated an intermediate node M2 and the intermediate node M2 has further
designated an intermediate node M3, the data packet can reach the AP server 190 via
the communication path R3. By causing the data packet of the MTC
communication to bypass the shortest path as described above, the traffic is
distributed and the concentration of traffic on a specific communication path is
10 prevented in advance.
[0136]
[2-6. Information Management Server]
(1) Configuration Example of Device
Fig. 21 is a block diagram illustrating an example of a configuration of the
15 information management server 270 in accordance with this embodiment.
Referring to Fig. 21, the informafion management server 270 includes a reception
unit 272, a transmission unit 274, a storage unit 280, and an information management
unit 282.
[0137]
20 The reception unit 272 and the transmission unit 274 are communication
interfaces for enabling the information management server 270 to communicate with
other communication devices.
[0138]
The storage unit 280 stores a master of the destination node data having
25 substantially the same data items as the destination node data illustrated in Fig. 18
using a storage medium. In addition, the storage unit 280 may store a master of
intermediate node data having substantially the same data items as the intermediate
node data illustrated in Figs. 14A and 14B. Further, the storage unit 280 may store
a master of forwarding destination data described in the first embodiment.
30 [0139]
The information management unit 282 provides a master management
SP310939WO00
42/54
function for information stored by the storage unit 280. For example, the
information management unit 282 provides an interface for accepting registration of
new information regarding an AP when the AP server 190 has been newly introduced
into the communication system 2. The interface, for example, may be a graphic
5 user interface (GUI) that accepts an information input from a user on a screen of a
device. Alternatively, the interface, for example, may be an application program
interface (API) that receives registration information from the AP server 190. In
addition, the interface provided by the information management unit 282 may accept
a change and deletion of registered information. When an update of a master
10 (addition, change, or deletion of information) occurs, the information management
unit 282 distributes update data based on a difference in the master to communication
nodes included in the communication system 2.
[0140]
(2) Example of Update Data
15 Fig. 22 is an explanatory diagram illustrating the example of the update data.
For example, it is assumed that a provider JOl has introduced new AP servers Dl, D3,
and D5. In this case a user (engineer) of the provider JO I registers information
regarding each of the AP servers Dl, D3, and D5 in the information management
server 270 via a user interface provided by the information management unit 282.
20 Here, the registered information, for example, can include an AP class, a terminal
class, a communication schedule for MTC communication, and the like
corresponding to each AP server. As a result, the information management unit 282
updates a master of destination node data stored by the storage unit 280, and
generates update data 283 as illustrated in Fig. 22.
25 [0141]
Referring to Fig. 22, the update data 283 is data describing information
regarding a corresponding AP class, terminal class, and communication schedule for
every application server, which can serve as a candidate for the destination node,
using a provider ID as a key. An "update division" having a value of "addition,"
30 "change," "deletion," or the like is assigned to each record of the update data 283.
An intermediate node receiving the above-described update data 283 from the
SP310939WO00
43/54
infonnation management server 270 causes separately stored destination node data to
be synchronized with a latest master using the update data 283.
[0142]
(3) Flow of Update Data Distribution Process
5 Figs. 23A and 23B are flowcharts each illustrating an example of the flow of
the update data distribution process by the information management server 270 in
accordance with this embodiment.
[0143]
Fig. 23A illustrates an example in which update data is distributed to an
10 intermediate node every time a master is updated. In the example of Fig. 23 A, first,
the information management unit 282 of the information management server 270
acquires registration information for the AP server 190 via a GUI (or from the AP
server 190) (step S272). Next, the information management unit 282 updates a
master of destination node data stored by the storage unit 280 using the acquired
15 registration information (step S274). Next, the information management unit 282
generates update data as illustrated in Fig. 22 based on a difference in the master
generated by the update (step S276). The transmission unit 274 distributes the
update data generated by the information management unit 282 to each intermediate
node (step S278). The update data may be broadcast to each intermediate node, and
20 may be separately unicast or multicast.
[0144]
Fig. 23B illustrates an example in which update data is distributed to an
intermediate node according to a request from the intermediate node. In the
example of Fig. 23B, when an update data distribution request is received by the
25 reception unit 272 of the information management server 270 from the intermediate
node, the process proceeds to step S284 (step S282). In step S284, the information
management unit 282 determines whether a difference has occurred in a master of
destination node data after previous distribution of update data (step S284). Here,
when the difference has occurred in the master of the destination node data, the
30 information management unit 282 generates update data based on the difference in
the master (step S286). The transmission unit 274 distributes the update data
SP310939WO00
44/54
generated by the information management unit 282 to an intermediate node of a
request source (step S278). On the other hand, when the difference has not
occurred in the master of the destination node data, the information management unit
282 notifies the intermediate node of the request source that there is no difference
5 (step S289).
[0145]
The present disclosure is not limited to the examples of Figs. 23 A and 23B,
and the information management server 270, for example, may determine the
presence/absence of the difference in the master periodically at a constant frequency,
10 and actively distribute update data to each intermediate node when the difference has
occurred.
[0146]
(4) Flow of Data Update Process
Fig. 24 is a flowchart illustrating an example of the flow of the destination
15 node data update process by the intermediate node in accordance with this
embodiment.
[0147]
Referring to Fig. 24, first, the reception unit 142 of the communication
device 240 receives update data of destination node data distributed from the
20 information management server 270 (step S291). Next, the information
management unit 254 determines whether there is a new AP class within the update
data (step S292). Here, when there is a new AP class within the update data, the
new AP class is added to the destination node data 251 illustrated in Fig. 18 (step
S293). In addition, the information management unit 254 determines whether there
25 is a new terminal class within the update data (step S294). Here, when there is a
new terminal class within the update data, the new terminal class is added to the
destination node data 251 (step S295). Further, the information management unit
254 determines whether the provider ID within the update data is a provider ID of a
new provider (step S296). Here, when the provider ID within the update data is a
30 provider ID of a new provider, the provider ID of the new provider is added to the
destination node data 251 (step S297). The information management unit 254 adds
SP310939WO00
45/54
(information such as an IP address or a host name of) a destination node
corresponding to a combination of an AP class, a terminal class, and a provider ID
within update data to the destination node data 251, or updates an existing
destination node (step S298).
5 [0148]
[2-7. Management of DRX]
Communication schedule information included in update data 283
illustrated in Fig. 22 can be further distributed from the intermediate node to each
corresponding terminal device 200. Alternatively, the information management
10 server 270 may distribute the communication schedule information separate from the
update data 283 to each terminal device 200. Each terminal device 200 receiving
the communication schedule information controls a sleep time of its own device
according to the communication schedule information, and implements an
intermittent operation (DRX: discontinuous reception).
15 [0149]
The control of the intermittent operation of the terminal device 200 may be
performed according to a simple parameter such as once daily ("every day") or once
weekly ("every week") like the communication schedule information illustrated in
Fig. 22. For example, when the parameter of once daily ("every day") has been
20 designated, the wireless reception unit 122 and the wireless transmission unit 124 of
the terminal device 200 wake up in an arbitrary time band only once daily, and
transmit the above-described data packet to the AP server 190 by generating AP data
in the time band. The communication schedule information may include
information regarding a time band of the wake-up (for example, start and end times,
25 a time length, or the like) in addition to a cycle of the intermittent operation.
[0150]
In addition, in each terminal device 200, according to the base station 220 or
another communication node, a cycle of a shorter auxiliary intermittent operation in
the time band of the above-described wake-up may be determined. In this case, the
30 wireless reception unit 122 and the wireless transmission unit 124 of the terminal
device 200 can sleep, for example, except for the timing at which a communication
SP310939WO00
46/54
resource for its own device lias been scheduled, even in the designated walce-up time
band. Thereby, power consumption of the terminal device 200 can be further
reduced.
[0151]
5 [2-8. Summary of Second Embodiment]
The second embodiment has been described above using Figs. 10 to 24. In
accordance with this embodiment, intermediate node designation information
designating an intermediate node different from a destination node of a data packet
on a path to the destination node is inserted into the destination field of a data packet
10 transmitted from an MTC terminal. Thereby, traffic of MTC communication is not
concentrated on a specific communication path, and bypasses to a path via the
designated intermediate node. As a result, traffic is distributed and congestion of
traffic in MTC communication is avoided or mitigated.
[0152]
15 In addition, in accordance with this embodiment, a device that inserts the
intermediate node designation information into the destination field may be a
communication node (for example, a base station or the like) that receives a data
packet from the MTC terminal. When the above-described communication node
inserts the intermediate node designation information into the data packet, it is
20 possible to introduce a technique of congestion avoidance in accordance with the
above-described embodiment without giving impact such as modification of a
processing logic to the MTC terminal.
[0153]
In addition, in accordance with this embodiment, the designated
25 intermediate node identifies an ultimate destination node of a data packet from
control information regarding the MTC terminal inserted within the data packet or
information transcribed to the reserved field. Accordingly, even when the
destination field of the data packet has been changed, the data packet can be
appropriately delivered to the ultimate destination node (for example, a
30 corresponding AP server) via the intermediate node.
[0154]
SP310939WO00
47/54
In this embodiment, because it is not necessary to transcribe information
regarding a destination node to the reserved field when the destination node is
identified using the control information regarding the MTC terminal, an existing
packet format can be effectively utilized. On the other hand, because each
5 intermediate node does not hold destination node data when the destination node is
identified from information transcribed to the reserved field, it is possible to reduce
processing costs necessary for referring to the destination node data or resources of a
storage medium.
[0155]
10 [2-9. Application Example]
In the second embodiment, an example in which a data packet transmitted
from an MTC terminal is bypassed to a path via an intermediate node has been
mainly described. However, a mechanism for setting the above-described
intermediate node is also applicable to a data packet transmitted to the MTC terminal.
15 For example, the communication device 140 illustrated in Fig. 10 may insert
intermediate node designation information into the destination field of the data
packet transmitted to the terminal device 200 according to a destination field update
process illustrated in Fig. 15D or 15E, and transcribe information such as an address
of the terminal device 200 described in the destination field to the reserved field.
20 [0156]
A series of control processes by each device described in this specification
may be implemented using one of software, hardware, and a combination of software
and hardware. A program constituting the software, for example, is pre-stored in a
storage medium provided inside or outside each device. Each program, for example,
25 is read to a random access memory (RAM) during execution, and executed by a
processor such as a central processing unit (CPU).
[0157]
In addition, an example in which the terminal devices 100 and 200, which
are MTC terminals, access a network according to wireless communication has been
30 mainly described in this specification. However, the effects of the above-described
two embodiments can be equally obtained even when the MTC terminals access the
SP310939WO00
48/54
network according to wired communication.
[0158]
The preferred embodiments of the present invention have been described
above with reference to the accompanying drawings, whilst the present invention is
5 not limited to the above examples, of course. A person skilled in the art may find
various alternations and modifications within the scope of the appended claims, and
it should be understood that they will naturally come under the technical scope of the
present invention.
10 Reference Signs List
[0159]
1, 2 Communication system
10 Core network
20 Network
15 100, 200Terminal device
120, 220Base station
140 Communication device (forwarding node)
240 Communication device (intermediate node)
270 Information management server
20 190 AP server

SP310939WO00
49/54
CLAIMS
Claim 1
A communication device comprising:
a communication control unit that inserts, into a destination field of a data
5 packet, intermediate node designation information designating an intermediate node
different from a destination node of the data packet on a path to the destination node;
and
a transmission unit that transmits the data packet into which the intermediate
node designation information is inserted.
10
Claim 2
The communication device according to claim 1, further comprising:
a reception unit that receives the data packet transmitted from a terminal
device or transmitted to the terminal device,
15 wherein the communication control unit inserts the intermediate node
designation information into the destination field of the data packet when the
terminal device is a machine-type communication (MTC) terminal.
Claim 3
20 The communication device according to claim 2, wherein the
communication control unit specifies an intermediate node to be designated for the
data packet from a plurality of intermediate node candidates using intermediate node
data for specifying the intermediate node to be designated.
25 Claim 4
The communication device according to claim 2, wherein the
communication control unit transcribes information described in the destination field
upon receipt of the data packet to another field.
30 Claim 5
The communication device according to claim 4, wherein the
SP310939WO00
50/54
communication control unit adds a flag indicating that the destination field is
changed to the data packet.
Claim 6
5 The communication device according to claim 1, wherein the
communication control unit inserts control information used for enabling the
intermediate node to identify the destination node of the data packet into the data
packet.
10 Claim 7
The communication device according to claim 1, wherein the
communication device is one of a plurality of intermediate node candidates.
Claim 8
15 The communication device according to claim 1, wherein the
communication device is an MTC terminal that generates the data packet.
Claim 9
A communication control method comprising:
20 inserting, into a destination field of a data packet, intermediate node
designation information designating an intermediate node different from a
destination node of the data packet on a path to the destination node; and
transmitting the data packet into which the intermediate node designation
information is inserted.
25
Claim 10
A communication device comprising:
a reception unit that receives a data packet transmitted from a terminal
device or transmitted to the terminal device, wherein the communication device is
30 designated in a destination field;
a communication control unit that identifies a destination node of the data
SP310939WO00
51/54
packet from information included in a field different from the destination field within
the data packet, and inserts destination node designation information designating the
identified destination node into the destination field; and
a transmission unit that transmits the data packet into which the destination
5 node designation information is inserted.
Claim 11
The communication device according to claim 10, further comprising:
a storage unit that stores destination node data in which control information
10 within the data packet is associated with the destination node of the data packet,
wherein the communication control unit identifies the destination node of
the data packet using the destination node data.
Claim 12
15 The communication device according to claim 11, wherein the control
information includes information specifying a terminal identifier (ID), a class, or a
group of the terminal device, an application (AP) ID or a class of an AP relating to
the data packet, or a provider that provides the AP.
20 Claim 13
The communication device according to claim 11, further comprising:
an information management unit that acquires update data for updating the
destination node data from an information management server and updates the
destination node data using the acquired update data.
25
Claim 14
The communication device according to claim 10, wherein the
communication control unit identifies the destination node of the data packet from
information transcribed from the destination field to a field different from the
30 destination field.
SP310939WO00
52/54
Claim 15
A communication control method for use in a communication device within
a communication network including a plurality of communication nodes, comprising:
receiving a data packet transmitted from a terminal device or transmitted to
5 the terminal device, wherein the communication device is designated in a destination
field;
identifying a destination node of the data packet from information included
in a field different from the destination field within the data packet;
inserting destination node designation information designating the identified
10 destination node into the destination field; and
transmitting the data packet into which the destination node designation
information is inserted.
Claim 16
15 A communication system comprising:
a first communication device including
a communication control unit that inserts, into a destination field of
a data packet, intermediate node designation information designating an intermediate
node different from a destination node of the data packet on a path to the destination
20 node, and
a transmission unit that transmits the data packet into which the
intermediate node designation information is inserted; and
a second communication device including
a reception unit that receives a data packet transmitted from a
25 terminal device or transmitted to the terminal device, wherein the communication
device is designated in a destination field,
a communication control unit that identifies a destination node of
the data packet from information included in a field different from the destination
field within the data packet, and inserts destination node designation information
30 designating the identified destination node into the destination field, and
a transmission unit that transmits the data packet into which the
SP310939WO00
53/54
destination node designation infonnation is inserted,
wherein the second communication device^ is a candidate for the
inteiTnediate node.
5 Claim 17
A communication device comprising:
a storage unit that stores destination node data in which control infonnation
within a data packet transmitted from an MTC terminal or transmitted to the MTC
terminal is associated with a destination node of the data packet;
10 a management unit that manages an update of the destination node data
stored by the storage unit; and
a transmission unit that transmits update" data relating to the destination node
data to an intermediate'node different from the destination node on a path to the
destination node of the data packet.
15
Claim 18
The communication device according to claim 17, wherein the control
information includes infonnation specifying a terminal ID, a class, or a group of an
MTC terminal, an AP ID or a class of an AP relating to the data packet, or a provider
20 that provides the AP.