WO2014184834A1 - 制御装置、通信システム、通信装置、通信方法及びプログラムが格納された非一時的なコンピュータ可読媒体 - Google Patents
制御装置、通信システム、通信装置、通信方法及びプログラムが格納された非一時的なコンピュータ可読媒体 Download PDFInfo
- Publication number
- WO2014184834A1 WO2014184834A1 PCT/JP2013/007609 JP2013007609W WO2014184834A1 WO 2014184834 A1 WO2014184834 A1 WO 2014184834A1 JP 2013007609 W JP2013007609 W JP 2013007609W WO 2014184834 A1 WO2014184834 A1 WO 2014184834A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- communication
- network
- request message
- connection
- connection request
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/18—Management of setup rejection or failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/53—Allocation or scheduling criteria for wireless resources based on regulatory allocation policies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
- H04W84/22—Self-organising networks, e.g. ad-hoc networks or sensor networks with access to wired networks
Definitions
- the present invention relates to a control device, a communication system, a communication device, a communication method, and a program, for example, a control process for controlling connection timing when the communication device is connected to a network.
- communication terminals such as personal computers, mobile phones, smartphones and the like have been diversified, and users holding a plurality of communication terminals are generally using a plurality of communication terminals depending on usage.
- the user needs to contract a communication line for each communication terminal.
- a user who owns a mobile phone and a smartphone needs to make a contract for using a communication line with a communication carrier for each communication terminal. Therefore, as the number of owned communication terminals increases, the burden of communication line contract charges mainly increases.
- M2M (Machine-to-Machine) communication becomes widespread in the future, the number of M2M devices managed by one company or group increases, and the burden on the communication line contract fee required for each managed M2M device also increases.
- Non-Patent Document 1 defined by 3GPP, which is a standardization organization related to mobile communication networks, discloses a network configuration for performing communication using an MTC (Machine Type Communication) device in a mobile communication network.
- the MTC device corresponds to an M2M device.
- An object of the present invention is to provide a control device, a communication system, a communication device, a communication method, and a program capable of efficiently and fairly allocating communication opportunities in order to solve the above-described problems.
- a control device includes: a monitoring unit that monitors a connection state to a network by a plurality of communication devices in which simultaneous communication is restricted; and a first communication device included in the plurality of communication devices. Determination of whether or not the first communication device is connectable to the network according to a connection status of the plurality of communication devices to the network when receiving a connection request message for requesting connection to the network And when the determination unit determines that the first communication device cannot be connected to the network, together with a determination result indicating that connection to the first communication device is impossible, And a communication unit for notifying the transmission timing of the connection request message.
- the communication system includes a plurality of communication devices for which simultaneous communication is restricted, and a connection status to the network by the plurality of communication devices, and is included in the first plurality of communication devices. Whether or not the first communication device can connect to the network according to the connection status of the plurality of communication devices to the network when a connection request message requesting connection to the network is received from the communication device And when it is determined that the connection of the first communication device to the network is impossible, the next connection request message is sent together with a determination result indicating that the connection to the first communication device is impossible. And a control device for notifying the transmission timing.
- a communication device is a communication device that is restricted from simultaneous communication with a plurality of other communication devices, and transmits a connection request message for requesting connection to a network; When it is determined in the control device arranged in the network that connection to the network is impossible according to the connection status of the other communication devices to the network, the next notified from the control device And an adjustment unit that performs reconnection processing to the network according to the transmission timing of the connection request message.
- a communication method for monitoring a connection state to a network by a plurality of communication devices to which simultaneous communication is restricted from the first communication device included in the plurality of communication devices to the network.
- the connection request message for requesting the connection is received, it is determined whether the first communication device can be connected to the network according to the connection status of the plurality of communication devices to the network, and the first communication device
- the transmission timing of the next connection request message is notified to the first communication device together with a determination result indicating that the connection is impossible. It is.
- a program includes a step of monitoring a connection status to a network by a plurality of communication devices to which simultaneous communication is restricted, and from the first communication device included in the plurality of communication devices to the network. Determining whether or not the first communication device can be connected to the network according to a connection status of the plurality of communication devices to the network when receiving a connection request message requesting connection to the network; When it is determined that the connection of the first communication device to the network is impossible, the transmission timing of the next connection request message is sent to the first communication device together with a determination result indicating that the connection is impossible. And a step of notifying the computer.
- control device it is possible to provide a control device, a communication system, a communication device, a communication method, and a program that can allocate communication opportunities efficiently and fairly.
- FIG. 1 is a configuration diagram of a control device according to a first embodiment
- FIG. 3 is a configuration diagram of a communication system according to a second exemplary embodiment.
- FIG. 3 is a configuration diagram of an M2M device according to a second exemplary embodiment. It is a figure which shows the flow of a connection process of the M2M device concerning Embodiment 2.
- FIG. It is a figure which shows the flow of a connection process of the M2M device concerning Embodiment 2.
- FIG. 10 is a diagram showing a flow of connection processing of an M2M device according to the third exemplary embodiment. It is a figure which shows the flow of a connection process of the M2M device concerning Embodiment 4.
- FIG. 10 is a diagram illustrating a flow of connection processing of an M2M device according to a fifth exemplary embodiment.
- FIG. 10 is a diagram illustrating a flow of connection processing of an M2M device according to a fifth exemplary embodiment. It is a figure which shows the flow of a communication process with the neighboring M2M device performed when the M2M device concerning Embodiment 6 starts.
- FIG. 10 is a diagram illustrating a flow of communication timing acquisition processing according to the sixth embodiment;
- the control device 10 in FIG. 1 includes a monitoring unit 20, a determination unit 30, and a communication unit 40.
- the control device 10 is an information processing device such as a server device.
- the control device 10 communicates with a communication device via a network, for example.
- the communication device may be, for example, a mobile phone terminal, a smartphone, a tablet terminal, a personal computer, an M2M device, or the like.
- the monitoring unit 20 monitors the connection status to the network by a plurality of communication devices for which simultaneous communication is restricted.
- the plurality of communication devices for which simultaneous communication is restricted are, for example, communication devices that can communicate by sharing one line contract, and the number of communication apparatuses that can simultaneously perform communication in one line contract is predetermined. It is a defined communication device.
- the number of communication devices that can simultaneously communicate in one line contract may be one or more than one.
- the plurality of communication devices that are restricted from simultaneous communication may be referred to as a plurality of communication devices that perform non-simultaneous communication.
- a set of a plurality of communication devices for which simultaneous communication is restricted may be referred to as a non-simultaneous communication group.
- the situation where the communication device is connected to the network is a situation where the communication device is permitted to communicate via the network.
- the determination unit 30 receives a connection request message for requesting connection to a network transmitted from a communication device included in a plurality of communication devices.
- the determination unit 30 determines whether or not the communication device that has transmitted the connection request message can be connected to the network according to the connection status of the plurality of communication devices to the network. For example, when more than a predetermined number of communication devices are already connected to the network, the determination unit 30 rejects the connection of the communication device that has transmitted the connection request message to the network.
- the determination unit 30 determines the network of the communication device that has transmitted the connection request message when less than a predetermined number of communication devices are already connected to the network, or when no communication device is connected to the network. Allow connection to.
- the communication device may transmit a connection request message to the network when, for example, power is turned on.
- the communication device may transmit a connection request message to the network when communication is resumed in a state where the communication device is disconnected from the network by not performing communication for a certain period of time.
- the communication unit 40 determines that the connection to the communication device that transmitted the connection request message is impossible. At the same time, a transmission timing for transmitting the connection request message is notified.
- the communication unit 40 may include the determination result and the transmission timing in the same message and transmit them to the communication device, or may transmit to the communication device using different messages.
- the transmission timing may be determined by the determination unit 30 or may be determined by the communication unit 40.
- the determination unit 30 or the communication unit 40 performs control so that a plurality of communication devices are not connected to the network at the same time. For example, the determination unit 30 or the communication unit 40 considers the timing at which the communication device currently connected to the network leaves the network, and the communication device that has determined that connection is not possible then transmits a connection request message. Determine timing.
- the determination unit 30 calculates the network disconnection timing of the currently connected communication device as needed and disconnects from the communication device via the communication unit 40 when triggered by a request for connection of a new communication device to the network. Notify timing. The calculation of the separation timing may be performed in the communication unit 40.
- control device 10 of FIG. 1 it is possible to determine whether or not a communication device that requests connection to a network can be connected according to the connection status of the other communication device to the network. Thereby, non-simultaneous communication in a plurality of communication devices can be realized.
- the control device 10 notifies the communication device of the transmission timing of the next connection request message, thereby controlling the connection schedule to the network between the plurality of communication devices. I can do it.
- the control device arranged in the network schedules a network between a plurality of communication devices, the connection status of other communication devices to the network or the number of communication devices requesting connection to the network is considered. I can do it. As a result, communication opportunities can be efficiently and fairly given to a plurality of communication devices.
- a 3G core network will be described as a network to which a communication device is connected.
- the 3G core network is a network defined in 3GPP, and is a mobile network managed by a mobile communication carrier or the like.
- an M2M device 80 will be described as an example of a communication apparatus.
- the M2M device may be referred to as UE (User Equipment).
- UE is a general term for mobile communication terminals defined in 3GPP.
- a 3G core network is used for explanation.
- the network in which the control device 10 is arranged is not limited to the 3G core network, and may be a network managed by a fixed carrier, for example.
- a mobile network managed by a mobile carrier may be a mobile network different from the 3G core network.
- the 3G core network includes a control device 10, an eNodeB 50, an MME (Mobility Management Entity) 60, and an HSS (Home Subscriber Server) 70.
- the eNodeB 50 is a base station used in LTE (Long Term Evolution), which is a radio network defined in 3GPP.
- LTE Long Term Evolution
- the eNodeB 50 communicates with the M2M device 80 via a wireless line.
- the eNodeB 50 is connected to the MME 60 in the 3G core network.
- the MME 60 performs movement management of the M2M device 80.
- the MME 60 manages the location registration area where the M2M device 80 is located, and calls the M2M device 80 when an incoming packet to the M2M device 80 occurs.
- the location registration area may be referred to as TA (Tracking Area), for example.
- the MME 60 transmits and receives control information within the 3G core network.
- the control information is data used to secure call resources of the M2M device 80 or communication resources for the M2M device 80, and is also referred to as C (Control) plane data.
- the communication resource is, for example, a buffer capacity or a memory capacity used for communication of the M2M device 80.
- data transmitted and received between communication devices such as audio data and image data is also referred to as user data or U (User) plane data.
- the MME 60 is connected to the eNodeB 50 and the HSS 70 in the 3G core network.
- the HSS 70 manages subscriber information of the M2M device 80.
- the subscriber information of the M2M device 80 includes identification information of the M2M device 80, information of services to which the M2M device 80 is subscribed, non-simultaneous communication group identifier that is information of the non-simultaneous communication group to which each M2M device 80 belongs, etc. It is.
- the HSS 70 may perform an authentication process using the subscriber information of the M2M device 80 when the M2M device 80 connects to the 3G core network.
- the HSS 70 is connected to the MME 60 and the control device 10 in the 3G core network.
- the control device 10 has already been connected to the 3G core network by another communication device belonging to the non-simultaneous communication group. Whether or not the M2M device 80 can be connected to the 3G core network is determined according to whether or not it is. Furthermore, the control apparatus 10 adjusts the connection timing with respect to the 3G core network between the communication apparatuses which belong to a non-simultaneous communication group.
- control device 10 has been described as a device different from the MME 60 or HSS 70, but the functions of the control device 10 may be mounted on the MME 60 or HSS 70. Further, some functions of the control device 10 such as the monitoring unit 20, the determination unit 30, or the communication unit 40 of the control device 10 may be mounted on the MME 60 or the HSS 70.
- the M2M device 80 is a device that autonomously transmits data to a counterpart communication device such as an application server without any user operation.
- the M2M device 80 is, for example, a vending machine having a communication function, and may periodically notify the application server of the product storage status.
- the M2M device 80 is not limited to a vending machine, and may be a device in which a communication function is installed in various other devices such as home appliances.
- the M2M device 80 may be a device in which a communication function is mounted on a wristwatch or the like worn by the user.
- the M2M device 80 may be a device in which a communication function is installed in a device that observes various information such as a smart meter and various environmental observation sensors.
- the M2M device 80 includes a 3G module 81 and an adjustment unit 82.
- the 3G module 81 is a module used to communicate with the eNodeB 50 arranged in the 3G core network. For example, the 3G module 81 performs a modulation process or the like to transmit data to the eNodeB 50. Alternatively, the 3G module 81 performs a demodulation process on data transmitted from the eNodeB 50 and the like.
- the adjustment unit 82 performs switching control of connection to the 3G core network and disconnection from the 3G core network. For example, when the control unit 10 is notified of the transmission timing of the connection request message, the adjustment unit 82 transmits the connection request message to the eNodeB 50 via the 3G module 81 based on the notified transmission timing. In addition, when the control unit 10 is notified of a message requesting the withdrawal from the 3G core network from the control device 10, the adjustment unit 82 transmits a message accepting the withdrawal to the eNodeB 50 via the 3G module 81, or from the M2M device 80. Once again, a message requesting to leave the 3G core network is transmitted.
- the M2M device 80 transmits an Attach request message to the eNodeB 50 (denoted by eNB in the figure) (S11).
- the Attach request message corresponds to a connection request message.
- the M2M device 80 transmits an Attach request message to the eNodeB 50 in order to connect to the 3G core network.
- the Attach request message includes subscriber information regarding the M2M device 80.
- a state where the M2M device is connected to the 3G core network may be referred to as an Attach state.
- a state in which the M2M device is detached from the 3G core network may be referred to as a “Detach state”.
- the eNodeB 50 transmits the Attach request message transmitted from the M2M device 80 to the MME 60 (S12).
- an authentication process is performed between the M2M device 80 and the HSS 70.
- the HSS 70 communicates a message regarding authentication processing with the M2M device 80 via the MME 60 (S13, S14).
- the HSS 70 performs authentication processing of the M2M device 80 using the subscriber information of the M2M device 80.
- the authentication process of the M2M device 80 may be a process of determining whether or not the subscriber information notified from the M2M device 80 matches the subscriber information registered in the HSS 70.
- the authentication process may be a process of determining whether to permit connection of the M2M device 80 to the 3G core network.
- the HSS 70 completes the authentication process of the M2M device 80 in steps S13 and S14, whether other communication devices in the non-simultaneous communication group to which the M2M device 80 belongs are attached to the 3G core network. In order to confirm whether or not, an asynchrony confirmation request message is transmitted (S15).
- the HSS 70 transmits the asynchronous confirmation request message including the subscriber identifier of the M2M device 80 and the group identifier of the asynchronous communication group to which the M2M device 80 belongs.
- the control device 10 includes, in addition to the M2M device 80, communication devices that have already attached to the 3G core network. Determine if it exists.
- the control device 10 permits non-simultaneous communication of the M2M device 80 (S16).
- the processing is ended in step S16, but the control apparatus 10 may transmit an Attach permission response message to the M2M device 80 after permitting non-simultaneous communication.
- the MME 60 may transmit an Attach permission response message to the M2M device 80.
- the M2M device 90 transmits an Attach request message to the eNodeB 50 (S21).
- the eNodeB 50 transmits the Attach request message transmitted from the M2M device 90 to the MME 60 (S22).
- an authentication process is performed between the M2M device 90 and the HSS 70.
- the HSS 70 communicates a message regarding authentication processing with the M2M device 90 via the MME 60 (S23, S24).
- the HSS 70 performs authentication processing of the M2M device 90 using the subscriber information of the M2M device 90.
- the control device 10 determines that the M2M device 90 is in a state of performing simultaneous communication with the M2M device 80 (S26). Therefore, the control apparatus 10 transmits a rejection response message that rejects the Attach of the M2M device 90 to the HSS 70 (S27). The control device 10 transmits the rejection response message including the subscriber identifier of the M2M device 90 and the back-off timer value indicating the time for which the M2M device 90 waits until the next Attach request message is transmitted. Further, the HSS 70 transmits a rejection response message transmitted from the control device 10 to the MME 60 (S28).
- the HSS 70 may transmit to the MME 60 a rejection response message in which a reason for rejecting the Attach of the M2M device 90 is added to the rejection response message transmitted from the control device 10.
- the HSS 70 may add a reason for refusal that another communication device in the same non-simultaneous communication group as the M2M device 90 is already connected to the 3G core network.
- the MME 60 When the MME 60 receives the rejection response message transmitted from the HSS 70, the MME 60 transmits an Attach rejection response message to the M2M device 90 (S29). The MME 60 transmits to the M2M device 90 the reason for rejecting the Attach and the back-off timer value notified from the control device 10 in the Attach rejection response message.
- the M2M device 90 when receiving the Attach rejection response message, the M2M device 90 starts a back-off timer.
- the M2M device 90 activates the back-off timer for the back-off timer value included in the Attach rejection response message.
- the M2M device 90 transmits an Attach request message to the eNodeB 50 again when the back-off timer expires (S30). Steps S30 to S35 are the same as steps S11 to S16 in FIG.
- the MME 60 may transmit an Attach permission response message to the M2M device 90 after the authentication processing of the M2M device 90 is completed in steps S23 and S24.
- the MME 60 transmits an Attach rejection response message to the M2M device 90 in Step S29.
- a Request request message requesting withdrawal may be transmitted to the M2M device 90. That is, the M2M device 90 is in a state where it has received the Attach permission response message after completion of the authentication in steps S23 and S24 and is connected to the 3G core network. Therefore, the MME 60 may transmit a Detach request message indicating that the MME 60 is to leave the 3G core network to the M2M device 90.
- the MME 60 may calculate the network leaving timing of the M2M device 90 and notify the M2M device 90 of the leaving timing (Deching timing).
- the connection timing of the M2M device to the 3G core network can be controlled by using the communication system according to the second embodiment of the present invention. That is, when the M2M device in the non-simultaneous communication group is already connected to the 3G core network, the control device 10 rejects Attach in consideration of the timing at which the already connected M2M device leaves the 3G core network. The back-off timer can be notified to the M2M device that performs the operation. As a result, the M2M device that has been refused Attach once is also given an opportunity to perform Attach again, and can secure a communication opportunity. In this way, the control apparatus 10 can impart a communication opportunity fairly to the M2M devices belonging to the non-simultaneous communication group.
- Steps S42 to S44 are the same as steps S27 to S29 in FIG.
- the control device 10 transmits a rejection response message for the M2M device 90 in step S42 and transmits a Detach request message for the M2M device 80 to the HSS 70 (S45).
- the control apparatus 10 transmits a Detach request message to the M2M device 80 in order to cause the M2M device 80 in the Attach state to leave the 3G core network.
- the control device 10 transmits the Detach request message including the subscriber identifier of the M2M device 80, the back-off timer value, and the reason for disconnection or withdrawal.
- the reason for disconnection or withdrawal may be, for example, “to connect another communication device in the same non-simultaneous communication group as the M2M device 80 to the 3G core network”.
- the HSS 70 transmits a Cancel Location message to the MME 60 (S46).
- the Cancel Location message has the same content as the Delete request message transmitted from the control device 10 in step S45.
- the MME 60 transmits a Delete request message to the M2M device 80 (S47).
- the Detach request message transmitted from the MME 60 to the M2M device 80 has the same content as the Detach request message transmitted from the control device 10 to the HSS 70.
- the M2M device 80 When receiving the Dtach request message, the M2M device 80 transmits a Detach accept message to the MME 60 in order to leave the 3G core network (S48). In addition, the M2M device 80 transmits a Delete accept message to the MME 60 and starts a back-off timer. The M2M device 80 transmits an Attach request message to the eNodeB 50 after the period of the back-off timer value notified in the Detach request message has elapsed and the back-off timer has expired.
- Step S49 the M2M device 90 transmits an Attach request message to the eNodeB 50 after the back-off timer that was started when the Attach rejection response message was received in Step S44 (S49).
- Steps S49 to S54 are the same as steps S30 to S35 of FIG.
- the control apparatus 10 allows the M2M device 90 to transmit the Attach request message after the M2M device 80 leaves the 3G core network, and notifies the back-off timer value of the M2M device 90 notified in the rejection response message in step S42.
- the control apparatus 10 assumes the time when the Detach request message is notified to the M2M device 80 in advance, and sets the back-off timer value so that the back-off timer in the M2M device 90 expires after the assumed time has elapsed. To do.
- the M2M device 80 already connected to the 3G core network is explicitly requested to leave the 3G core network. Messages can be sent.
- the control device 10 can shorten the back-off timer set in the M2M device 90 that has newly requested connection to the 3G core network. Therefore, compared with the operation in the second embodiment, the M2M device 90 can be connected to the 3G core network at an early stage.
- the control apparatus 10 determines that the M2M device 80 corresponds to non-simultaneous communication because there is no M2M device connected to the 3G core network in addition to the M2M device 80 in step S66. In this case, the control device 10 transmits a non-simultaneous communication permission response message to the M2M device 80 (S67). At this time, the control device 10 notifies the M2M device 80 of the permitted communication time or communication timer value using the non-simultaneous communication permission response message (S67).
- the M2M device 80 When the communication time is notified from the control device 10, the M2M device 80 starts a communication timer and connects to the 3G core network until the communication time expires.
- the M2M device 80 may transmit a message for leaving the 3G core network to the MME 60 after the communication time has expired.
- the message for leaving the 3G core network corresponds to a Detach request message or a Detach accept message.
- the control apparatus 10 may transmit a Detach request message to the M2M device 80 via the HSS 70 and the MME 60 when the communication time of the M2M device 80 expires.
- the control device 10 determines that the M2M device 90 has been connected after the communication time of the M2M device 80 has expired.
- a back-off timer value to be notified to the M2M device 90 may be set so that an Attach request message can be transmitted. That is, the control apparatus 10 may determine the back-off timer value notified to the M2M device 90 based on the remaining time until the communication time of the M2M device 80 expires.
- the M2M device connected to the 3G core network can be notified of the time allowed to connect to the 3G core network. I can do it.
- the control device 10 sets a back-off timer value for the M2M device that is newly connected to the 3G core network in consideration of the communication time allocated to the already connected M2M device, so that the 3G core network is newly set. Communication opportunities can also be given to M2M devices connected to.
- the M2M device 80 transmits an Attach request message to the eNodeB 50 (S71).
- the Attach request message includes subscriber information regarding the M2M device 80 and a temporary communication flag.
- the temporary communication flag is a flag indicating that temporary communication for receiving notification of the communication time determined by the control device 10 is requested in a state where the M2M device 80 is not connected to the 3G core network.
- the communication time determined by the control device 10 indicates a time during which the M2M device 80 can continue the Attach state. Furthermore, the communication time determined by the control device 10 indicates the timing or time at which the M2M device 80 next transmits the Attach request message.
- Steps S73 to S75 are the same as steps S13 to S15 in FIG.
- the reception process is a process of receiving a request for temporary communication notified from a plurality of M2M devices.
- the control device 10 executes reception processing in order to calculate communication times of a plurality of M2M devices.
- the control device 10 starts a batch reception timer.
- the control device 10 calculates the communication time of the M2M device that has requested temporary communication before the batch reception timer expires. The time from the activation of the collective acceptance timer to the expiration of the collective acceptance timer may be determined in advance, and dynamically depending on the number of temporary communication requests, etc. It may be changed.
- the control device 10 transmits a temporary communication permission message to the HSS 70 (S77).
- the control apparatus 10 notifies the subscriber identifier of the M2M device 80 and the temporary communication permission time using the temporary communication permission message.
- the HSS 70 transmits the temporary communication permission message transmitted from the control device 10 to the MME 60 (S78).
- the MME 60 transmits the temporary communication permission message transmitted from the HSS 70 to the M2M device 80 (S79).
- the MME 60 notifies the M2M device 80 of the temporary communication permission time determined by the control device 10 using the temporary communication permission message.
- the M2M device 80 starts a temporary communication timer. The temporary communication timer expires when the temporary communication permission time notified in the temporary communication permission message elapses.
- the M2M device 90 transmits an Attach request to the eNodeB 50 (S80). Similar to step S71, the Attach request in step S80 has subscriber identification information of the M2M device 90 and a temporary communication flag. Steps S80 to S84 are the same as steps S71 to S75 in FIG.
- Step S85 to S87 are the same as steps S77 to S79 in FIG.
- the control device 10 calculates the communication time of each M2M device accepted while the collective acceptance timer is activated (S88). In this figure, the control apparatus 10 calculates the communication time of each of the M2M devices 80 and 90.
- the communication time calculated by the control device 10 includes a communication start time and a communication end time.
- the control apparatus 10 transmits a communication time notification message including the subscriber identifier of the M2M device 80 and the communication time to the HSS 70 in order to notify the communication time to the M2M device 80 (S89).
- HSS70 transmits the communication time message transmitted from the control apparatus 10 to MME60 (S90).
- the MME 60 notifies the M2M device 80 of the communication time of the M2M device 80 determined by the control apparatus 10 using the communication time notification message to the M2M device 80 (S91).
- the M2M device 80 leaves the 3G core network when the temporary communication timer expires after receiving the communication time notification message.
- the M2M device 80 transmits an Attach request message to the eNodeB 50 at the communication start time specified in the communication time notification message, and transmits a Detach request message to the eNodeB 50 at the communication end time specified in the communication time notification message.
- Steps S92 to S94 are processes for notifying the M2M device 90 of the communication time, and are the same as Steps S89 to S91, and thus detailed description thereof is omitted.
- step S76 the reception process in step S76 will be further described.
- the control device 10 receives the asynchrony confirmation request message in which the temporary communication flag is set, the M2M device that requests the temporary communication is after a predetermined time has elapsed since the temporary communication request was made in the past. Whether or not temporary communication is permitted may be determined according to whether or not the temporary communication is permitted. In such a case, the control device 10 sets a temporary communication disapproval timer for each M2M device, and disallows a temporary communication request when a temporary communication request is made before the temporary communication disapproval timer expires. It is good.
- the M2M device can be used unconditionally and temporarily regardless of the Attach status of other M2M devices in the non-simultaneous communication group. Can communicate. Since the M2M device can perform temporary communication unconditionally, it can immediately receive notification of normal communication timing different from temporary communication without setting a period determined by the back-off timer. Furthermore, the control apparatus 10 can calculate communication times of a plurality of M2M devices that have made connection requests to the 3G core network within a predetermined period by using the collective acceptance timer.
- a plurality of M2Ms that have made a connection request to the 3G core network within a predetermined period of time are compared with the process of calculating the backhaul timer value to the M2M device each time a connection request is made from the M2M device to the 3G core network. Since the communication time of devices can be calculated in a lump, scheduling processing for a plurality of M2M devices can be executed efficiently.
- the M2M device is notified of the normal communication timing after the collective acceptance timer expires, but the collective acceptance timer period is backoff due to Attach rejection.
- the time is sufficiently smaller than the period, it is possible to obtain an immediate effect that a normal communication timing notification can be received immediately.
- the process flow in which the M2M devices 80 and 90 set the temporary communication flag and transmit the Attach request message has been described.
- the M2M device 80 does not set the temporary communication flag.
- the control device 10 determines whether or not a predetermined period has elapsed since the time when the Attach request message was transmitted in the past for the M2M devices 80 and 90, and when the predetermined period has elapsed.
- the Attach request message transmitted from the M2M device 80 or 90 may be determined as an Attach request for requesting temporary communication, and temporary communication may be permitted.
- the control device 10 Instead of determining whether or not a predetermined period has elapsed, the control device 10 temporarily transmits an Attach request after a predetermined time in a predetermined date or hour / minute / second unit. Communication may be permitted.
- the Attach request for requesting temporary communication and the normal Attach request are, for example, the Attach request transmitted during the communication time permitted by the control device 10 as a normal Attach request, and transmitted at other times. You may distinguish an Attach request from an Attach request which requests
- an Attach request transmitted during a communication time permitted by the control device 10 may be an Attach request for requesting temporary communication, and an Attach request transmitted at any other time may be distinguished from a normal Attach request. .
- each M2M device belonging to the non-simultaneous communication group does not acquire the communication timing from the control apparatus 10, but the representative M2M device acquires the communication timing of other M2M devices in the non-simultaneous communication group.
- the M2M device 90 is activated when the power switch is pressed by the user (S101).
- the M2M device 90 activates the representative timer immediately after activation (S102).
- the representative timer is a timer used to determine a representative M2M device among a plurality of M2M devices belonging to the non-simultaneous communication group.
- the M2M device 90 transmits a neighbor investigation message to neighboring M2M devices while the representative timer is running (S103).
- the M2M device 90 may transmit a neighbor investigation message to any neighboring M2M device without specifying a destination. That is, the M2M device 90 may transmit a neighbor investigation message as a broadcast message to neighboring M2M devices.
- the M2M device 90 when the M2M device 90 has information on the M2M device in the non-simultaneous communication group, the M2M device in the non-simultaneous communication group is designated as a transmission destination, and a neighbor investigation message is sent to each M2M device May be sent.
- the M2M device 90 when there is no active M2M device in the vicinity of the M2M device 90, the M2M device 90 does not receive a response message to the neighbor investigation message.
- the M2M device 90 stops the representative timer after a predetermined time has elapsed (S104).
- the M2M device 90 operates as a representative M2M device in the non-simultaneous communication group by not receiving a response message from another M2M device in response to the neighbor investigation message.
- the M2M device 90 that has become the representative M2M device starts a participation acceptance timer (S105).
- the M2M device 80 is activated (S106) and the representative timer is activated (S107).
- the M2M device 80 is an M2M device that belongs to the same non-simultaneous communication group as the M2M device 90.
- the M2M device 80 transmits a neighbor investigation message to the neighboring M2M device (S108).
- the M2M device 90 displays a representative information notification message to notify that the own apparatus is the representative M2M device. Is transmitted to the M2M device 80 (S109).
- the M2M device 80 determines that the own apparatus is not the representative M2M device.
- the representative timer is forcibly stopped (S110).
- the M2M device 90 stops the participation reception timer after a predetermined time has elapsed (S111).
- the M2M device 80 is activated before the expiry period of the representative timer of the M2M device 90 and the proximity investigation is performed, the same processing as in steps S108 and S109 is performed, and the M2M device 90 becomes the representative. Good. In other words, in this case, the M2M device 90 becomes a representative because it is the terminal that first performed the proximity check before the representative timer expiration period.
- the representative determination method is not limited to the method shown in FIG. 9, and any method may be used.
- it may be determined by transmission / reception of the representative priority between the M2M devices (information on whether or not to become a representative preferentially by device specifications, service type, etc.).
- the representative priority information on whether or not to become a representative preferentially by device specifications, service type, etc.
- the other M2M device is set as a representative.
- the result of the neighborhood survey shows that it has the highest priority, it becomes a representative.
- the representative is transferred to the M2M device that transmitted the neighbor investigation message.
- the representative may be determined at random by transmission and reception between M2M devices activated within a certain period. Specifically, it is selected whether or not it becomes a representative using a random number in each M2M device. After the determination, the selection results are transmitted and received between the M2M devices, and it is determined whether or not the representative has determined. If the representatives overlap or no one becomes a representative, the random selection operation is repeated until the representative can be determined.
- the representative is not limited to one M2M device, and a plurality of M2M devices may be selected.
- the number of the plurality of units may be in accordance with the number of simultaneously communicable allowed in the non-simultaneous communication group or may be irrelevant.
- representative M2M devices in a plurality of M2M devices belonging to the non-simultaneous communication group can be determined by the M2M devices communicating with each other. Thereafter, the M2M device 90 acquires the communication timing of the M2M device 80 from the control apparatus 10 together with the communication timing of the M2M device 90 as the representative M2M device.
- Wireless LAN communication may be used for communication between the M2M device 90 and the M2M device 80.
- near field communication such as infrared communication, Bluetooth (registered trademark), or Zigbee (registered trademark) may be used for communication between the M2M device 90 and the M2M device 80.
- the M2M device 90 transmits an Attach request message to the eNodeB 50 in order to connect to the 3G core network (S121). Further, the M2M device 90 transmits an Attach request message and starts a communication timer.
- steps S122 to S126 are the same as steps S12 to S16 in FIG.
- the M2M device 90 transmits a non-simultaneous communication group information notification message to the control device 10 (S127).
- the M2M device 90 sets that the M2M device 90 and the M2M device 80 exist in the non-simultaneous communication group, and transmits a non-simultaneous communication group information notification message to the communication timing control device 30.
- control device 10 transmits a non-simultaneous communication group information notification response message to the M2M device 90 as a response message to the non-simultaneous communication group information notification message (S128).
- the control apparatus 10 sets the communication timing of the M2M device 80 and the M2M device 90, and transmits a non-simultaneous communication group information notification response message to the M2M device 90.
- the M2M device 90 stops the communication timer after receiving the non-simultaneous communication group information notification response message. Furthermore, the M2M device 90 stops the communication timer, leaves the 3G core network, and transitions to the Detach state. The M2M device 90 may stop the communication timer when the non-simultaneous communication group information notification response message is received, or may stop the communication timer when a predetermined time elapses after the communication timer is started.
- the M2M device 90 stops the communication timer after a predetermined period of time has elapsed after the communication timer is started, the M2M device 90 is longer than the time that is expected from the transmission of the Attach request until the reception of the non-simultaneous communication group information notification response message Set the time to start the communication timer.
- the M2M device 90 may continue (extend) the current Attach state according to the communication timing included in the received non-simultaneous communication group information notification response message.
- the M2M device 90 transmits a communication timing notification message to the M2M device 80 (S129).
- the communication timing notification message is used to notify the M2M device 80 of the communication timing of the M2M device 80 set in the non-simultaneous communication group information notification response message.
- the M2M device 90 may transmit a communication timing notification message to the M2M device 80 in the Attach state when its own Attach state continues.
- the M2M device 80 transmits an Attach request message to the eNodeB 50 based on the communication timing set in the communication timing notification (S130).
- the representative M2M device sends another M2M together with its own communication timing from the control device 10. Get the communication timing of the device.
- the control device 10 does not receive the communication timing request for each of the plurality of M2M devices belonging to the non-simultaneous communication group and calculates the communication timing, but calculates the communication timings of the plurality of M2M devices all at once. I can do it. Therefore, the control apparatus 10 can calculate the communication timing of each M2M device efficiently. Furthermore, since the number of times the message for the purpose of acquiring the communication timing is transmitted from the M2M device is reduced, the control device 10 also reduces the processing load.
- the representative M2M device makes an inquiry about the communication timing of other M2M devices, the amount of communication in the 3G core network can be reduced.
- the identification information used for identifying each M2M device between the M2M devices in FIG. 9 may be an ISIM used as a subscriber identifier of the 3G network.
- Each M2M device uses ISIM to notify that it has started up or is a representative M2M device.
- the identification information used for identifying each M2M device between the M2M devices in FIG. 9 may be a service terminal identifier different from the subscriber identifier of the 3G network.
- the service terminal identifier is an identifier managed in an external server device or the like arranged in an external network different from the 3G core network.
- the M2M device 90 transmits a service terminal identifier to the control apparatus 10 in order to identify each M2M device by using the non-simultaneous communication group information notification message. Therefore, the control device 10 and the HSS 70 may acquire a service terminal identifier for identifying each M2M device from the external server device.
- the control device 10 and the HSS 70 acquire the service terminal identifier from the external server device in advance, and can identify each M2M device even when the service terminal identifier is notified from the M2M device 90. I can do it.
- the present invention has been described as a hardware configuration, but the present invention is not limited to this.
- the present invention can also realize the processing of the control device by causing a CPU (Central Processing Unit) to execute a computer program.
- a CPU Central Processing Unit
- Non-transitory computer readable media include various types of tangible storage media (tangible storage medium).
- Examples of non-transitory computer-readable media include magnetic recording media (eg flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (eg magneto-optical discs), CD-ROMs (Read Only Memory), CD-Rs, CD-R / W, semiconductor memory (for example, mask ROM, PROM (Programmable ROM), EPROM (Erasable ROM), flash ROM, RAM (Random Access Memory)) are included.
- the program may also be supplied to the computer by various types of temporary computer-readable media. Examples of transitory computer readable media include electrical signals, optical signals, and electromagnetic waves.
- the temporary computer-readable medium can supply the program to the computer via a wired communication path such as an electric wire and an optical fiber, or a wireless communication path.
- control device 20 monitoring unit 30 determination unit 40 communication unit 50 eNodeB 60 MME 70 HSS 80 M2M device 81 3G module 82 Adjustment unit 90 M2M device
Abstract
Description
以下、図面を参照して本発明の実施の形態について説明する。図1の制御装置10は、監視部20、判定部30及び通信部40を有している。
続いて、図2を用いて本発明の実施の形態2にかかる通信システムの構成例について説明する。本図においては、通信装置が接続するネットワークとして、3Gコアネットワークを用いて説明する。3Gコアネットワークは、3GPPにおいて規定されたネットワークであり、移動通信事業者等が管理するモバイルネットワークである。さらに、本図においては、通信装置の1つの例として、M2Mデバイス80を用いて説明する。M2Mデバイスは、UE(User Equipment)と称されてもよい。UEは、3GPPにおいて規定されている移動通信端末の総称である。
続いて、図6を用いて本発明の実施の形態3にかかるM2Mデバイス90の接続要求が拒否される際の処理の流れについて説明する。ここで、M2Mデバイス80は、図4において説明したように、3Gコアネットワークへ接続している状態(Attach状態)とする。さらに、本図においては図示を省略しているが、ステップS41の前に、図5のステップS21~S25のAttach要求に関する処理が実行されている。
続いて、図7を用いて本発明の実施の形態4にかかるM2Mデバイス80が3Gコアネットワークへ接続する際の処理の流れについて説明する。本図のステップS61~66は、図4のステップS11~16と同様であるため詳細な説明を省略する。
続いて、図8A及び図8Bを用いて本発明の実施の形態5にかかるAttach処理の流れについて説明する。はじめに、M2Mデバイス80は、eNodeB50へAttachリクエストメッセージを送信する(S71)。Attachリクエストメッセージは、M2Mデバイス80に関する加入者情報及び一時通信フラグを有している。一時通信フラグは、M2Mデバイス80が3Gコアネットワークへ接続していない状態において、制御装置10において決定された通信時間の通知を受けるための一時通信を要求することを示すフラグである。制御装置10において決定された通信時間は、M2Mデバイス80がAttach状態を継続することが出来る時間を示している。さらに、制御装置10において決定された通信時間は、M2Mデバイス80が次にAttachリクエストメッセージを送信するタイミングもしくは時刻を示している。
続いて、図9を用いて本発明の実施の形態6にかかるM2Mデバイスが起動した際に実行する近隣M2Mデバイスとの通信処理の流れについて説明する。図9においては、非同時通信グループに属するそれぞれのM2Mデバイスが制御装置10から通信タイミングを取得するのではなく、代表M2Mデバイスが非同時通信グループ内の他のM2Mデバイスの通信タイミングを取得することを前提とする。
20 監視部
30 判定部
40 通信部
50 eNodeB
60 MME
70 HSS
80 M2Mデバイス
81 3Gモジュール
82 調整部
90 M2Mデバイス
Claims (25)
- 同時通信が制限される複数の通信装置によるネットワークへの接続状況を監視する監視手段と、
前記複数の通信装置に含まれる第1の通信装置から前記ネットワークへの接続を要求する接続要求メッセージを受信した際に、前記複数の通信装置のネットワークへの接続状況に応じて前記第1の通信装置が前記ネットワークへ接続可能か否かを判定する判定手段と、
前記判定手段において前記第1の通信装置の前記ネットワークへの接続が不可と判定された場合、前記第1の通信装置へ、接続が不可であることを示す判定結果とともに、次の前記接続要求メッセージの送信タイミングを通知する通信手段と、を備える制御装置。 - 前記判定手段は、
前記複数の通信装置に含まれる1つ以上の複数の通信装置が既に前記ネットワークへ接続している場合、前記第1の通信装置の前記ネットワークへの接続を不可と判定する、請求項1に記載の制御装置。 - 前記判定手段において前記第1の通信装置の前記ネットワークへの接続が不可と判定された場合、前記通信手段は、
既に前記ネットワークへ接続している通信装置へ、前記ネットワークから離脱することを要求する離脱要求メッセージを送信する、請求項1又は2に記載の制御装置。 - 前記通信手段は、
前記離脱要求メッセージを送信するとともに、次に前記接続要求メッセージを送信する送信タイミングを通知する、請求項3に記載の制御装置。 - 前記判定手段は、
前記第1の通信装置の前記ネットワークへの接続を許可する場合、前記第1の通信装置へ通信許可時間を割り当てる、請求項1乃至4のいずれか1項に記載の制御装置。 - 前記判定手段は、
前記複数の通信装置に含まれる少なくとも1つの通信装置から前記接続要求メッセージが送信された場合、前記接続要求メッセージを送信した通信装置の前記ネットワークへの接続を一時的に許可し、前記ネットワークへの接続を一時的に許可した通信装置へ、次に前記接続要求メッセージを送信する送信タイミングを通知する、請求項1乃至5のいずれか1項に記載の制御装置。 - 前記判定手段は、
一時通信フラグが設定されている初期接続要求メッセージを送信した通信装置の前記ネットワークへの接続を一時的に許可する、請求項6に記載の制御装置。 - 前記判定手段は、
前記初期接続要求メッセージを受信した際に、前記初期接続要求メッセージを送信した通信装置が、以前に前記初期接続要求メッセージを送信してから予め定められた期間を経過しているか否かに応じて、前記ネットワークへの接続を一時的に許可するか否かを判定する、請求項7に記載の制御装置。 - 前記判定手段は、
前記接続要求メッセージを受信した際に、前記接続要求メッセージを送信した通信装置が、以前に前記接続要求メッセージを送信してから予め定められた期間を経過しているかに応じて、前記接続要求メッセージを送信した通信装置の前記ネットワークへの接続を一時的に許可するか否かを判定する、請求項1乃至5のいずれか1項に記載の制御装置。 - 前記通信手段は、
前記判定手段において前記同時通信が制限される複数の通信装置のうち代表装置として動作する前記第1の通信装置が前記ネットワークへ接続可能と判定された場合に、前記第1の通信装置の通信タイミングとともに前記複数の通信装置に含まれる他の通信装置の通信タイミングを示すメッセージを前記第1の通信装置へ送信する、請求項1に記載の制御装置。 - 同時通信が制限される複数の通信装置と、
前記複数の通信装置によるネットワークへの接続状況を監視し、前記複数の通信装置に含まれる第1の通信装置から前記ネットワークへの接続を要求する接続要求メッセージを受信した際に、前記複数の通信装置のネットワークへの接続状況に応じて前記第1の通信装置が前記ネットワークへ接続可能か否かを判定し、前記第1の通信装置の前記ネットワークへの接続が不可と判定された場合、前記第1の通信装置へ、接続が不可であることを示す判定結果とともに、次の前記接続要求メッセージの送信タイミングを通知する制御装置と、を備える通信システム。 - 前記制御装置は、
前記複数の通信装置に含まれる1つ以上の複数の通信装置が既に前記ネットワークへ接続している場合、前記第1の通信装置の前記ネットワークへの接続を不可と判定する、請求項11に記載の通信システム。 - 前記制御装置は、
前記第1の通信装置の前記ネットワークへの接続を不可と判定した場合、既に前記ネットワークへ接続している通信装置へ、前記ネットワークから離脱することを要求する離脱要求メッセージを送信する、請求項11又は12に記載の通信システム。 - 前記制御装置は、
前記離脱要求メッセージを送信するとともに、次に前記接続要求メッセージを送信する送信タイミングを通知する、請求項13に記載の通信システム。 - 前記制御装置は、
前記第1の通信装置の前記ネットワークへの接続を許可する場合、前記第1の通信装置へ通信許可時間を割り当てる、請求項11乃至14のいずれか1項に記載の通信システム。 - 前記制御装置は、
前記複数の通信装置に含まれる少なくとも1つの通信装置から前記接続要求メッセージが送信された場合、前記接続要求メッセージを送信した通信装置の前記ネットワークへの接続を一時的に許可し、前記ネットワークへの接続を一時的に許可した通信装置へ、次に前記接続要求メッセージを送信する送信タイミングを通知する、請求項11乃至15のいずれか1項に記載の通信システム。 - 前記制御装置は、
次に前記接続要求メッセージを送信する送信タイミングの通知を要求することを示す識別子を含む初期接続要求メッセージを送信した通信装置の前記ネットワークへの接続を一時的に許可する、請求項16に記載の通信システム。 - 前記通信装置は、
前記初期接続要求メッセージを受信した際に、前記初期接続要求メッセージを送信した通信装置が、以前に前記初期接続要求メッセージを送信してから予め定められた期間を経過しているか否かに応じて、前記ネットワークへの接続を一時的に許可するか否かを判定する、請求項17に記載の通信システム。 - 前記制御装置は、
前記接続要求メッセージを受信した際に、前記接続要求メッセージを送信した通信装置が、以前に前記接続要求メッセージを送信してから予め定められた期間を経過しているかに応じて、前記接続要求メッセージを送信した通信装置の前記ネットワークへの接続を一時的に許可するか否かを判定する、請求項11乃至15のいずれか1項に記載の通信システム。 - 前記通信装置は、
前記同時通信が制限される複数の通信装置のうち代表装置として動作し、前記ネットワークへ接続可能と判定された場合に、自装置の通信タイミングとともに前記複数の通信装置に含まれる他の通信装置の通信タイミングの取得を要求するメッセージを前記制御装置へ送信し、
前記制御装置は、前記代表装置として動作する通信装置の通信タイミングとともに、前記他の通信装置の通信タイミングを示すメッセージを前記代表装置として動作する通信装置へ送信する、請求項11に記載の通信システム。 - 前記複数の通信装置は、自律的に通信を行うM2Mデバイスである、請求項11乃至20のいずれか1項に記載の通信システム。
- 前記ネットワークは、移動通信事業者によって管理されるネットワークであり、前記制御装置は、前記ネットワークに配置される、請求項11乃至21のいずれか1項に記載の通信システム。
- 他の複数の通信装置との同時通信が制限される通信装置であって、
ネットワークへの接続を要求する接続要求メッセージを送信する通信手段と、
前記ネットワークに配置されている制御装置において前記他の複数の通信装置の前記ネットワークへの接続状況に応じて前記ネットワークへの接続が不可と判定された場合に、前記制御装置から通知される次の前記接続要求メッセージの送信タイミングに応じて、前記ネットワークへ再接続処理を行う調整手段と、を有する通信装置。 - 同時通信が制限される複数の通信装置によるネットワークへの接続状況を監視し、
前記複数の通信装置に含まれる第1の通信装置から前記ネットワークへの接続を要求する接続要求メッセージを受信した際に、前記複数の通信装置のネットワークへの接続状況に応じて前記第1の通信装置が前記ネットワークへ接続可能か否かを判定し、
前記第1の通信装置の前記ネットワークへの接続が不可と判定された場合、前記第1の通信装置へ、接続が不可であることを示す判定結果とともに、次の前記接続要求メッセージの送信タイミングを通知する通信方法。 - 同時通信が制限される複数の通信装置によるネットワークへの接続状況を監視するステップと、
前記複数の通信装置に含まれる第1の通信装置から前記ネットワークへの接続を要求する接続要求メッセージを受信した際に、前記複数の通信装置のネットワークへの接続状況に応じて前記第1の通信装置が前記ネットワークへ接続可能か否かを判定するステップと、
前記第1の通信装置の前記ネットワークへの接続が不可と判定された場合、前記第1の通信装置へ、接続が不可であることを示す判定結果とともに、次の前記接続要求メッセージの送信タイミングを通知するステップと、をコンピュータに実行させるプログラムが格納された非一時的なコンピュータ可読媒体。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/888,238 US20160066333A1 (en) | 2013-05-15 | 2013-12-26 | Control apparatus, communication system, communication apparatus, communication method, and non-transitory computer readable medium storing program |
EP13884680.3A EP2999293B1 (en) | 2013-05-15 | 2013-12-26 | Representative for mtc-group |
JP2015516760A JP6337890B2 (ja) | 2013-05-15 | 2013-12-26 | 制御装置、通信システム、通信装置、通信方法及びプログラム |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2013103219 | 2013-05-15 | ||
JP2013-103219 | 2013-05-15 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014184834A1 true WO2014184834A1 (ja) | 2014-11-20 |
Family
ID=51897855
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2013/007609 WO2014184834A1 (ja) | 2013-05-15 | 2013-12-26 | 制御装置、通信システム、通信装置、通信方法及びプログラムが格納された非一時的なコンピュータ可読媒体 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20160066333A1 (ja) |
EP (1) | EP2999293B1 (ja) |
JP (1) | JP6337890B2 (ja) |
WO (1) | WO2014184834A1 (ja) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2022013958A1 (ja) * | 2020-07-15 | 2022-01-20 | 日本電気株式会社 | 基地局装置、サービスの提供方法及びプログラムを記録したプログラム記録媒体 |
WO2023062878A1 (ja) * | 2021-10-13 | 2023-04-20 | 株式会社ソラコム | Mnoが有する無線通信インフラを利用して提供される無線通信サービスの設定を管理するための装置、方法及びそのためのプログラム |
WO2023063126A1 (ja) * | 2021-10-13 | 2023-04-20 | 株式会社ソラコム | 情報処理装置、情報処理方法及びプログラム |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11218416B1 (en) | 2020-08-18 | 2022-01-04 | Verizon Patent And Licensing Inc. | Service aware admission control for IoT applications |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH09261735A (ja) * | 1996-03-27 | 1997-10-03 | Toshiba Corp | 無線通信システム |
JP2000333249A (ja) * | 1999-05-14 | 2000-11-30 | Mitsubishi Materials Corp | 無線通信アクセスシステムおよびその記録媒体 |
JP2001045571A (ja) * | 1999-05-24 | 2001-02-16 | Matsushita Electric Ind Co Ltd | 情報端末およびその通信方法 |
WO2006101168A1 (ja) * | 2005-03-23 | 2006-09-28 | Nec Corporation | 呼受付制御システム及び呼受付制御方法 |
WO2009133599A1 (ja) * | 2008-04-28 | 2009-11-05 | 富士通株式会社 | 無線通信システムにおける接続処理方法並びに無線基地局及び無線端末 |
WO2013021532A1 (ja) * | 2011-08-08 | 2013-02-14 | 日本電気株式会社 | 輻輳制御装置、輻輳制御方法 |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6418148B1 (en) * | 1995-10-05 | 2002-07-09 | Lucent Technologies Inc. | Burst-level resource allocation in cellular systems |
WO2011121921A1 (ja) * | 2010-03-29 | 2011-10-06 | パナソニック株式会社 | 通信ノード及びネットワークノード |
EP2509374A1 (en) * | 2011-04-05 | 2012-10-10 | Panasonic Corporation | Detachment of a mobile terminal (MTC) from a mobile communication system |
US9439073B2 (en) * | 2012-07-02 | 2016-09-06 | Panasonic Intellectual Property Corporation Of America | Server and communication terminal |
US8709250B2 (en) * | 2012-07-12 | 2014-04-29 | Heliae Development, Llc | Tubular electro-acoustic aggregation device |
-
2013
- 2013-12-26 EP EP13884680.3A patent/EP2999293B1/en active Active
- 2013-12-26 WO PCT/JP2013/007609 patent/WO2014184834A1/ja active Application Filing
- 2013-12-26 US US14/888,238 patent/US20160066333A1/en not_active Abandoned
- 2013-12-26 JP JP2015516760A patent/JP6337890B2/ja active Active
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH09261735A (ja) * | 1996-03-27 | 1997-10-03 | Toshiba Corp | 無線通信システム |
JP2000333249A (ja) * | 1999-05-14 | 2000-11-30 | Mitsubishi Materials Corp | 無線通信アクセスシステムおよびその記録媒体 |
JP2001045571A (ja) * | 1999-05-24 | 2001-02-16 | Matsushita Electric Ind Co Ltd | 情報端末およびその通信方法 |
WO2006101168A1 (ja) * | 2005-03-23 | 2006-09-28 | Nec Corporation | 呼受付制御システム及び呼受付制御方法 |
WO2009133599A1 (ja) * | 2008-04-28 | 2009-11-05 | 富士通株式会社 | 無線通信システムにおける接続処理方法並びに無線基地局及び無線端末 |
WO2013021532A1 (ja) * | 2011-08-08 | 2013-02-14 | 日本電気株式会社 | 輻輳制御装置、輻輳制御方法 |
Non-Patent Citations (2)
Title |
---|
"Services and System Aspects; Service requirements for Machine-Type Communications (MTC); Stage 1 (Release 11)", 3GPP TS 22.368 V11.3.0, September 2011 (2011-09-01) |
See also references of EP2999293A4 |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2022013958A1 (ja) * | 2020-07-15 | 2022-01-20 | 日本電気株式会社 | 基地局装置、サービスの提供方法及びプログラムを記録したプログラム記録媒体 |
WO2023062878A1 (ja) * | 2021-10-13 | 2023-04-20 | 株式会社ソラコム | Mnoが有する無線通信インフラを利用して提供される無線通信サービスの設定を管理するための装置、方法及びそのためのプログラム |
WO2023063126A1 (ja) * | 2021-10-13 | 2023-04-20 | 株式会社ソラコム | 情報処理装置、情報処理方法及びプログラム |
Also Published As
Publication number | Publication date |
---|---|
JPWO2014184834A1 (ja) | 2017-02-23 |
US20160066333A1 (en) | 2016-03-03 |
EP2999293B1 (en) | 2020-03-25 |
JP6337890B2 (ja) | 2018-06-06 |
EP2999293A1 (en) | 2016-03-23 |
EP2999293A4 (en) | 2016-12-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10887940B2 (en) | Policy determination system, policy determination method, and non-transitory computer-readable medium | |
EP3386220B1 (en) | Methods and apparatus for communication in a mobile communication system | |
EP2896264B1 (en) | Initiation of inter-device communication in wireless communication systems | |
KR101673831B1 (ko) | 무선 통신 시스템에서 디바이스 간 통신 인가 및 데이터 스니핑 | |
US20150111574A1 (en) | Relay device, wireless terminal device, communication system and communication method | |
US10098176B2 (en) | Mobile communications system, control apparatus, policy supply system, state transition control method, and policy supply method | |
US20220394592A1 (en) | Access Control at a Relay User Equipment | |
US10327196B2 (en) | Apparatus and methods for intelligent scheduling in hybrid networks based on client identity | |
US20170094495A1 (en) | Method for supporting proximity-based service configuring for ue | |
JP6337890B2 (ja) | 制御装置、通信システム、通信装置、通信方法及びプログラム | |
US11006289B2 (en) | Communication system, service common apparatus, mobile network node apparatus, and data communication method | |
JP6337891B2 (ja) | 通信システム、通信タイミング制御装置、接続制御装置、通信タイミング制御方法及びプログラム | |
RU2765377C2 (ru) | Способ, узел сети и пользовательское устройство для подключения носимых устройств к сети мобильной связи | |
CN113382454A (zh) | 一种通信方法与装置 | |
WO2011147362A1 (zh) | 选择公众陆地移动通信网络接入网络的方法和装置 | |
WO2017146076A1 (ja) | ゲートウェイ装置、通信方法、及び、非一時的なコンピュータ可読媒体 | |
WO2014029292A1 (zh) | 控制网络与终端信令连接的方法及系统 | |
WO2017146077A1 (ja) | 中継ノード装置、通信制御方法、及び、非一時的なコンピュータ可読媒体 | |
JP2021073808A (ja) | 端末デバイス間の関連付けを確立するための方法及びデバイス | |
WO2017146075A1 (ja) | 通信システム、通信方法、及び、非一時的なコンピュータ可読媒体 | |
JP2018023156A (ja) | 基地局およびその制御方法 | |
JP2016019136A (ja) | タイミング制御サーバ、通信システム、通信端末、通信タイミング制御方法及びプログラム |
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: 13884680 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2015516760 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14888238 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2013884680 Country of ref document: EP |