WO2013114504A1 - Appareil et procédés pour optimiser une utilisation des ressources pour une pluralité de dispositifs de communication - Google Patents

Appareil et procédés pour optimiser une utilisation des ressources pour une pluralité de dispositifs de communication Download PDF

Info

Publication number
WO2013114504A1
WO2013114504A1 PCT/JP2012/007977 JP2012007977W WO2013114504A1 WO 2013114504 A1 WO2013114504 A1 WO 2013114504A1 JP 2012007977 W JP2012007977 W JP 2012007977W WO 2013114504 A1 WO2013114504 A1 WO 2013114504A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
congestion
mobile terminal
released
connection
Prior art date
Application number
PCT/JP2012/007977
Other languages
English (en)
Inventor
Chan Wah Ng
Keigo Aso
Yan Steven ZHANG
Hong Cheng
Takahisa Aoyama
Original Assignee
Panasonic Corporation
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 Panasonic Corporation filed Critical Panasonic Corporation
Publication of WO2013114504A1 publication Critical patent/WO2013114504A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H04W48/06—Access restriction performed under specific conditions based on traffic conditions

Definitions

  • This disclosure relates to the field of telecommunications in a packet-switched data communications network. More particularly, it concerns the update of routing policies for a large group of communication devices.
  • the cellular telecommunications has been under constant evolution, from the earlier days of GSM (Global System for Mobile communications) networks, to GPRS (General Packet Radio Service), to the modern system of UMTS (Universal Mobile Telecommunications System) which can be found in various big cities around the world.
  • GSM Global System for Mobile communications
  • GPRS General Packet Radio Service
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • today's cellular network is no longer only providing services for human oriented communications (such as voice, short text message transmission and access to the global Internet).
  • new services have even been expanded to cover non-human communications, such as machine-to-machine (M2M) or machine-type communications (MTC).
  • M2M machine-to-machine
  • MTC machine-type communications
  • Machine-type communications can cover a very wide range of applications, from measurement collection from sensors, to remote control of devices. For such communications, delay need not be the foremost consideration, since they have a set of characteristics that is different from human
  • machine-type communication in 3GPP consists of various communication devices that access the 3GPP cellular network (also known as the Evolved Packet System, or EPS) to communicate with a server that is inside/outside of the cellular network or to communicate with other communication devices in the cellular network.
  • the application communicating with devices can be located in the server or in the other node connecting to the server.
  • NPL 1 3GPP TS 22.368v11.2.0, "Service Requirements for Machine-Type Communications (MTC); Stage 1", Jun 2011.
  • NPL 2 3GPP TS 23.401v10.4.0, "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access", Jun 2011.
  • GPRS General Packet Radio Service
  • one such optimization is to reduce the amount of signaling when some portion of the cellular network, or the Evolved Packet System (EPS), is overloaded. This is done according to ⁇ Non-Patent Document 2 ⁇ using a mobility management or a session management backoff mechanism.
  • An exemplary EPS network 110 is shown in Fig.
  • PGW Packet Data Network Gateway
  • MME Mobility Management Entity
  • IWF MTC Inter-Working Function
  • eNB 150 and 152 NB: Node B, BS: Base Station.
  • Mobile devices also known as User Equipment or UE 100, 102 and 104 obtain communication services from the 3GPP network by attaching to the radio access network of the base stations eNB 150 and 152, as shown by the attachment 190, 192 and 194.
  • the interface 170 allows packet forwarding on the User Plane (U-Plane) between the PGW 120 and SGW 130.
  • the interfaces 174 and 176 allow packet forwarding between the SGW 130 and the respective base stations of the mobile devices. To do so, one or more EPS bearers are established between the PGW 120 and the mobile device through the SGW 130 and eNB 150.
  • the interface 172 between SGW 130 and MME 140, and the interfaces 178 and 180 between MME 140 and the base stations eNB 150 and 152 allow Control Plane (C-Plane) signaling to be performed.
  • C-Plane Control Plane
  • the C-plane interfaces allow the SGW to send a downlink data notification to the MME 140, and the MME 140 can send paging messages to trigger device 100 to establish connection via the base stations eNB 150.
  • the interfaces 184 and 182 allow control signals to be passed between the MTC Interworking Function (IWF) 142 and the MME 140 or PGW 120 respectively.
  • the IWF 142 provides certain access interfaces to a MTC server 160 that is outside of the network 110 through the interface 194. For example, when the server 160 wishes to send triggers to one of the devices, it may do so via the IWF 142.
  • Congestion control is used to limit the amount of mobility management (MM) signaling, such as location update or service request, or to limit the amount of session management (SM) signaling, such as the creation of new or modification of existing packet data network (PDN) connections / bearer.
  • MM mobility management
  • SM session management
  • PDN packet data network
  • Congestion control mechanism is also disclosed in ⁇ Patent Document 1 ⁇ , and general access control methods are disclosed in ⁇ Patent Document 2 ⁇ and ⁇ Patent Document 3 ⁇ .
  • the present disclosure provides for a server apparatus.
  • the server apparatus comprising a determination unit to determine whether congestion occurs or may occur or not in the network; a selection unit to, when it is determined that the congestion occurs or may occur, select a mobile terminal of the plurality of mobile terminals attempting to establish a new connection; and a transmission unit to transmit a first message to the selected mobile terminal, the first message including information indicating to refrain from establishment of the new connection.
  • the present disclosure has the advantage of reducing unnecessary signaling.
  • Fig. 1 illustrates the network architecture of a cellular network according to a prior art.
  • Fig. 2A shows the message sequence chart of a congestion backoff procedure.
  • Fig. 2B shows the message sequence chart of a cell-level preemption procedure.
  • Fig. 3 depicts a message sequence diagram of a congestion backoff procedure according to an example embodiment of the present disclosure.
  • Fig. 4A depicts a message sequence diagram of the server procedure to detect network congestion according to an example embodiment of the present disclosure.
  • Fig. 4B depicts a message sequence diagram of the server procedure to detect network congestion according to an example embodiment of the present disclosure.
  • Fig. 5A depicts a message sequence diagram of a device triggering procedure during preemption according to an example embodiment of the present disclosure.
  • FIG. 5B depicts a message sequence diagram of a device triggering procedure during preemption according to an example embodiment of the present disclosure.
  • Fig. 6A depicts an approach to providing bearer release indication according to an example embodiment of the present disclosure.
  • Fig. 6B depicts an approach to providing bearer release indication according to an example embodiment of the present disclosure.
  • Fig. 7A depicts an approach to detecting the device that is using re-allocated resources during congestion backoff according to an example embodiment of the present disclosure.
  • Fig. 7B depicts an approach to detecting the device that is using re-allocated resources during congestion backoff according to an example embodiment of the present disclosure.
  • FIG. 7C depicts an approach to detecting the device that is using re-allocated resources during congestion backoff according to an example embodiment of the present disclosure.
  • Fig. 7D depicts an approach to detecting the device that is using re-allocated resources during congestion backoff according to an example embodiment of the present disclosure.
  • Fig. 8A depicts a device behavior upon receiving a condition trigger during preemption according to an example embodiment of the present disclosure.
  • Fig. 8B depicts a device behavior upon receiving a condition trigger during preemption according to an example embodiment of the present disclosure.
  • Fig. 8C depicts a device behavior upon receiving a condition trigger during preemption according to an example embodiment of the present disclosure.
  • Fig. 9A depicts a network approach during congestion backoff or preemption according to an example embodiment of the present disclosure.
  • Fig. 9B depicts a network approach during congestion backoff or preemption according to an example embodiment of the present disclosure.
  • Fig. 10 shows an example architecture of the server according to an example embodiment of the present disclosure.
  • Fig. 11 shows an example architecture of a mobile device according to an example embodiment of the present disclosure.
  • server may, but not limited to, mean MTC server.
  • mobile device or simply “device” may, but not limited to, mean “MTC devices” or simply User Equipment.
  • present disclosure may be practiced without these specific details.
  • session management congestion control may be initiated. This is shown in Fig. 2A, starting with the server 160 sending a device trigger request 210 to the IWF 142.
  • the IWF 142 then proceeds to send the device trigger 212 to the MME 140, which will process it and deliver the device trigger 214 to mobile device 100.
  • the IWF can select from SMS (Short Message Service), control plane signaling such as NAS (Non-Access Stratum) signaling and user plane such as data packet.
  • SMS Short Message Service
  • control plane signaling such as NAS (Non-Access Stratum) signaling
  • user plane such as data packet.
  • the IWF 142 selects the way to send the device trigger 214 over the interface between the IWF 142 and MME 140, and then the MME 140 transmits the device trigger to the mobile device 100 over the NAS signaling.
  • PDN Packet Data Network
  • Bearer resource allocation / modification request a session management signaling (Packet Data Network (PDN) connectivity request message 216 or Bearer resource allocation / modification request). Since the network is congested, MME 140 rejects this request with the message 218. In message 218, a backoff timer is given. This backoff timer will restrict the mobile device 100 from initiating further session management signaling until the backoff timer has expired, as indicated by process 220.
  • PDN Packet Data Network
  • the mobile device 100 Upon expiry, the mobile device 100 then repeats the SM signaling for new PDN connection establishment procedure or Bearer establishment/modification/deactivation procedure (BEARER RESOURCE ALLOCATION REQUEST/BEARER RESOURCE MODIFICATION REQUEST/DEACTIVATE EPS BEARER CONTEXT REQUEST) starting with message 222. Assuming network congestion has been resolved, MME 140 will accept this request message, and proceed to create a new PDN connection or a new/modified bearer by sending the create session request 224 to SGW 130, which is relayed as message 226 to the PGW 120. After the response message 228 from the PGW 120 has been received by the mobile device 100 as message 230, the PDN connection is established, and the device 100 can start sending uplink data 232 through this newly created PDN connection.
  • Bearer establishment/modification/deactivation procedure BEARER RESOURCE ALLOCATION REQUEST/BEARER RESOURCE MODIFICATION REQUEST/DEACTIV
  • the congestion control may be initiated for the mobility management signaling such as Attach Request, Detach Request, Service Request and Tracking/Routing Area Update.
  • the Device Trigger 212 will cause MME to send a paging to the mobile device 100. This paging will cause Service Request, which is a mobility management message. If the MME 140 is performing mobility management congestion control, MME 140 rejects this Service Request with the message 218. Upon expiry, the mobile device 100 then repeats the Service Request procedure as message 222. Assuming network congestion has been resolved, MME 140 will accept this request message, and proceed to send the bearer modification request as message 224 to SGW 130, which is relayed as message 226 to the PGW 120. After the response message 228 from the PGW 120 has been received by the mobile device 100 as message 230, the bearer/PDN connection is activated, and the device 100 can start sending uplink data 232 through this activated bearer/PDN connection.
  • the congestion control may be initiated by the radio resource limitation.
  • a mobile device's radio bearer corresponding to a dedicated bearer may be released by the eNB due to the preemption.
  • the mobile device may start dedicated bearer request but may be rejected by the MME. This is illustrated in Fig. 2B.
  • device 100 has a dedicated EPS bearer as indicated by process 240.
  • eNB 150 performs preemption, releasing resource of device 100 in order to allocate it to device 104.
  • the eNB 150 performs the preemption procedure 250 when there is resource limitation as indicated by the process 248.
  • the eNB 150 first checks the Allocation and Retention Priority (ARP) values as indicated by process 252.
  • ARP Allocation and Retention Priority
  • the eNB 150 will need to inform device 100 (as shown by the radio resource control reconfiguration message 254), device 104 (as shown by the radio resource control reconfiguration message 258) and MME 140 (as shown by the indication 256).
  • Server 160 will notice the communication with device 100 fails. However, the server 160 does not know why bearer was released. As such, the server may trigger the device to establish the dedicated bearer again, causing unnecessary signaling since any subsequent attempts at establishing dedicated bearer would fail as long as the congestion situation at the network is not relieved.
  • the server may perform steps as described below in order to reduce such unnecessary signaling.
  • the server 160 determines if there is congestion in the network. If the server 160 determines that congestion has happened or the congestion is going to happen, the server 160 sends device trigger requesting backoff to selected devices which may initiate mobile originated session management / mobility management signaling in step 310. Once selected, the server sends a device trigger request 320 to network 110, which would forward the device trigger 325 to the selected device (say, device 100).
  • the server can include information which would indicate to the recipient that a session management/mobility management backoff should be enforced. This information can be included in the container for application information in the device trigger message.
  • the message itself can be formatted as a dedicated control message only for the request of back-off (e.g. Device Back-off Trigger) which is similar to the reject message including a back-off timer) transmitted over the interface between the server and the network 110.
  • back-off e.g. Device Back-off Trigger
  • the device 100 receives the device trigger 325, the device 100 would not be sending session management/mobility management signaling as indicated by process 330 during some backoff period.
  • the server 160 Once the server 160 has determined that congestion condition has been relieved in process 340, it can then send another device trigger request 350 to the device 100 via the network 110.
  • the device 100 upon receiving the device trigger 355, will then know that the session management / mobility management backoff is no longer in effect.
  • the device can then resume sending session management signaling, such as sending a request 360 for dedicated bearer.
  • the server 160 can determine that there is congestion in the network.
  • the server may receive indication from the network or from the mobile devices. These are illustrated in Fig. 4A and Fig. 4B.
  • the server 160 may first send a registration request 410 to the network 110 to ask for congestion indications to be sent by the network whenever one of the specified mobile devices have met with congestion. Such a request can be sent only once, or pre-installed at the time of subscription.
  • the network 110 When a device, say device 100, meets a congestion situation 422 in the network 110 (such as the request 420 sent by device 100 is rejected with a backoff timer), the network 110 would then send a congestion indication 424 to the server 160. Alternatively, the network may send congestion indication to the server when the network predicts (based on the current consumption level of network resources) that congestion is going to happen. In Fig. 4B, a prior registration is not necessary. Whenever a device, say device 100, meets a congestion situation 452 in the network 110 (such as the request 450 sent by device 100 is rejected with a backoff timer), the network 110 would then record that device 100 has been backoff.
  • a congestion situation 422 in the network 110 such as the request 420 sent by device 100 is rejected with a backoff timer
  • the network 110 can immediately checked if the recipient of the device trigger has been backoff or if there is congestion in the network 110. If so, the network 110 can reject the trigger request 460 with a congestion indication 462.
  • the network includes the cause of congestion in the congestion indication which is informed to the server 160.
  • the cause of congestion indicates which network node is suffering from the congestion, the MME 140 or the IWF 142. If the indication indicates the congestion in the MME, the server can know that the MME 140 suffers from the congestion (e.g. congestion for mobility management signaling). Therefore, in this case, the server sends the device trigger to the mobile devices. This trigger requests not to send session management / mobility management signaling to the network. On the other hand, if the indication indicates the congestion in the IWF (or the interface between the server and the IWF) which means that the congestion is cased by the IWF, the server suppresses (stop/delay) sending the device trigger requests to the IWF.
  • the congestion indication can inform the congestion only for the general congestion which is not APN-based congestion
  • the congestion in the MME included in the congestion indication is applied to only the general mobility management congestion. Therefore, based on the indication, the server can decide to suppress the initiation of data packets, or suppress sending data packets to mobile devices that the server knows are currently in idle mode. This is because downlink packets sent to mobile devices will trigger paging of the mobile devices and thus service requests from the mobile devices.
  • network 110 can simply bring a copy of the principle to test its authenticity.
  • the actual network node(s) that sends the congestion indication 424/462 may be the MME 140 or IWF 142.
  • the MME 140 can reject the device trigger request 460 and inform the congestion indication 424/462.
  • the IWF142 can reject the device trigger request 460 and inform the congestion indication 424/462.
  • the server 160 may also determine congestion occurs or is going to occur through the server's internal determination, such as based on condition of communication with devices, for example, how many device triggers were sent and how many bearers were established. A person skilled in the art would also appreciate that similar ways are available for the server to determine that the congestion situation is relieved in process 340.
  • the server must next decide which devices need to be backoffed in process 310.
  • the server may select the target devices such as the device that are already communicating with the server since the device in connected mode may send SM signaling (e.g. new bearer establishment procedure) in order to start new communication with the server 160 soon; the devices that are preempted since the device may send SM signaling (e.g. new bearer establishment procedure), or the devices when access not yet started since the device may send SM signaling (e.g. new bearer establishment procedure) in order to initiate mobile originated communication soon.
  • SM signaling e.g. new bearer establishment procedure
  • congestion detection process 300 various example approaches are listed for the congestion detection process 300, target device selection process 310, and congestion relief detection process 340. A person skilled in the art would appreciate that any combination of the above processes may be practiced in actual implementation.
  • Fig. 5A and Fig. 5B shows a more detailed realization of the present disclosure.
  • device 100 already has a dedicated bearer established as indicated by process 500.
  • the server 160 may send a device trigger 510/512 to another device 104.
  • device 104 decides to set up a new dedicated bearer.
  • the request 514 is sent.
  • device 100 and device 104 are located in the same cell, and the cell is currently congested such that the network 110 performs the preemption procedure 250 to release the dedicated bearer of device 100 and allocates the resource to device 104 instead.
  • the server 160 will receive a bearer release indication indicated that the network initiated bearer release has been performed, as shown by process 530.
  • the bearer release indication 610 can be sent by the network 110 to the server 160.
  • the base station eNB 150 When the base station eNB 150 performs the preemption 250, it will send a bearer release indication to the MME 140.
  • This bearer release indication can indicate that the bearer release has been performed due to the preemption.
  • the MME 140 Upon receiving this indication from the base station eNB 150, the MME 140 can then transmit a bearer release indication to the server via the IWF 142. In this case the MME 140 may start bearer release procedure to the SGW 130 and PGW 120.
  • the MME 140 upon receiving the bearer release indication from the base station eNB 150, the MME 140 informs the SGW 130 to tear down the preempted bearer. When this bearer tear down reaches the PGW 120, the PGW 120 can send a bearer release indication to the server 160.
  • the device 100 when the dedicated bearer of device 100 is preempted, the device 100 will receives indication from the network in the form of a radio resource control re-configuration message. The device 100 can then send an application-layer bearer release indication 620 indicating the network initiated bearer release has been performed to server 160 via its default bearer.
  • the server 160 After receiving the bearer release indication in process 530, the server 160 then determines the details of the bearer release in process 532. Here, the server 160 needs to determine if the bearer release has been performed by the preemption and if other devices registered with the server has preempted device 100. There are various approaches how the server 160 can make such a determination. These would be described later with the aid of Fig. 7A, Fig. 7B, and Fig. 7C.
  • the server 160 will next send device 100 a device trigger 540. This device trigger 540 will specify the conditions which must be specified before device 100 should respond to the trigger. Various possible conditions are described later with the aid of Fig. 8A, Fig. 8B, and Fig. 8C. Once the conditions are satisfied in process 550, device 100 will then attempts to set up its dedicated bearer with the request 552.
  • the server 160 may detect in process 560 that device 104 has completed its transmission and had tear down its dedicated bearer or has changed the cell. In this case, it is possible that the released resources from device 104 can then be allocated to device 100. Hence, the server 160 can send a second device trigger 562 to device 100. This second device trigger 562 will cause device 100 to abort the prior trigger 540 with condition, and immediately respond with a request 564 for a dedicated bearer.
  • Other possibilities of new dynamic change detected by the server 160 in process 560 that will cause the server 160 to send the second trigger may include the detection of device 104 leaving the cell where device 100 is located, the detection of some other devices with dedicated bearers leaving the cell where device 100 is located, or the detection of some other devices located in the same cell as device 100 tearing down their dedicated bearers. These possibilities are based on the assumption that the resources in the cell where device 100 is located have been freed.
  • Fig 7A, Fig. 7B, Fig. 7C, and Fig. 7D show different ways in which the server 160 can determine which device pre-empted device 100.
  • the server can start a timer whenever it sends a trigger as illustrated in Fig. 7A.
  • the server 160 starts a timer 710 after sending a device trigger request 510 to device 104. If the bearer release indication 720 is received before the expiry of the timer 710, the server 160 can deduce that device 104 has preempted device 100 with reasonably high confidence since the device 104 which received the device trigger might have established a bearer by preempting the device 100.
  • the server 160 can start a timer whenever it receives a bearer release indication as illustrated in Fig. 7B.
  • the server 160 starts a timer 732 after receiving the bearer release indication 730. If the server 160 receives the start of data stream 740 over a dedicated bearer with one of the devices (say, device 104) before the expiry of timer 732, then the server 160 can deduce that device 104 has preempted device 100 with reasonably high confidence.
  • the server can compare the cells of each device with the cell of device 100 as illustrated in Fig. 7C.
  • each device will update the server 160 of the cell the device is currently in. This may be the cell-ID broadcasted by each base station.
  • the server 160 can then compares the cell-ID of each device which may have preempted the device 140 with the cell-ID of device 100, as illustrated by the process 752 in Fig. 7C.
  • the bearer release indication 750 is assumed to contain information for identifying device 100.
  • the bearer release indication 750 may further contain the cell-ID of the cell where preemption has taken place.
  • the server can compare the guaranteed bit rate (GBR) of the dedicated bearer that is pre-empted and compare this GBR with the GBR of any newly started dedicated bearer communications as shown in Fig. 7D.
  • the bearer release indication 760 contains the GBR of the bearer that is released.
  • the server 160 compared this GBR value with the GBR of the newly started dedicated bearer session, as illustrated in process 772.
  • the server 160 can deduce that the device 104 has preempted device 100 with higher confidence.
  • the server 160 may start a timer after receiving the bearer release indication, while also compare the cell-ID of all the devices.
  • Fig. 8A, Fig. 8B and Fig. 8C shows examples of triggers with different conditions that the server 160 can send.
  • the server 160 may send a trigger 840 containing the condition of a cell change. This will let the recipient knows that it should attempt to re-establish its dedicated bearer only when it has change its cell.
  • the device 100 transmits a request 552 for dedicated bearer.
  • the condition contained in the trigger may be the drop of monitored cell activity to below a certain specified value. This means that the device will record the cell activity upon being pre-empted. This is shown as the process 832.
  • the device 100 After being pre-empted, the device 100 will then monitor the cell activity. When the device 100 has monitored the cell level to drop below the level specified by the condition in the received trigger as indicated by process 852, it can then request for new dedicated bearer. Finally, the condition contained in the trigger may simply be a timeout value, as illustrated in Fig. 8C.
  • the server 160 sends the trigger 844 with condition of timeout to device 100
  • the device 100 first starts a timer 834. When this timer 834 has expired (as shown as 854), the device 100 can then send the request 552 for a new dedicated bearer.
  • the base station can informs Device 100 who preempted its bearer, Device 100 then informs this to the Server 160 in the application-level release indication.
  • eNB or device 100 may need identifiers mapping function in this case in order to map the identifiers used between the eNB and the mobile devices to the identifiers used between the network or external entities (such as server 160).
  • Another possibility is for the network to inform the server 160 who pre-empted device-100.
  • the eNB informs MME that Device 100 has been pre-empted by Device-104.
  • MME checks if Device 104 belongs to the same server. If same, the MME informs the Server that Device 100 has been preempted by Device 104.
  • the MME simply informs the Server that Device 100 is preempted (but not by who).
  • the server can then choose to ask network to send indication when the preemptor changes cells or tear down and the server (or Device 100) requests the network/eNB to send an indication when device 104 leaves the cell or when device-104 tear downs its bearer.
  • timers can be used to detect if a device's bearer has been preempted (and by who) in previous descriptions.
  • the server can ask the network for hints on the timer value. This makes use of some features (e.g. UPCON or U-Plane congestion) where network will monitor the traffic on the mobile device's data plane. Hence, network may have some empirical statistics on how long device 104 will use the dedicated bearer.
  • preemption is performed by the base stations at a cell level.
  • preemption can also be performed by the MME at a EPS-wide level where upon receiving the bearer set-up request from one mobile device, the MME may select, if resources are limited, the bearer of another mobile device to be released such that the associated resources may be allocated to the first mobile device.
  • Various aspects of the present disclosure can still be applied when the MME performs such forms of EPS-wide preemption.
  • the network 110 delays forwarding of device trigger 910 sent from the server 160 until after the congestion is released. This is indicated by the suspense process 912 and resume process 920.
  • the node in network 110 that performs such suspense and resume process can be the MME 140 or the IWF 142.
  • the MME needs to know the APN of the device trigger, then decides whether to forward the device trigger or suspend it based on whether the APN is currently congested.
  • the MME can remember this so that device triggers for this device will be suspended.
  • Such suspension can also be used for dedicated bearer request initiated by the device 100 without a device trigger.
  • the server 160 instead of sending a trigger request 910 through the network, sends an application layer trigger 950 directly to the device 100 (e.g. using the established default bearer of the device 100). This will cause the device 100 to initiate a request 952 for dedicated bearer.
  • the network 110 upon recognizing the congestion or preemption situation from process 900, will suspend this dedicated bearer request as shown by process 954. Only until the congestion situation is relieved, then the network 110 performs the resume process 960 and proceeds to establish the dedicated bearer.
  • process 900 is a preemption of device 100 dedicated bearer to be allocated to, say device 104
  • the MME can store the preemption related information such as "Device 104 borrows resource from Device 100"). Subsequently, when the server 160 sends a new trigger or when device 100 asks for dedicated bearer, the MME will suspend the request until Device 104 releases the resource. The MME then re-allocate the released resource to Device 100.
  • Fig. 10 shows an example architecture 1000 of the server 160 according to an example embodiment of the present disclosure, comprising of a Communications Interface 1010, a Congestion Indication Receiving Means 1020, a Target Device Selection Means 1030, and a Conditional Triggering Means 1040.
  • Communications Interface 1010 is a functional block comprises of the hardware and firmware necessary to enable the server to communicate with other nodes. It may include the antenna, transmitting circuitry and receiving circuitry.
  • Congestion Indication Receiving Means 1020 receives congestion indication from the network or mobile device. When congestion or preemption is detected, the Target Device Selection Means 1030 is triggered to select the mobile device for triggering.
  • Condition Triggering Means 1040 sets up and transmit conditional device triggers to mobile devices.
  • Fig. 11 shows an example architecture 1100 of a mobile device according to an example embodiment of the present disclosure, comprising of a Communication Interface 1110, a Conditional Trigger Receiving Means 1120, a Condition Checking means 1130, a Bearers Setup Means 1140, and a Signaling Suppression Means 1150.
  • Communications Interface 1110 is a functional block comprises of the hardware and firmware necessary to enable a device to communicate with the cellular base station. It may include the antenna, transmitting circuitry and receiving circuitry. It also implements the radio access control and signalling to the cellular radio network, and the transport of data packets over the cellular radio access. It is obvious to anyone skilled in the art that this does not preclude the system to be used in a wired environment, i.e. the Communication Interface 1110 can be replaced with wired transmission means. It is also possible that the Communications Interface 1110 is in fact running on top of another layer of communication stack, e.g. the Unlicensed Mobile Access (UMA) or any variance of the Generic Access Network (GAN).
  • UMA Unlicensed Mobile Access
  • GAN Generic Access Network
  • the Communication Interface 1110 also comprises the protocol for the Non-Access Stratum (NAS) layer that implements the control plane signalling and initiation of user plane transport of data between the mobile device and the cellular network.
  • NAS Non-Access Stratum
  • the Conditional Triggering Receiving Means 1120 allows the mobile device to receive triggers with conditions sent from the server. It processes the conditions specified in a received trigger, and if necessary, sets up the Condition Checking Means 1130 to check for fulfillment of conditions and Signaling Suppression Means 1150 to suppress the injection of signaling (e.g. SM messages) to the network while conditions are not fulfilled.
  • Signaling Suppression Means 1150 to suppress the injection of signaling (e.g. SM messages) to the network while conditions are not fulfilled.
  • the Condition Checking Means 1130 checks for the fulfillment of conditions as specified by the Conditional Triggering Receiving Means 1120. When conditions are fulfilled, the Condition Checking Means 1130 may trigger the Bearers Setup Means 1140 to send request for dedicated bearer to the network.
  • the Bearers Setup Means 1140 sends request to the network for setting up of dedicated bearers.
  • the Signaling Suppression Means 1150 suppresses control-plane messages sent to the network when a condition associated with a condition trigger is not yet fulfilled.
  • the 3GPP evolved packet system architecture is assumed with the use of network architectural elements such as the MME, PGW and SGW.
  • MME Mobility Management Entity
  • PGW Packet Data Network
  • SGW Serving Gateway
  • the disclosure may be applied to any other packet-switched network architectures, such as the 3GPP2, WiMax, the Generalized Packet Radio Service (GRPS) system, which involve the installation of filters to direct packets into different bearers or carrier mediums.
  • GRPS Generalized Packet Radio Service
  • the transmission unit transmits a second message to the mobile terminal, the second message prompting to establish the new connection.
  • the determination unit determines whether congestion occurs or may occur or not in the network on a basis of congestion information indicating a congestion situation in the network transmitted from a predetermined apparatus in the network.
  • the determination unit determines that the congestion is released on a basis of congestion released information indicating that congestion in the network is released transmitted from a predetermined apparatus in the network.
  • the determination unit determines whether congestion occurs or may occur or not in the network on a basis of information indicating that a connection with the mobile terminal is released, transmitted from a predetermined apparatus or the mobile terminal in the network.
  • the selection unit when selecting the mobile terminal attempting to establish a new connection, selects the mobile terminal with which the connection is released.
  • the determination unit determines that the congestion is released.
  • the determination unit determines whether congestion occurs or may occur or not in the network on a basis of information indicating that a connection with the mobile terminal is released, transmitted from a predetermined apparatus or the mobile terminal in the network, when selecting the mobile terminal attempting to establish a new connection, the selection unit selects the mobile terminal with which the connection is released, and in the case of releasing a connection with a mobile terminal other than the mobile terminal with which the connection is released, the determination unit determines that the congestion is released.
  • the present disclosure provides for a communication control method.
  • the communication control method comprising the steps of: a determination step of determining whether congestion occurs or may occur or not in the network; a selection step of, when it is determined that the congestion occurs or may occur, selecting a mobile terminal of the plurality of mobile terminals attempting to establish a new connection; and a transmission step of transmitting a first message to the selected mobile terminal, the first message including information indicating to refrain from establishment of the new connection.
  • determination as to whether congestion occurs or may occur or not in the network is made on a basis of congestion information indicating a congestion situation in the network transmitted from a predetermined apparatus in the network.
  • releasing of the congestion is determined on a basis of congestion released information indicating that congestion in the network is released, transmitted from a predetermined apparatus in the network.
  • determination as to whether congestion occurs or may occur or not in the network is made on a basis of information indicating that a connection with the mobile terminal is released, transmitted from a predetermined apparatus or the mobile terminal in the network.
  • the mobile terminal with which the connection is released is selected.
  • determination as to whether congestion occurs or may occur or not in the network is made on a basis of information indicating that a connection with the mobile terminal is released, transmitted from a predetermined apparatus or the mobile terminal in the network, when selecting the mobile terminal attempting to establish a new connection in the selection step, the mobile terminal with which the connection is released is selected, and in the case of releasing a connection with a mobile terminal other than the mobile terminal with which the connection is released, releasing of the congestion is determined.
  • the above aspects may be implemented by combination. These aspects may be implemented by a program to let a computer implement the method and recording medium recorded the program in addition to the apparatus and the communication control method.
  • each functional block of Fig.10 and Fig.11 may be implemented by hardware such as CPU or memory of any computer.
  • any computer implements program that processes of each function are described, and the each functional block may be implemented.
  • flow charts or sequence charts of the above-mentioned embodiment may be implemented by hardware such as CPU or memory.
  • each functional block and each processing for sequence charts used in the description of the embodiments of the present disclosure as given above can be realized as LSI (Large Scale Integration), typically represented by the integrated circuit. These may be produced as one chip individually or may be designed as one chip to include a part or all. Here, it is referred as LSI, while it may be called IC, system LSI, super LSI, or ultra LSI, depending on the degree of integration.
  • LSI Large Scale Integration
  • the technique of integrated circuit is not limited only to LSI and it may be realized as a dedicated circuit or a general-purpose processor.
  • FPGA Field Programmable Gate Array
  • a reconfigurable processor in which connection or setting of circuit cell inside LSI can be reconfigured, may be used.
  • the functional blocks may be integrated by using such technique. For example, the adaptation of biotechnology is one of such possibilities.
  • the disclosure has the advantage of reducing unnecessary signaling. Therefore, the disclosure can be advantageously used as the update of routing policies for a large group of communication devices.

