WO2011135794A1 - Communication method, communication system, communication device, and management node - Google Patents

Communication method, communication system, communication device, and management node Download PDF

Info

Publication number
WO2011135794A1
WO2011135794A1 PCT/JP2011/002229 JP2011002229W WO2011135794A1 WO 2011135794 A1 WO2011135794 A1 WO 2011135794A1 JP 2011002229 W JP2011002229 W JP 2011002229W WO 2011135794 A1 WO2011135794 A1 WO 2011135794A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
time interval
access time
communication
mtc device
Prior art date
Application number
PCT/JP2011/002229
Other languages
French (fr)
Japanese (ja)
Inventor
啓吾 阿相
Original Assignee
パナソニック株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by パナソニック株式会社 filed Critical パナソニック株式会社
Publication of WO2011135794A1 publication Critical patent/WO2011135794A1/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • H04W72/044Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446Resources in time domain, e.g. slots or frames
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor

Definitions

  • the present invention relates to a communication method, a communication system, a communication device, and a management node for transmitting data from a plurality of communication devices to a data collection server via a wireless network and communicating data between the communication devices.
  • MTC Machine Type to Machine Type Communication
  • M2M communication Machine Type to Machine Type Communication
  • MTC devices one or more devices that are located at the end and appropriately collect necessary information operate, and are detected by sensing functions (for example, temperature, seismic intensity, and water volume) that each MTC device has.
  • the measured information is collected in a server (hereinafter referred to as an MTC server) that manages the MTC device, and various services are provided to users (clients) based on the information.
  • the user is provided with a service based on information notified from the MTC device via the MTC server.
  • a wired network such as a telephone line or a DSL (Digital Subscriber Line) line
  • a wireless network such as a cellular phone network
  • a wireless communication system usually used for a mobile phone or the like is optimized for a mobile phone and is not necessarily optimal for an MTC device that provides a service specialized for M2M communication.
  • MTC device that provides a service specialized for M2M communication.
  • the MTC device does not have a voice call function, the paging is always performed. Since it is not necessary to be able to receive, such an operation becomes unnecessary.
  • a method (Time Control) is conceived in which a time interval for the MTC device to access the network is specified in advance, and access is controlled within the time interval.
  • a time interval for the MTC device to access the network is specified in advance, and access is controlled within the time interval.
  • the MTC device receives a notification of a time interval during which access is permitted from the network or the MTC server, and connects to the network at an arbitrary timing within the specified time. Since the access timing is randomly determined by each MTC device, even when the same time interval is notified to a plurality of MTC devices, the access timing is distributed so that access is not concentrated. Yes.
  • the network only specifies a common time interval for a plurality of MTC devices (for example, MTC devices belonging to the same group), and limits the time for the MTC devices to access the network.
  • the management cost on the network side can be reduced.
  • FIG. 19 is a sequence chart for explaining the problem to be solved by the present invention.
  • the MTC devices 1A and 1B belong to the same group and are assigned the same access time interval P1.
  • An object of the present invention is to provide a communication method, a communication system, a communication device, and a management node.
  • the present invention is a communication method for transmitting data from a plurality of communication devices to a data collection server via a wireless network and communicating data between the communication devices, A first access time interval for transmitting each data from the plurality of communication devices to the data collection server from a management node that manages the plurality of communication devices to the plurality of communication devices, and the plurality of communication Assigning a second access time interval for transmitting and receiving each piece of data between devices;
  • the plurality of communication devices transmitting each piece of data to the data collection server in the assigned first access time interval; Transmitting and receiving data between the plurality of communication devices in the allocated second access time interval; and It was set as the structure which has.
  • the present invention is a communication system for transmitting data from a plurality of communication devices to a data collection server via a wireless network and communicating data between the communication devices, A first access time interval for transmitting each data from the plurality of communication devices to the data collection server from a management node that manages the plurality of communication devices to the plurality of communication devices, and the plurality of communication Allocating means for allocating a second access time interval for transmitting and receiving each data between devices; Means for the plurality of communication devices to transmit each data to the data collection server in the assigned first access time interval; Means for transmitting and receiving data between the plurality of communication devices in the allocated second access time interval; It was set as the structure which has.
  • the present invention provides a communication device in a communication system for transmitting data from a plurality of communication devices to a data collection server via a wireless network and communicating data between the communication devices.
  • the present invention provides a communication system in which data is transmitted from a plurality of communication devices to a data collection server via a wireless network and data is communicated between the communication devices.
  • a management node that manages the device, A first access time interval for transmitting each piece of data from the plurality of communication devices to the data collection server and a first number for transmitting / receiving each piece of data between the plurality of communication devices to the plurality of communication devices.
  • the first access time interval for transmitting each data from the plurality of communication devices to the data collection server and the first access time for transmitting / receiving each data between the plurality of communication devices. Since two access time intervals are allocated, when data is transmitted from a plurality of communication devices to the data collection server via the wireless network and data is communicated between the communication devices, congestion and packet loss are reduced. be able to.
  • the block diagram which shows an example of the network structure in the 1st Embodiment of this invention Explanatory drawing which shows the communication sequence in the 1st Embodiment of this invention
  • Explanatory drawing which shows the modification of the communication sequence of FIG. Explanatory drawing which shows the allocation sequence of the time interval of FIG.2 and FIG.3 in detail
  • Explanatory drawing which shows the modification of the allocation sequence of FIG. The block diagram which shows in detail the structure of the data transmission source MTC device in FIG.
  • Explanatory drawing which shows the modification of the communication sequence of FIG. The block diagram which shows the structure of the data request origin MTC device in FIG. 1 in detail
  • the flowchart for demonstrating the request processing of the data transmission origin MTC device in the 2nd Embodiment of this invention The flowchart for demonstrating the data transmission process of the data transmission origin MTC device in the 2nd Embodiment of this invention Explanatory drawing which shows the communication sequence in the 3rd Embodiment of this invention. Timing chart for explaining the processing of the data transmission source MTC device in the third embodiment of the present invention
  • the block diagram which shows in detail the structure of the data request origin MTC device in the 3rd Embodiment of this invention Explanatory drawing which shows the modification of the communication sequence in the 3rd Embodiment of this invention.
  • FIG. 1 is a diagram illustrating an example of a network configuration according to the first embodiment of this invention.
  • MTC device 1A and the MTC device 1B are operating as a plurality of MTC devices.
  • These MTC devices 1A and 1B have a 3GPP interface as a radio access module, and can be connected to a network (for example, 3GPP core network) 4 via a base station (eNB: evolved Node B) 3, for example. .
  • eNB evolved Node B
  • the network 4 includes an MME (Mobility Management Entity) 5, an S-GW (Serving Gateway) 6, and a P-GW (Packet Data Gateway) 7 that manage the MTC devices 1A and 1B and the MTC server 2.
  • the entities 5, 6, and 7 manage the connection state of the MTC devices 1A and 1B, establish and manage connections necessary for the MTC devices 1A and 1B to access the MTC server 2, and transfer data.
  • the MTC server 2 is a server that manages the MTC devices 1A and 1B, and provides services to the user U based on various information notified from the MTC devices 1A and 1B.
  • the MTC device 1A and the MTC device 1B generate a connection with the MTC server 2 via the 3GPP core network 4, and notify the MTC server 2 of collected data and events.
  • the MTC server 2 and the MTC device 1B require the data held by the MTC device 1A.
  • both of the MTC devices (the MTC device 1B and other MTC devices ( (Not shown)) may be requested to transmit data.
  • wireless access module which MTC device 1A, 1B hold
  • wireless systems such as WiMAX (trademark) and WLAN
  • the entities 5, 6, and 7 in the core network 4 shown in FIG. 1 represent functional blocks in the case of using 3GPP LTE / SAE (Long Term Term Evolution / System Architecture) Evolution as a radio access system. However, depending on the radio access system to be used, it is replaced with an appropriate entity name having the same function.
  • eNB 3 is RNC / BSC (Radio Network Controller / Base Station Controller)
  • MME 5 is SGSN (Serving GPRS Support Node)
  • P-GW 7 is GGSN (Gateway GPRS). Support Node).
  • the MTC server 2 may be disposed in the 3GPP core network 4.
  • FIG. 2 is a sequence chart illustrating an example of processing when communication is performed among the MTC device 1A, the MTC server 2, and the MTC device 1B.
  • the MTC device 1A and the MTC device 1B are assigned two access time intervals from the network 4 side. One is an access time interval TP1 indicating a time during which communication with the MTC server 2 is permitted, and the other is an access time interval TP2 indicating a time during which communication between the MTC devices 1A-1B is permitted.
  • the notification method of the access time intervals TP1 and TP2 is not limited to the dynamic notification method to be described later, and the operator or the MTC server 2 and the MTC user U specify the MTC devices 1A and 1B that perform communication between MTC devices,
  • the access time intervals TP1 and TP2 may be assigned in advance. In this case, it may be stored in advance in the subscription data of each MTC device 1A, 1B, or may be notified when each MTC device 1A, 1B is connected to the network 4.
  • the MTC device 1A and the MTC device 1B that have been assigned the access time intervals TP1 and TP2 can recognize that they can communicate with other MTC devices in the access time interval TP2.
  • the MTC device 1A When there is data to be notified to the MTC server 2, the MTC device 1A that has received the notification of these access time intervals TP1 and TP2 has a start time indicated by the access time interval TP1 to the MTC server 2. Then, transmission of data to the MTC server 2 is started at an arbitrary timing within the access time interval TP1 (data transmission interval TP11 ⁇ TP1). Although not shown in (2), the MTC device 1B also similarly has an access time interval TP1 when there is data to be notified to the MTC server 2 when the start time indicated by the access time interval TP1 is reached. Transmission of data to the MTC server 2 is started at an arbitrary timing.
  • the MTC device 1B makes a data request to the MTC device 1A at an arbitrary timing after the start time indicated by the access time interval TP2 between the MTC devices. Send.
  • the MTC device 1A receives a data transmission request from the MTC device 1B, if the received timing is within the access time interval TP2, the MTC device 1A accepts the request and receives necessary data. Is started (data transmission interval TP21 ⁇ TP2).
  • the timing at which the request from the MTC device 1B is received is within the range of the access time interval TP1 to the MTC server 2, the request is rejected and data is not transmitted.
  • the MTC device 1A transmits data in response to a request from the MTC server 2
  • the MTC device 1A starts data transmission when the timing at which the request from the MTC server 2 is received is within the access time interval TP1.
  • data transmission is not performed when it is within the range of the access time interval TP2.
  • the request may be set to be accepted if the request is from the MTC server 2. That is, TP1 and TP2 are effective access time intervals for communication with the server 2, and TP2 is set as an effective access time interval for communication between the MTC devices 1A-1B.
  • an access time interval TP1 that permits communication between the MTC devices 1A, 1B and the MTC server 2 and the MTC device 1A
  • the MTC devices 1A and 1B may not be connected to the network 4 after acquiring the access time intervals TP1 and TP2 until an arbitrary time within the designated access time intervals TP1 and TP2.
  • the MTC device 1A does not need to be connected to the network 4 until data transmission to the MTC server 2 is performed. Further, the MTC device 1B does not need to be connected to the network 4 until a data request is transmitted to the MTC device 1A.
  • the access time interval TP2 assigned to communication with other MTC devices is arranged after the access time interval TP1 assigned to communication with the MTC server 2, but instead, FIG. As shown in FIG. 5, the access time interval TP2 may be arranged before the access time interval TP1.
  • the MTC device 1B since the MTC device 1B can transmit data to the MTC server 2 after acquiring information from the MTC device 1A, the MTC device 1B notifies the MTC server 2 of data considering the information acquired from the MTC device 1A. be able to.
  • the MTC device 1B transmits to the MTC server 2 including the data acquired from the MTC device 1A, the MTC device 1A determines that the data transmitted to the MTC device 1B does not need to be transmitted to the MTC server 2. May be. Thereby, the traffic and load which generate
  • FIG. 4 is an example of a sequence chart showing how access time intervals TP1 and TP2 are dynamically allocated to the MTC device 1A and the MTC device 1B.
  • (1) In assigning time intervals (11) When the MTC device 1B wants to communicate with the MTC device 1A, the MTC device 1B first transmits to the MME 5 (or the MTC server 2) an MTC device communication request indicating that communication with the MTC device 1A is performed. (12) (13) When the MME 5 receives the communication request between the MTC devices, the MME 5 prevents the access to the MTC device 1A by the MTC device 1B from affecting the communication with the MTC server 2 by the MTC device 1A. The access time intervals TP1 and TP2 are both assigned to the MTC device 1B and the MTC device 1A.
  • the MTC device 1A and the MTC device 1B are managed by the same MME 5, but if the MTC devices 1A and 1B are managed by different MMEs, the MTC device 1B to the MTC device Access time intervals TP1 and TP2 are determined by exchanging messages between the MME that has received the inter-communication request and the MME that manages the MTC device 1A. Further, when the MTC server 2 holds the function of the MME 5 in the first embodiment of the present invention, the MTC device 1B transmits an inter-MTC device communication request to the MTC server 2. In this case, the MTC server 2 determines appropriate access time intervals TP1 and TP2 and assigns them to the respective MTC devices 1A and 1B.
  • Access time intervals TP1 and TP2 are determined by exchanging messages.
  • the MTC device A and the MTC device B that have received notification of these access time intervals TP1 and TP2 recognize that communication between devices is possible in the access time interval TP2. It is desirable that the MTC device 1A obtains information (ID or IP address of the MTC device 1B) indicating the communication partner to which access is permitted (communication partner who has requested access) together with the access time intervals TP1 and TP2. As a result, the MTC device 1A can recognize that an access request comes from the MTC device 1B within the access time interval TP2, and at the same time, can reject an access request from an MTC device other than the MTC device 1B. After receiving the notification of the access time intervals TP1 and TP2 based on FIG. 4, each of the MTC devices 1A and 1B transmits and receives data as shown in the processes (2), (3), and (4) described with reference to FIG. Do.
  • the MTC device communication request indicating that the MTC device 1A communicates with the MTC device 1B instead. May be sent.
  • the MTC device 1A transmits a communication request between MTC devices.
  • the access time interval TP2 for inter-device communication can be assigned only when the MTC device 1A that actually transmits data determines that inter-device communication is necessary. It is desirable that the MTC device 1B obtains information (ID and IP address of the MTC device 1A) indicating the communication partner permitted to access, together with the access time intervals TP1 and TP2.
  • the MTC device 1B can recognize that it can access the MTC device 1A within the access time interval TP2, and at the same time, rejects an access request from an MTC device other than the MTC device 1A. can do.
  • each of the MTC devices 1A and 1B After receiving the notification of the access time intervals TP1 and TP2 based on FIG. 5, each of the MTC devices 1A and 1B transmits and receives data as shown in the processes (2), (3), and (4) described with reference to FIG. Do.
  • the MTC device 1B in FIG. 4 and the MTC device 1A in FIG. May include explicit information (for example, a flag) requesting that the access time interval TP2 be allocated before the access time interval TP1.
  • the MME 5 that has received the communication request between MTC devices transmits the communication request between the MTC devices 1B or 1A from other MTC devices in order to generate its own transmission data.
  • the access time interval TP2 may be assigned before the access time interval TP1.
  • the MTC device 1B in FIG. 4 and the MTC device 1A in FIG. 5 do not include the ID of the MTC device that is the communication partner in the communication request between MTC devices, but the MME 5 that has received the communication request between MTC devices is appropriate communication. You may select a partner. In this case, information (MTC device ID and IP address) indicating the MTC device requesting the data is notified to the communication partner selected by the MME 5 together with the access time intervals TP1 and TP2. On the other hand, information on the selected communication partner (ID and IP address of the MTC device) is also notified to the requesting MTC device together with the access time intervals TP1 and TP2.
  • an MTC device holding the information requested by the communication request between MTC devices may be selected.
  • the MTC device that transmits the communication request between MTC devices includes an identifier indicating the type of information desired to be acquired in the message.
  • the function of the MME 5 that processes the communication request between the MTC devices may be held by the MTC server 2 or other entities (P-GW 7, S-GW 6) in the network 4.
  • the MTC device that requests data does not include the ID of the MTC device that is the communication partner in the communication request between MTC devices, but receives the request.
  • the MTC server 2 may select an appropriate communication partner.
  • the access time intervals TP1 and TP2 are notified to the communication partner selected by the MTC server 2, and information related to the selected communication partner is notified to the MTC device that is the request source and the request destination. .
  • FIG. 6 is a block diagram showing an example of the configuration of the data transmission source MTC device 1A that receives a request from the data request source MTC device 1B and transmits data to the MTC device 1B in the first embodiment of the present invention. It is.
  • the MTC device 1A illustrated in FIG. 6 includes an interface 101, a setting information acquisition unit 102, a request processing unit 103, a network connection unit 104, an information holding unit 105, and a connection time determination unit 106.
  • the interface 101 includes lower layer protocol modules directly related to the interface 101 of the MTC device 1A itself. This lower layer protocol module has functions necessary for basic data communication, including mechanisms such as signal modulation, encoding compression, media access control, link layer control, and functions of the entire physical layer and data link layer. Has been implemented.
  • the setting information acquisition unit 102 has a function for acquiring necessary setting information from the MME 5 when connected to the network 4, and acquires TP1 and TP2 assigned by the MME 5 as access time intervals.
  • the access time interval TP1 assigned for communication with the MTC server 2 has already been assigned, only the access time interval TP2 assigned for communication with the other MTC device 1B needs to be notified.
  • an MTC device that does not require assignment of the access time interval TP1 may assign only the access time interval TP2.
  • the counterpart MTC device 1B does not communicate with the MTC server 2 and communicates only with the MTC device 1A itself, only the access time interval TP2 needs to be assigned to the counterpart MTC device 1B.
  • the MTC device 1A itself does not communicate with the MTC server 2 and communicates only with the counterpart MTC device 1B, only the access time interval TP2 needs to be assigned to the MTC device 1A. .
  • the access time intervals TP1 and TP2 are obtained by a method in which the network 4 side assigns both access time intervals TP1 and TP2 in advance when the MTC device 1A and the MTC device 1B are connected to the network, and the network 4 side is the MTC device 1A. There is a method of assigning in response to a request from 1B.
  • the MTC devices 1A and 1B are assigned access time intervals TP1 and TP2 when they first connect to the network 4 or when they first access the MTC server 2.
  • the setting information acquisition unit 102 recognizes that communication with the counterpart MTC device 1B is necessary as shown in FIGS. 5 (11) and 12 (12).
  • a communication request is transmitted to MME 5 to request assignment of access time interval TP2 for communication between MTC devices, and to instruct information holding unit 105 to hold acquired access time intervals TP1 and TP2.
  • the information holding unit 105 has a function of holding information acquired from the MTC server 2 and the MME 5 in addition to the time intervals TP1 and TP2 that can access the network 4, the next connection time determined by the connection time determination unit 106, and the like. Have.
  • the request processing unit 103 has a function of processing an access request received from the MTC server 2 or another MTC device 1B.
  • a data transmission request is received, it is determined whether the transmission source of the request is the MTC server 2 or the MTC device 1B. If the request source is the MTC server 2, if the timing of receiving the request is within the access time interval TP1 assigned to the communication with the MTC server 2, the request is accepted and responded. On the other hand, if the request source is the MTC device 1B, the request is rejected if the request is received within the access time interval TP1. When the timing of receiving the request is within the access time interval TP2 allocated for communication with the other MTC device 1B, the request is accepted and responded.
  • the request processing unit 103 sends the data requested from the counterpart MTC device 1B to the MTC server 2. May not be transmitted at the access time interval TP1. This is because when the counterpart MTC device 1B transmits to the MTC server 2 data generated in consideration of data acquired from the MTC device 1A, or data including data acquired from the MTC device 1A itself, the MTC device 1A. Can avoid unnecessary data or duplicate transmission of the same data, thereby reducing traffic.
  • the MTC device 1A has all the information held by the MTC device 1A itself in the access time interval TP2.
  • the counterpart MTC device 1B does not need to transmit data to the MTC server 2 in the subsequent access time interval TP1 in the data request transmitted to the MTC device 1A in the access time interval TP2.
  • Information for example, a flag may be included.
  • the MTC device 1A When this information is included in the data request, the MTC device 1A does not need to transmit the data transmitted to the counterpart MTC device 1B in the access time interval TP2 to the MTC server 2 in the subsequent access time interval TP1. to decide. Then, it is determined that only data that has not been transmitted to the counterpart MTC device 1B is transmitted to the MTC server 2.
  • the MTC device 1B may include an identifier representing the type of data requested in the data request.
  • connection time determination unit 106 has a function of determining a time (next connection time) at which the MTC device 1A itself connects to the network 4 next time.
  • the access time interval TP1 is assigned, the MTC device 1A can be disconnected from the network 4 after the communication with the MTC server 2 is completed within the access time interval TP1.
  • the access time interval TP2 is assigned, it is necessary to accept an access request from another MTC device 1B, so the start time of the access time interval TP2 becomes the next connection time.
  • the network connection unit 104 executes processing for newly connecting to the network 4 using the interface 101 and connection processing performed when connecting to the network 4 at the next connection time determined by the connection time determination unit 106. It has a function to do. Further, processing for disconnecting from the network 4 is performed according to an instruction from the connection time determination unit 106.
  • FIG. 8 is a block diagram showing an example of the configuration of the data request source MTC device 1B that transmits a data request to the data transmission source MTC device 1A and receives data from the MTC device 1A in the first embodiment of the present invention.
  • FIG. The MTC device 1B illustrated in FIG. 8 includes an interface 101, a setting information acquisition unit 102, a data acquisition unit 107, a network connection unit 104, an information holding unit 105, and a connection time determination unit 106. . Since the interface 101 and the setting information acquisition unit 102 are the same as those in the case of the MTC device 1A, description thereof is omitted.
  • the setting information acquisition unit 102 recognizes that communication with the counterpart MTC device 1A is necessary as shown in FIGS. 4 (11) and 12 (12).
  • An MTC inter-device communication request is transmitted to the MME 5 to request assignment of an access time interval TP2 for MTC device communication, and to instruct the information holding unit 105 to hold the acquired access time intervals TP1 and TP2.
  • the connection time determination unit 106 has a function of determining a time (next connection time) when the MTC device 1B itself connects to the network 4 next time.
  • the access time interval TP1 is assigned, if communication (for example, data transmission) with the MTC server 2 is required, the access time interval TP1 is performed within the access time interval TP1.
  • the MTC device 1B can be disconnected from the network 4 after the communication with the MTC server 2 is completed.
  • the access time interval TP2 for communication between the MTC devices is assigned, it is possible to transmit an access request to the other MTC device 1A, so the next connection within the access time interval TP2 is possible. Determine the time.
  • the data acquisition unit 107 In response to the completion of the connection processing from the network connection unit 104 to the network 4, the data acquisition unit 107 refers to the information holding unit 105, and the counterpart MTC device 1 A that is permitted to access within the access time interval TP 2. An access request message (data transmission request) is transmitted. As shown in FIG. 3, when the access time interval TP2 is assigned before the access time interval TP1, the data acquisition unit 107 considers the data acquired from the counterpart MTC device 1A and sends it to the MTC server 2. Data to be transmitted may be generated.
  • the MTC device 1B is an MTC device having a role of transmitting data to the MTC server 2 instead of the counterpart MTC device 1A
  • the data including the data acquired from the counterpart MTC device 1A is stored in the MTC server 2 Send to.
  • FIG. 9 is a block diagram illustrating an example of the configuration of the MME 5 according to the first embodiment of this invention.
  • the setting information notification unit 502 has a function of assigning access time intervals TP1 and TP2 to the MTC devices 1A and 1B, and when receiving a communication request between MTC devices from the MTC device 1A or MTC device 1B, The access time intervals TP1 and TP2 are determined and notified to the requesting MTC device 1A and the MTC device 1B as the communication counterpart of the MTC device 1A via the interface 501 and held in the information holding unit 503, for example. .
  • the MTC device 1A and the MTC device 1B are connected between the MTC devices separately from the access time interval TP1 used for communication with the MTC server 2.
  • the access time interval TP2 used for communication it is possible to avoid a situation in which communication with another MTC device must be performed simultaneously with communication with the MTC server 2, thereby reducing congestion and packet loss. It becomes possible to make it.
  • FIG. 10 is a sequence chart illustrating an example of processing when the MTC device 1A, the MTC server 2, and the MTC device 1B perform communication in the second embodiment of the present invention.
  • a data transmission request between the MTC devices 1A-1B is made within the access time interval TP1 used for communication with the MTC server 2.
  • the MTC device 1A and the MTC device 1B receive assignment of access time intervals TP1 and TP2 from the MME 5.
  • the allocated access time intervals TP1 and TP2 are the same as those described in the first embodiment of the present invention.
  • the MTC device 1A transmits data to the MTC server 2 at the data transmission interval TP11 within the access time interval TP1.
  • the MTC device 1B sends a data transmission request to the MTC device 1A in the access time interval TP1.
  • the MTC device 1A receives a data transmission request from another MTC device 1B in the access time interval TP1, it returns only a response message, and does not transmit data in the access time interval TP1.
  • the response message notifies the MTC device 1B that the data request has been accepted, and recognizes that the actual data transmission is performed at the access time interval TP2.
  • the MTC device 1A performs data transmission for the data request received in the access time interval TP1 in the data transmission interval TP21 within the access time interval TP2.
  • the timing for starting data transmission in the access time interval TP2 can be determined by the MTC device 1A arbitrarily determining. For example, when it is necessary to send data to an MTC device (not shown) other than the MTC device 1B, the MTC device 1A gives priority to the data transmission and then starts data transmission to the MTC device 1B. can do.
  • FIG. 11 is a flowchart showing an example of processing performed by the request processing unit 103 of the MTC device 1A itself in the access time interval TP1 (step S1). If the request is not received within the access time interval TP1 (NO in step S2), the request processing unit 103 ends without doing anything (step S2 ⁇ S6).
  • the request processing unit 103 determines whether the transmission source of the request is the MTC server 2 or the MTC device 1B. (Step S3). If the request source is the MTC server 2 (NO in step S3), the request is accepted and responded, and data transmission is started (step S7).
  • the request source is the MTC device 1B (YES in step S3)
  • the request is accepted and a response is returned, but no data is transmitted within the access time interval TP1 (step S4).
  • the information holding unit 105 is instructed to hold information related to the data transmission request received from the MTC device 1B (step S5).
  • the information held includes the ID and IP address of the MTC device 1B, the type of requested data, and the like. Further, when receiving a request from a plurality of MTC devices, the request processing unit 105 instructs the information holding unit 105 to hold information regarding each request.
  • the request processing unit 103 may include information related to the time to start data transmission in the access time interval TP2 in the response message transmitted to the requesting MTC device 1B.
  • the requesting MTC device 1B has only to connect to the network 4 immediately before the data transmission from the MTC device 1A is started in the access time interval TP2, so that it connects to the network 4 more than necessary and power consumption increases. Can be prevented.
  • the request processing unit 103 may include a time interval TP2 in which data transmission is possible in the response message transmitted to the requesting MTC device 1B. That is, the MTC device 1B connects to the network 4 within the accessible time TP1 allocated in advance from the network, and transmits a request message to the MTC device 1A. In this case, the MTC device 1B receives the notification of the access time interval TP2 not from the MME 5 but from the MTC device 1A. Further, the MTC device 1B may transmit a request message to the MTC device 1A via the MTC server 2. The MTC server 2 transfers the request message received from the MTC device 1B to the MTC device 1A. However, when the MTC server 2 receives the request message from the MTC device 1B and the MTC device 1A is not connected to the network 4, the MTC server 2 requests the request after the MTC device 1A connects to the network 4. Forward the message.
  • TP2 time interval in which data transmission is possible in the response message transmitted to the requesting MTC device 1
  • the access time interval notified from the MTC device 1A may be the TP2 itself or an arbitrary time interval within the range of the TP2.
  • the MTC device 1A can be divided into a time interval used for communication with the MTC device 1B and a time interval used for communication with the MTC server 2 and other MTC devices.
  • the MTC device 1B receives the notification of the access time interval TP2 from the MTC device 1A, the MTC device 1B connects to the network 4 at the start time of TP2, and waits for data transmission from the MTC device 1A.
  • a request message for requesting data transmission to the MTC device 1A is transmitted again at an arbitrary timing in TP2. Which of these is executed can be instructed by the MTC device 1A.
  • the MTC device 1A when the MTC device 1A wants to arbitrarily determine the time to communicate with the MTC device 1B in the access time interval TP2, it instructs the MTC device 1B to wait for data from the MTC device 1A. Further, when it is not necessary for the MTC device 1A to specify the time for communication with the MTC device 1B in the access time interval TP2, the MTC device 1A transmits a request to the MTC device 1B at an arbitrary timing in the TP2. Instruct.
  • connection time determination unit 106 in FIG. 6 refers to the information holding unit 105 to confirm whether communication with the MTC server 2 or another MTC device 1B is necessary for data transmission or the like. If there is, the MTC device 1A itself has a function of determining the time to connect to the next network (next connection time) and the timing to disconnect. When it is necessary to communicate with the MTC server 2, the allocated access time interval TP1 is confirmed, and an arbitrary timing within the access time interval TP1 is determined as the connection time. At that timing, the network connection unit 104 is instructed to connect to the network 4, and communication with the MTC server 2 is started.
  • the network connection unit 104 is instructed to disconnect from the network 4.
  • communication with other MTC servers other than MTC server 2 is required, after communication with another MTC server is complete
  • FIG. 12 is a flowchart illustrating an example of processing performed by the connection time determination unit 106 of the MTC device 1A that has been assigned the access time intervals TP1 and TP2 in the second embodiment of this invention.
  • the connection time determination unit 106 refers to the information holding unit 105 at the end of the access time interval TP1, and confirms whether a data transmission request from the MTC device has been received within the access time interval TP1 (step S11, S12).
  • step S12 If a data transmission request has not been received (NO in step S12), it is determined that there is no need to connect to the network at the access time interval TP2, and no connection is made to the network at the access time interval TP2 (step S13). If a data transmission request has been received (YES in step S12), an arbitrary timing of the access time interval TP2 is determined as a connection time, and the network connection unit 104 is instructed to connect to the network at that timing (step) S12 ⁇ S15), communication with the MTC device 1B is started (step S16). If a data transmission request has been received from another MTC device other than the MTC device 1B, the connection time is determined for each communication partner, and then the data transmission request is first sent to the network. Instruct to connect.
  • connection time determination unit 106 refers to the information holding unit 105 at the end of the access time interval TP1 and confirms that requests are received from a plurality of MTC devices in the access time interval TP1, the access time interval TP2
  • the order in which data transmission is started can be arbitrarily determined. For example, by confirming the type of requested data and starting data transmission to an MTC device that is requesting high priority data, high priority data can be delivered first. When there is no priority or when the same type of data is requested, data transmission may be started in the order in which the requests are received, or the order may be determined randomly. Also, by starting data transmission first from an MTC device with a large amount of data to be transmitted, even if there is data that takes time to complete transmission, it is possible to control data transmission to be completed within an access time interval. it can.
  • connection time determination unit 106 refers to the information holding unit 105 at the end of the access time interval TP1, and determines that an MTC device that has not received a request in the access time interval TP1 (for example, to transmit data in advance). When there is a transmission partner), it may be determined that data should be transmitted before the MTC device that has received the request. For example, when the time for starting data transmission with the communication partner is already determined in the access time interval TP2, priority is given to transmission to the MTC device, and after the end of the communication, the access time interval TP1 Data transmission to the MTC device that has received the request may be started.
  • the connection time determination unit 106 has a function of determining a time (next connection time) when the MTC device 1B is connected to the network 4 next time.
  • the access time interval TP1 is assigned, if communication (for example, data transmission) with the MTC server 2 is required, the access time interval TP1 is performed within the access time interval TP1.
  • the connection time determination unit 106 also refers to the information holding unit 105, and when it is confirmed that communication described later with the MTC device 1A is performed in the access time interval TP2, the network time 4 is set at the start time of the access time interval TP2.
  • the network connection unit 104 is instructed to connect to the network.
  • the MTC device 1A receives a notification of the time when the MTC device 1A starts data transmission to the MTC device 1B, the MTC device 1A instructs the connection unit 104 to connect to the network 4 before that time. Further, as described above, the access time interval TP2 in which data transmission with the MTC device 1A can be performed may be directly notified from the MTC device 1A.
  • the data acquisition unit 107 transmits a data request to the counterpart MTC device 1A at the access time interval TP1. To do.
  • the information holding unit 105 holds information indicating that communication with the counterpart MTC device 1A is performed in the access time interval TP2.
  • the data acquisition unit 107 refers to the information holding unit 107 and is permitted to access within the access time interval TP 2.
  • An access request message (data transmission request) is transmitted to 1A.
  • the MTC device 1A when the MTC device 1B requests data transmission to the MTC device 1A, it is within the access time interval TP1 used for communication with the MTC server 2. Therefore, the MTC device 1A can determine whether or not it is necessary to connect to the network 4 in the access time interval TP2 used for communication between the MTC devices 1A-1B. As a result, when there is no request from the MTC device 1B, the MTC device 1A does not need to be connected to the network 4 at the access time interval TP2, so that power consumption can be reduced.
  • FIG. 13 is a sequence chart showing an example of processing when the MTC device 1A, the MTC server 2, and the MTC device 1B perform communication in the third embodiment of the present invention, and FIG. It is a timing chart for explaining processing.
  • the MTC device 1A is idle in order to suppress power consumption in the remaining interval of the access time interval TP1. Transition to mode.
  • the MTC device that is the transmission source can be specified at the paging reception timing, so even if paging is received, connection to the network 4 (transition to the connected mode) is possible. do not have to.
  • the MTC device 1A and the MTC device 1B receive assignment of access time intervals from the MME 5 (or eNB 3).
  • the allocated time intervals are the paging reception time interval TP1-1 based on the request from the MTC server 2, the paging reception time interval TP1-2 based on the request from the MTC device 2, and the first embodiment of the present invention.
  • There are three access time intervals TP2 described. Note that the paging reception time intervals TP1-1 and TP1-2 are included in the access time interval TP1 described in the first embodiment of the present invention (TP1 TP1-1 + TP1-2).
  • the paging reception time interval TP1-2 is associated with information related to the MTC device 1B, and indicates a time interval for receiving a request from the MTC device 1B.
  • the allocation method is the same as that described with reference to FIG. 4 and FIG. 5 in the first embodiment of the present invention, and thus the description thereof is omitted.
  • the MTC device 1B transmits a request message to the MTC device 1A and acquires the paging reception time interval TP1-2 using the response message. Good. In this case, only TP1 or TP1 and TP1-1 are notified to the MTC device 1B, and the MTC device 1B transmits a request message at an arbitrary time in the TP1 or TP1-1. Then, the request message is transmitted again within the paging reception time interval TP1-2 notified by the response message. That is, the MTC device 1A that has received the request message from the MTC device 1B designates the paging reception time interval for the MTC device 1B within the range of the access time interval TP1, and performs manual notification.
  • FIG. 15 is a block diagram showing an example of the configuration of the MTC device 1A according to the third embodiment of the present invention.
  • the MTC device 1A illustrated in FIG. 15 includes an interface 101, a setting information acquisition unit 102, a paging reception unit 108, a network connection unit 104, an information holding unit 105, and a connection time determination unit 106.
  • the interface 101 includes lower layer protocol modules that are directly related to the interface of the MTC device 1A. This lower layer protocol module has functions necessary for basic data communication, including mechanisms such as signal modulation, encoding compression, media access control, link layer control, and functions of the entire physical layer and data link layer. Has been implemented.
  • the setting information acquisition unit 102 has a function for acquiring necessary setting information from the MME 5 when connected to the network 4.
  • As an acquisition method there are a method in which the network 4 side allocates these time intervals in advance and a method in which the network 4 side allocates a request from the MTC devices 1A and 1B. In the former case, the MTC devices 1A and 1B are assigned these time intervals when connected to the network 4 and when accessing the MTC server 2.
  • the setting information acquisition unit 102 performs (1) time interval allocation shown in FIG. (11)
  • a communication request between MTC devices is transmitted to the MME 5, and an allocation of an access time interval for communication between MTC devices is requested.
  • the notified paging reception time interval is associated with information on the corresponding MTC device (ID or IP address of the MTC device), and the information holding unit 105 holds information on the MTC device corresponding to the paging time interval. Is done.
  • the information holding unit 105 has a function of holding information acquired from the MTC server 2 and the MME 5, the next connection time determined by the connection time determination unit 106, and the like. (13)
  • the MTC device 1B instructs the information holding unit 105 to hold the access time intervals TP1 and TP2 acquired from the MME 5.
  • procedures (2) to (6) in FIG. 16 are the same as procedures (2) to (6) shown in FIG.
  • the information holding unit 105 holds information indicating that the data request is transmitted from the counterpart MTC device 1B.
  • connection time determination unit 106 refers to the information holding unit 105 and confirms whether communication with the MTC server 2 or another MTC device 1B is necessary for data transmission or the like. Has a function of determining the time when the MTC device 1A itself connects to the network 4 next time (next connection time) and the timing of disconnection.
  • the allocated access time interval TP1 is confirmed, and an arbitrary timing within the access time interval TP1 is determined as the connection time.
  • the network connection unit 104 is instructed to connect to the network 4, and communication with the MTC server 2 is started. After the communication with the MTC server 2 is completed, if it is still within the time interval of the access time interval TP1, the network connection unit 104 is instructed to shift to the idle mode.
  • connection time determination unit 106 When the connection time determination unit 106 refers to the information holding unit 105 and confirms that paging is received at the paging reception time interval TP1-2, the connection time determination unit 106 connects to the network 4 at the access time interval TP2, and It is determined that it is necessary to transmit data to the destination MTC device 1B.
  • the connection time determination unit 106 refers to the information holding unit 105 at the end of the access time interval TP1, and confirms whether or not paging has been received within the paging reception time interval TP1-2 (step S12a). If not (NO in step S12a), it is determined that it is not necessary to connect to the network 4 in the access time interval TP2, and the network is not connected in the access time interval TP2 (steps S13 and S14). If there is (YES in step S12a), an arbitrary timing of the access time interval TP2 is determined as a connection time (step S15), the network connection unit 104 is instructed to connect to the network 4 at that timing, and paging reception is performed. Communication with the counterpart MTC device 1B corresponding to the time interval TP1-2 is started (step S16).
  • the network connection unit 104 executes processing for newly connecting to the network 4 using the interface 101 and connection processing performed when connecting to the network 4 at the next connection time determined by the connection time determination unit 106. It has a function to do. Further, according to an instruction from the connection time determination unit 106, processing for disconnecting from the network 4 and processing for transitioning to the idle mode are performed.
  • the connection time determination unit 106 has a function of determining a time (next connection time) when the MTC device 1B itself connects to the network 4 next time.
  • the access time interval TP1 is assigned, if communication (for example, data transmission) with the MTC server 2 is required, the access time interval TP1 is performed within the access time interval TP1.
  • connection time determination unit 106 refers to the information holding unit 105, and when it is confirmed that communication described later with the counterpart MTC device 1A is performed in the access time interval TP2, the start time of the access time interval TP2 The network connection unit 106 is instructed to connect to the network 4.
  • the data acquisition unit 108 If the data acquisition unit 108 refers to the information holding unit 105 and determines that communication with the counterpart MTC device 1A is necessary, the data acquisition unit 108 transmits data addressed to the counterpart MTC device 1A at the paging reception time interval TP1-2. Send a request. Further, although the response to the transmitted data request is not received, information indicating that communication with the counterpart MTC device 1A is performed in the access time interval TP2 is held in the information holding unit 105.
  • the MTC device 1B according to the third embodiment of the present invention does not recognize the paging reception time intervals TP1-1 and TP1-2 like the MTC device 1B according to the second embodiment of the present invention.
  • the request transmitted by the MTC device 1B itself may reach the MTC device 1A within the paging reception time interval TP1-1 from the MTC server 2.
  • the MTC device 1A misrecognizes paging by a request from the MTC device B as paging by a request from the MTC server 2.
  • the procedures (11), (12), and (13) in (1) time interval allocation shown in FIG. 18 are the same as the procedures (11), (12), and (13) described in FIG. (11)
  • the MTC device 1B When the MTC device 1B wants to communicate with the MTC device A, the MTC device 1B first transmits to the MME 5 (or the MTC server 2) an inter-MTC device communication request indicating communication with the MTC device 1A. (12) (13)
  • the MME 5 receives the communication request between the MTC devices, the MME 5 prevents the access to the MTC device 1A by the MTC device 1B from affecting the communication with the MTC server 2 by the MTC device 1A.
  • the access time intervals TP1 and TP2 are both assigned to the MTC device 1B and the MTC device 1A.
  • procedures (2) to (6) in FIG. 18 are the same as procedures (2) to (6) shown in FIG.
  • this problem can be solved by transferring the request message for data transmission between the MTC devices 1A and 1B via the MTC server 2.
  • the MTC device 1B transmits a request message for the MTC device 1A to the MTC server 2 within the access time interval TP1.
  • the request message is not immediately transferred to the MTC device 1A, but the range of the paging reception time interval TP1-2 from the MTC device.
  • the data is transferred to the MTC device 1A.
  • the MTC device 1A can reliably receive the paging by the request message from the MTC device 1B within the range of the paging reception time interval TP1-2.
  • the transmission source can be specified based on the timing of receiving the paging. Therefore, the MTC device 1A can make a transition to the idle mode immediately after the communication with the MTC server 2 is completed, and the power consumption can be suppressed.
  • Each functional block used in the description of the above embodiment is typically realized as an LSI that is an integrated circuit. These may be individually made into one chip, or may be made into one chip so as to include a part or all of them. Although referred to as LSI here, it may be referred to as IC, system LSI, super LSI, or ultra LSI depending on the degree of integration. Further, the method of circuit integration is not limited to LSI's, and implementation using dedicated circuitry or general purpose processors is also possible. An FPGA (Field Programmable Gate Array) that can be programmed after manufacturing the LSI, or a reconfigurable processor that can reconfigure the connection and setting of circuit cells inside the LSI may be used. Further, if integrated circuit technology comes out to replace LSI's as a result of the advancement of semiconductor technology or a derivative other technology, it is naturally also possible to carry out function block integration using this technology. For example, biotechnology can be applied.
  • LSI Field Programmable Gate Array
  • the present invention has an effect of reducing congestion and packet loss when data is transmitted from a plurality of communication devices to a data collection server via a wireless network and data is communicated between the communication devices. It can be used for 3GPP (3rd Generation Partnership Project) MTC (Machine Type Communication).

