WO2016074724A1 - Atténuation de l'encombrement dans un réseau de communication - Google Patents

Atténuation de l'encombrement dans un réseau de communication Download PDF

Info

Publication number
WO2016074724A1
WO2016074724A1 PCT/EP2014/074466 EP2014074466W WO2016074724A1 WO 2016074724 A1 WO2016074724 A1 WO 2016074724A1 EP 2014074466 W EP2014074466 W EP 2014074466W WO 2016074724 A1 WO2016074724 A1 WO 2016074724A1
Authority
WO
WIPO (PCT)
Prior art keywords
network node
node
wireless device
embms
network
Prior art date
Application number
PCT/EP2014/074466
Other languages
English (en)
Inventor
Xiaohui Wang
Mårten ÅKERMAN
Original Assignee
Telefonaktiebolaget L M Ericsson (Publ)
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 Telefonaktiebolaget L M Ericsson (Publ) filed Critical Telefonaktiebolaget L M Ericsson (Publ)
Priority to PCT/EP2014/074466 priority Critical patent/WO2016074724A1/fr
Publication of WO2016074724A1 publication Critical patent/WO2016074724A1/fr

Links

Classifications

    • 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/12—Avoiding congestion; Recovering from congestion
    • H04L47/122—Avoiding congestion; Recovering from congestion by diverting traffic away from congested entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]