Abstract

La présente invention se rapporte à un appareil formant serveur qui communique avec une pluralité de terminaux mobiles via un réseau. L'appareil formant serveur selon l'invention comprend : un module de détermination, qui est utilisé afin de déterminer si une congestion a lieu ou peut avoir lieu, ou non, au sein du réseau ; un module de sélection qui, quand il est déterminé que la congestion a lieu ou peut avoir lieu, sélectionne un terminal mobile parmi la pluralité de terminaux mobiles qui tentent d'établir une nouvelle connexion ; et un module de transmission, qui est utilisé afin de transmettre un premier message au terminal mobile sélectionné, le premier message contenant des informations qui indiquent qu'il faut éviter d'établir la nouvelle connexion.
PCT/JP2012/007977 2012-01-30 2012-12-13 Appareil et procédés pour optimiser une utilisation des ressources pour une pluralité de dispositifs de communication WO2013114504A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2012-017144 2012-01-30
JP2012017144 2012-01-30

Publications (1)

Publication Number Publication Date
WO2013114504A1 true WO2013114504A1 (fr) 2013-08-08

Family

ID=47520218

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2012/007977 WO2013114504A1 (fr) 2012-01-30 2012-12-13 Appareil et procédés pour optimiser une utilisation des ressources pour une pluralité de dispositifs de communication