Abstract

When transmitting data from a plurality of communication devices to a data collection server via a wireless network and communicating data between the respective communication devices via the wireless network, congestion and a packet loss are reduced. By the configuration, when transmitting data from MTC devices (1A, 1B) to an MTC server (2) and communicating data between the MTC devices (1A) and (1B), an MME (5) which manages the MTC devices (1A, 1B) and the MTC server (2) allocates a first access time interval (TP1) for transmitting each data from the MTC devices (1A, 1B) to the MTC server (2) and a second access time interval (TP2) for transmitting and receiving each data between the MTC devices (1A) and (1B).

Description

通信方法、通信システム及び通信デバイス並びに管理ノードCommunication method, communication system, communication device, and management node
 本発明は、無線網を介して複数の通信デバイスからデータ収集サーバに対してデータを送信するとともに各通信デバイスの間でデータを通信する通信方法、通信システム及び通信デバイス並びに管理ノードに関する。 The present invention relates to a communication method, a communication system, a communication device, and a management node for transmitting data from a plurality of communication devices to a data collection server via a wireless network and communicating data between the communication devices.
 携帯電話のような豊富なユーザインタフェースを備えた端末を用いたユーザを主体とするコミュニケーション(Human to Human(H2H)、Human to Machine(H2M))とは異なり、ユーザによる直接的な操作を必要とせず、単独で動作可能なデバイス(以下、MTC(Machine Type Communication)デバイス)を用いたコミュニケーションの形態として、マシン間コミュニケーション(Machine to Machine CommunicationやMachine Type Communicationと呼ばれる。以下、M2M通信)が存在する。M2M通信では、末端に位置し必要な情報を適宜収集する1つ又は複数のデバイス(以下、MTCデバイス)が動作するとともに、各MTCデバイスが備えるセンシング機能(例えば、気温、震度、水量)によって検出・計測された情報が、MTCデバイスを管理しているサーバ(以下、MTCサーバ)に集約され、その情報を元に様々なサービスがユーザ(クライアント)へ提供される。ユーザはMTCサーバを介して、MTCデバイスから通知された情報に基づくサービスの提供を受ける。 Unlike communication (Human to Human (H2H), Human to Machine (H2M)), which uses a terminal equipped with a rich user interface such as a mobile phone, direct operation by the user is required. As a form of communication using a device that can operate independently (hereinafter referred to as MTC (Machine Type Communication) device), there is an inter-machine communication (called Machine Type to Machine Type Communication or Machine Type Type Communication, hereinafter referred to as M2M communication). . In M2M communication, one or more devices (hereinafter referred to as MTC devices) that are located at the end and appropriately collect necessary information operate, and are detected by sensing functions (for example, temperature, seismic intensity, and water volume) that each MTC device has. The measured information is collected in a server (hereinafter referred to as an MTC server) that manages the MTC device, and various services are provided to users (clients) based on the information. The user is provided with a service based on information notified from the MTC device via the MTC server.
 上記のMTCデバイスとMTCサーバとの間の通信経路を確立する手段として、電話回線やDSL(Digital Subscriber Line)回線などの有線網だけでなく、携帯電話網などの無線網を活用することができる。特に無線を用いた場合は、MTCデバイスの設置場所に関する制限がほぼなくなるため、広範囲にMTCデバイスを設置することが可能となり、非常に有効な通信手段であると言える。 As means for establishing a communication path between the MTC device and the MTC server, not only a wired network such as a telephone line or a DSL (Digital Subscriber Line) line but also a wireless network such as a cellular phone network can be used. . In particular, when wireless is used, restrictions on the installation location of the MTC device are almost eliminated, so that it is possible to install the MTC device in a wide range, and it can be said that this is a very effective communication means.
 しかしながら、通常、携帯電話などで用いられる無線通信システムは携帯電話向けに最適化されたものであり、M2M通信に特化したサービスを提供するMTCデバイスにとって、必ずしも最適なものとは言えない。例えば、携帯電話であれば、自分宛の音声通話の着信を受けるために定期的にネットワーク側からのページングをチェックする必要があるが、音声通話機能を持たないMTCデバイスであれば、常時ページングを受けられる状態である必要はないため、そのような動作は不要となる。 However, a wireless communication system usually used for a mobile phone or the like is optimized for a mobile phone and is not necessarily optimal for an MTC device that provides a service specialized for M2M communication. For example, in the case of a mobile phone, it is necessary to periodically check paging from the network side in order to receive an incoming voice call addressed to itself. However, if the MTC device does not have a voice call function, the paging is always performed. Since it is not necessary to be able to receive, such an operation becomes unnecessary.
 また、MTCデバイスは設置場所が多岐にわたる上に、ユーザとの接触が少ないため、電力が常に供給される状態に置かれる可能性は少ない。そのため、電池やバッテリーなどの限りがある電力を用いる必要があるので、消費電力をできるだけ抑え、動作時間を長くすることが求められている。特に、通信に使用する無線インタフェースによって消費される電力は無視できないものであり、MTCデバイス向けに無線通信システムを最適化することは、無線通信を用いるMTCデバイスにとっては必要不可欠な課題である。現在3GPP(3rd Generation Partnership Project)では、携帯電話網をM2M通信向けに最適化するための議論が行われている(下記の非特許文献1参照、下記の非特許文献2参照)。 In addition, since MTC devices have a wide range of installation locations and few contact with the user, there is little possibility of being placed in a state where power is always supplied. Therefore, since it is necessary to use limited electric power such as a battery or a battery, it is required to suppress power consumption as much as possible and lengthen the operation time. In particular, power consumed by a radio interface used for communication cannot be ignored, and optimizing a radio communication system for an MTC device is an indispensable problem for an MTC device using radio communication. Currently, 3GPP (3rd Generation Partnership Project) discusses optimization of the mobile phone network for M2M communication (see Non-Patent Document 1 below and Non-Patent Document 2 below).
 さらに、設置規模が大きくなればなるほど、動作するMTCデバイスの数も膨大なものとなることが予想される。このため、大量のMTCデバイスが同時にネットワークへ接続し、データの送受信を開始した場合、無線ネットワーク及びコアネットワーク内で輻輳が発生してしまうことが予想される。そのため、できるだけアクセスが集中しないようにする仕組みも必要となる。 Furthermore, it is expected that the larger the installation scale, the greater the number of MTC devices that operate. For this reason, when a large number of MTC devices are simultaneously connected to the network and data transmission / reception is started, it is expected that congestion will occur in the wireless network and the core network. For this reason, a mechanism to minimize access concentration is also necessary.
 このように、消費電力の削減を考えると、MTCデバイスが常時ネットワークへ接続し、サーバとのコネクションを確保しておく状態は現実的ではなく、必要な時に必要な時間だけネットワークへ接続できるようにするのが適切である。そのための方法として、MTCデバイスがネットワークへアクセスする時間間隔をあらかじめ指定し、その時間間隔の中でアクセスするように制御する方法(Time Control)が考えられている。また、同じ時間間隔が複数のMTCデバイスに指定されている場合、複数のMTCデバイスが同時にネットワークへアクセスした場合に発生する輻輳を回避できるようにする必要もある。 In this way, considering the reduction of power consumption, it is not realistic that the MTC device is always connected to the network and the connection with the server is ensured, so that it can be connected to the network only when necessary when necessary. It is appropriate to do. As a method for that purpose, a method (Time Control) is conceived in which a time interval for the MTC device to access the network is specified in advance, and access is controlled within the time interval. In addition, when the same time interval is specified for a plurality of MTC devices, it is also necessary to avoid congestion that occurs when a plurality of MTC devices access the network at the same time.
 現在考えられている方法では、MTCデバイスは、ネットワーク又はMTCサーバからアクセスが許可される時間間隔の通知を受け、指定された時間内の任意のタイミングでネットワークへ接続する。アクセスするタイミングは、各MTCデバイスによってランダムに決められるため、同じ時間間隔が複数のMTCデバイスに通知されている場合であっても、それがアクセスするタイミングを分散させ、アクセスが集中しないようにしている。この方法により、ネットワークは複数のMTCデバイス(例えば、同一グループに属しているMTCデバイス群)に対して共通の時間間隔を指定するだけで、そのMTCデバイス群がネットワークにアクセスする時間を制限することができ、さらに各MTCデバイスの判断でアクセスタイミングが決まるため、ネットワーク側の管理コストも削減することができる。 In the currently considered method, the MTC device receives a notification of a time interval during which access is permitted from the network or the MTC server, and connects to the network at an arbitrary timing within the specified time. Since the access timing is randomly determined by each MTC device, even when the same time interval is notified to a plurality of MTC devices, the access timing is distributed so that access is not concentrated. Yes. By this method, the network only specifies a common time interval for a plurality of MTC devices (for example, MTC devices belonging to the same group), and limits the time for the MTC devices to access the network. In addition, since the access timing is determined by the determination of each MTC device, the management cost on the network side can be reduced.
 すべてのMTCデバイスが1つのMTCサーバとの間でしか通信をしない場合は、MTCデバイスにとっての通信相手は常に1つであり、コネクションも1つで十分であるため使用する帯域や管理コストは最小限で済む。しかし、1つのMTCデバイスが、他のMTCデバイス、又は他のMTCサーバと通信を行うことが可能である場合は、MTCサーバへのデータ送信と同時に別の通信相手に対してもデータを送信するため、使用する帯域及びMTCデバイスの処理コストも増える。また、MTCデバイスにとってMTCサーバへのデータ送信は基本動作の1つであり、MTCデバイスとしての機能を果たすために重要な動作である。このため、同じ時間間隔がそれぞれのMTCデバイスに割り当てられている場合には、MTCサーバへのデータ送信中に別のMTCデバイスからのリクエストを受ける可能性が高くなる。 When all MTC devices communicate with only one MTC server, there is always only one communication partner for the MTC device, and one connection is sufficient, so the bandwidth and management costs used are minimal. It's all you need However, if one MTC device can communicate with another MTC device or another MTC server, it transmits data to another communication partner simultaneously with data transmission to the MTC server. Therefore, the bandwidth to be used and the processing cost of the MTC device also increase. For the MTC device, data transmission to the MTC server is one of basic operations, and is an important operation for fulfilling the function as the MTC device. For this reason, when the same time interval is allocated to each MTC device, there is a high possibility of receiving a request from another MTC device during data transmission to the MTC server.
 しかしながら、別のMTCデバイスから要求を受けたMTCデバイスは、MTCサーバと要求元のMTCデバイスの両方に対して同時にデータを送信する必要があるため、送信処理に要する負荷が増すだけでなく、送信されるデータによってネットワークに輻輳が発生する。図19は、本発明が解決しようとする課題を説明するためのシーケンスチャートであり、(1)においてMTCデバイス1A及び1Bは、同じグループに属していて同じアクセス時間間隔P1が割り当てられている。図19を参照して説明すると、(2)MTCデバイス1Aがアクセス時間間隔P1内のデータ送信間隔P11でMTCサーバ2と通信をしている際に、(3)MTCデバイス1Bからデータ要求を受けて、(4)アクセス時間間隔P1内のデータ送信間隔P12でMTCデバイスBへデータを送信する場合、MTCサーバ2へのデータ送信とMTCデバイス1Bへのデータ送信が同時に行われてしまう間隔P13が生じる。これにより、送信データに遅延が生じることや、使用可能な帯域を越えてしまった場合にはパケットロスも発生してしまうという問題点がある。 However, an MTC device that has received a request from another MTC device needs to transmit data to both the MTC server and the requesting MTC device at the same time. The network is congested by the data that is generated. FIG. 19 is a sequence chart for explaining the problem to be solved by the present invention. In (1), the MTC devices 1A and 1B belong to the same group and are assigned the same access time interval P1. Referring to FIG. 19, (2) when the MTC device 1A communicates with the MTC server 2 at the data transmission interval P11 within the access time interval P1, (3) receives a data request from the MTC device 1B. (4) When data is transmitted to the MTC device B at the data transmission interval P12 within the access time interval P1, the interval P13 at which data transmission to the MTC server 2 and data transmission to the MTC device 1B are performed simultaneously is performed. Arise. As a result, there is a problem in that transmission data is delayed and packet loss occurs when the available bandwidth is exceeded.
 本発明は上記の問題点に鑑み、無線網を介して複数の通信デバイスからデータ収集サーバに対してデータを送信するとともに各通信デバイスの間でデータを通信する場合に、輻輳及びパケットロスを低減させることができる通信方法、通信システム及び通信デバイス並びに管理ノードを提供することを目的とする。 In view of the above problems, the present invention reduces congestion and packet loss when data is transmitted from a plurality of communication devices to a data collection server via a wireless network and data is communicated between the communication devices. An object of the present invention is to provide a communication method, a communication system, a communication device, and a management node.
 本発明は上記目的を達成するために、無線網を介して複数の通信デバイスからデータ収集サーバに対してデータを送信するとともに各通信デバイスの間でデータを通信する通信方法であって、
 前記複数の通信デバイスを管理する管理ノードから前記複数の通信デバイスに対して、前記複数の通信デバイスから各データを前記データ収集サーバに送信するための第1のアクセス時間間隔と、前記複数の通信デバイス間で各データを送受信するための第2のアクセス時間間隔を割り当てる割り当てステップと、
 前記割り当てられた第1のアクセス時間間隔において前記複数の通信デバイスが前記データ収集サーバに各データを送信するステップと、
 前記割り当てられた第2のアクセス時間間隔において前記複数の通信デバイス間で各データを送受信するステップとを、
 有する構成とした。