Definitions

  • the embodiments of the present invention relates to congestion mitigation in wireless communication networks, and in particular to handling of congestion during
  • a service request from a wireless device may be rejected by the network, and even ongoing sessions can be dropped.
  • Congestion may occur in a network for many i o different reasons. Some examples are e.g. high demands in a relatively small area during rush hour or sport events, or, during events of great national or international interest, such as the Olympic Games or political issues. Another reason for congestion may be emergency situations. In some emergency situations, network infrastructures may be damaged and thus decrease the capacity of the
  • service requests may instead be rejected by the network, and on-going sessions may be dropped.
  • the document describes a method where: when a large number of users requests the same web page at approximately the same time, a 30 gateway provides the web page to an RA node for distribution via broadcast instead of via a plurality of unicast channels, which implies a more efficient use of radio resources. However, at severe congestion, the requests for the web page would not even reach the gateway, since they would be rejected before that.
  • a method for network congestion mitigation.
  • the method is to be performed by a network node in a communication network.
  • the method comprises entering a congestion mitigation mode, CMM, and further receiving a service request originating from a wireless device.
  • the method further comprises redirecting the wireless device to a predefined eMBMS session in response to said service request; when the service request fulfills a criterion related to priority.
  • a method for supporting congestion mitigation.
  • the method is to be performed by a network node in a communication network,
  • the method comprises indicating, to another network node, a set of RA nodes being configured for access to eMBMS.
  • a method for supporting congestion mitigation.
  • the method is to be performed by a Radio Access, RA, node in a communication network.
  • the method comprises receiving an instruction from a network node in CMM mode to hand over a wireless device, currently served by the RA node, to another RA node.
  • the method further comprises initiating a handover of the wireless device to the other RA node in response to the received instruction.
  • a method is provided for supporting congestion mitigation. The method is to be performed by a network node in a communication network.
  • the method comprises receiving information indicating congestion in the communication network and signaling an instruction to enter a Congestion Mitigation Mode, CMM, to at least one network node in the communication network, based on the received information.
  • a network node is provided, which is configured for network congestion mitigation.
  • the network node is configured to enter a congestion mitigation mode, CMM and to receive a service request originating from a wireless device.
  • the network node is further configured to redirect the wireless device to a predefined eMBMS session in response to said service request, when the service request fulfills a criterion related to priority.
  • a network node which is configured for supporting congestion mitigation.
  • the network node is configured to indicate, to another network node, a set of RA nodes being configured for access to eMBMS.
  • a Radio Access, RA, node is provided, which is configured for supporting congestion mitigation, and is operable in a communication network.
  • the RA node is configured to receive an instruction from a network node in CMM mode to hand over a wireless device, currently served by the RA node, to another RA node; and further to initiate a handover of the wireless device to the other RA node in response to the received instruction.
  • a network node configured for supporting congestion mitigation, and is operable in a communication network.
  • the network node is configured to receive information indicating congestion in the communication network; and further to instruct a network node to enter a Congestion Mitigation Mode, CMM, based on the received information.
  • CMM Congestion Mitigation Mode
  • a computer program which comprises instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the aspects 1 -4.
  • a carrier which contains the computer program of the previous aspect.
  • Figure 1 shows an LTE network configured for eMBMS according to the prior art.
  • Figures 2-5 are flow charts showing methods performed by a network node according to exemplifying embodiments.
  • Figure 6 is a flow chart, showing a method performed by a network node according to an exemplifying embodiment.
  • Figure 7 is a flow chart, showing a method performed by a network node according to an exemplifying embodiment.
  • Figure 8 is a flow chart, showing a method performed by a network node according to an exemplifying embodiment.
  • Figures 9-12 a-c illustrate different implementations of network nodes according to exemplifying embodiments.
  • the inventors have realized that an alternative to rejecting or dropping non-prioritized users during highly congested situations, is to instead redirect such users to a broadcast service, such as enhanced Multimedia Broadcast Multicast Service, eMBMS, in LTE systems.
  • a broadcast service such as enhanced Multimedia Broadcast Multicast Service, eMBMS
  • eMBMS enhanced Multimedia Broadcast Multicast Service
  • the solution disclosed herein is primarily intended for LTE networks, and will mainly be described herein in terms of LTE. However, the solution is also applicable in other types of systems having similar broadcast services, such as FeMBMS (Further enhanced MBMS) to be specified, e.g. in 5G.
  • the LTE broadcast service eMBMS
  • MBSFN Multicast-broadcast single-frequency network
  • eMBMS provides transport features for sending the same content information to a plurality of users. For example, content could be sent to all users in a cell via broadcast, or, to a given set of users in a cell via multicast. A subset of the available radio resources in a cell or network could be used for eMBMS, while the remaining available radio resources could be used to support transmissions towards a particular user, i.e. so-called unicast services.
  • eMBMS Radio Access, RA, node or multiple RA nodes for transmission to multiple wireless devices.
  • RA Radio Access
  • MBSFN Radio Access
  • a specific area where one or several RA nodes/cells transmit the same content is referred to as an MBSFN area.
  • LTE broadcast services A typical envisioned use for LTE broadcast services is the provision of video, e.g. TV, and other multimedia services, which require much capacity.
  • eMBMS reuses existing LTE spectrum for broadcast, which enables network operators to offer e.g. mobile TV without the need for additional expensive licensed spectrum, and without requiring new infrastructure and end-user devices.
  • the eMBMS service can offer many more TV programs in a specific radio frequency spectrum as compared to traditional terrestrial TV broadcasting, e.g. since eMBMS may be employed based on the principles of Interactive Multicast, such that TV content only is transmitted where there currently are viewers.
  • the eMBMS service also provides better system spectral efficiency than video-on-demand over traditional cellular unicasting services, since in eMBMS, each TV program is only transmitted once in each cell, also if there are several viewers of that program in the same cell.
  • the MBSFN transmission mode further improves the spectral efficiency, in that it is based on the principles of
  • Dynamic single frequency networks DSFN. This implies that it dynamically forms single-frequency networks, SFNs, i.e. groups of adjacent base stations sending the same signal simultaneously on the same frequency sub-carriers. This may be applied e.g. when there are mobile TV viewers of the same TV program content in the adjacent cells.
  • SFNs single-frequency networks
  • the LTE OFDMA downlink modulation and multiple access scheme eliminates self-interference caused by the SFN :s.
  • MBSFN is a transmission mode which exploits LTE's OFDM radio interface to send multicast or broadcast data as a multi-cell transmission over a synchronized single- frequency network, SFN.
  • the transmissions from the multiple cells are sufficiently tightly synchronized for each to arrive at the UE within the OFDM Cyclic Prefix so as to avoid Inter-Symbol Interference.
  • this makes the MBSFN transmission appear to a wireless device as a transmission from a single large cell, which dramatically increases the Signal-to-interference Ratio, SIR, due to the absence of inter-cell interference.
  • Figure 1 illustrates the architecture of an LTE network operable to provide eMBMS services.
  • the initiated reader may notice that there are some additional nodes, as compared to a regular LTE architecture. These additional nodes are outlined with a bold line in figure 1 , in order for them to be easier to identify.
  • the nodes should be seen as logical nodes or functions, rather than physical nodes. However, the nodes could also be implemented as physical nodes.
  • Figure 1 shows a wireless device 1 01 , also denoted “UE” in the figure.
  • the wireless device is served by an RA node 102, also denoted “eNB” in the figure.
  • the wireless device 101 may also be referred to as camping on a cell provided by the RA node, or as being connected to the RA node 102, or as being connected to the network via the RA node 1 02.
  • the RA node 1 02 is connected to a network node 1 03, also denoted Mobility Management Entity, MME.
  • MME Mobility Management Entity
  • the MME handles e.g. connection and release of bearers to a wireless device and also handles wireless device transitions between I DLE and ACTIVE state.
  • One MME is connected to a plurality of RA nodes, which in their turn may serve a plurality of wireless devices.
  • a Serving Gateway, S-GW, 107 connects the LTE core network, also denoted Evolved Packet Core, EPC, to the LTE Radio Access Network, RAN.
  • EPC Evolved Packet Core
  • RAN LTE Radio Access Network
  • P-GW, 108 Packet Data Network Gateway, P-GW, 108, connects the EPC to the internet 1 09, and/or some other Packet Data Network, PDN. So far, the described nodes are all part of a standard LTE architecture.
  • the nodes in figure 1 which are dedicated to LTE broadcast services, are the Multi- cell/Multicast Coordination Entity, MCE 104; the eMBMS Gateway, MBMS GW, 105; and the Broadcast Multicast Service Center, BM-SC, 106.
  • MCE 104 the Multi- cell/Multicast Coordination Entity
  • MBMS GW the eMBMS Gateway
  • BM-SC Broadcast Multicast Service Center
  • the MCE 104 is a logical node in the RAN handling allocation of radio resources and transmission parameters, such as time-frequency resources and transport format, across the cells in an MBSFN area.
  • the MCE 104 can control multiple RA nodes, each handling one or more cells.
  • the BM-SC 106 is located in the EPC, and is responsible for authorization and authentication of content providers, charging, and the overall configuration of the data flow through the core network.
  • the MBMS GW 105 is a logical node handling multicast of IP packets from the MB-SC 106 to all RA nodes involved in transmission in an MBSFN area.
  • the MBMS GW also handles session control signaling via the MME.
  • wireless device or “wireless terminal” encompasses any type of wireless node which is able to communicate with a network node, such as a base station, or with another wireless device by transmitting and/or receiving wireless signals.
  • wireless device encompasses, but is not limited to: a user equipment, a mobile terminal, a stationary or mobile wireless device for machine-to-machine communication, an integrated or embedded wireless card, an externally plugged in wireless card, a dongle, etc.
  • RA node as used in this disclosure is intended to encompass any type of radio base station, e.g. an eNB, NodeB, a pico or micro node, Home eNodeB or Home NodeB, or any other type of network node which is capable of wireless communication with a wireless device.
  • network node may refer to a wireless access point as defined above, but also encompasses other types of nodes residing in a wireless network and which are capable of communicating with one or more RA nodes, either directly or indirectly, e.g. a centralized network node performing one or more specific functions.
  • a network node may at the same time serve as a wireless access point, and also perform one or more additional functions on behalf of other nodes or access points in the network.
  • CMM Congestion Mitigation Mode
  • MME such as the MME 103 in the LTE network illustrated in figure 1
  • this functionality could be located in another network node, e.g. in another type of communication system.
  • Figure 2 illustrates a method performed by a network node operable in a
  • the method illustrated in figure 2 comprises entering 202 a CMM. This may be done in response to receiving 201 an instruction from another network node, e.g. an OSS node.
  • the action 201 has a dashed outline in figure 2, since it is not necessarily considered to be a part of the method.
  • the method further comprises receiving 203 a service request originating from a wireless device.
  • the term "originating from” here refers to that the service request is sent from a wireless device, but will probably be sent via an RA node, and therefore not be received directly from the wireless device.
  • the method in figure 2 further comprises, in response to the received service request, when the service request fulfills a criterion, redirecting 205 the wireless device to a predefined eMBMS session.
  • the MME being in the CMM mode, receives a service request, it determines whether the service request fulfills a criterion, e.g. related to priority.
  • the service request fulfills the criterion, e.g. has a certain (low) priority
  • the wireless device is redirected to a certain eMBMS service instead of being set up for the requested service.
  • the fulfilling of a criterion relates to that there are certain prioritized users and functions that should get regular service also in CMM mode. This is illustrated in figure 4, where it is determined whether the received service request is an emergency service request 403 or a priority service request 404.
  • Emergency service requests are e.g. requests associated with important functions, such as dialing 1 1 2 or 91 1 .
  • Priority service requests could be e.g. requests associated with hospitals, fire-fighters or other public or private functions defined as important.
  • users it could be possible for users to become priority subscribers in some other, e.g. monetary, way. Consequently, the method described above may comprise determining 403, 404 a priority of the received service request, and redirecting the wireless device to a predefined eMBMS session, only when the determined priority belongs to a predefined priority group.
  • the predefined priority group may be defined e.g. as comprising priorities related to non-prioritized users and non-prioritized services. In other words, the redirection may be performed e.g.
  • a priority threshold or a set of rules could, for example, be used to determine whether the priority of the service request belongs to the predefined priority group.
  • the alternative for service requests belonging to this priority group would be rejection.
  • CMM mode the service requests are instead redirected to eMBMS.
  • the CMM mode is a special mode, which should be regarded as a separate mode as compared to a "regular" mode, i.e. a mode in which the network node is in when operating according to regular procedure. Just as the network node may be triggered to enter the CMM mode at network congestion, the network node may later be triggered to exit the CMM mode and return to its regular mode, e.g. when the congestion situation is over.
  • the CMM mode is intended for use in situations of severe congestion, where service requests from ordinary users would otherwise have been rejected, or services, if set up, would have been dropped.
  • a service request which according to the method above would have been redirected to an eMBMS service, would probably have been rejected.
  • the method described above enables an informative alternative to rejection of the service request.
  • Users requesting e.g. a unicast service, a broadcast service or a call set-up will be redirected to a predefined broadcast service, which provides relevant information concerning e.g. an emergency situation.
  • the predefined broadcast service could e.g. be indicated or provided to the MME by the OSS together with the instruction to enter the CMM mode.
  • the OSS could provide information on the network set-up of the eMBMS sessions for emergency. There could be different information provided e.g. for different regions. The information could be updated e.g. by the OSS, when needed.
  • the information provided by the predefined eMBMS service could be of different types, such as video, text, audio or combinations thereof.
  • the information could be displayed on the wireless device as would the requested service.
  • the MME could send a notification, such as a flash SMS, to the wireless device when in CMM, to be displayed on the wireless device. A flash SMS appears on the display of a wireless device directly without user action.
  • not all RA nodes in a wireless communication network are configured for eMBMS.
  • the MME may initiate a handover of the wireless device to an RA node that is configured for access to eMBMS. This is illustrated in figure 3 as action 306.
  • the handover could be initiated by that the MME sends an instruction to the RA node serving the wireless device, that the wireless device should be handed over to another, specified RA node.
  • the RA node receiving the instruction should then assist in initiating a handover procedure and executing the handover even though there is no other indication of that a handover is needed.
  • the handover may be performed according to a regular handover procedure. Contrary to the conventional handover procedure based on the signal strengths of the RAs at the wireless devices, the procedure of handover to eMBMS enabled cells is based on the cell data stored in the MME.
  • the MME does not have information on which RA nodes that are configured for eMBMS. Therefore, the MME needs to retrieve such information in order to be able to initiate a handover of the wireless device to an adequate RA node.
  • the MME could retrieve 503 information indicating a set of one or more RA nodes being configured for access to eMBMS, e.g. from an MCE node or from the OSS. By retrieving is meant e.g. that the MME could receive the information upon request, as part of a set-up, or receive it on regular basis. The information could be received from the OSS in association with the receiving of an instruction to enter the CMM mode.
  • the information on which RA nodes that are configured for eMBMS could be collected from the RA nodes.
  • the information could be stored in the MME, e.g. in form of a look-up table, a list or a record, for use during the operation in CMM mode.
  • the MME could initiate a handover of a wireless device to a suitable RA node and handle 504 service requests according to the CMM procedure.
  • the redirecting to an eMBMS service may comprise sending 305, a control message, such as an RRC message, to the RA node serving the wireless device, indicating the eMBMS session.
  • a control message such as an RRC message
  • the RA node may schedule the wireless device to receive the eMBMS session, e.g. on certain radio resources allocated for broadcast.
  • Embodiments herein further relate to a second, corresponding method, for supporting congestion mitigation.
  • the second method is performed by another network node than the network node described above as an MME.
  • An embodiment of this second method is illustrated in figure 6.
  • the method comprises indicating 602, to another network node, a set of RA nodes being configured for access to eMBMS, thereby enabling the other network node to redirect a wireless device, which has requested a service, to a predefined eMBMS session, when the wireless device is served by an RA node which is not configured for access to eMBMS.
  • the network node indicating 602 the information may do this e.g. in response to a request for such information, which is illustrated in figure 6 as action 601 .
  • the action 601 is here illustrated with a dashed outline to show that this is only one alternative.
  • the network node to which the information is indicated is a network node as the one described above as an MME.
  • the network node indicating the set of RA nodes could be a MCE or an OSS node, as described above, since both these nodes have access to the information on which RA nodes that are configured for eMBMS.
  • the network node indicating the information could alternatively be an RA node being configured for eMBMS.
  • the indicated set of RA nodes may only comprise information on the RA node itself being configured for eMBMS.
  • the other network node (MME) would then need to accumulate information from a plurality of such RA nodes.
  • Embodiments herein further relate to a third, corresponding method, for supporting congestion mitigation, performed by an RA node.
  • An embodiment of this third method is illustrated in figure 7.
  • the method comprises receiving 701 an instruction from a network node in CMM mode to hand over a wireless device, currently served by the 5 RA node, to another RA node; and further initiating 702 a handover of the wireless device, denoted "WD" in the figure, to the other RA node in response to the received instruction.
  • the performing of this third method enabling a redirection of the wireless device from a service requested by the wireless device to a predefined eMBMS service, as previously described.
  • the RA node should initiate the handover
  • the handover may be performed according to a regular handover procedure.
  • Embodiments herein further relate to fourth corresponding method, for supporting 15 congestion mitigation, performed by an OSS node, e.g. a physical and/or logical network node which is part of the OSS.
  • the method comprises receiving 801 one or more indications of severe congestion in the communication network and then signaling 802 an instruction, to at least one network node (MME), to enter a CMM.
  • MME network node
  • the method may be assumed to comprise a decision 20 of whether the network node should be instructed to enter a CMM or not, based on the received information.
  • the received information may be reports of rejected service requests, dropped service sessions, network failure, or any other indication of that there is, or will soon be, a congestion in the network.
  • the performing of this method enables the at least one network node to redirect wireless devices requesting a
  • the method may further
  • Action 803 has a dashed outline, to emphasize that this information could instead be provided e.g. by an MCE or be derived from a number of RA nodes.
  • FIG. 9a An exemplifying embodiment of a network node, such as the one exemplified as and denoted MME above, is illustrated in a general manner in figure 9a.
  • the network node will also here be denoted MME, as an example, in order to more easily separate it from other descriptions of network nodes herein.
  • the MME 900 is configured to perform at least one of the method embodiments described above with reference to any of figures 2-5.
  • the MME 900 is associated with the same technical features, objects and advantages as the previously described method embodiments.
  • the node will be described in brief in order to avoid unnecessary repetition.
  • the MME may be implemented and/or described as follows:
  • the MME 900 is configured for network congestion mitigation.
  • the MME 900 comprises processing circuitry 901 and a communication interface 902.
  • the processing circuitry 901 is configured to cause the MME 900 to enter a congestion mitigation mode, CMM, and further to receive a service request originating from a wireless device.
  • the processing circuitry 901 is further configured to cause the MME to redirect the wireless device to a predefined eMBMS session in response to said service request, when the service request fulfills a criterion related to priority.
  • I/O Input/Output
  • the processing circuitry 901 could, as illustrated in figure 9b, comprise processing means, such as a processor 903, e.g. a CPU, and a memory 904 for storing or holding instructions.
  • the memory would then comprise instructions, e.g. in form of a computer program 905, which when executed by the processing means 903 causes the MME 900 to perform the actions described above.
  • the processing circuitry 901 here comprises a receiving unit 906, configured to cause the MME to receive an instruction to enter a CMM mode.
  • the processing circuitry further comprises a switching unit 907, configured to cause the MME to enter a CMM mode in response to an instruction to do so.
  • the processing circuitry further comprises a receiving unit 908, configured to cause the MME to receive a service request originating from a wireless device.
  • the receiving units 906 and 908 are here illustrated as two different units, but could alternatively be one receiving unit configured for these tasks.
  • the processing circuitry 901 further comprises a redirecting unit 909, configured to cause the MME to redirect the wireless device to a predefined eMBMS session ; in response to said service request, when the service request fulfills a criterion related to priority.
  • the processing circuitry could comprise more units, such as a determining unit for determining whether the received service request fulfills the criterion. This task could alternatively be assumed to be performed by one of the other units, e.g. the redirecting unit 909.
  • embodiments described herein such as receiving information on a set of one or more RA nodes configured for eMBMS; and initiating a handover of a wireless device which is served by an RA node which is not configured for eMBMS.
  • the MME 900 may be assumed to comprise further functionality, for carrying out regular node functions.
  • Embodiments herein also relate to a network node 1 000 configured for carrying out embodiments of the method denoted "second method" above. That is, the method for providing information on RA nodes configured for access to eMBMS, illustrated e.g. in figure 6.
  • the network node 1000 is configured to perform at least one of the method embodiments described above with reference to figure 6.
  • the network node 1000 is associated with the same technical features, objects and advantages as the previously described method embodiments. The node will be described in brief in order to avoid unnecessary repetition.
  • the network node 1000 is configured for supporting congestion mitigation.
  • the network node 1000 comprises processing circuitry 1001 and a communication interface 1002.
  • the processing circuitry 1001 is configured to cause the network node to indicate, to another network node, a set of RA nodes being configured for access to eMB S.
  • I/O Input/Output
  • the processing circuitry 1001 could, as illustrated in figure 10b, comprise processing means, such as a processor 1003, and a memory 1 004 for storing or holding instructions.
  • the memory would then comprise instructions, e.g. in form of computer program 1005, which when executed by the processing means 1003 causes the network node 1000 to perform the actions described above.
  • the processing circuitry 1 001 comprises an indicating unit 1 006, configured to cause the network node to indicate, to another network node, a set of RA nodes being configured for access to eMBMS.
  • the indicating could be done e.g. in response to a request for such information received from the other network node.
  • the processing circuitry 1001 may comprise a receiving unit, configured to cause the network node to receive such a request.
  • the network node 1000 may be assumed to comprise further functionality, for carrying out regular node functions. These functions would be at least partly different depending on whether the network node is an MCE or a node comprised in the OSS on a higher hierarchical level in the wireless communication network.
  • Embodiments herein also relate to an RA node 1 100, configured for carrying out embodiments of the method denoted "third method" above. That is, the method for receiving instructions from e.g. an MME to hand over a wireless device and then initiating a handover procedure for the wireless device, illustrated e.g. in figure 7.
  • An exemplifying embodiment of an RA node is illustrated in a general manner in figure 1 1 a.
  • the RA node 1 100 is configured to perform at least one of the method embodiments described above with reference to figure 7.
  • the network node 1 100 is associated with the same technical features, objects and advantages as the previously described method embodiments. The node will be described in brief in order to avoid unnecessary repetition.
  • the RA node is suitable for supporting congestion mitigation, and is configured to be operable in a communication network.
  • the RA node 1 1 00 comprises processing circuitry 1 1 01 and a communication interface 1 1 02, the processing circuitry 1 101 is configured to cause the network node 1 100 to receive an instruction, from a network node in CMM mode, to hand over a wireless device, currently served by the RA node 1 1 00, to another RA node.
  • the processing circuitry 1 1 01 is further configured to cause the network node 1 1 00 to initiate a handover of the wireless device to the other RA node in response to the received instruction.
  • the communication interface 1 1 02 which may also be denoted e.g. Input/Output (I/O) interface, includes a network interface for sending data to and receiving data from other network nodes over an air interface or over a backhaul interface.
  • I/O Input/Output
  • the processing circuitry could, as illustrated in figure 1 1 b, comprise processing means, such as a processor 1 103, and a memory 1 104 for storing or holding instructions.
  • the memory would then comprise instructions, e.g. in form of computer program 1 105, which when executed by the processing means 1 103 causes the network node 1 100 to perform the actions described above.
  • the processing circuitry 1 101 here comprises a receiving unit 1 106, configured to cause the RA node 1 100 to receive an instruction to hand over a wireless device to another RA node.
  • the processing circuitry 1 101 further comprises a handover unit 1 1 07, configured to cause the network node to initiate a handover of the wireless device to the other RA node.
  • the network node 1 100 may be assumed to comprise further functionality, for carrying out regular RA node functions.
  • Embodiments herein also relate to a network node, configured for carrying out embodiments of the method denoted "fourth method” above. That is, the method for receiving information indicating a severe congestion and instructing a network node (MME) to enter a CMM, illustrated e.g. in figure 8.
  • the network node may be assumed to be part of an OSS.
  • An exemplifying embodiment of such a network node is illustrated in a general manner in figure 1 2a.
  • the network node 1200 is configured to perform at least one of the method embodiments described above with reference to figure 8.
  • the network node 1200 is associated with the same technical features, objects and advantages as the previously described method embodiments. The node will be described in brief in order to avoid unnecessary repetition.
  • the network node 1200 is configured to be operable in a communication network.
  • the network node comprises processing circuitry 1201 and a communication interface 1202, the processing circuitry 1 201 is configured to cause the network node 1200 to receive information indicating congestion in the communication network, and to signal an instruction to enter a Congestion Mitigation Mode, CMM, to at least one network node in the communication network, based on the received information.
  • the communication interface 1202 which may also be denoted e.g. Input/Output (I/O) interface, includes a network interface for sending data to and receiving data from other network nodes.
  • the processing circuitry could, as illustrated in figure 12b comprise processing means, such as a processor 1203, and a memory 1 204 for storing or holding instructions.
  • the memory would then comprise instructions, e.g. in form of a computer program 1205, which when executed by the processing means 1203 causes the network node 1200 to perform the actions described above.
  • the processing circuitry here comprises a receiving unit 1206, configured to cause the network node to receive information indicating congestion in the communication network.
  • the processing circuitry 1201 further comprises a signaling unit 1207, configured to cause the network node to signal an instruction to enter a Congestion Mitigation Mode, CMM, to at least one network node in the communication network, based on the received information.
  • CMM Congestion Mitigation Mode
  • the network node 1200 may be assumed to comprise further functionality, for carrying out e.g. regular OSS node functions. Concluding remarks
  • Particular examples include one or more suitably configured digital signal processors and other known electronic circuits, e.g. discrete logic gates interconnected to perform a specialized function, or Application Specific Integrated Circuits (ASICs).
  • digital signal processors and other known electronic circuits, e.g. discrete logic gates interconnected to perform a specialized function, or Application Specific Integrated Circuits (ASICs).
  • ASICs Application Specific Integrated Circuits
  • At least some of the steps, functions, procedures, modules, units and/or blocks described above may be implemented in software such as a computer program for execution by suitable processing circuitry including one or more processing units.
  • the software could be carried by a carrier, such as an electronic signal, an optical signal, a radio signal, or a computer readable storage medium before and/or during the use of the computer program in the network nodes.
  • the flow diagram or diagrams presented herein may be regarded as a computer flow diagram or diagrams, when performed by one or more processors.
  • a corresponding apparatus may be defined as a group of function modules, where each step performed by the processor corresponds to a function module.
  • the function modules are implemented as a computer program running on the processor.
  • processing circuitry includes, but is not limited to, one or more microprocessors, one or more Digital Signal Processors, DSPs, one or more Central Processing Units, CPUs, and/or any suitable programmable logic circuitry such as one or more Field Programmable Gate Arrays, FPGAs, or one or more
  • PLCs Programmable Logic Controllers
  • the units or modules in the arrangements in the different nodes described above could be implemented by a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g. stored in a memory.
  • processors as well as the other digital hardware, may be included in a single application-specific integrated circuitry, ASIC, or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a-chip, SoC.
  • SoC system-on-a-chip

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des nœuds de réseau et des procédés mis en œuvre dans ces nœuds pour atténuer l'encombrement d'un réseau. Un procédé mis en œuvre dans un premier nœud de réseau comprend : le passage en mode d'atténuation d'encombrement (CMM); la réception d'une demande de service provenant d'un dispositif sans fil; et, en réponse à ladite demande de service, lorsque cette dernière remplit un critère, la redirection du dispositif sans fil vers une session eMBMS prédéfinie, ce qui fournit une alternative centrée sur l'information au rejet de la demande de service.
PCT/EP2014/074466 2014-11-13 2014-11-13 Atténuation de l'encombrement dans un réseau de communication WO2016074724A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2014/074466 WO2016074724A1 (fr) 2014-11-13 2014-11-13 Atténuation de l'encombrement dans un réseau de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2014/074466 WO2016074724A1 (fr) 2014-11-13 2014-11-13 Atténuation de l'encombrement dans un réseau de communication