Country Status (1)

Country Link
WO (1) WO2013114504A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015026109A1 (fr) * 2013-08-18 2015-02-26 엘지전자 주식회사 Procédé et dispositif destinés à annuler le déclenchement d'un dispositif dans un système de communication sans fil
WO2016060809A1 (fr) * 2014-10-16 2016-04-21 Qualcomm Incorporated Commande de préemption de transmission pour des composantes porteuses améliorées
US10129689B2 (en) 2015-11-02 2018-11-13 Definition Networks, Inc. Systems and methods for machine-type communication

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1615394A1 (fr) * 2004-07-06 2006-01-11 Motorola, Inc. Méthode et appareil pour la gestion de perte de données en paquets dans un réseau sans fil
US20100037284A1 (en) 2005-06-28 2010-02-11 Joachim Sachs Means and method for controlling network access in integrated communications networks
US20110007713A1 (en) 2008-02-05 2011-01-13 Panasonic Corporation Mobile communication device and mobile communication method
WO2011100540A1 (fr) 2010-02-12 2011-08-18 Interdigital Patent Holdings, Inc. Contrôle d'accès et contrôle de congestion dans des communications de machine à machine

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1615394A1 (fr) * 2004-07-06 2006-01-11 Motorola, Inc. Méthode et appareil pour la gestion de perte de données en paquets dans un réseau sans fil
US20100037284A1 (en) 2005-06-28 2010-02-11 Joachim Sachs Means and method for controlling network access in integrated communications networks
US20110007713A1 (en) 2008-02-05 2011-01-13 Panasonic Corporation Mobile communication device and mobile communication method
WO2011100540A1 (fr) 2010-02-12 2011-08-18 Interdigital Patent Holdings, Inc. Contrôle d'accès et contrôle de congestion dans des communications de machine à machine
US20110199905A1 (en) * 2010-02-12 2011-08-18 Interdigital Patent Holdings, Inc. Access control and congestion control in machine-to-machine communication

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access", 3GPP TS 23.401V10.4.0, June 2011 (2011-06-01)
3GPP: "Service Requirements for Machine-Type Communications (MTC); Stage I(3GPP TS 22.368vl 1.2.0)", June 2011 (2011-06-01)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015026109A1 (fr) * 2013-08-18 2015-02-26 엘지전자 주식회사 Procédé et dispositif destinés à annuler le déclenchement d'un dispositif dans un système de communication sans fil
CN105474739A (zh) * 2013-08-18 2016-04-06 Lg电子株式会社 在无线通信系统中取消设备触发的方法和设备
US9967905B2 (en) 2013-08-18 2018-05-08 Lg Electronics Inc. Method and device for cancelling device trigger in wireless communication system
CN105474739B (zh) * 2013-08-18 2019-11-29 Lg 电子株式会社 在无线通信系统中取消设备触发的方法和设备
WO2016060809A1 (fr) * 2014-10-16 2016-04-21 Qualcomm Incorporated Commande de préemption de transmission pour des composantes porteuses améliorées
US10149293B2 (en) 2014-10-16 2018-12-04 Qualcomm Incorporated Transmission preemption for enhanced component carriers
US10499394B2 (en) 2014-10-16 2019-12-03 Qualcomm Incorporated Transmission preemption for enhanced component carriers
US10959226B2 (en) 2014-10-16 2021-03-23 Qualcomm Incorporated Transmission preemption for enhanced component carriers
US10129689B2 (en) 2015-11-02 2018-11-13 Definition Networks, Inc. Systems and methods for machine-type communication