In order to achieve the above object, the present invention is a communication method for transmitting data from a plurality of communication devices to a data collection server via a wireless network and communicating data between the communication devices,
A first access time interval for transmitting each data from the plurality of communication devices to the data collection server from a management node that manages the plurality of communication devices to the plurality of communication devices, and the plurality of communication Assigning a second access time interval for transmitting and receiving each piece of data between devices;
The plurality of communication devices transmitting each piece of data to the data collection server in the assigned first access time interval;
Transmitting and receiving data between the plurality of communication devices in the allocated second access time interval; and
It was set as the structure which has.
 また本発明は上記目的を達成するために、無線網を介して複数の通信デバイスからデータ収集サーバに対してデータを送信するとともに各通信デバイスの間でデータを通信する通信システムであって、
 前記複数の通信デバイスを管理する管理ノードから前記複数の通信デバイスに対して、前記複数の通信デバイスから各データを前記データ収集サーバに送信するための第1のアクセス時間間隔と、前記複数の通信デバイス間で各データを送受信するための第2のアクセス時間間隔を割り当てる割り当て手段と、
 前記割り当てられた第1のアクセス時間間隔において前記複数の通信デバイスが前記データ収集サーバに各データを送信する手段と、
 前記割り当てられた第2のアクセス時間間隔において前記複数の通信デバイス間で各データを送受信する手段とを、
 有する構成とした。
In order to achieve the above object, the present invention is a communication system for transmitting data from a plurality of communication devices to a data collection server via a wireless network and communicating data between the communication devices,
A first access time interval for transmitting each data from the plurality of communication devices to the data collection server from a management node that manages the plurality of communication devices to the plurality of communication devices, and the plurality of communication Allocating means for allocating a second access time interval for transmitting and receiving each data between devices;
Means for the plurality of communication devices to transmit each data to the data collection server in the assigned first access time interval;
Means for transmitting and receiving data between the plurality of communication devices in the allocated second access time interval;
It was set as the structure which has.
 また本発明は上記目的を達成するために、無線網を介して複数の通信デバイスからデータ収集サーバに対してデータを送信するとともに各通信デバイスの間でデータを通信する通信システムにおける前記通信デバイスであって、
 前記複数の通信デバイスを管理する管理ノードから前記複数の通信デバイスに対して、前記複数の通信デバイスから各データを前記データ収集サーバに送信するための第1のアクセス時間間隔と、前記複数の通信デバイス間で各データを送受信するための第2のアクセス時間間隔を割り当てられた場合にその割り当てを受け付ける手段と、
 前記割り当てられた第1のアクセス時間間隔において前記データ収集サーバに各データを送信する手段と、
 前記割り当てられた第2のアクセス時間間隔において他の前記通信デバイス間で各データを送受信する手段とを、
 有する構成とした。
In order to achieve the above object, the present invention provides a communication device in a communication system for transmitting data from a plurality of communication devices to a data collection server via a wireless network and communicating data between the communication devices. There,
A first access time interval for transmitting each data from the plurality of communication devices to the data collection server from a management node that manages the plurality of communication devices to the plurality of communication devices, and the plurality of communication Means for accepting assignment when a second access time interval for transmitting and receiving data between devices is assigned;
Means for transmitting each data to the data collection server in the assigned first access time interval;
Means for transmitting and receiving data between the other communication devices in the allocated second access time interval;
It was set as the structure which has.
 また本発明は上記目的を達成するために、無線網を介して複数の通信デバイスからデータ収集サーバに対してデータを送信するとともに各通信デバイスの間でデータを通信する通信システムにおいて前記複数の通信デバイスを管理する管理ノードであって、
 前記複数の通信デバイスに対して、前記複数の通信デバイスから各データを前記データ収集サーバに送信するための第1のアクセス時間間隔と、前記複数の通信デバイス間で各データを送受信するための第2のアクセス時間間隔を割り当てる割り当て手段を、
 有する構成とした。
In order to achieve the above object, the present invention provides a communication system in which data is transmitted from a plurality of communication devices to a data collection server via a wireless network and data is communicated between the communication devices. A management node that manages the device,
A first access time interval for transmitting each piece of data from the plurality of communication devices to the data collection server and a first number for transmitting / receiving each piece of data between the plurality of communication devices to the plurality of communication devices. Assigning means for assigning two access time intervals,
It was set as the structure which has.
 この構成により、複数の通信デバイスに対して、複数の通信デバイスから各データをデータ収集サーバに送信するための第1のアクセス時間間隔と、複数の通信デバイス間で各データを送受信するための第2のアクセス時間間隔を割り当てるので、無線網を介して複数の通信デバイスからデータ収集サーバに対してデータを送信するとともに各通信デバイスの間でデータを通信する場合に、輻輳及びパケットロスを低減させることができる。 With this configuration, for the plurality of communication devices, the first access time interval for transmitting each data from the plurality of communication devices to the data collection server and the first access time for transmitting / receiving each data between the plurality of communication devices. Since two access time intervals are allocated, when data is transmitted from a plurality of communication devices to the data collection server via the wireless network and data is communicated between the communication devices, congestion and packet loss are reduced. be able to.
 本発明によれば、無線網を介して複数の通信デバイスからデータ収集サーバに対してデータを送信するとともに各通信デバイスの間でデータを通信する場合に、輻輳及びパケットロスを低減させることができる。 According to the present invention, when data is transmitted from a plurality of communication devices to a data collection server via a wireless network and data is communicated between the communication devices, congestion and packet loss can be reduced. .
本発明の第1の実施の形態におけるネットワーク構成の一例を示すブロック図The block diagram which shows an example of the network structure in the 1st Embodiment of this invention 本発明の第1の実施の形態における通信シーケンスを示す説明図Explanatory drawing which shows the communication sequence in the 1st Embodiment of this invention 図2の通信シーケンスの変形例を示す説明図Explanatory drawing which shows the modification of the communication sequence of FIG. 図2及び図3の時間間隔の割り当てシーケンスを詳しく示す説明図Explanatory drawing which shows the allocation sequence of the time interval of FIG.2 and FIG.3 in detail 図4の割り当てシーケンスの変形例を示す説明図Explanatory drawing which shows the modification of the allocation sequence of FIG. 図1におけるデータ送信元MTCデバイスの構成を詳しく示すブロック図The block diagram which shows in detail the structure of the data transmission source MTC device in FIG. 図3の通信シーケンスの変形例を示す説明図Explanatory drawing which shows the modification of the communication sequence of FIG. 図1におけるデータ要求元MTCデバイスの構成を詳しく示すブロック図The block diagram which shows the structure of the data request origin MTC device in FIG. 1 in detail 図1におけるMMEの構成を詳しく示すブロック図The block diagram which shows the structure of MME in FIG. 1 in detail 本発明の第2の実施の形態における通信シーケンスを示す説明図Explanatory drawing which shows the communication sequence in the 2nd Embodiment of this invention. 本発明の第2の実施の形態におけるデータ送信元MTCデバイスのリクエスト処理を説明するためのフローチャートThe flowchart for demonstrating the request processing of the data transmission origin MTC device in the 2nd Embodiment of this invention 本発明の第2の実施の形態におけるデータ送信元MTCデバイスのデータ送信処理を説明するためのフローチャートThe flowchart for demonstrating the data transmission process of the data transmission origin MTC device in the 2nd Embodiment of this invention 本発明の第3の実施の形態における通信シーケンスを示す説明図Explanatory drawing which shows the communication sequence in the 3rd Embodiment of this invention. 本発明の第3の実施の形態におけるデータ送信元MTCデバイスの処理を説明するためのタイミングチャートTiming chart for explaining the processing of the data transmission source MTC device in the third embodiment of the present invention 本発明の第3の実施の形態におけるデータ要求元MTCデバイスの構成を詳しく示すブロック図The block diagram which shows in detail the structure of the data request origin MTC device in the 3rd Embodiment of this invention 本発明の第3の実施の形態における通信シーケンスの変形例を示す説明図Explanatory drawing which shows the modification of the communication sequence in the 3rd Embodiment of this invention. 本発明の第3の実施の形態におけるデータ送信元MTCデバイスのデータ送信処理を説明するためのフローチャートThe flowchart for demonstrating the data transmission process of the data transmission origin MTC device in the 3rd Embodiment of this invention 本発明の第3の実施の形態における通信シーケンスの変形例を示す説明図Explanatory drawing which shows the modification of the communication sequence in the 3rd Embodiment of this invention. 本発明が解決しようとする課題を説明するためのシーケンスチャートSequence chart for explaining problems to be solved by the present invention
 以下、図面を参照して本発明の実施の形態について説明する。
 (第1の実施の形態)
 図1は、本発明の第1の実施の形態におけるネットワーク構成の一例を示す図である。複数のMTCデバイスとして、MTCデバイス1AとMTCデバイス1Bが動作している場合について考える。これらのMTCデバイス1A、1Bは、無線アクセスモジュールとして、3GPPインタフェースを備えており、例えば基地局(eNB:evolved Node B)3を介してネットワーク(例えば、3GPPコアネットワーク)4へ接続することができる。ネットワーク4には、MTCデバイス1A、1B及びMTCサーバ2を管理するMME(Mobility Management Entity)5や、S-GW(Serving Gateway)6、P-GW(Packet Data Gateway)7が存在し、これらのエンティティ5、6、7は、MTCデバイス1A、1Bの接続状態の管理や、MTCデバイス1A、1BがMTCサーバ2へアクセスするために必要なコネクションの確立・管理及びデータの転送などを行う。また、MTCサーバ2は、各MTCデバイス1A、1Bを管理するサーバであり、各MTCデバイス1A、1Bから通知されたさまざまな情報を基に、ユーザUへサービスを提供する。MTCデバイス1A及びMTCデバイス1Bは、3GPPコアネットワーク4を介してMTCサーバ2との間にコネクションを生成し、収集したデータやイベントなどをMTCサーバ2へ通知する。本実施の形態では、MTCサーバ2及びMTCデバイス1Bが、MTCデバイス1Aが保持しているデータを必要としている場合を想定しているが、どちらもMTCデバイス(MTCデバイス1Bと他のMTCデバイス(不図示))からデータの送信を要求される場合でもよい。