Publications (1)

Publication Number Publication Date
WO2016074724A1 true WO2016074724A1 (fr) 2016-05-19

Family

ID=51897275

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2014/074466 WO2016074724A1 (fr) 2014-11-13 2014-11-13 Atténuation de l'encombrement dans un réseau de communication

Country Status (1)

Country Link
WO (1) WO2016074724A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10291941B2 (en) 2017-03-09 2019-05-14 At&T Mobility Ii Llc Pre-caching video content to devices using LTE broadcast
CN110036669A (zh) * 2016-10-11 2019-07-19 瑞典爱立信有限公司 系统信息中的mbms载波类型

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2440002A2 (fr) * 2010-10-05 2012-04-11 HTC Corporation Procédé de gestion de contrôle de congestion à base APN et dispositif de communication associé
EP2557818A1 (fr) * 2011-08-12 2013-02-13 Alcatel Lucent Procédé pour la fourniture d'une continuité de services diffusés en multidiffusion dans un réseau sans fil, nýud de réseau correspondant et équipement utilisateur

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2440002A2 (fr) * 2010-10-05 2012-04-11 HTC Corporation Procédé de gestion de contrôle de congestion à base APN et dispositif de communication associé
EP2557818A1 (fr) * 2011-08-12 2013-02-13 Alcatel Lucent Procédé pour la fourniture d'une continuité de services diffusés en multidiffusion dans un réseau sans fil, nýud de réseau correspondant et équipement utilisateur

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; MBMS Improvements; MBMS operation on Demand (Release 12)", 8 August 2014 (2014-08-08), XP050806178, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/SA4/Docs/> [retrieved on 20140808] *
"LTE; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (3GPP TS 36.300 version 11.3.0 Release 11)", TECHNICAL SPECIFICATION, EUROPEAN TELECOMMUNICATIONS STANDARDS INSTITUTE (ETSI), 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS ; FRANCE, vol. 3GPP RAN 2, no. V11.3.0, 1 November 2012 (2012-11-01), XP014093330 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110036669A (zh) * 2016-10-11 2019-07-19 瑞典爱立信有限公司 系统信息中的mbms载波类型
CN110036669B (zh) * 2016-10-11 2022-03-18 瑞典爱立信有限公司 系统信息中的mbms载波类型
US10291941B2 (en) 2017-03-09 2019-05-14 At&T Mobility Ii Llc Pre-caching video content to devices using LTE broadcast