Similar Documents

Publication Publication Date Title
CN110447250B (zh) 用于无线通信系统中层之间交互的方法及其设备
US11589208B2 (en) Method for transmitting data in CIoT system and device therefor
EP3402299B1 (fr) Dispositif d'utilisateur et procédé d'émission de données associé, et noeud de réseau et procédé d'émission de données associé
KR101479895B1 (ko) 세션 관리 및 이동성 관리에 관련된 데이터를 처리하는 방법
US10681767B2 (en) Method and apparatus for performing RRC connection resume in wireless communication system
US9622178B2 (en) Method for processing data associated with idle mode signaling reduction in a wireless communication system
KR101771260B1 (ko) 이동 통신 시스템에서 사용자 단말의 접속 제어 방법 및 장치
JP7075061B2 (ja) ユーザ機器、モビリティ管理ノード、およびその通信方法
EP3419319A1 (fr) Transmission de demande de service et équipement d'utilisateur, et réception de requête de service et station de base
JP2020502954A (ja) 無線通信システムにおけるｖ２ｘ通信を行う方法及びこのための装置
EP3407645A1 (fr) Procédé pour commander une congestion dans un système de communication sans fil et dispositif pour ce dernier
US10575318B2 (en) Data transmission method and user equipment, and data reception method and base station
US20190182789A1 (en) Method for performing location registration by remote ue in wireless communication system, and apparatus therefor
CN106416417B (zh) 用于在无线网络中建立非活跃定时器的节点和方法
EP2739111A2 (fr) Procédé permettant de sélectionner et d'établir un trajet de communication D2D dans des réseaux capillaires MTC
EP3435699B1 (fr) Procédé de transmission de message, et équipement d'utilisateur
US20190342735A1 (en) Access control and scheduling mechanism for mtc devices
EP3342198A1 (fr) Commandes d'at améliorées pour régulation de temporisation de repli
WO2011135790A1 (fr) Dispositif de communication et nœud de réseau
WO2013114504A1 (fr) Appareil et procédés pour optimiser une utilisation des ressources pour une pluralité de dispositifs de communication
WO2013145519A1 (fr) Appareil et procédés de gestion de ressources parmi de multiples dispositifs de communication

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: 12812404

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

NENP Non-entry into the national phase

Ref country code: JP

122 Ep: pct application non-entry in european phase

Ref document number: 12812404

Country of ref document: EP

Kind code of ref document: A1