Embodiments of the present invention will be described below with reference to the drawings.
(First embodiment)
FIG. 1 is a diagram illustrating an example of a network configuration according to the first embodiment of this invention. Consider a case where the MTC device 1A and the MTC device 1B are operating as a plurality of MTC devices. These MTC devices 1A and 1B have a 3GPP interface as a radio access module, and can be connected to a network (for example, 3GPP core network) 4 via a base station (eNB: evolved Node B) 3, for example. . The network 4 includes an MME (Mobility Management Entity) 5, an S-GW (Serving Gateway) 6, and a P-GW (Packet Data Gateway) 7 that manage the MTC devices 1A and 1B and the MTC server 2. The entities 5, 6, and 7 manage the connection state of the MTC devices 1A and 1B, establish and manage connections necessary for the MTC devices 1A and 1B to access the MTC server 2, and transfer data. The MTC server 2 is a server that manages the MTC devices 1A and 1B, and provides services to the user U based on various information notified from the MTC devices 1A and 1B. The MTC device 1A and the MTC device 1B generate a connection with the MTC server 2 via the 3GPP core network 4, and notify the MTC server 2 of collected data and events. In the present embodiment, it is assumed that the MTC server 2 and the MTC device 1B require the data held by the MTC device 1A. However, both of the MTC devices (the MTC device 1B and other MTC devices ( (Not shown)) may be requested to transmit data.
 なお、MTCデバイス1A、1Bが保持する無線アクセスモジュールとしては、WiMAX(登録商標)やWLANなどの他の無線システムを用いてもよく、3GPPインタフェースに限定されない。また、図1に示されているコアネットワーク4内のエンティティ5、6、7は、無線アクセスシステムとして3GPPのLTE/SAE(Long Term Evolution/System Architecture Evolution)を用いた場合の機能ブロックを表しているが、使用する無線アクセスシステムに応じて、同様の機能を保持する適切なエンティティ名に置き換えられる。例えば、3GPPのUMTS(Universal Mobile Telecommunication System)を用いた場合は、eNB3はRNC/BSC(Radio Network Controller/Base Station Controller)、MME5はSGSN(Serving GPRS Support Node)、P-GW7はGGSN(Gateway GPRS Support Node)に置き換えられる。また、MTCサーバ2は、3GPPコアネットワーク4内に配置されていてもよい。 In addition, as a radio | wireless access module which MTC device 1A, 1B hold | maintains, other radio | wireless systems, such as WiMAX (trademark) and WLAN, may be used, and it is not limited to a 3GPP interface. In addition, the entities 5, 6, and 7 in the core network 4 shown in FIG. 1 represent functional blocks in the case of using 3GPP LTE / SAE (Long Term Term Evolution / System Architecture) Evolution as a radio access system. However, depending on the radio access system to be used, it is replaced with an appropriate entity name having the same function. For example, when 3GPP UMTS (Universal Mobile Telecommunication System) is used, eNB 3 is RNC / BSC (Radio Network Controller / Base Station Controller), MME 5 is SGSN (Serving GPRS Support Node), and P-GW 7 is GGSN (Gateway GPRS). Support Node). Further, the MTC server 2 may be disposed in the 3GPP core network 4.
 図2は、MTCデバイス1A、MTCサーバ2及びMTCデバイス1Bとの間で通信を行う際の処理の一例を示すシーケンスチャートである。まず、
(1)MTCデバイス1A及びMTCデバイス1Bは、ネットワーク4側から2つのアクセス時間間隔が割り当てられる。一つは、MTCサーバ2との通信が許可された時間を示すアクセス時間間隔TP1であり、もう一方はMTCデバイス1A-1B間の通信が許可された時間を示すアクセス時間間隔TP2である。アクセス時間間隔TP1、TP2の通知方法は後述する動的な通知方法に限らず、オペレータ又はMTCサーバ2及びMTCユーザUが、MTCデバイス間通信をするMTCデバイス1A、1Bを特定し、それぞれに対してアクセス時間間隔TP1及びTP2をあらかじめ割り当ててもよい。この場合、各MTCデバイス1A、1Bのサブスクリプションデータの中にあらかじめ保持してもよいし、各MTCデバイス1A、1Bがネットワーク4に接続した際に通知してもよい。アクセス時間間隔TP1、TP2の割り当てを受けたMTCデバイス1AとMTCデバイス1Bは、アクセス時間間隔TP2において他のMTCデバイスと通信が可能であることを認識することができる。
FIG. 2 is a sequence chart illustrating an example of processing when communication is performed among the MTC device 1A, the MTC server 2, and the MTC device 1B. First,
(1) The MTC device 1A and the MTC device 1B are assigned two access time intervals from the network 4 side. One is an access time interval TP1 indicating a time during which communication with the MTC server 2 is permitted, and the other is an access time interval TP2 indicating a time during which communication between the MTC devices 1A-1B is permitted. The notification method of the access time intervals TP1 and TP2 is not limited to the dynamic notification method to be described later, and the operator or the MTC server 2 and the MTC user U specify the MTC devices 1A and 1B that perform communication between MTC devices, The access time intervals TP1 and TP2 may be assigned in advance. In this case, it may be stored in advance in the subscription data of each MTC device 1A, 1B, or may be notified when each MTC device 1A, 1B is connected to the network 4. The MTC device 1A and the MTC device 1B that have been assigned the access time intervals TP1 and TP2 can recognize that they can communicate with other MTC devices in the access time interval TP2.
(2)これらのアクセス時間間隔TP1、TP2の通知を受けたMTCデバイス1Aは、MTCサーバ2へ通知するデータがある場合は、MTCサーバ2へのアクセス時間間隔TP1で示されている開始時刻になったら、アクセス時間間隔TP1内の任意のタイミングでMTCサーバ2へデータの送信を開始する(データ送信間隔TP11≦TP1)。なお、(2)では示されていないが、MTCデバイス1Bも同様に、MTCサーバ2へ通知するデータがある場合は、アクセス時間間隔TP1で示されている開始時刻になったら、アクセス時間間隔TP1内の任意のタイミングでMTCサーバ2へデータの送信を開始する。
(3)一方、MTCデバイス1Bは、MTCデバイス1Aから取得したいデータがある場合は、MTCデバイス間のアクセス時間間隔TP2で示されている開始時間の後の任意のタイミングでMTCデバイス1Aへデータ要求を送信する。
(4)MTCデバイス1Aは、MTCデバイス1Bからデータの送信要求を受けた際に、要求を受けたタイミングが、アクセス時間間隔TP2の範囲内である場合には、その要求を受け入れて必要なデータの送信を開始する(データ送信間隔TP21≦TP2)。一方、MTCデバイス1Bからの要求を受けたタイミングが、MTCサーバ2へのアクセス時間間隔TP1の範囲内であった場合には、要求を拒否してデータの送信を行わない。
(2) When there is data to be notified to the MTC server 2, the MTC device 1A that has received the notification of these access time intervals TP1 and TP2 has a start time indicated by the access time interval TP1 to the MTC server 2. Then, transmission of data to the MTC server 2 is started at an arbitrary timing within the access time interval TP1 (data transmission interval TP11 ≦ TP1). Although not shown in (2), the MTC device 1B also similarly has an access time interval TP1 when there is data to be notified to the MTC server 2 when the start time indicated by the access time interval TP1 is reached. Transmission of data to the MTC server 2 is started at an arbitrary timing.
(3) On the other hand, when there is data to be acquired from the MTC device 1A, the MTC device 1B makes a data request to the MTC device 1A at an arbitrary timing after the start time indicated by the access time interval TP2 between the MTC devices. Send.
(4) When the MTC device 1A receives a data transmission request from the MTC device 1B, if the received timing is within the access time interval TP2, the MTC device 1A accepts the request and receives necessary data. Is started (data transmission interval TP21 ≦ TP2). On the other hand, when the timing at which the request from the MTC device 1B is received is within the range of the access time interval TP1 to the MTC server 2, the request is rejected and data is not transmitted.
 また、MTCデバイス1Aは、MTCサーバ2からの要求を受けてデータの送信を行う場合、MTCサーバ2からの要求を受けたタイミングがアクセス時間間隔TP1の範囲内である場合にはデータ送信を開始し、アクセス時間間隔TP2の範囲内である場合にはデータ送信を行わない。なお、要求を受けたタイミングがアクセス時間間隔TP2であっても、MTCサーバ2からの要求である場合は受け入れるように設定してもよい。つまり、TP1とTP2はサーバ2との通信に対して有効なアクセス時間間隔であり、TP2はMTCデバイス1A-1B間の通信に対して有効なアクセス時間間隔として設定する。 In addition, when the MTC device 1A transmits data in response to a request from the MTC server 2, the MTC device 1A starts data transmission when the timing at which the request from the MTC server 2 is received is within the access time interval TP1. However, data transmission is not performed when it is within the range of the access time interval TP2. Even when the timing of receiving the request is the access time interval TP2, the request may be set to be accepted if the request is from the MTC server 2. That is, TP1 and TP2 are effective access time intervals for communication with the server 2, and TP2 is set as an effective access time interval for communication between the MTC devices 1A-1B.
 このように、MTCデバイス1AがMTCサーバ2だけでなく、他のMTCデバイス1Bと通信を行う場合、MTCデバイス1A、1BとMTCサーバ2間の通信を許可するアクセス時間間隔TP1と、MTCデバイス1A-1B同士の通信を許可するアクセス時間間隔TP2とを分けて割り当てることで、MTCサーバ2へのデータ送信と、MTCデバイス1A、1Bへのデータ送信が同時に行われることを防ぐことができる。なお、MTCデバイス1A、1Bは、アクセス時間間隔TP1、TP2を取得した後、指定されたアクセス時間間隔TP1、TP2内の任意の時刻になるまでネットワーク4に接続していなくてもよい。すなわち、MTCデバイス1Aは、MTCサーバ2へデータ送信を行うまではネットワーク4に接続している必要はない。また、MTCデバイス1Bは、MTCデバイス1Aに対してデータ要求を送信するまではネットワーク4に接続している必要はない。 As described above, when the MTC device 1A communicates not only with the MTC server 2, but also with another MTC device 1B, an access time interval TP1 that permits communication between the MTC devices 1A, 1B and the MTC server 2 and the MTC device 1A By separately assigning the access time interval TP2 that permits communication between -1B, it is possible to prevent the data transmission to the MTC server 2 and the data transmission to the MTC devices 1A and 1B from being performed simultaneously. Note that the MTC devices 1A and 1B may not be connected to the network 4 after acquiring the access time intervals TP1 and TP2 until an arbitrary time within the designated access time intervals TP1 and TP2. That is, the MTC device 1A does not need to be connected to the network 4 until data transmission to the MTC server 2 is performed. Further, the MTC device 1B does not need to be connected to the network 4 until a data request is transmitted to the MTC device 1A.
 また、図2では、他のMTCデバイスとの通信に割り当てられたアクセス時間間隔TP2が、MTCサーバ2との通信に割り当てられたアクセス時間間隔TP1よりも後に配置されているが、代わりに図3に示すように、アクセス時間間隔TP2がアクセス時間間隔TP1よりも前に配置されてもよい。この場合、MTCデバイス1Bは、MTCデバイス1Aからの情報を取得した後にMTCサーバ2へのデータ送信を行うことができるため、MTCデバイス1Aから取得した情報を考慮したデータをMTCサーバ2へ通知することができる。また、MTCデバイス1Bが、MTCデバイス1Aから取得したデータも含めてMTCサーバ2へ送信する場合、MTCデバイス1Aは、MTCデバイス1Bへ送信したデータをMTCサーバ2へ送信する必要がないと判断してもよい。これにより、MTCデバイスAがMTCサーバ2へデータを送信することで発生するトラフィックや負荷を減らすことができる。 In FIG. 2, the access time interval TP2 assigned to communication with other MTC devices is arranged after the access time interval TP1 assigned to communication with the MTC server 2, but instead, FIG. As shown in FIG. 5, the access time interval TP2 may be arranged before the access time interval TP1. In this case, since the MTC device 1B can transmit data to the MTC server 2 after acquiring information from the MTC device 1A, the MTC device 1B notifies the MTC server 2 of data considering the information acquired from the MTC device 1A. be able to. When the MTC device 1B transmits to the MTC server 2 including the data acquired from the MTC device 1A, the MTC device 1A determines that the data transmitted to the MTC device 1B does not need to be transmitted to the MTC server 2. May be. Thereby, the traffic and load which generate | occur | produce when MTC device A transmits data to the MTC server 2 can be reduced.
 図4は、MTCデバイス1AとMTCデバイス1Bに対してアクセス時間間隔TP1及びTP2が動的に割り当てられる様子を表しているシーケンスチャートの一例である。(1)時間間隔の割り当てにおいて、
(11)MTCデバイス1Bは、MTCデバイス1Aと通信を行いたい場合、まずMME5(又はMTCサーバ2)に対して、MTCデバイス1Aと通信を行うことを示すMTCデバイス間通信要求を送信する。
(12)(13)MME5は、このMTCデバイス間通信要求を受けた場合、MTCデバイス1BによるMTCデバイス1Aへのアクセスが、MTCデバイス1AによるMTCサーバ2との通信に影響が及ぶことを防ぐために、アクセス時間間隔TP1及びTP2の両方をMTCデバイス1B及びMTCデバイス1Aへ割り当てる。
FIG. 4 is an example of a sequence chart showing how access time intervals TP1 and TP2 are dynamically allocated to the MTC device 1A and the MTC device 1B. (1) In assigning time intervals,
(11) When the MTC device 1B wants to communicate with the MTC device 1A, the MTC device 1B first transmits to the MME 5 (or the MTC server 2) an MTC device communication request indicating that communication with the MTC device 1A is performed.
(12) (13) When the MME 5 receives the communication request between the MTC devices, the MME 5 prevents the access to the MTC device 1A by the MTC device 1B from affecting the communication with the MTC server 2 by the MTC device 1A. The access time intervals TP1 and TP2 are both assigned to the MTC device 1B and the MTC device 1A.
 ここでは、MTCデバイス1AとMTCデバイス1Bは、同じMME5によって管理されていることを想定しているが、各MTCデバイス1A、1Bが異なるMMEによって管理されている場合は、MTCデバイス1BからMTCデバイス間通信要求を受けたMMEと、MTCデバイス1Aを管理しているMMEとの間でメッセージ交換を行うことでアクセス時間間隔TP1、TP2が決定される。また、本発明の第1の実施の形態におけるMME5の機能をMTCサーバ2が保持している場合は、MTCデバイス1BはMTCデバイス間通信要求をMTCサーバ2へ送信する。この場合、MTCサーバ2が適切なアクセス時間間隔TP1、TP2を決定し、それぞれのMTCデバイス1A、1Bへ割り当てる。なお、各MTCデバイス1A、1Bが異なるMTCサーバによって管理されている場合は、MTCデバイス1BからMTCデバイス間通信要求を受けたMTCサーバと、MTCデバイス1Aを管理しているMTCサーバとの間でメッセージ交換を行うことでアクセス時間間隔TP1、TP2が決定される。 Here, it is assumed that the MTC device 1A and the MTC device 1B are managed by the same MME 5, but if the MTC devices 1A and 1B are managed by different MMEs, the MTC device 1B to the MTC device Access time intervals TP1 and TP2 are determined by exchanging messages between the MME that has received the inter-communication request and the MME that manages the MTC device 1A. Further, when the MTC server 2 holds the function of the MME 5 in the first embodiment of the present invention, the MTC device 1B transmits an inter-MTC device communication request to the MTC server 2. In this case, the MTC server 2 determines appropriate access time intervals TP1 and TP2 and assigns them to the respective MTC devices 1A and 1B. When each MTC device 1A, 1B is managed by a different MTC server, between the MTC server that has received the MTC device communication request from the MTC device 1B and the MTC server that manages the MTC device 1A. Access time intervals TP1 and TP2 are determined by exchanging messages.
 これらのアクセス時間間隔TP1、TP2の通知を受けたMTCデバイスAとMTCデバイスBは、アクセス時間間隔TP2の中でデバイス間通信が可能であることを認識する。MTCデバイス1Aは、アクセス時間間隔TP1、TP2とともに、アクセスが許可された通信相手(アクセスを要求した通信相手)を示す情報(MTCデバイス1BのIDやIPアドレス)を取得することが望ましい。これにより、MTCデバイス1Aはアクセス時間間隔TP2の中でMTCデバイス1Bからアクセス要求が来ることを認識することができると同時に、MTCデバイス1B以外のMTCデバイスからのアクセス要求を拒絶することができる。図4に基づくアクセス時間間隔TP1、TP2の通知を受けた後は、各MTCデバイス1A、1Bは図2を用いて説明した処理(2)(3)(4)に示すようにデータの送受信を行う。 The MTC device A and the MTC device B that have received notification of these access time intervals TP1 and TP2 recognize that communication between devices is possible in the access time interval TP2. It is desirable that the MTC device 1A obtains information (ID or IP address of the MTC device 1B) indicating the communication partner to which access is permitted (communication partner who has requested access) together with the access time intervals TP1 and TP2. As a result, the MTC device 1A can recognize that an access request comes from the MTC device 1B within the access time interval TP2, and at the same time, can reject an access request from an MTC device other than the MTC device 1B. After receiving the notification of the access time intervals TP1 and TP2 based on FIG. 4, each of the MTC devices 1A and 1B transmits and receives data as shown in the processes (2), (3), and (4) described with reference to FIG. Do.
 また、(1)時間間隔の割り当てでは、代わりに図5(11)(12)(13)に示すように、MTCデバイス1Aが、MTCデバイス1Bとの通信を行うことを示すMTCデバイス間通信要求を送信してもよい。この場合、MTCデバイス1Aは、MTCデバイス1Bに対して送信するデータがあると判断した場合に、MTCデバイス間通信要求を送信する。これにより、実際にデータを送信する側のMTCデバイス1Aがデバイス間通信を必要と判断した場合に限り、デバイス間通信用のアクセス時間間隔TP2の割り当てを受けることが可能となる。MTCデバイス1Bは、アクセス時間間隔TP1、TP2とともに、アクセスが許可された通信相手を示す情報(MTCデバイス1AのIDやIPアドレス)を取得することが望ましい。これにより、MTCデバイス1Bはアクセス時間間隔TP2の中でMTCデバイス1Aに対してアクセスすることが可能であることを認識することができると同時に、MTCデバイス1A以外のMTCデバイスからのアクセス要求を拒絶することができる。図5に基づくアクセス時間間隔TP1、TP2の通知を受けた後は、各MTCデバイス1A、1Bは図2を用いて説明した処理(2)(3)(4)に示すようにデータの送受信を行う。 In (1) time interval allocation, as shown in FIGS. 5 (11), (12), and (13), the MTC device communication request indicating that the MTC device 1A communicates with the MTC device 1B instead. May be sent. In this case, when it is determined that there is data to be transmitted to the MTC device 1B, the MTC device 1A transmits a communication request between MTC devices. As a result, the access time interval TP2 for inter-device communication can be assigned only when the MTC device 1A that actually transmits data determines that inter-device communication is necessary. It is desirable that the MTC device 1B obtains information (ID and IP address of the MTC device 1A) indicating the communication partner permitted to access, together with the access time intervals TP1 and TP2. As a result, the MTC device 1B can recognize that it can access the MTC device 1A within the access time interval TP2, and at the same time, rejects an access request from an MTC device other than the MTC device 1A. can do. After receiving the notification of the access time intervals TP1 and TP2 based on FIG. 5, each of the MTC devices 1A and 1B transmits and receives data as shown in the processes (2), (3), and (4) described with reference to FIG. Do.
 なお、図3に示すような順番(TP2→TP1)のアクセス時間間隔TP2、TP1の割り当てを受けたい場合は、図4におけるMTCデバイス1B、及び図5におけるMTCデバイス1Aは、MTCデバイス間通信要求の中に、アクセス時間間隔TP2をアクセス時間間隔TP1よりも前に割り当てることを要求する明示的な情報(例えば、フラグ)を含めて送信してもよい。また、明示的な情報を含める代わりに、MTCデバイス間通信要求を受けたMME5が、デバイス間通信要求を送信したMTCデバイス1B又は1Aが、自身の送信データを生成するために他のMTCデバイスからの情報を必要とするMTCデバイスであると判断した場合には、アクセス時間間隔TP2をアクセス時間間隔TP1よりも前に割り当てるようにしてもよい。 When it is desired to receive the allocation of the access time intervals TP2 and TP1 in the order (TP2 → TP1) as shown in FIG. 3, the MTC device 1B in FIG. 4 and the MTC device 1A in FIG. May include explicit information (for example, a flag) requesting that the access time interval TP2 be allocated before the access time interval TP1. Further, instead of including explicit information, the MME 5 that has received the communication request between MTC devices transmits the communication request between the MTC devices 1B or 1A from other MTC devices in order to generate its own transmission data. When it is determined that the information is an MTC device that requires this information, the access time interval TP2 may be assigned before the access time interval TP1.
 また、図4におけるMTCデバイス1B、及び図5におけるMTCデバイス1AがMTCデバイス間通信要求に通信相手となるMTCデバイスのIDを含めるのではなく、MTCデバイス間通信要求を受信したMME5が適切な通信相手を選択してもよい。この場合、MME5が選択した通信相手に対してアクセス時間間隔TP1、TP2とともに、データを要求しているMTCデバイスを示す情報(MTCデバイスのIDやIPアドレス)が通知される。一方、要求元のMTCデバイスに対しても、選択された通信相手に関する情報(MTCデバイスのIDやIPアドレス)がアクセス時間間隔TP1、TP2とともに通知される。MME5が適切な通信相手を選択する際の方法として、MTCデバイス間通信要求によって要求された情報を保持しているMTCデバイスを選択するようにしてもよい。この場合、MTCデバイス間通信要求を送信するMTCデバイスは、取得したい情報の種類を示す識別子をメッセージの中に含めて送信する。 In addition, the MTC device 1B in FIG. 4 and the MTC device 1A in FIG. 5 do not include the ID of the MTC device that is the communication partner in the communication request between MTC devices, but the MME 5 that has received the communication request between MTC devices is appropriate communication. You may select a partner. In this case, information (MTC device ID and IP address) indicating the MTC device requesting the data is notified to the communication partner selected by the MME 5 together with the access time intervals TP1 and TP2. On the other hand, information on the selected communication partner (ID and IP address of the MTC device) is also notified to the requesting MTC device together with the access time intervals TP1 and TP2. As a method when the MME 5 selects an appropriate communication partner, an MTC device holding the information requested by the communication request between MTC devices may be selected. In this case, the MTC device that transmits the communication request between MTC devices includes an identifier indicating the type of information desired to be acquired in the message.
 また、MTCデバイス間通信要求を処理するMME5の機能を、MTCサーバ2やネットワーク4内の他のエンティティ(P-GW7、S-GW6)が保持してもよい。なお、この場合においても、図4及び図5の場合と同様に、データを要求するMTCデバイスがMTCデバイス間通信要求の中に通信相手となるMTCデバイスのIDを含めるのではなく、要求を受信するMTCサーバ2が適切な通信相手を選択してもよい。この場合、MTCサーバ2が選択した通信相手に対してアクセス時間間隔TP1、TP2が通知されるとともに、要求元及び要求先であるMTCデバイスに対して、選択された通信相手に関する情報が通知される。 Further, the function of the MME 5 that processes the communication request between the MTC devices may be held by the MTC server 2 or other entities (P-GW 7, S-GW 6) in the network 4. In this case as well, as in the case of FIGS. 4 and 5, the MTC device that requests data does not include the ID of the MTC device that is the communication partner in the communication request between MTC devices, but receives the request. The MTC server 2 may select an appropriate communication partner. In this case, the access time intervals TP1 and TP2 are notified to the communication partner selected by the MTC server 2, and information related to the selected communication partner is notified to the MTC device that is the request source and the request destination. .
 <MTCデバイス1Aの構成>
 図6は、本発明の第1の実施の形態において、データ要求元MTCデバイス1Bから要求を受けてMTCデバイス1Bに対してデータを送信するデータ送信元MTCデバイス1Aの構成の一例を示すブロック図である。図6に示されているMTCデバイス1Aは、インタフェース101と、設定情報取得部102と、リクエスト処理部103と、ネットワーク接続部104と、情報保持部105と接続時刻決定部106を有している。インタフェース101は、MTCデバイス1A自身のインタフェース101に直接関連する下位レイヤプロトコルモジュールを含んでいる。この下位レイヤプロトコルモジュールには、信号変調、エンコード圧縮、メディアアクセス制御、リンクレイヤ制御などのメカニズムを始めとする基本的なデータ通信に必要な機能、及び、物理層及びデータリンク層全体の機能が実装されている。