Similar Documents

Publication Publication Date Title
US10028109B2 (en) Group communication over LTE eMBMS
US9432820B2 (en) Method for efficiently supporting multiple simultaneous group PTT calls requiring low call setup latency
US9681419B2 (en) Seamless and resource efficient roaming for group call services on broadcast/multicast networks
CN108886669B (zh) 广播和单播递送之间的流送服务的动态切换
JP5610609B2 (ja) 無線送信方法、無線送信装置及び基地局装置
EP3198958B1 (fr) Gestion de ressources de communication
WO2015096718A1 (fr) Procédé, dispositif, et système, permettant d&#39;assurer la continuité d&#39;un service de communication de groupe
US20130039250A1 (en) Method to Indicate MBMS Reception Status to Enable Service Continuity
EP2928220B1 (fr) Méthode, système, station de base et epc en grappe pour l&#39;établissement de contexte d&#39;appel de groupe
EP3348081B1 (fr) Continuation de session de transmission en continu
US20150079979A1 (en) Seamless and resource efficient roaming for group call services on broadcast/multicast networks
US20170111934A1 (en) Method for obtaining ue counting result, method and apparatus for suspending data transmission
US20200329347A1 (en) Multicast/broadcast service to radio access networks with core networks
US10021709B2 (en) Method for determining priorities of services and wireless equipment thereof
US20150296402A1 (en) Evolved node b resource management based on interest indicators
EP3087764B1 (fr) Procédés, noeud utilisateur et noeud réseau dans un réseau de service de diffusion multidiffusion multimédia (mbms)
EP2903310A1 (fr) Services multimédia/radiodiffusion multimédia
WO2016074724A1 (fr) Atténuation de l&#39;encombrement dans un réseau de communication
EP3206417B1 (fr) Procédé et appareil de communication de groupe
WO2015139748A1 (fr) Transmissions dans des systèmes sans fil
JP2017505073A (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: 14796776

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14796776

Country of ref document: EP

Kind code of ref document: A1