<Configuration of MTC device 1A>
FIG. 6 is a block diagram showing an example of the configuration of the data transmission source MTC device 1A that receives a request from the data request source MTC device 1B and transmits data to the MTC device 1B in the first embodiment of the present invention. It is. The MTC device 1A illustrated in FIG. 6 includes an interface 101, a setting information acquisition unit 102, a request processing unit 103, a network connection unit 104, an information holding unit 105, and a connection time determination unit 106. . The interface 101 includes lower layer protocol modules directly related to the interface 101 of the MTC device 1A itself. This lower layer protocol module has functions necessary for basic data communication, including mechanisms such as signal modulation, encoding compression, media access control, link layer control, and functions of the entire physical layer and data link layer. Has been implemented.
 また、設定情報取得部102は、ネットワーク4へ接続している際にMME5から必要な設定情報を取得するため機能を有し、アクセス時間間隔としてMME5によって割り当てられたTP1とTP2を取得する。なお、MTCサーバ2との通信に割り当てられるアクセス時間間隔TP1がすでに割り当てられている場合は、他のMTCデバイス1Bとの通信に割り当てられるアクセス時間間隔TP2のみ通知を受ければよい。また、アクセス時間間隔TP1の割り当てが不要なMTCデバイスは、アクセス時間間隔TP2のみを割り当ててもよい。例えば、相手先MTCデバイス1BがMTCサーバ2とは通信せず、MTCデバイス1A自身とのみ通信を行う場合、相手先MTCデバイス1Bに対してはアクセス時間間隔TP2のみを割り当てればよい。また、別な例として、MTCデバイス1A自身がMTCサーバ2とは通信せず、相手先MTCデバイス1Bとのみ通信を行う場合、MTCデバイス1Aに対してはアクセス時間間隔TP2のみを割り当てればよい。 Also, the setting information acquisition unit 102 has a function for acquiring necessary setting information from the MME 5 when connected to the network 4, and acquires TP1 and TP2 assigned by the MME 5 as access time intervals. When the access time interval TP1 assigned for communication with the MTC server 2 has already been assigned, only the access time interval TP2 assigned for communication with the other MTC device 1B needs to be notified. In addition, an MTC device that does not require assignment of the access time interval TP1 may assign only the access time interval TP2. For example, when the counterpart MTC device 1B does not communicate with the MTC server 2 and communicates only with the MTC device 1A itself, only the access time interval TP2 needs to be assigned to the counterpart MTC device 1B. As another example, when the MTC device 1A itself does not communicate with the MTC server 2 and communicates only with the counterpart MTC device 1B, only the access time interval TP2 needs to be assigned to the MTC device 1A. .
 アクセス時間間隔TP1、TP2の取得方法としては、MTCデバイス1A及びMTCデバイス1Bがネットワークへ接続した際に、ネットワーク4側があらかじめアクセス時間間隔TP1、TP2の両方を割り当てる方法と、ネットワーク4側がMTCデバイス1A、1Bからの要求を受けて割り当てる方法がある。前者の場合、MTCデバイス1A、1Bは、ネットワーク4へ最初に接続する時や、MTCサーバ2へ最初にアクセスする時に、アクセス時間間隔TP1、TP2の割り当てを受ける。一方、後者の場合は、設定情報取得部102は、先述した図5(11)(12)に示すように、相手先MTCデバイス1Bとの通信が必要であることを認識した場合にMTCデバイス間通信要求をMME5へ送信して、MTCデバイス間通信用のアクセス時間間隔TP2の割り当てを要求し、また、取得したアクセス時間間隔TP1、TP2を情報保持部105へ保持するよう指示する。また、情報保持部105は、ネットワーク4へアクセスできる時間間隔TP1、TP2の他にMTCサーバ2及びMME5から取得した情報や、接続時刻決定部106によって決定された次回接続時刻などを保持する機能を有している。 The access time intervals TP1 and TP2 are obtained by a method in which the network 4 side assigns both access time intervals TP1 and TP2 in advance when the MTC device 1A and the MTC device 1B are connected to the network, and the network 4 side is the MTC device 1A. There is a method of assigning in response to a request from 1B. In the former case, the MTC devices 1A and 1B are assigned access time intervals TP1 and TP2 when they first connect to the network 4 or when they first access the MTC server 2. On the other hand, in the latter case, the setting information acquisition unit 102 recognizes that communication with the counterpart MTC device 1B is necessary as shown in FIGS. 5 (11) and 12 (12). A communication request is transmitted to MME 5 to request assignment of access time interval TP2 for communication between MTC devices, and to instruct information holding unit 105 to hold acquired access time intervals TP1 and TP2. The information holding unit 105 has a function of holding information acquired from the MTC server 2 and the MME 5 in addition to the time intervals TP1 and TP2 that can access the network 4, the next connection time determined by the connection time determination unit 106, and the like. Have.
 また、リクエスト処理部103は、MTCサーバ2、又は他のMTCデバイス1Bから受信したアクセス要求を処理する機能を有している。データ送信の要求を受けた場合、その要求の送信元がMTCサーバ2であるかMTCデバイス1Bであるかを判別する。要求元がMTCサーバ2である場合は、要求を受けたタイミングが、MTCサーバ2との通信に割り当てられたアクセス時間間隔TP1の範囲内である場合はその要求を受け入れて応答する。一方、要求元がMTCデバイス1Bである場合は、要求を受けたタイミングがアクセス時間間隔TP1の範囲内である場合はその要求を拒否する。要求を受けたタイミングが、他のMTCデバイス1Bとの通信に割り当てられたアクセス時間間隔TP2内である場合は、その要求を受け入れて応答する。 Moreover, the request processing unit 103 has a function of processing an access request received from the MTC server 2 or another MTC device 1B. When a data transmission request is received, it is determined whether the transmission source of the request is the MTC server 2 or the MTC device 1B. If the request source is the MTC server 2, if the timing of receiving the request is within the access time interval TP1 assigned to the communication with the MTC server 2, the request is accepted and responded. On the other hand, if the request source is the MTC device 1B, the request is rejected if the request is received within the access time interval TP1. When the timing of receiving the request is within the access time interval TP2 allocated for communication with the other MTC device 1B, the request is accepted and responded.
 また、図3に示すように、アクセス時間間隔TP1よりも前にアクセス時間間隔TP2が割り当てられている場合、リクエスト処理部103は、相手先MTCデバイス1Bから要求されたデータについて、MTCサーバ2への送信が不要であると判断し、アクセス時間間隔TP1において送信しないようにしてもよい。これは、相手先MTCデバイス1Bが、MTCデバイス1Aから取得したデータを考慮して生成したデータ、あるいはMTCデバイス1A自身から取得したデータを含むデータをMTCサーバ2へ送信する場合に、MTCデバイス1Aが不要なデータあるいは同じデータを重複して送信することを避けることができるため、トラフィックを軽減することができる。 As shown in FIG. 3, when the access time interval TP2 is assigned before the access time interval TP1, the request processing unit 103 sends the data requested from the counterpart MTC device 1B to the MTC server 2. May not be transmitted at the access time interval TP1. This is because when the counterpart MTC device 1B transmits to the MTC server 2 data generated in consideration of data acquired from the MTC device 1A, or data including data acquired from the MTC device 1A itself, the MTC device 1A. Can avoid unnecessary data or duplicate transmission of the same data, thereby reducing traffic.
 さらに、アクセス時間間隔TP1よりも前にアクセス時間間隔TP2が割り当てられている場合、図7に示すように、MTCデバイス1Aは、MTCデバイス1A自身が保持する情報をアクセス時間間隔TP2ですべて相手先MTCデバイス1Bへ送信した場合には、続くアクセス時間間隔TP1においてMTCサーバ2へのデータ送信をする必要がないと判断することができる(図7では、図3に示す(4)データ送信なし)。これらの場合、相手先MTCデバイス1Bは、アクセス時間間隔TP2においてMTCデバイス1Aに対して送信するデータ要求の中に、続くアクセス時間間隔TP1ではMTCサーバ2へのデータを送信する必要がないことを示す情報(例えば、フラグ)を含めてもよい。この情報がデータ要求に含まれている場合、MTCデバイス1Aは、アクセス時間間隔TP2において相手先MTCデバイス1Bへ送信したデータについては、続くアクセス時間間隔TP1においてMTCサーバ2へ送信する必要がないと判断する。そして、相手先MTCデバイス1Bへ送信しなかったデータのみをMTCサーバ2へ送信すると判断する。なお、MTCデバイス1Bは、データ要求の中で、要求するデータの種類を表す識別子を含めてもよい。 Further, when the access time interval TP2 is assigned before the access time interval TP1, as shown in FIG. 7, the MTC device 1A has all the information held by the MTC device 1A itself in the access time interval TP2. In the case of transmission to the MTC device 1B, it can be determined that it is not necessary to transmit data to the MTC server 2 in the subsequent access time interval TP1 ((4) No data transmission shown in FIG. 3 in FIG. 7). . In these cases, the counterpart MTC device 1B does not need to transmit data to the MTC server 2 in the subsequent access time interval TP1 in the data request transmitted to the MTC device 1A in the access time interval TP2. Information (for example, a flag) may be included. When this information is included in the data request, the MTC device 1A does not need to transmit the data transmitted to the counterpart MTC device 1B in the access time interval TP2 to the MTC server 2 in the subsequent access time interval TP1. to decide. Then, it is determined that only data that has not been transmitted to the counterpart MTC device 1B is transmitted to the MTC server 2. Note that the MTC device 1B may include an identifier representing the type of data requested in the data request.
 また、接続時刻決定部106は、MTCデバイス1A自身が次回ネットワーク4へ接続する時刻(次回接続時刻)を決定する機能を有している。アクセス時間間隔TP1の割り当てを受けている場合、アクセス時間間隔TP1内であれば、MTCデバイス1AはMTCサーバ2との通信が終了した後、ネットワーク4から切断することができる。さらにアクセス時間間隔TP2の割り当てを受けている場合は、他のMTCデバイス1Bからのアクセス要求を受け入れる必要があるため、アクセス時間間隔TP2の開始時刻が次回の接続時刻となる。 Further, the connection time determination unit 106 has a function of determining a time (next connection time) at which the MTC device 1A itself connects to the network 4 next time. When the access time interval TP1 is assigned, the MTC device 1A can be disconnected from the network 4 after the communication with the MTC server 2 is completed within the access time interval TP1. Further, when the access time interval TP2 is assigned, it is necessary to accept an access request from another MTC device 1B, so the start time of the access time interval TP2 becomes the next connection time.
 また、ネットワーク接続部104は、インタフェース101を用いて新たにネットワーク4に接続するための処理や、接続時刻決定部106によって決められた次回接続時刻にネットワーク4へ接続する際に行う接続処理を実行する機能を有している。また、接続時刻決定部106の指示により、ネットワーク4から切断するための処理を行う。 In addition, the network connection unit 104 executes processing for newly connecting to the network 4 using the interface 101 and connection processing performed when connecting to the network 4 at the next connection time determined by the connection time determination unit 106. It has a function to do. Further, processing for disconnecting from the network 4 is performed according to an instruction from the connection time determination unit 106.
 <MTCデバイス1Bの構成>
 図8は、本発明の第1の実施の形態において、データ送信元MTCデバイス1Aにデータ要求を送信してMTCデバイス1Aからのデータを受信するデータ要求元MTCデバイス1Bの構成の一例を示すブロック図である。図8に示されているMTCデバイス1Bは、インタフェース101と、設定情報取得部102と、データ取得部107と、ネットワーク接続部104と、情報保持部105と接続時刻決定部106を有している。インタフェース101と設定情報取得部102は、MTCデバイス1Aの場合と同じであるため説明を省略する。なお、設定情報の取得方法としては、設定情報取得部102は、先述した図4(11)(12)に示すように、相手先MTCデバイス1Aとの通信が必要であることを認識した場合にMTCデバイス間通信要求をMME5へ送信して、MTCデバイス間通信用のアクセス時間間隔TP2の割り当てを要求し、また、取得したアクセス時間間隔TP1、TP2を情報保持部105へ保持するよう指示する。
<Configuration of MTC device 1B>
FIG. 8 is a block diagram showing an example of the configuration of the data request source MTC device 1B that transmits a data request to the data transmission source MTC device 1A and receives data from the MTC device 1A in the first embodiment of the present invention. FIG. The MTC device 1B illustrated in FIG. 8 includes an interface 101, a setting information acquisition unit 102, a data acquisition unit 107, a network connection unit 104, an information holding unit 105, and a connection time determination unit 106. . Since the interface 101 and the setting information acquisition unit 102 are the same as those in the case of the MTC device 1A, description thereof is omitted. As a setting information acquisition method, the setting information acquisition unit 102 recognizes that communication with the counterpart MTC device 1A is necessary as shown in FIGS. 4 (11) and 12 (12). An MTC inter-device communication request is transmitted to the MME 5 to request assignment of an access time interval TP2 for MTC device communication, and to instruct the information holding unit 105 to hold the acquired access time intervals TP1 and TP2.
 接続時刻決定部106は、MTCデバイス1B自身が次回ネットワーク4へ接続する時刻(次回接続時刻)を決定する機能を有している。アクセス時間間隔TP1の割り当てを受けている場合、MTCサーバ2との通信(例えば、データ送信)が必要な場合はアクセス時間間隔TP1内に行う。このとき、アクセス時間間隔TP1内であればMTCデバイス1BはMTCサーバ2との通信が終了した後、ネットワーク4から切断することができる。さらにMTCデバイス間通信用のアクセス時間間隔TP2の割り当てを受けている場合は、他のMTCデバイス1Aに対してのアクセス要求を送信することが可能であるため、アクセス時間間隔TP2内で次回の接続時間を決定する。 The connection time determination unit 106 has a function of determining a time (next connection time) when the MTC device 1B itself connects to the network 4 next time. When the access time interval TP1 is assigned, if communication (for example, data transmission) with the MTC server 2 is required, the access time interval TP1 is performed within the access time interval TP1. At this time, within the access time interval TP1, the MTC device 1B can be disconnected from the network 4 after the communication with the MTC server 2 is completed. Further, when the access time interval TP2 for communication between the MTC devices is assigned, it is possible to transmit an access request to the other MTC device 1A, so the next connection within the access time interval TP2 is possible. Determine the time.
 データ取得部107は、ネットワーク接続部104からネットワーク4への接続処理が完了したことを受け、情報保持部105を参照し、アクセス時間間隔TP2内でのアクセスが許可されている相手先MTCデバイス1Aに対してアクセス要求メッセージ(データ送信要求)を送信する。なお、図3に示すように、アクセス時間間隔TP1よりも前にアクセス時間間隔TP2が割り当てられた場合、データ取得部107は、相手先MTCデバイス1Aから取得したデータを考慮してMTCサーバ2へ送信するデータを生成してもよい。例えば、MTCデバイス1Bが、相手先MTCデバイス1Aの代わりにMTCサーバ2へデータを送信する役割をもったMTCデバイスである場合は、相手先MTCデバイス1Aから取得したデータを含むデータをMTCサーバ2へ送信する。 In response to the completion of the connection processing from the network connection unit 104 to the network 4, the data acquisition unit 107 refers to the information holding unit 105, and the counterpart MTC device 1 A that is permitted to access within the access time interval TP 2. An access request message (data transmission request) is transmitted. As shown in FIG. 3, when the access time interval TP2 is assigned before the access time interval TP1, the data acquisition unit 107 considers the data acquired from the counterpart MTC device 1A and sends it to the MTC server 2. Data to be transmitted may be generated. For example, when the MTC device 1B is an MTC device having a role of transmitting data to the MTC server 2 instead of the counterpart MTC device 1A, the data including the data acquired from the counterpart MTC device 1A is stored in the MTC server 2 Send to.
 <MMEの構成>
 図9は、本発明の第1の実施の形態におけるMME5の構成の一例を示すブロック図である。設定情報通知部502は、MTCデバイス1A、1Bに対して、アクセス時間間隔TP1、TP2を割り当てる機能を有し、MTCデバイス1A又はMTCデバイス1Bから、MTCデバイス間通信要求を受けた場合、適切なアクセス時間間隔TP1、TP2を決めて、それを例えば要求元のMTCデバイス1Aと、MTCデバイス1Aの通信相手となるMTCデバイス1Bへインタフェース501を介して通知し、また、情報保持部503に保持する。
<Configuration of MME>
FIG. 9 is a block diagram illustrating an example of the configuration of the MME 5 according to the first embodiment of this invention. The setting information notification unit 502 has a function of assigning access time intervals TP1 and TP2 to the MTC devices 1A and 1B, and when receiving a communication request between MTC devices from the MTC device 1A or MTC device 1B, The access time intervals TP1 and TP2 are determined and notified to the requesting MTC device 1A and the MTC device 1B as the communication counterpart of the MTC device 1A via the interface 501 and held in the information holding unit 503, for example. .
 以上、説明したように、本発明の第1の実施の形態によれば、MTCデバイス1AとMTCデバイス1Bは、MTCサーバ2との通信に使用するアクセス時間間隔TP1とは別に、MTCデバイス間の通信に使用するアクセス時間間隔TP2の割り当てを受けることで、MTCサーバ2との通信と同時に別のMTCデバイスとの通信を行わなければならない状況を回避することができるため、輻輳やパケットロスを軽減させることが可能となる。 As described above, according to the first embodiment of the present invention, the MTC device 1A and the MTC device 1B are connected between the MTC devices separately from the access time interval TP1 used for communication with the MTC server 2. By assigning the access time interval TP2 used for communication, it is possible to avoid a situation in which communication with another MTC device must be performed simultaneously with communication with the MTC server 2, thereby reducing congestion and packet loss. It becomes possible to make it.
 (第2の実施の形態)
 本発明の第2の実施の形態のネットワーク構成は、図1を用いて説明した第1の実施の形態と同様のネットワーク構成であるため説明を省略する。図10を参照しながら、本発明の第2の実施の形態における処理について説明する。図10は、本発明の第2の実施の形態において、MTCデバイス1A、MTCサーバ2及びMTCデバイス1Bが通信を行う場合の処理の一例を示すシーケンスチャートである。第2の実施の形態では、MTCデバイス1A-1B間のデータ送信要求を、MTCサーバ2との通信に使用するアクセス時間間隔TP1内において行う。
(1)MTCデバイス1A及びMTCデバイス1BはMME5からアクセス時間間隔TP1、TP2の割り当てを受ける。割り当てられるアクセス時間間隔TP1、TP2は、本発明の第1の実施の形態で説明したものと同じである。
(2)MTCデバイス1Aは、アクセス時間間隔TP1内のデータ送信間隔TP11においてMTCサーバ2へのデータ送信を行う。
(Second Embodiment)
The network configuration of the second embodiment of the present invention is the same as that of the first embodiment described with reference to FIG. Processing in the second exemplary embodiment of the present invention will be described with reference to FIG. FIG. 10 is a sequence chart illustrating an example of processing when the MTC device 1A, the MTC server 2, and the MTC device 1B perform communication in the second embodiment of the present invention. In the second embodiment, a data transmission request between the MTC devices 1A-1B is made within the access time interval TP1 used for communication with the MTC server 2.
(1) The MTC device 1A and the MTC device 1B receive assignment of access time intervals TP1 and TP2 from the MME 5. The allocated access time intervals TP1 and TP2 are the same as those described in the first embodiment of the present invention.
(2) The MTC device 1A transmits data to the MTC server 2 at the data transmission interval TP11 within the access time interval TP1.
(3)一方、MTCデバイス1Bは、アクセス時間間隔TP1において、MTCデバイス1Aに対してデータ送信要求を送る。MTCデバイス1Aがアクセス時間間隔TP1において他のMTCデバイス1Bからデータ送信の要求を受けた場合、応答メッセージのみを返し、アクセス時間間隔TP1ではデータの送信は行わない。応答メッセージは、MTCデバイス1Bに対して、データ要求が受け入れられたことを通知し、実際のデータ送信はアクセス時間間隔TP2で行われることを認識させる。
(4)MTCデバイス1Aは、アクセス時間間隔TP2内のデータ送信間隔TP21において、アクセス時間間隔TP1において受信したデータ要求に対するデータ送信を行う。アクセス時間間隔TP2におけるデータ送信を開始するタイミングは、MTCデバイス1Aが任意に判断して決めることができる。例えば、MTCデバイス1Aは、MTCデバイス1B以外の他のMTCデバイス(不図示)へデータを送る必要があった場合、そのデータ送信を優先して行った後、MTCデバイス1Bへのデータ送信を開始することができる。
(3) On the other hand, the MTC device 1B sends a data transmission request to the MTC device 1A in the access time interval TP1. When the MTC device 1A receives a data transmission request from another MTC device 1B in the access time interval TP1, it returns only a response message, and does not transmit data in the access time interval TP1. The response message notifies the MTC device 1B that the data request has been accepted, and recognizes that the actual data transmission is performed at the access time interval TP2.
(4) The MTC device 1A performs data transmission for the data request received in the access time interval TP1 in the data transmission interval TP21 within the access time interval TP2. The timing for starting data transmission in the access time interval TP2 can be determined by the MTC device 1A arbitrarily determining. For example, when it is necessary to send data to an MTC device (not shown) other than the MTC device 1B, the MTC device 1A gives priority to the data transmission and then starts data transmission to the MTC device 1B. can do.
 <MTCデバイス1Aの構成及び処理>
 本発明の第2の実施の形態におけるMTCデバイス1Aの構成について図6を用いて説明する。リクエスト処理部103は、MTCサーバ2又は他のMTCデバイス1Bから受信したアクセス要求を処理する機能を有している。図11は、アクセス時間間隔TP1(ステップS1)においてMTCデバイス1A自身のリクエスト処理部103が行う処理の一例を示すフローチャートである。アクセス時間間隔TP1内でリクエストを受けなかった場合(ステップS2でNO)、リクエスト処理部103は何もせずに終了する(ステップS2→S6)。一方、アクセス時間間隔TP1内でデータ送信の要求を受けた場合(ステップS2でYES)、リクエスト処理部103は、その要求の送信元がMTCサーバ2であるかMTCデバイス1Bであるかを判別する(ステップS3)。要求元がMTCサーバ2である場合(ステップS3でNO)は、その要求を受け入れて応答し、データの送信を開始する(ステップS7)。
<Configuration and Processing of MTC Device 1A>
The configuration of the MTC device 1A according to the second embodiment of the present invention will be described with reference to FIG. The request processing unit 103 has a function of processing an access request received from the MTC server 2 or another MTC device 1B. FIG. 11 is a flowchart showing an example of processing performed by the request processing unit 103 of the MTC device 1A itself in the access time interval TP1 (step S1). If the request is not received within the access time interval TP1 (NO in step S2), the request processing unit 103 ends without doing anything (step S2 → S6). On the other hand, when a request for data transmission is received within the access time interval TP1 (YES in step S2), the request processing unit 103 determines whether the transmission source of the request is the MTC server 2 or the MTC device 1B. (Step S3). If the request source is the MTC server 2 (NO in step S3), the request is accepted and responded, and data transmission is started (step S7).
 一方、要求元がMTCデバイス1Bである場合(ステップS3でYES)は、その要求を受け入れてレスポンスを返すが、アクセス時間間隔TP1内ではデータの送信は行わない(ステップS4)。さらに、この場合、MTCデバイス1Bから受信したデータ送信要求に関する情報を情報保持部105へ保持するよう指示する(ステップS5)。保持される情報は、MTCデバイス1BのIDやIPアドレス、要求されたデータの種類などである。また、リクエスト処理部105は、複数のMTCデバイスからリクエストを受けた場合、それぞれの要求に関する情報を情報保持部105へ保持するよう指示する。なお、リクエスト処理部103は、要求元のMTCデバイス1Bへ送信するレスポンスメッセージの中に、アクセス時間間隔TP2においてデータ送信を開始する時刻に関する情報を含めてもよい。これにより、要求元のMTCデバイス1Bは、アクセス時間間隔TP2においてMTCデバイス1Aからデータ送信が開始される直前にネットワーク4へ接続すればよいため、必要以上にネットワーク4へ接続し、消費電力が増加するのを防ぐことができる。 On the other hand, if the request source is the MTC device 1B (YES in step S3), the request is accepted and a response is returned, but no data is transmitted within the access time interval TP1 (step S4). Further, in this case, the information holding unit 105 is instructed to hold information related to the data transmission request received from the MTC device 1B (step S5). The information held includes the ID and IP address of the MTC device 1B, the type of requested data, and the like. Further, when receiving a request from a plurality of MTC devices, the request processing unit 105 instructs the information holding unit 105 to hold information regarding each request. Note that the request processing unit 103 may include information related to the time to start data transmission in the access time interval TP2 in the response message transmitted to the requesting MTC device 1B. As a result, the requesting MTC device 1B has only to connect to the network 4 immediately before the data transmission from the MTC device 1A is started in the access time interval TP2, so that it connects to the network 4 more than necessary and power consumption increases. Can be prevented.
 また、リクエスト処理部103は、要求元のMTCデバイス1Bへ送信するレスポンスメッセージの中に、データ送信が可能である時間間隔TP2を含めてもよい。すなわち、MTCデバイス1Bは、あらかじめネットワークから割り当てられたアクセス可能時間TP1の中でネットワーク4へ接続し、MTCデバイス1Aに対してリクエストメッセージを送信する。この場合、MTCデバイス1Bは、MME5からではなく、MTCデバイス1Aからアクセス時間間隔TP2の通知を受けることになる。また、MTCデバイス1Bは、リクエストメッセージを、MTCサーバ2を介してMTCデバイス1Aへ送信してもよい。MTCサーバ2は、MTCデバイス1Bから受けたリクエストメッセージをMTCデバイス1Aへ転送する。しかし、MTCサーバ2がMTCデバイス1Bからリクエストメッセージを受信した際に、MTCデバイス1Aがネットワーク4に接続していなかった場合、MTCサーバ2は、MTCデバイス1Aがネットワーク4に接続してから、リクエストメッセージの転送を行う。 Further, the request processing unit 103 may include a time interval TP2 in which data transmission is possible in the response message transmitted to the requesting MTC device 1B. That is, the MTC device 1B connects to the network 4 within the accessible time TP1 allocated in advance from the network, and transmits a request message to the MTC device 1A. In this case, the MTC device 1B receives the notification of the access time interval TP2 not from the MME 5 but from the MTC device 1A. Further, the MTC device 1B may transmit a request message to the MTC device 1A via the MTC server 2. The MTC server 2 transfers the request message received from the MTC device 1B to the MTC device 1A. However, when the MTC server 2 receives the request message from the MTC device 1B and the MTC device 1A is not connected to the network 4, the MTC server 2 requests the request after the MTC device 1A connects to the network 4. Forward the message.
 なお、MTCデバイス1Aから通知されるアクセス時間間隔は、TP2そのものであってもよいし、TP2の範囲内の任意の時間間隔であってもよい。後者の場合、MTCデバイス1Aは、MTCデバイス1Bとの通信に使用する時間間隔とMTCサーバ2や他のMTCデバイスとの通信に使用する時間間隔と分けることができる。MTCデバイス1Aからアクセス時間間隔TP2の通知を受けたMTCデバイス1Bは、TP2の開始時刻にネットワーク4へ接続し、MTCデバイス1Aからのデータ送信を待ち受ける。又は、TP2の中の任意のタイミングで再度MTCデバイス1Aへデータ送信を要求するためのリクエストメッセージを送信する。これらのどちらを実行するかは、MTCデバイス1Aが指示することができる。例えば、MTCデバイス1Aが、アクセス時間間隔TP2において、MTCデバイス1Bと通信をする時刻を任意に決定したい場合は、MTCデバイス1Bに対して、MTCデバイス1Aからのデータを待ち受けるよう指示する。また、MTCデバイス1Aが、アクセス時間間隔TP2において、MTCデバイス1Bとの通信をする時刻を指定する必要が無い場合は、MTCデバイス1Bに対してTP2の中の任意のタイミングでリクエストを送信するよう指示する。 Note that the access time interval notified from the MTC device 1A may be the TP2 itself or an arbitrary time interval within the range of the TP2. In the latter case, the MTC device 1A can be divided into a time interval used for communication with the MTC device 1B and a time interval used for communication with the MTC server 2 and other MTC devices. Receiving the notification of the access time interval TP2 from the MTC device 1A, the MTC device 1B connects to the network 4 at the start time of TP2, and waits for data transmission from the MTC device 1A. Alternatively, a request message for requesting data transmission to the MTC device 1A is transmitted again at an arbitrary timing in TP2. Which of these is executed can be instructed by the MTC device 1A. For example, when the MTC device 1A wants to arbitrarily determine the time to communicate with the MTC device 1B in the access time interval TP2, it instructs the MTC device 1B to wait for data from the MTC device 1A. Further, when it is not necessary for the MTC device 1A to specify the time for communication with the MTC device 1B in the access time interval TP2, the MTC device 1A transmits a request to the MTC device 1B at an arbitrary timing in the TP2. Instruct.
 また、図6における接続時刻決定部106は、情報保持部105を参照し、データ送信などのためにMTCサーバ2や他のMTCデバイス1Bとの通信が必要であるか否かを確認し、必要がある場合はMTCデバイス1A自身が次回ネットワークへ接続する時刻(次回接続時刻)や切断するタイミングを決定する機能を有している。MTCサーバ2との通信を行う必要がある場合は、割り当てられているアクセス時間間隔TP1を確認し、アクセス時間間隔TP1内の任意のタイミングを接続時刻として決定する。そしてそのタイミングでネットワーク接続部104に対しネットワーク4へ接続するよう指示し、MTCサーバ2との通信を開始する。MTCサーバ2との通信が終了した後、まだアクセス時間間隔TP1内である場合は、ネットワーク4から切断するようネットワーク接続部104へ指示する。なお、MTCサーバ2以外の他のMTCサーバと通信が必要である場合は、他のMTCサーバとの通信が終了した後、まだアクセス時間間隔TP1内である場合に、ネットワーク4から切断する。 Further, the connection time determination unit 106 in FIG. 6 refers to the information holding unit 105 to confirm whether communication with the MTC server 2 or another MTC device 1B is necessary for data transmission or the like. If there is, the MTC device 1A itself has a function of determining the time to connect to the next network (next connection time) and the timing to disconnect. When it is necessary to communicate with the MTC server 2, the allocated access time interval TP1 is confirmed, and an arbitrary timing within the access time interval TP1 is determined as the connection time. At that timing, the network connection unit 104 is instructed to connect to the network 4, and communication with the MTC server 2 is started. If communication is still within the access time interval TP1 after the communication with the MTC server 2 ends, the network connection unit 104 is instructed to disconnect from the network 4. In addition, when communication with other MTC servers other than MTC server 2 is required, after communication with another MTC server is complete | finished, when it is still in access time interval TP1, it will disconnect from the network 4.
 また、接続時刻決定部106は、情報保持部105を参照してアクセス時間間隔TP1においてMTCデバイス1Bからのデータ送信要求を受けたことを確認した場合は、アクセス時間間隔TP2においてネットワークに接続し、データの送信を行う必要があると判断する。図12は、本発明の第2の実施の形態において、アクセス時間間隔TP1、TP2の割り当てを受けているMTCデバイス1Aの接続時刻決定部106が行う処理の一例を示すフローチャートである。図12において、接続時刻決定部106は、アクセス時間間隔TP1の終了時に情報保持部105を参照して、アクセス時間間隔TP1内にMTCデバイスからのデータ送信要求を受信したかどうかを確認する(ステップS11、S12)。データ送信要求を受信していなかった場合(ステップS12でNO)は、アクセス時間間隔TP2においてネットワークに接続する必要がないと判断し、アクセス時間間隔TP2ではネットワークに接続しない(ステップS13)。データ送信要求を受信していた場合(ステップS12でYES)は、アクセス時間間隔TP2の任意のタイミングを接続時刻として決定し、そのタイミングでネットワーク接続部104に対しネットワークへ接続するよう指示し(ステップS12→S15)、MTCデバイス1Bとの通信を開始する(ステップS16)。なお、MTCデバイス1B以外の他のMTCデバイスからもデータ送信要求を受信していた場合には、それぞれの通信相手に対して接続時刻を決定した後、最初にデータ送信を開始するタイミングでネットワークに接続するよう指示する。 Further, when the connection time determination unit 106 confirms that the data transmission request from the MTC device 1B is received in the access time interval TP1 with reference to the information holding unit 105, the connection time determination unit 106 connects to the network in the access time interval TP2. Judge that it is necessary to send data. FIG. 12 is a flowchart illustrating an example of processing performed by the connection time determination unit 106 of the MTC device 1A that has been assigned the access time intervals TP1 and TP2 in the second embodiment of this invention. In FIG. 12, the connection time determination unit 106 refers to the information holding unit 105 at the end of the access time interval TP1, and confirms whether a data transmission request from the MTC device has been received within the access time interval TP1 (step S11, S12). If a data transmission request has not been received (NO in step S12), it is determined that there is no need to connect to the network at the access time interval TP2, and no connection is made to the network at the access time interval TP2 (step S13). If a data transmission request has been received (YES in step S12), an arbitrary timing of the access time interval TP2 is determined as a connection time, and the network connection unit 104 is instructed to connect to the network at that timing (step) S12 → S15), communication with the MTC device 1B is started (step S16). If a data transmission request has been received from another MTC device other than the MTC device 1B, the connection time is determined for each communication partner, and then the data transmission request is first sent to the network. Instruct to connect.
 また、接続時刻決定部106は、アクセス時間間隔TP1の終了時に情報保持部105を参照して、アクセス時間間隔TP1において複数のMTCデバイスからリクエストを受けていることを確認した場合、アクセス時間間隔TP2においてデータ送信を開始する順番を任意に決めることができる。例えば、要求されたデータの種類を確認し、優先度が高いデータを要求しているMTCデバイスに対して先にデータ送信を開始することで、優先度の高いデータを先に届けることができる。また、優先度がない場合や、同じ種類のデータを要求されている場合は、要求を受けた順番にデータ送信を開始してもよいし、ランダムに順番を決めてもよい。また、送信するデータ量が大きいMTCデバイスから先にデータ送信を開始することで、送信の完了まで時間を要するデータがあったとしても、アクセス時間間隔内でデータ送信を完了するよう制御することができる。 When the connection time determination unit 106 refers to the information holding unit 105 at the end of the access time interval TP1 and confirms that requests are received from a plurality of MTC devices in the access time interval TP1, the access time interval TP2 The order in which data transmission is started can be arbitrarily determined. For example, by confirming the type of requested data and starting data transmission to an MTC device that is requesting high priority data, high priority data can be delivered first. When there is no priority or when the same type of data is requested, data transmission may be started in the order in which the requests are received, or the order may be determined randomly. Also, by starting data transmission first from an MTC device with a large amount of data to be transmitted, even if there is data that takes time to complete transmission, it is possible to control data transmission to be completed within an access time interval. it can.
 また、接続時刻決定部106は、アクセス時間間隔TP1の終了時に情報保持部105を参照して、アクセス時間間隔TP1においてリクエストを受けていないMTCデバイス(例えば、あらかじめデータを送信することが決められた送信相手)がいる場合、リクエストを受けたMTCデバイスよりも先にデータを送信するべきと判断してもよい。例えば、アクセス時間間隔TP2において通信相手との間でデータ送信を開始する時間がすでに決まっている場合には、そのMTCデバイスへの送信を優先して行い、その通信の終了後にアクセス時間間隔TP1でリクエストを受けたMTCデバイスに対するデータ送信を開始してもよい。 In addition, the connection time determination unit 106 refers to the information holding unit 105 at the end of the access time interval TP1, and determines that an MTC device that has not received a request in the access time interval TP1 (for example, to transmit data in advance). When there is a transmission partner), it may be determined that data should be transmitted before the MTC device that has received the request. For example, when the time for starting data transmission with the communication partner is already determined in the access time interval TP2, priority is given to transmission to the MTC device, and after the end of the communication, the access time interval TP1 Data transmission to the MTC device that has received the request may be started.
 <MTCデバイス1Bの構成及び処理>
 本発明の第2の実施の形態におけるMTCデバイス1Bの構成について図8を用いて説明する。接続時刻決定部106は、MTCデバイス1Bが次回ネットワーク4へ接続する時刻(次回接続時刻)を決定する機能を有している。アクセス時間間隔TP1の割り当てを受けている場合、MTCサーバ2との通信(例えば、データ送信)が必要な場合はアクセス時間間隔TP1内に行う。接続時刻決定部106はまた、情報保持部105を参照し、MTCデバイス1Aとの後述する通信がアクセス時間間隔TP2において行われることが確認された場合に、アクセス時間間隔TP2の開始時刻にネットワーク4に接続するようネットワーク接続部104へ指示する。なお、MTCデバイス1Aから、MTCデバイス1AがMTCデバイス1Bに対してデータ送信を開始する時刻の通知を受けている場合は、その時刻の前にネットワーク4に接続するよう接続部104へ指示する。また、先述したように、MTCデバイス1Aとのデータ送信が可能なアクセス時間間隔TP2は、MTCデバイス1Aから直接通知されてもよい。
<Configuration and Processing of MTC Device 1B>
The configuration of the MTC device 1B in the second embodiment of the present invention will be described with reference to FIG. The connection time determination unit 106 has a function of determining a time (next connection time) when the MTC device 1B is connected to the network 4 next time. When the access time interval TP1 is assigned, if communication (for example, data transmission) with the MTC server 2 is required, the access time interval TP1 is performed within the access time interval TP1. The connection time determination unit 106 also refers to the information holding unit 105, and when it is confirmed that communication described later with the MTC device 1A is performed in the access time interval TP2, the network time 4 is set at the start time of the access time interval TP2. The network connection unit 104 is instructed to connect to the network. When the MTC device 1A receives a notification of the time when the MTC device 1A starts data transmission to the MTC device 1B, the MTC device 1A instructs the connection unit 104 to connect to the network 4 before that time. Further, as described above, the access time interval TP2 in which data transmission with the MTC device 1A can be performed may be directly notified from the MTC device 1A.
 データ取得部107は、情報保持部105を参照して、相手先MTCデバイス1Aとの通信が必要であると判断される場合は、アクセス時間間隔TP1において相手先MTCデバイス1A宛にデータ要求を送信する。また、送信したデータ要求に対する応答を受けた場合は、アクセス時間間隔TP2において相手先MTCデバイス1Aとの通信が行われることを示す情報を情報保持部105へ保持する。データ取得部107はまた、ネットワーク接続部104からネットワーク4への接続処理が完了したことを受け、情報保持部107を参照し、アクセス時間間隔TP2内でのアクセスが許可されている相手先MTCデバイス1Aに対してアクセス要求メッセージ(データ送信要求)を送信する。 If the data acquisition unit 107 refers to the information holding unit 105 and determines that communication with the counterpart MTC device 1A is necessary, the data acquisition unit 107 transmits a data request to the counterpart MTC device 1A at the access time interval TP1. To do. When receiving a response to the transmitted data request, the information holding unit 105 holds information indicating that communication with the counterpart MTC device 1A is performed in the access time interval TP2. In response to the completion of the connection processing from the network connection unit 104 to the network 4, the data acquisition unit 107 refers to the information holding unit 107 and is permitted to access within the access time interval TP 2. An access request message (data transmission request) is transmitted to 1A.
 以上、説明したように、本発明の第2の実施の形態によれば、MTCデバイス1BがMTCデバイス1Aへデータ送信を要求する場合は、MTCサーバ2との通信に使用するアクセス時間間隔TP1内でリクエストを受信することができるため、MTCデバイス1Aが、MTCデバイス1A-1B間の通信に使用するアクセス時間間隔TP2においてネットワーク4へ接続する必要があるか否かを判断することができる。これにより、MTCデバイス1Aは、MTCデバイス1Bからの要求がなかった場合には、アクセス時間間隔TP2においてネットワーク4に接続する必要がないため、消費電力を削減することが可能となる。 As described above, according to the second embodiment of the present invention, when the MTC device 1B requests data transmission to the MTC device 1A, it is within the access time interval TP1 used for communication with the MTC server 2. Therefore, the MTC device 1A can determine whether or not it is necessary to connect to the network 4 in the access time interval TP2 used for communication between the MTC devices 1A-1B. As a result, when there is no request from the MTC device 1B, the MTC device 1A does not need to be connected to the network 4 at the access time interval TP2, so that power consumption can be reduced.
 (第3の実施の形態)
 図13を参照しながら、本発明の第3の実施の形態における処理について説明する。図13は、本発明の第3の実施の形態において、MTCデバイス1A、MTCサーバ2及びMTCデバイス1Bが通信を行う場合の処理の一例を示すシーケンスチャートであり、図14は、MTCデバイス1Aの処理を説明するためのタイミングチャートである。第3の実施の形態では、MTCデバイス1Aは、アクセス時間間隔TP1内の途中でMTCサーバ2との通信が終了した後は、アクセス時間間隔TP1の残りの間隔における消費電力を抑えるために、アイドルモードへ遷移する。さらに、他のMTCデバイスがリクエストメッセージを送信した場合には、ページングの受信タイミングで送信元のMTCデバイスを特定することができるため、ページングを受けたとしてもネットワーク4へ接続(コネクテッドモードへ遷移)する必要はない。
(Third embodiment)
Processing in the third exemplary embodiment of the present invention will be described with reference to FIG. FIG. 13 is a sequence chart showing an example of processing when the MTC device 1A, the MTC server 2, and the MTC device 1B perform communication in the third embodiment of the present invention, and FIG. It is a timing chart for explaining processing. In the third embodiment, after the communication with the MTC server 2 is completed in the middle of the access time interval TP1, the MTC device 1A is idle in order to suppress power consumption in the remaining interval of the access time interval TP1. Transition to mode. Further, when another MTC device transmits a request message, the MTC device that is the transmission source can be specified at the paging reception timing, so even if paging is received, connection to the network 4 (transition to the connected mode) is possible. do not have to.
(1)MTCデバイス1A及びMTCデバイス1Bは、MME5(又はeNB3)からアクセス時間間隔の割り当てを受ける。割り当てられる時間間隔は、MTCサーバ2からの要求に基づくページング受信時間間隔TP1-1と、MTCデバイス2からの要求に基づくページング受信時間間隔TP1-2と、本発明の第1の実施の形態で説明したアクセス時間間隔TP2の3つである。なお、ページング受信時間間隔TP1-1及びTP1-2は、本発明の第1の実施の形態で説明したアクセス時間間隔TP1の中に含まれている(TP1=TP1-1+TP1-2)。ページング受信時間間隔TP1-2は、MTCデバイス1Bに関する情報が関連付けられており、MTCデバイス1Bからの要求を受信する時間間隔であることを示す。割り当て方法は、本発明の第1の実施の形態において、図4と図5を用いて説明した内容と同じであるため説明を省略する。 (1) The MTC device 1A and the MTC device 1B receive assignment of access time intervals from the MME 5 (or eNB 3). The allocated time intervals are the paging reception time interval TP1-1 based on the request from the MTC server 2, the paging reception time interval TP1-2 based on the request from the MTC device 2, and the first embodiment of the present invention. There are three access time intervals TP2 described. Note that the paging reception time intervals TP1-1 and TP1-2 are included in the access time interval TP1 described in the first embodiment of the present invention (TP1 = TP1-1 + TP1-2). The paging reception time interval TP1-2 is associated with information related to the MTC device 1B, and indicates a time interval for receiving a request from the MTC device 1B. The allocation method is the same as that described with reference to FIG. 4 and FIG. 5 in the first embodiment of the present invention, and thus the description thereof is omitted.
 また、本発明の第2の実施の形態において説明したように、MTCデバイス1Bは、MTCデバイス1Aに対してリクエストメッセージを送信し、その応答メッセージでページング受信時間間隔TP1-2を取得してもよい。この場合、MTCデバイス1Bには、TP1又はTP1とTP1-1のみが通知されており、MTCデバイス1Bは、TP1又はTP1-1内の任意の時刻にリクエストメッセージを送信する。そして応答メッセージにより通知されたページング受信時間間隔TP1-2の中で再度リクエストメッセージの送信を行う。すなわち、MTCデバイス1Bからリクエストメッセージを受けたMTCデバイス1Aは、アクセス時間間隔TP1の範囲内にMTCデバイス1B用のページング受信時間間隔を指定し手通知する。 Further, as described in the second embodiment of the present invention, the MTC device 1B transmits a request message to the MTC device 1A and acquires the paging reception time interval TP1-2 using the response message. Good. In this case, only TP1 or TP1 and TP1-1 are notified to the MTC device 1B, and the MTC device 1B transmits a request message at an arbitrary time in the TP1 or TP1-1. Then, the request message is transmitted again within the paging reception time interval TP1-2 notified by the response message. That is, the MTC device 1A that has received the request message from the MTC device 1B designates the paging reception time interval for the MTC device 1B within the range of the access time interval TP1, and performs manual notification.
 図13、図14において、
(2)MTCデバイス1Aは、アクセス時間間隔TP1内の送信間隔TP11においてMTCサーバ2へのデータ送信を行う。
(3)そして、アクセス時間間隔TP1内の途中でMTCサーバ2との通信が終了した後は、アクセス時間間隔TP1の残りの間隔(=TP1-TP11)における消費電力を抑えるために、アイドルモードへ遷移する。
(4)一方、MTCデバイスBは、MTCデバイス1Aに対してアクセスする必要がある場合は、アクセス時間間隔TP1内のページング受信時間間隔TP1-2において、MTCデバイス1Aに対してデータ送信要求を送る。
(5)(6)一方、MTCデバイス1Aがページング受信時間間隔TP1-2においてページングを受けた場合は、そのページングはMTCデバイス1Bからのページングであると認識し、アクセス時間間隔TP2においてアイドルモードから復帰して、MTCデバイス1Bへデータ送信を開始する(送信間隔P21)。もしもページング受信時間間隔TP1-2において、ページングを受けなかった場合には、アクセス時間間隔TP2においてネットワーク4へ接続せずに非接続状態を維持する。
13 and 14,
(2) The MTC device 1A transmits data to the MTC server 2 at the transmission interval TP11 within the access time interval TP1.
(3) Then, after the communication with the MTC server 2 is completed in the middle of the access time interval TP1, in order to reduce power consumption in the remaining interval (= TP1-TP11) of the access time interval TP1, the idle mode is entered. Transition.
(4) On the other hand, when MTC device B needs to access MTC device 1A, it sends a data transmission request to MTC device 1A at paging reception time interval TP1-2 within access time interval TP1. .
(5) (6) On the other hand, when the MTC device 1A has received paging in the paging reception time interval TP1-2, the paging is recognized as paging from the MTC device 1B, and from the idle mode in the access time interval TP2. After returning, data transmission to the MTC device 1B is started (transmission interval P21). If paging is not received in the paging reception time interval TP1-2, the connection state is not connected to the network 4 in the access time interval TP2.
 <MTCデバイス1Aの構成及び処理>
 図15は、本発明の第3の実施の形態におけるMTCデバイス1Aの構成の一例を示すブロック図である。図15に図示されているMTCデバイス1Aは、インタフェース101と、設定情報取得部102と、ページング受信部108と、ネットワーク接続部104と、情報保持部105と接続時刻決定部106を有している。インタフェース101は、MTCデバイス1Aのインタフェースに直接関連する下位レイヤプロトコルモジュールを含んでいる。この下位レイヤプロトコルモジュールには、信号変調、エンコード圧縮、メディアアクセス制御、リンクレイヤ制御などのメカニズムを始めとする基本的なデータ通信に必要な機能、及び、物理層及びデータリンク層全体の機能が実装されている。
<Configuration and Processing of MTC Device 1A>
FIG. 15 is a block diagram showing an example of the configuration of the MTC device 1A according to the third embodiment of the present invention. The MTC device 1A illustrated in FIG. 15 includes an interface 101, a setting information acquisition unit 102, a paging reception unit 108, a network connection unit 104, an information holding unit 105, and a connection time determination unit 106. . The interface 101 includes lower layer protocol modules that are directly related to the interface of the MTC device 1A. This lower layer protocol module has functions necessary for basic data communication, including mechanisms such as signal modulation, encoding compression, media access control, link layer control, and functions of the entire physical layer and data link layer. Has been implemented.
 また、設定情報取得部102は、ネットワーク4へ接続している際にMME5から必要な設定情報を取得するための機能を有している。ここでは、アクセス時間間隔としてMME5によって割り当てられたアクセス時間間隔TP1(=ページング受信時間間隔TP1-1+TP1-2)とアクセス時間間隔TP2を取得する。なお、アクセス時間間隔TP1がすでに割り当てられている場合は、ページング受信時間間隔TP1-1、TP1-2及びアクセス時間間隔TP2のみ通知を受ければよい。取得方法としては、ネットワーク4側があらかじめこれらの時間間隔を割り当てる方法と、MTCデバイス1A、1Bからの要求を受けてネットワーク4側が割り当てる方法がある。前者の場合、MTCデバイス1A、1Bは、ネットワーク4への接続時や、MTCサーバ2へのアクセス時に、これらの時間間隔の割り当てを受ける。 The setting information acquisition unit 102 has a function for acquiring necessary setting information from the MME 5 when connected to the network 4. Here, the access time interval TP1 (= paging reception time interval TP1-1 + TP1-2) and the access time interval TP2 assigned by the MME 5 are acquired as the access time interval. If the access time interval TP1 is already assigned, only the paging reception time intervals TP1-1 and TP1-2 and the access time interval TP2 need be notified. As an acquisition method, there are a method in which the network 4 side allocates these time intervals in advance and a method in which the network 4 side allocates a request from the MTC devices 1A and 1B. In the former case, the MTC devices 1A and 1B are assigned these time intervals when connected to the network 4 and when accessing the MTC server 2.
 一方、後者の場合は、設定情報取得部102は、図16に示す(1)時間間隔の割り当てにおいて、
(11)MTCデバイス1Bとの通信が必要であることを認識した場合にMTCデバイス間通信要求をMME5へ送信し、MTCデバイス間通信用のアクセス時間間隔の割り当てを要求する。
(12)そして、MME5から取得したアクセス時間間隔TP1(=ページング受信時間間隔TP1-1+TP1-2)及びアクセス時間間隔TP2を情報保持部105へ保持するよう指示する。通知されたページング受信時間間隔には、対応するMTCデバイスに関する情報(MTCデバイスのIDやIPアドレス)が関連付けられており、情報保持部105には、ページング時間間隔と対応するMTCデバイスに関する情報が保持される。また、情報保持部105は、これらの時間間隔のほかにMTCサーバ2及びMME5から取得した情報や、接続時刻決定部106によって決定された次回接続時刻などを保持する機能を有している。
(13)また、MTCデバイス1Bは、MME5から取得したアクセス時間間隔TP1、TP2を情報保持部105へ保持するよう指示する。
 ここで、図16における手順(2)~(6)は、図13に示す手順(2)~(6)と同じであるので、その詳細な説明を省略する。
On the other hand, in the latter case, the setting information acquisition unit 102 performs (1) time interval allocation shown in FIG.
(11) When recognizing that communication with the MTC device 1B is necessary, a communication request between MTC devices is transmitted to the MME 5, and an allocation of an access time interval for communication between MTC devices is requested.
(12) Then, the information holding unit 105 is instructed to hold the access time interval TP1 (= paging reception time interval TP1-1 + TP1-2) and the access time interval TP2 acquired from the MME 5. The notified paging reception time interval is associated with information on the corresponding MTC device (ID or IP address of the MTC device), and the information holding unit 105 holds information on the MTC device corresponding to the paging time interval. Is done. In addition to these time intervals, the information holding unit 105 has a function of holding information acquired from the MTC server 2 and the MME 5, the next connection time determined by the connection time determination unit 106, and the like.
(13) In addition, the MTC device 1B instructs the information holding unit 105 to hold the access time intervals TP1 and TP2 acquired from the MME 5.
Here, procedures (2) to (6) in FIG. 16 are the same as procedures (2) to (6) shown in FIG.
 図15に戻り、ページング受信部108は、MME5から送信されたページングを受信した際に、受信したタイミングがページング受信時間間隔TP1-2内であった場合は、相手先MTCデバイス1Bからのアクセス要求に基づくページングであると判断し、情報保持部105に対して、相手先MTCデバイス1Bからデータ要求が送信されたことを示す情報を保持する。 Returning to FIG. 15, when the paging reception unit 108 receives the paging transmitted from the MME 5, if the received timing is within the paging reception time interval TP1-2, the access request from the counterpart MTC device 1B Therefore, the information holding unit 105 holds information indicating that the data request is transmitted from the counterpart MTC device 1B.
 また、接続時刻決定部106は、情報保持部105を参照し、データ送信などのためにMTCサーバ2や他のMTCデバイス1Bとの通信が必要であるか否かを確認し、必要がある場合はMTCデバイス1A自身が次回ネットワーク4へ接続する時刻(次回接続時刻)や切断するタイミングを決定する機能を有している。MTCサーバ2との通信を行う必要がある場合は、割り当てられているアクセス時間間隔TP1を確認し、アクセス時間間隔TP1内の任意のタイミングを接続時刻として決定する。そしてそのタイミングでネットワーク接続部104に対しネットワーク4へ接続するよう指示し、MTCサーバ2との通信を開始する。MTCサーバ2との通信が終了した後、まだアクセス時間間隔TP1の時間間隔内である場合は、アイドルモードへ遷移するようネットワーク接続部104へ指示する。 In addition, the connection time determination unit 106 refers to the information holding unit 105 and confirms whether communication with the MTC server 2 or another MTC device 1B is necessary for data transmission or the like. Has a function of determining the time when the MTC device 1A itself connects to the network 4 next time (next connection time) and the timing of disconnection. When it is necessary to communicate with the MTC server 2, the allocated access time interval TP1 is confirmed, and an arbitrary timing within the access time interval TP1 is determined as the connection time. At that timing, the network connection unit 104 is instructed to connect to the network 4, and communication with the MTC server 2 is started. After the communication with the MTC server 2 is completed, if it is still within the time interval of the access time interval TP1, the network connection unit 104 is instructed to shift to the idle mode.
 また、接続時刻決定部106は、情報保持部105を参照して、ページング受信時間間隔TP1-2においてページングを受けていることを確認した場合は、アクセス時間間隔TP2においてネットワーク4に接続し、相手先MTCデバイス1Bへデータの送信を行う必要があると判断する。図17は、本発明の第3の実施の形態において、アクセス時間間隔TP1(=ページング受信時間間隔TP1-1+TP1-2)とアクセス時間間隔TP2の割り当てを受けているMTCデバイス1Aが、アクセス時間間隔TP1が終了する際(ステップS11)に行う処理の一例を示すフローチャートである。 When the connection time determination unit 106 refers to the information holding unit 105 and confirms that paging is received at the paging reception time interval TP1-2, the connection time determination unit 106 connects to the network 4 at the access time interval TP2, and It is determined that it is necessary to transmit data to the destination MTC device 1B. FIG. 17 shows an example in which the MTC device 1A assigned the access time interval TP1 (= paging reception time interval TP1-1 + TP1-2) and the access time interval TP2 in the third embodiment of the present invention It is a flowchart which shows an example of the process performed when TP1 is complete | finished (step S11).
 図17において、接続時刻決定部106は、アクセス時間間隔TP1の終了時に情報保持部105を参照し、ページング受信時間間隔TP1-2内にページングを受信したかどうかを確認する(ステップS12a)。なかった場合(ステップS12aでNO)は、アクセス時間間隔TP2においてネットワーク4に接続する必要がないと判断し、アクセス時間間隔TP2ではネットワークに接続しない(ステップS13、S14)。あった場合(ステップS12aでYES)は、アクセス時間間隔TP2の任意のタイミングを接続時刻として決定し(ステップS15)、そのタイミングでネットワーク接続部104に対しネットワーク4へ接続するよう指示し、ページング受信時間間隔TP1-2に対応する相手先MTCデバイス1Bとの通信を開始する(ステップS16)。 In FIG. 17, the connection time determination unit 106 refers to the information holding unit 105 at the end of the access time interval TP1, and confirms whether or not paging has been received within the paging reception time interval TP1-2 (step S12a). If not (NO in step S12a), it is determined that it is not necessary to connect to the network 4 in the access time interval TP2, and the network is not connected in the access time interval TP2 (steps S13 and S14). If there is (YES in step S12a), an arbitrary timing of the access time interval TP2 is determined as a connection time (step S15), the network connection unit 104 is instructed to connect to the network 4 at that timing, and paging reception is performed. Communication with the counterpart MTC device 1B corresponding to the time interval TP1-2 is started (step S16).
 また、ネットワーク接続部104は、インタフェース101を用いて新たにネットワーク4に接続するための処理や、接続時刻決定部106によって決められた次回接続時刻にネットワーク4へ接続する際に行う接続処理を実行する機能を有している。また、接続時刻決定部106の指示により、ネットワーク4から切断するための処理や、アイドルモードへ遷移する処理を行う。 In addition, the network connection unit 104 executes processing for newly connecting to the network 4 using the interface 101 and connection processing performed when connecting to the network 4 at the next connection time determined by the connection time determination unit 106. It has a function to do. Further, according to an instruction from the connection time determination unit 106, processing for disconnecting from the network 4 and processing for transitioning to the idle mode are performed.
 <MTCデバイス1Bの構成及び処理>
 本発明の第3の実施の形態におけるMTCデバイス1Bの構成について、図8を用いて説明する。接続時刻決定部106は、MTCデバイス1B自身が次回ネットワーク4へ接続する時刻(次回接続時刻)を決定する機能を有している。アクセス時間間隔TP1の割り当てを受けている場合、MTCサーバ2との通信(例えば、データ送信)が必要な場合はアクセス時間間隔TP1内に行う。また、接続時刻決定部106は情報保持部105を参照して、相手先MTCデバイス1Aとの後述する通信がアクセス時間間隔TP2において行われることが確認された場合に、アクセス時間間隔TP2の開始時刻にネットワーク4に接続するようネットワーク接続部106へ指示する。
<Configuration and Processing of MTC Device 1B>
The configuration of the MTC device 1B according to the third embodiment of the present invention will be described with reference to FIG. The connection time determination unit 106 has a function of determining a time (next connection time) when the MTC device 1B itself connects to the network 4 next time. When the access time interval TP1 is assigned, if communication (for example, data transmission) with the MTC server 2 is required, the access time interval TP1 is performed within the access time interval TP1. In addition, the connection time determination unit 106 refers to the information holding unit 105, and when it is confirmed that communication described later with the counterpart MTC device 1A is performed in the access time interval TP2, the start time of the access time interval TP2 The network connection unit 106 is instructed to connect to the network 4.
 データ取得部108は、情報保持部105を参照して、相手先MTCデバイス1Aとの通信が必要であると判断される場合は、ページング受信時間間隔TP1-2において相手先MTCデバイス1A宛にデータ要求を送信する。また、送信したデータ要求に対する応答は受けないが、アクセス時間間隔TP2において相手先MTCデバイス1Aとの通信が行われることを示す情報を情報保持部105へ保持する。 If the data acquisition unit 108 refers to the information holding unit 105 and determines that communication with the counterpart MTC device 1A is necessary, the data acquisition unit 108 transmits data addressed to the counterpart MTC device 1A at the paging reception time interval TP1-2. Send a request. Further, although the response to the transmitted data request is not received, information indicating that communication with the counterpart MTC device 1A is performed in the access time interval TP2 is held in the information holding unit 105.
 なお、本発明の第3の実施の形態におけるMTCデバイス1Bが本発明の第2の実施の形態におけるMTCデバイス1Bのように、ページング受信時間間隔TP1-1、TP1-2を認識せずに、アクセス時間間隔TP1のみを認識している場合、MTCデバイス1B自身が送信したリクエストが、MTCサーバ2からのページング受信時間間隔TP1-1内にMTCデバイス1Aに届いてしまう可能性がある。この場合、MTCデバイス1Aは、MTCデバイスBからのリクエストによるページングを、MTCサーバ2からのリクエストによるページングであると誤認識してしまう。 Note that the MTC device 1B according to the third embodiment of the present invention does not recognize the paging reception time intervals TP1-1 and TP1-2 like the MTC device 1B according to the second embodiment of the present invention. When only the access time interval TP1 is recognized, the request transmitted by the MTC device 1B itself may reach the MTC device 1A within the paging reception time interval TP1-1 from the MTC server 2. In this case, the MTC device 1A misrecognizes paging by a request from the MTC device B as paging by a request from the MTC server 2.
 図18に示す(1)時間間隔の割り当てにおける手順(11)(12)(13)は、図4で説明した手順(11)(12)(13)と同じであり、
(11)MTCデバイス1Bは、MTCデバイスAと通信を行いたい場合、まずMME5(又はMTCサーバ2)に対して、MTCデバイス1Aと通信を行うことを示すMTCデバイス間通信要求を送信する。
(12)(13)MME5は、このMTCデバイス間通信要求を受けた場合、MTCデバイス1BによるMTCデバイス1Aへのアクセスが、MTCデバイス1AによるMTCサーバ2との通信に影響が及ぶことを防ぐために、アクセス時間間隔TP1及びTP2の両方をMTCデバイス1B及びMTCデバイス1Aへ割り当てる。
 また、図18における手順(2)~(6)は、図13に示す手順(2)~(6)と同じであるので、その詳細な説明を省略する。
The procedures (11), (12), and (13) in (1) time interval allocation shown in FIG. 18 are the same as the procedures (11), (12), and (13) described in FIG.
(11) When the MTC device 1B wants to communicate with the MTC device A, the MTC device 1B first transmits to the MME 5 (or the MTC server 2) an inter-MTC device communication request indicating communication with the MTC device 1A.
(12) (13) When the MME 5 receives the communication request between the MTC devices, the MME 5 prevents the access to the MTC device 1A by the MTC device 1B from affecting the communication with the MTC server 2 by the MTC device 1A. The access time intervals TP1 and TP2 are both assigned to the MTC device 1B and the MTC device 1A.
In addition, procedures (2) to (6) in FIG. 18 are the same as procedures (2) to (6) shown in FIG.
 そこで、MTCデバイス1A-1B間のデータ送信のためのリクエストメッセージは、MTCサーバ2を介して転送するようにすることでこの問題を解決することができる。MTCデバイス1Bがアクセス時間間隔TP1内でMTCデバイス1Aに対するリクエストメッセージをMTCサーバ2宛に送信したとする。そしてそのリクエストメッセージをMTCサーバ2がページング受信時間間隔TP1-1内で受信した場合、そのリクエストメッセージをMTCデバイス1Aに直ぐに転送するのではなく、MTCデバイスからのページング受信時間間隔TP1-2の範囲内になってからMTCデバイス1Aへ転送する。これにより、MTCデバイス1Aは、MTCデバイス1Bからのリクエストメッセージによるページングをページング受信時間間隔TP1-2の範囲内で確実に受信することができる。 Therefore, this problem can be solved by transferring the request message for data transmission between the MTC devices 1A and 1B via the MTC server 2. Assume that the MTC device 1B transmits a request message for the MTC device 1A to the MTC server 2 within the access time interval TP1. When the MTC server 2 receives the request message within the paging reception time interval TP1-1, the request message is not immediately transferred to the MTC device 1A, but the range of the paging reception time interval TP1-2 from the MTC device. Then, the data is transferred to the MTC device 1A. Thereby, the MTC device 1A can reliably receive the paging by the request message from the MTC device 1B within the range of the paging reception time interval TP1-2.
 以上、説明したように、本発明の第3の実施の形態によれば、MTCデバイス1BがMTCデバイス1Aへデータ要求する場合は、ページングを受けたタイミングに基づいて送信元を特定することができるため、MTCデバイス1Aが、MTCサーバ2との通信が終了した後すぐにアイドルモードへ遷移することができ、消費電力を抑えることが可能となる。 As described above, according to the third embodiment of the present invention, when the MTC device 1B makes a data request to the MTC device 1A, the transmission source can be specified based on the timing of receiving the paging. Therefore, the MTC device 1A can make a transition to the idle mode immediately after the communication with the MTC server 2 is completed, and the power consumption can be suppressed.
 なお、上記実施の形態の説明に用いた各機能ブロックは、典型的には集積回路であるLSIとして実現される。これらは個別に1チップ化されてもよいし、一部又はすべてを含むように1チップ化されてもよい。ここでは、LSIとしたが、集積度の違いにより、IC、システムLSI、スーパーLSI、ウルトラLSIと呼称されることもある。また、集積回路化の手法はLSIに限るものではなく、専用回路又は汎用プロセッサで実現してもよい。LSI製造後に、プログラムすることが可能なFPGA(Field Programmable Gate Array)や、LSI内部の回路セルの接続や設定を再構成可能なリコンフィギュラブ ル・プロセッサーを利用してもよい。さらには、半導体技術の進歩又は派生する別技術によりLSIに置き換わる集積回路化の技術が登場すれば、当然、その技術を用いて機能ブロックの集積化を行ってもよい。例えば、バイオ技術の適用などが可能性としてあり得る。 Each functional block used in the description of the above embodiment is typically realized as an LSI that is an integrated circuit. These may be individually made into one chip, or may be made into one chip so as to include a part or all of them. Although referred to as LSI here, it may be referred to as IC, system LSI, super LSI, or ultra LSI depending on the degree of integration. Further, the method of circuit integration is not limited to LSI's, and implementation using dedicated circuitry or general purpose processors is also possible. An FPGA (Field Programmable Gate Array) that can be programmed after manufacturing the LSI, or a reconfigurable processor that can reconfigure the connection and setting of circuit cells inside the LSI may be used. Further, if integrated circuit technology comes out to replace LSI's as a result of the advancement of semiconductor technology or a derivative other technology, it is naturally also possible to carry out function block integration using this technology. For example, biotechnology can be applied.
 本発明は、無線網を介して複数の通信デバイスからデータ収集サーバに対してデータを送信するとともに各通信デバイスの間でデータを通信する場合に、輻輳及びパケットロスを低減するという効果を有し、3GPP(3rd Generation Partnership Project)のMTC(Machine Type Communication)に利用することができる。 The present invention has an effect of reducing congestion and packet loss when data is transmitted from a plurality of communication devices to a data collection server via a wireless network and data is communicated between the communication devices. It can be used for 3GPP (3rd Generation Partnership Project) MTC (Machine Type Communication).

Claims (19)

  1.  無線網を介して複数の通信デバイスからデータ収集サーバに対してデータを送信するとともに各通信デバイスの間でデータを通信する通信方法であって、
     前記複数の通信デバイスを管理する管理ノードから前記複数の通信デバイスに対して、前記複数の通信デバイスから各データを前記データ収集サーバに送信するための第1のアクセス時間間隔と、前記複数の通信デバイス間で各データを送受信するための第2のアクセス時間間隔を割り当てる割り当てステップと、
     前記割り当てられた第1のアクセス時間間隔において前記複数の通信デバイスが前記データ収集サーバに各データを送信するステップと、
     前記割り当てられた第2のアクセス時間間隔において前記複数の通信デバイス間で各データを送受信するステップとを、
     有する通信方法。
    A communication method for transmitting data from a plurality of communication devices to a data collection server via a wireless network and communicating data between the communication devices,
    A first access time interval for transmitting each data from the plurality of communication devices to the data collection server from a management node that manages the plurality of communication devices to the plurality of communication devices, and the plurality of communication Assigning a second access time interval for transmitting and receiving each piece of data between devices;
    The plurality of communication devices transmitting each piece of data to the data collection server in the assigned first access time interval;
    Transmitting and receiving data between the plurality of communication devices in the allocated second access time interval; and
    Communication method having.
  2.  前記割り当てステップは、前記管理ノードが、前記複数の通信デバイスから、前記複数の通信デバイス間で各データを送受信する要求があった場合に、前記第1及び第2のアクセス時間間隔を動的に前記複数の通信デバイスに割り当てることを特徴とする請求項1に記載の通信方法。 The assigning step dynamically sets the first and second access time intervals when there is a request from the plurality of communication devices to transmit / receive each data between the plurality of communication devices. 2. The communication method according to claim 1, wherein the communication method is assigned to the plurality of communication devices.
  3.  前記割り当てステップは、前記第1のアクセス時間間隔より前記第2のアクセス時間間隔が先になるように割り当てることを特徴とする請求項1又は2に記載の通信方法。 3. The communication method according to claim 1, wherein the assigning step assigns the second access time interval ahead of the first access time interval.
  4.  データ要求元の前記通信デバイスがデータ送信元の前記通信デバイスに対するデータ送信要求を前記第1のアクセス時間間隔において送信し、
     前記データ送信元の通信デバイスがデータを前記データ要求元の通信デバイスに対して前記第2のアクセス時間間隔において送信することを特徴とする請求項1又は2に記載の通信方法。
    The communication device of the data request source transmits a data transmission request to the communication device of the data transmission source in the first access time interval;
    The communication method according to claim 1, wherein the data transmission source communication device transmits data to the data request source communication device in the second access time interval.
  5.  前記割り当てステップは、前記管理ノードが前記第1のアクセス時間間隔を、前記管理ノードがデータ送信元の前記通信デバイスを呼び出すための第1のページング時間間隔と、データ要求元の前記通信デバイスがデータ送信元の前記通信デバイスを呼び出すための第2のページング時間間隔に分割して前記複数の通信デバイスに割り当て、
     前記データ収集サーバにデータを送信する前記通信デバイスが、前記第1のアクセス時間間隔内の途中で前記データ送信を終了した場合に前記第1のアクセス時間間隔内の残りの時間間隔でアイドルモードに遷移するとともに、前記第2のページング時間間隔において前記データ要求元の通信デバイスからデータ要求を受信した場合に、前記第2のアクセス時間間隔において前記アイドルモードから復帰してデータを前記データ要求元の通信デバイスにデータを送信することを特徴とする請求項1に記載の通信方法。
    In the allocation step, the management node sets the first access time interval, the management node calls the communication device that is the data transmission source, and the communication device that is the data request source transmits the data. Dividing into a second paging time interval for calling the communication device of the transmission source and assigning to the plurality of communication devices;
    When the communication device that transmits data to the data collection server ends the data transmission in the middle of the first access time interval, the communication device enters the idle mode in the remaining time interval within the first access time interval. And when the data request is received from the data requesting communication device in the second paging time interval, the data request source data is returned from the idle mode in the second access time interval. The communication method according to claim 1, wherein data is transmitted to the communication device.
  6.  無線網を介して複数の通信デバイスからデータ収集サーバに対してデータを送信するとともに各通信デバイスの間でデータを通信する通信システムであって、
     前記複数の通信デバイスを管理する管理ノードから前記複数の通信デバイスに対して、前記複数の通信デバイスから各データを前記データ収集サーバに送信するための第1のアクセス時間間隔と、前記複数の通信デバイス間で各データを送受信するための第2のアクセス時間間隔を割り当てる割り当て手段と、
     前記割り当てられた第1のアクセス時間間隔において前記複数の通信デバイスが前記データ収集サーバに各データを送信する手段と、
     前記割り当てられた第2のアクセス時間間隔において前記複数の通信デバイス間で各データを送受信する手段とを、
     有する通信システム。
    A communication system for transmitting data to a data collection server from a plurality of communication devices via a wireless network and communicating data between the communication devices,
    A first access time interval for transmitting each data from the plurality of communication devices to the data collection server from a management node that manages the plurality of communication devices to the plurality of communication devices, and the plurality of communication Allocating means for allocating a second access time interval for transmitting and receiving each data between devices;
    Means for the plurality of communication devices to transmit each data to the data collection server in the assigned first access time interval;
    Means for transmitting and receiving data between the plurality of communication devices in the allocated second access time interval;
    Communication system having.
  7.  前記割り当て手段は、前記管理ノードが、前記複数の通信デバイスから、前記複数の通信デバイス間で各データを送受信する要求があった場合に、前記第1及び第2のアクセス時間間隔を動的に前記複数の通信デバイスに割り当てることを特徴とする請求項6に記載の通信システム。 The allocating unit dynamically sets the first and second access time intervals when the management node makes a request to transmit / receive data between the plurality of communication devices from the plurality of communication devices. The communication system according to claim 6, wherein the communication system is assigned to the plurality of communication devices.
  8.  前記割り当て手段は、前記第1のアクセス時間間隔より前記第2のアクセス時間間隔が先になるように割り当てることを特徴とする請求項6又は7に記載の通信システム。 The communication system according to claim 6 or 7, wherein the assigning means assigns the second access time interval before the first access time interval.
  9.  データ要求元の前記通信デバイスがデータ送信元の前記通信デバイスに対するデータ送信要求を前記第1のアクセス時間間隔において送信し、
     前記データ送信元の通信デバイスがデータを前記データ要求元の通信デバイスに対して前記第2のアクセス時間間隔において送信することを特徴とする請求項6又は7に記載の通信システム。
    The communication device of the data request source transmits a data transmission request to the communication device of the data transmission source in the first access time interval;
    The communication system according to claim 6 or 7, wherein the data transmission source communication device transmits data to the data request source communication device in the second access time interval.
  10.  前記割り当て手段は、前記管理ノードが前記第1のアクセス時間間隔を、前記管理ノードがデータ送信元の前記通信デバイスを呼び出すための第1のページング時間間隔と、データ要求元の前記通信デバイスがデータ送信元の前記通信デバイスを呼び出すための第2のページング時間間隔に分割して前記複数の通信デバイスに割り当て、
     前記データ収集サーバにデータを送信する前記通信デバイスが、前記第1のアクセス時間間隔内の途中で前記データ送信を終了した場合に前記第1のアクセス時間間隔内の残りの時間間隔でアイドルモードに遷移するとともに、前記第2のページング時間間隔において前記データ要求元の通信デバイスからデータ要求を受信した場合に、前記第2のアクセス時間間隔において前記アイドルモードから復帰してデータを前記データ要求元の通信デバイスにデータを送信することを特徴とする請求項6に記載の通信システム。
    The assigning means includes: a first access time interval for the management node; a first paging time interval for the management node to call the communication device that is a data transmission source; Dividing into a second paging time interval for calling the communication device of the transmission source and assigning to the plurality of communication devices;
    When the communication device that transmits data to the data collection server ends the data transmission in the middle of the first access time interval, the communication device enters the idle mode in the remaining time interval within the first access time interval. And when the data request is received from the data requesting communication device in the second paging time interval, the data request source data is returned from the idle mode in the second access time interval. The communication system according to claim 6, wherein data is transmitted to the communication device.
  11.  無線網を介して複数の通信デバイスからデータ収集サーバに対してデータを送信するとともに各通信デバイスの間でデータを通信する通信システムにおける前記通信デバイスであって、
     前記複数の通信デバイスを管理する管理ノードから前記複数の通信デバイスに対して、前記複数の通信デバイスから各データを前記データ収集サーバに送信するための第1のアクセス時間間隔と、前記複数の通信デバイス間で各データを送受信するための第2のアクセス時間間隔を割り当てられた場合にその割り当てを受け付ける手段と、
     前記割り当てられた第1のアクセス時間間隔において前記データ収集サーバに各データを送信する手段と、
     前記割り当てられた第2のアクセス時間間隔において他の前記通信デバイス間で各データを送受信する手段とを、
     有する通信デバイス。
    The communication device in a communication system that transmits data to a data collection server from a plurality of communication devices via a wireless network and communicates data between the communication devices,
    A first access time interval for transmitting each data from the plurality of communication devices to the data collection server from a management node that manages the plurality of communication devices to the plurality of communication devices, and the plurality of communication Means for accepting assignment when a second access time interval for transmitting and receiving data between devices is assigned;
    Means for transmitting each data to the data collection server in the assigned first access time interval;
    Means for transmitting and receiving data between the other communication devices in the allocated second access time interval;
    Having a communication device.
  12.  前記管理ノードに対して、前記複数の通信デバイス間で各データを送受信する要求を送信する手段と、
     前記要求に応答して前記管理ノードにより前記第1及び第2のアクセス時間間隔が動的に割り当てられた場合にその割り当てを受け付ける手段とを、
     さらに有することを特徴とする請求項11に記載の通信デバイス。
    Means for transmitting a request to transmit / receive each data among the plurality of communication devices to the management node;
    Means for accepting the assignment when the first and second access time intervals are dynamically assigned by the management node in response to the request;
    The communication device according to claim 11, further comprising:
  13.  前記第1のアクセス時間間隔より前記第2のアクセス時間間隔が先になるように割り当てられている場合、前記先に割り当てられた第2のアクセス時間間隔において他の前記通信デバイスにデータを送信した後、前記後に割り当てられた第1のアクセス時間間隔において前記サーバにデータを送信する必要があるか否かを判断して不要な場合に送信しないことを特徴とする請求項11又は12に記載の通信デバイス。 When the second access time interval is assigned to be earlier than the first access time interval, data is transmitted to the other communication device in the second access time interval assigned earlier. 13. The method according to claim 11, further comprising determining whether or not it is necessary to transmit data to the server in the first access time interval assigned later and not transmitting the data when it is unnecessary. Communication device.
  14.  データ要求元の前記通信デバイスである場合に、データ送信元の前記通信デバイスに対するデータ要求を前記第1のアクセス時間間隔において送信し、
     前記データ送信元の通信デバイスである場合に、データを前記データ要求元の通信デバイスに対して前記第2のアクセス時間間隔において送信することを特徴とする請求項11又は12に記載の通信デバイス。
    When the communication device is a data requesting source, a data request for the communication device of a data transmission source is transmitted in the first access time interval,
    13. The communication device according to claim 11, wherein when the communication device is the data transmission source communication device, data is transmitted to the data request source communication device in the second access time interval.
  15.  前記管理ノードが前記第1のアクセス時間間隔を、前記管理ノードがデータ送信元の前記通信デバイスを呼び出すための第1のページング時間間隔と、データ要求元の前記通信デバイスがデータ送信元の前記通信デバイスを呼び出すための第2のページング時間間隔に分割して前記複数の通信デバイスに割り当てた場合にその割り当てを受け付け、
     前記データ収集サーバにデータを送信する前記通信デバイスである場合に、前記第1のアクセス時間間隔内の途中で前記データ送信を終了したときに前記第1のアクセス時間間隔内の残りの時間間隔でアイドルモードに遷移し、前記第2のページング時間間隔においてデータ送信要求元の前記通信デバイスからデータ要求を受信したときに、前記第2のアクセス時間間隔において前記アイドルモードから復帰してデータを前記データ送信要求元の通信デバイスにデータを送信することを特徴とする請求項11に記載の通信デバイス。
    The management node uses the first access time interval, the management node calls the communication device that is the data transmission source, the first paging time interval, and the communication device that is the data request source uses the communication that is the data transmission source. Accepting the assignment when assigned to the plurality of communication devices divided into second paging time intervals for calling the device;
    In the case of the communication device that transmits data to the data collection server, when the data transmission is terminated in the middle of the first access time interval, the remaining time interval within the first access time interval. When transitioning to the idle mode and receiving a data request from the communication device that is a data transmission request source in the second paging time interval, the data is returned from the idle mode in the second access time interval and data is transferred to the data The communication device according to claim 11, wherein the communication device transmits data to a communication device that is a transmission request source.
  16.  無線網を介して複数の通信デバイスからデータ収集サーバに対してデータを送信するとともに各通信デバイスの間でデータを通信する通信システムにおいて前記複数の通信デバイスを管理する管理ノードであって、
     前記複数の通信デバイスに対して、前記複数の通信デバイスから各データを前記データ収集サーバに送信するための第1のアクセス時間間隔と、前記複数の通信デバイス間で各データを送受信するための第2のアクセス時間間隔を割り当てる割り当て手段を、
     有する管理ノード。
    A management node for managing the plurality of communication devices in a communication system for transmitting data from a plurality of communication devices to a data collection server via a wireless network and communicating data between the communication devices;
    A first access time interval for transmitting each piece of data from the plurality of communication devices to the data collection server and a first number for transmitting / receiving each piece of data between the plurality of communication devices to the plurality of communication devices. Assigning means for assigning two access time intervals,
    Management node that has.
  17.  前記割り当て手段は、前記複数の通信デバイスから、前記複数の通信デバイス間で各データを送受信する要求があった場合に、前記第1及び第2のアクセス時間間隔を動的に前記複数の通信デバイスに割り当てることを特徴とする請求項16に記載の管理ノード。 The assigning means dynamically assigns the first and second access time intervals when there is a request from the plurality of communication devices to transmit / receive data between the plurality of communication devices. The management node according to claim 16, wherein the management node is assigned to the management node.
  18.  前記割り当て手段は、前記第1のアクセス時間間隔より前記第2のアクセス時間間隔が先になるように割り当てることを特徴とする請求項16又は17に記載の管理ノード。 The management node according to claim 16 or 17, wherein the assigning means assigns the second access time interval before the first access time interval.
  19.  前記割り当て手段は、前記第1のアクセス時間間隔を、前記管理ノードがデータ送信元の前記通信デバイスを呼び出すための第1のページング時間間隔と、データ要求元の前記通信デバイスがデータ送信元の前記通信デバイスを呼び出すための第2のページング時間間隔に分割して前記複数の通信デバイスに割り当てることを特徴とする請求項16又は17に記載の管理ノード。 The assigning means includes the first access time interval, a first paging time interval for the management node to call the communication device that is a data transmission source, and the communication device that is a data request source is the data transmission source. The management node according to claim 16 or 17, wherein the management node is divided into second paging time intervals for calling a communication device and assigned to the plurality of communication devices.
PCT/JP2011/002229 2010-04-27 2011-04-15 Communication method, communication system, communication device, and management node WO2011135794A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2010-102730 2010-04-27
JP2010102730 2010-04-27

Publications (1)

Publication Number Publication Date
WO2011135794A1 true WO2011135794A1 (en) 2011-11-03

Family

ID=44861121

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2011/002229 WO2011135794A1 (en) 2010-04-27 2011-04-15 Communication method, communication system, communication device, and management node

Country Status (1)

Country Link
WO (1) WO2011135794A1 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014087720A1 (en) * 2012-12-05 2014-06-12 ソニー株式会社 Communication control device, communication control method, terminal, and program
WO2015019465A1 (en) * 2013-08-08 2015-02-12 富士通株式会社 Radio communication system, radio communication method, and radio station
CN109525506A (en) * 2018-12-13 2019-03-26 南京天溯自动化控制系统有限公司 Dynamic data sending method based on data volume

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009051829A1 (en) * 2007-10-19 2009-04-23 Smith Medical Pm, Inc. Wireless telecommunications network adaptable for patient monitoring
JP2010028636A (en) * 2008-07-23 2010-02-04 Fujitsu Ltd Base station, mobile station, and method for controlling communication

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009051829A1 (en) * 2007-10-19 2009-04-23 Smith Medical Pm, Inc. Wireless telecommunications network adaptable for patient monitoring
JP2010028636A (en) * 2008-07-23 2010-02-04 Fujitsu Ltd Base station, mobile station, and method for controlling communication

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014087720A1 (en) * 2012-12-05 2014-06-12 ソニー株式会社 Communication control device, communication control method, terminal, and program
CN104798424A (en) * 2012-12-05 2015-07-22 索尼公司 Communication control device, communication control method, terminal, and program
JPWO2014087720A1 (en) * 2012-12-05 2017-01-05 ソニー株式会社 COMMUNICATION CONTROL DEVICE, COMMUNICATION CONTROL METHOD, TERMINAL DEVICE, AND PROGRAM
US9661613B2 (en) 2012-12-05 2017-05-23 Sony Corporation Communication control device, communication control method, terminal device, and program
CN104798424B (en) * 2012-12-05 2018-11-13 索尼公司 Communication control unit, communication control method, terminal installation
US10278221B2 (en) 2012-12-05 2019-04-30 Sony Corporation Communication control device, communication control method, terminal device, and program
WO2015019465A1 (en) * 2013-08-08 2015-02-12 富士通株式会社 Radio communication system, radio communication method, and radio station
KR20160030962A (en) * 2013-08-08 2016-03-21 후지쯔 가부시끼가이샤 Radio communication system, radio communication method, and radio station
JPWO2015019465A1 (en) * 2013-08-08 2017-03-02 富士通株式会社 Wireless communication system, wireless communication method, and wireless station
KR101715579B1 (en) 2013-08-08 2017-03-13 후지쯔 가부시끼가이샤 Wireless communication system, method for wireless communication, and wireless station
US10419909B2 (en) 2013-08-08 2019-09-17 Fujitsu Connected Technologies Limited Wireless communication system, method for wireless communication, and wireless station
CN109525506A (en) * 2018-12-13 2019-03-26 南京天溯自动化控制系统有限公司 Dynamic data sending method based on data volume

Similar Documents

Publication Publication Date Title
US11871295B2 (en) Registration management method for terminal accessing 5G network on non-3GPP access
JP7013498B2 (en) Data scheduling methods, base stations and systems
CN114189815B (en) Method and apparatus for terminal communication in mobile communication system
US8243615B2 (en) Allocation of user equipment identifier
CN107534987B (en) Data scheduling method, base station and system
US20150111574A1 (en) Relay device, wireless terminal device, communication system and communication method
JP6730447B2 (en) Data transmission method, apparatus and session management device
KR20180012325A (en) MTC service management using NFV
WO2015018232A1 (en) Device-to-device connection management method and apparatus, and base station
CN113873478A (en) Communication method and device
CN108781402A (en) Special core net emigration processing method, equipment and system
CN105490713A (en) Bluetooth connection method, Bluetooth device and system
WO2011135794A1 (en) Communication method, communication system, communication device, and management node
JP5181845B2 (en) Wireless communication system, arbitration device, and arbitration method
CN114286397B (en) Transmission link switching method and related products
WO2024094160A1 (en) Link configuration method, communication apparatus, and storage medium
JP2008079087A (en) Communication server, communication system, and communication method
JP6645677B2 (en) Link establishment method and device
CN117014900A (en) Communication method and communication device
JP2020171052A (en) Relay transmission method and device
JP2013239837A (en) Network node and server
KR20030062018A (en) Method for transmitting wireless data in a mobile communication system
JP2018023156A (en) Base station and control method thereof

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11774583

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11774583

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP