WO2012156943A1 - Procédés et appareil d'activation de services à commutation de circuits - Google Patents

Procédés et appareil d'activation de services à commutation de circuits Download PDF

Info

Publication number
WO2012156943A1
WO2012156943A1 PCT/IB2012/052493 IB2012052493W WO2012156943A1 WO 2012156943 A1 WO2012156943 A1 WO 2012156943A1 IB 2012052493 W IB2012052493 W IB 2012052493W WO 2012156943 A1 WO2012156943 A1 WO 2012156943A1
Authority
WO
WIPO (PCT)
Prior art keywords
switched domain
packet
circuit
switched
mobility management
Prior art date
Application number
PCT/IB2012/052493
Other languages
English (en)
Inventor
Marko NIEMI
Ilkka HEIKKINEN
Original Assignee
Renesas Mobile 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
Priority claimed from US13/111,166 external-priority patent/US20120294143A1/en
Priority claimed from GB1108424.1A external-priority patent/GB2490948B/en
Application filed by Renesas Mobile Corporation filed Critical Renesas Mobile Corporation
Priority to DE112012002157.6T priority Critical patent/DE112012002157T5/de
Publication of WO2012156943A1 publication Critical patent/WO2012156943A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H04W36/00224—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies between packet switched [PS] and circuit switched [CS] network technologies, e.g. circuit switched fallback [CSFB]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • Embodiments of the present invention relate generally to wireless communication technology and, in particular embodiments, relate to an apparatus, method and computer- readable storage medium for enabling circuit-switched services during mobility management congestion control.
  • Wireless and mobile networking technologies have been developing at a rapid pace. Driven by consumer demand and fuelled by continuous advances in battery technology and the ability to manufacture small and highly capable devices, many advancements have also been made in relation to the production of devices that utilize these developing technologies. These devices are becoming ubiquitous in the modern world and are increasingly being employed for use in communication, gaming, social networking, content generation, content sharing, scheduling and numerous other activities.
  • apparatus for enabling circuit-switched services, the apparatus comprising: a processing system arranged to cause the apparatus at least: to cause transmission of a first mobility management message from user equipment to a core network that includes a packet- switched domain and a circuit-switched domain, such that a said first mobility management message is transmitted to a component of a said packet-switched domain, the user equipment being arranged to receive a rejection message from a said packet- switched domain component in response to the first mobility management message, the rejection message indicating congestion as a cause for rejection of the first mobility management message, and indicating whether circuit-switched services are permitted or forbidden; and to cause a packet-switched domain back-off timer to run in response to receipt of the rejection message, the apparatus being arranged to defer transmission of any mobility management messages to a component of the packet-switched domain while the packet-switched domain back-off timer is running; wherein in the event that the rejection message indicates that circuit-switched services
  • apparatus for enabling circuit-switched services, the apparatus comprising: a processing system arranged to cause the apparatus at least: to be capable of receiving a first mobility management message at a core network from user equipment, the core network including a packet-switched domain and a circuit-switched domain, the first mobility management message being receivable at a component of the packet-switched domain; to detect congestion in the core network, and in response thereto: to cause transmission of a rejection message from the packet-switched domain component to a said user equipment in response to receipt of the first mobility management message, the rejection message indicating congestion as a cause for rejection of the first mobility management message; wherein the rejection message is such that receipt of the rejection message at a said user equipment causes the user equipment to run a packet-switched domain back-off timer indicating a time during which the user equipment defers transmission of any further mobility management messages to the packet-switched domain component, wherein the rejection message further indicates whether circuit-switched
  • the processing system described above may comprise at least one processor and at least one memory including computer program instructions, the at least one memory and the computer program instructions being configured to, with the at least one processor, cause the apparatus at least to perform as described above.
  • a method for enabling circuit-switched services comprising: causing transmission of a first mobility management message from user equipment to a core network that includes a packet-switched domain and a circuit-switched domain, wherein the first mobility management message is transmitted to a component of the packet-switched domain; receiving a rejection message at the user equipment from the packet-switched domain component in response to the first mobility management message, the rejection message indicating congestion as a cause for rejection of the first mobility management message, and indicating whether circuit-switched services are permitted or forbidden; and running a packet-switched domain back-off timer in response to receipt of the rejection message, the user equipment being arranged to defer transmission of any mobility management messages to a component of the packet-switched domain while the packet-switched domain back-off timer is running; wherein, in the event that the rejection message indicates that circuit-switched services are permitted, the user equipment is permitted to transmit a second mobility management message to
  • a method for enabling circuit-switched services comprising: receiving a first mobility management message at a core network from user equipment, the core network including a packet-switched domain and a circuit-switched domain, the first mobility management message being received at a component of the packet-switched domain; detecting congestion in the core network, and in response thereto, causing transmission of a rejection message from the packet-switched domain component to the user equipment in response to receipt of the first mobility management message, the rejection message indicating congestion as a cause for rejection of the first mobility management message, wherein the rejection message is such that receipt of the rejection message at the user equipment causes the user equipment to run a packet-switched domain back-off timer indicating a time during which the user equipment defers transmission of any further mobility management messages to the packet-switched domain component, wherein the rejection message further indicates whether circuit-switched services are permitted or forbidden, and wherein in the event that the rejection message indicates that circuit- switched
  • Example embodiments of the present invention provide an apparatus, method and computer-readable storage medium for enabling circuit-switched services during mobility management congestion control.
  • a method includes various operations from the perspective of a user equipment (UE). The method includes causing transmission of a first mobility management message from a UE to a core network including a packet-switched domain and a circuit-switched domain.
  • the method may include causing transmission of the first mobility management message to a component (e.g. MME/SGSN) of the packet-switched domain.
  • This mobility management message may include, for example, a request to attach to the packet-switched domain, perform a routing area update or receive a packet-switched service.
  • the method may also include receiving a rejection message at the UE from the packet-switched domain component (e.g. MME/SGSN) in response to the first mobility management message.
  • the rejection message indicates congestion as a cause for rejection of the first mobility management message, and may also include a value of the packet-switched domain back-off timer. Consequently, the method may include running a packet-switched domain back-off timer (e.g. starting at the packet-switched domain back-off timer value) in response to receipt of the rejection message.
  • the packet- switched domain back-off timer in this example indicates a time during which the UE defers transmission of any further mobility management messages to the packet-switched domain component.
  • the indication in the rejection message that circuit-switched services are permitted enables the apparatus to cause transmission of a second mobility management message from the user equipment to a component of the circuit-switched domain (e.g. MSC), while the back-off timer is running.
  • the method may further include causing transmission of the second mobility management message from the UE to the component of the circuit- switched domain.
  • the rejection message may include an indication whether circuit-switched services are permitted or forbidden.
  • transmission of the second mobility management message may be caused in an instance in which the rejection message indicates that circuit-switched services are permitted.
  • the user equipment in the event that the rejection message indicates that circuit- switched services are not permitted, the user equipment is caused to defer transmission of any mobility management messages from the user equipment to a component of the circuit-switched domain while the packet-switched domain back-off timer is running. In an embodiment, in the event that the rejection message indicates that circuit- switched services are not permitted, the user equipment is caused to run a circuit- switched domain back-off timer, the apparatus being arranged to defer transmission of any mobility management messages to a component of the circuit-switched domain while the circuit-switched domain back-off timer is running. In one example, the value for the circuit-switched domain back-off timer is indicated to the user equipment in the rejection message, and in this case, the user equipment is caused to start the circuit-switched domain back-off timer at that value.
  • a method includes various operations from the perspective of a packet-switched domain component (e.g. MME/SGSN).
  • the method of this aspect includes receiving a first mobility management message at a core network from a UE.
  • This mobility management message may include, for example, a request to attach to the packet-switched domain, perform a routing area update or receive a packet-switched service.
  • the core network includes a packet- switched domain and a circuit-switched domain, and the first mobility management message is received at the packet-switched domain component.
  • the method also includes detecting congestion in the core network; and in response thereto, causing transmission of a rejection message from the packet-switched domain component to the UE in response to receipt of the first mobility management message.
  • the rejection message indicates congestion as a cause for rejection of the first mobility management message, and may also include a value of the packet-switched domain back-off timer. Consequently, receipt of the rejection message at the UE causes the UE to run a packet-switched domain back-off timer (e.g. starting at the packet- switched domain back-off timer value) indicating a time during which the UE defers transmission of any further mobility management messages to the packet-switched domain component. Further, the rejection message indicates whether circuit-switched services are permitted or forbidden during running of the back-off timer.
  • a packet-switched domain back-off timer e.g. starting at the packet- switched domain back-off timer value
  • receipt of the rejection message at the UE causes the UE to transmit a second mobility management message from the UE to a component of the circuit-switched domain (e.g. MSC) while the back-off timer is running.
  • a component of the circuit-switched domain e.g. MSC
  • FIG. 1 illustrates one example of a communication system according to an example embodiment of the present invention
  • FIG. 2 illustrates a block diagram showing an apparatus in accordance with an example embodiment of the present invention
  • FIGS. 3 to 6 are flowcharts illustrating various operations in methods according to example embodiments of the present invention.
  • circuitry refers to any or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry); (b) combinations of circuits and software (and/or firmware), such as (as applicable): (i) a combination of processor(s) or (ii) portions of processor(s)/software (including digital signal processors)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions); and (c) circuits, such as a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation, even if the software or firmware is not physically present.
  • circuitry applies to all uses of this term in this application, including in any claims.
  • circuitry would also cover an implementation of merely a processor (or multiple processors) or portion of a processor and its (or their) accompanying software and/or firmware.
  • circuitry would also cover, for example and if applicable to the particular claim element, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in server, a cellular network device, or other network device.
  • FIG. 1 illustrates a generic system diagram in which a device such as user equipment (UE) 10 or other mobile terminal is shown in an example communication environment in which embodiments of the present invention may be employed.
  • the system includes one or more radio access networks (RANs) that provide an air interface between a UE and one or more core networks of appropriate operators.
  • RANs radio access networks
  • These core networks may provide network services such as packet-switched services and/or circuit-switched services to users via one or more external networks.
  • the system may include a number of different RANs including one or more
  • GSM/Edge Radio Access Networks GERANs
  • Universal Terrestrial Radio Access Networks UTRANs
  • E-UTRANs Evolved UTRANs
  • 2G second generation
  • 3G third generation
  • These RANs may include one or more base stations, node Bs, evolved node Bs (eNBs) or the like (generally a "base site"), each of which may have a coverage area that defines a region within which UEs 10 may utilize the respective base sites to access the core network(s).
  • the RANs may also include one or more base station controllers (BSCs), radio network controllers (RNCs) that control communication to and from groups of base sites, etc.
  • BSCs base station controllers
  • RNCs radio network controllers
  • the core network(s) may include a packet-switched domain for providing packet- switched services to users, and/or a circuit-switched domain for providing circuit- switched services to users.
  • the packet-switched domain may include components such as a Mobility Management Entity (MME) 16, Serving GPRS Support Node - SGSN (shown integrated into the same components), Gateway GPRS Support Node - GGSN 18 or the like, which in one example, may form part of the Evolved Packet Core (EPC) of the System Architecture Evolution (SAE).
  • EPC Evolved Packet Core
  • SAE System Architecture Evolution
  • the circuit-switched domain may include components such as a Mobile Switching Center (MSC) 20, Media Gateway (MGW) 22 or the like.
  • MSC Mobile Switching Center
  • MGW Media Gateway
  • the GGSN, MGW and/or UE may be coupled to one or more data or Internet Protocol (IP) packet data networks (PDNs) 24, such as one or more local area networks, wide area networks (for example, the Internet) or the like.
  • IP Internet Protocol
  • PDNs packet data networks
  • a particular GGSN by which a UE accesses a PDN may be referred to by its access point name (APN), and the respective UE may be considered to have a subscription to the APN.
  • APN access point name
  • the MGW 22 of the circuit-switched domain may be coupled to one or more circuit-switched networks 26 such as a public switched telephone network (PSTN), integrated services digital network (ISDN) or the like.
  • the PDN 24 and PSTN/IDDN may be coupled to a 3rd Generation Partnership Program (3GPP) IP Multimedia Subsystem (IMS) 28.
  • 3GPP 3rd Generation Partnership Program
  • IMS IP Multimedia Subsystem
  • the packet-switched components, circuit-switched components and other components of the system may include one or more processors that may define processing circuitry either alone or in combination with one or more memories that may store instructions that, when executed by the one or more processors, cause the respective components to perform corresponding functions as described herein.
  • the core network(s) may include a collection of various different nodes, devices or functions that may be in communication with each other via corresponding wired and/or wireless interfaces.
  • the illustration of FIG. 1 should be understood to be an example of a broad view of certain elements of the system and not an all inclusive or detailed view of the system or the core network(s).
  • the core network(s) may employ one or more mobile access mechanisms such as wideband code division multiple access (W-CDMA), CDMA2000, global system for mobile communications (GSM), general packet radio service (GPRS), long term evolution (LTE), LTE Advanced (LTE-A) or the like.
  • W-CDMA wideband code division multiple access
  • CDMA2000 Code Division Multiple Access 2000
  • GSM global system for mobile communications
  • GPRS general packet radio service
  • LTE long term evolution
  • LTE-A LTE Advanced
  • One or more UEs 10 may be configured to communicate with one other or other devices via the core network(s).
  • each of the UEs may include an antenna or antennas for transmitting signals to and for receiving signals from a base site of a RAN.
  • other devices such as processing devices (e.g. personal computers, server computers or the like) may be coupled to the UE via the core network(s).
  • processing devices e.g. personal computers, server computers or the like
  • the UEs may be operable in one of three modes. In a mode A, the UE may be simultaneously attached to both packet-switched domain (e.g. GPRS) and circuit- switched domain (e.g. GSM), and may support simultaneous operation of services from both domains.
  • packet-switched domain e.g. GPRS
  • GSM circuit- switched domain
  • the UE may be simultaneously attached to both packet- switched domain (e.g. GPRS) and circuit-switched domain (e.g. GSM), but may only support operation of services from one domain at a time.
  • packet- switched domain e.g. GPRS
  • circuit-switched domain e.g. GSM
  • the UE may only support attachment to and receive services from the packet-switched domain (e.g. GPRS).
  • the UE 10 may be a mobile communication device such as, for example, a mobile telephone, portable digital assistant (PDA), pager, laptop computer, or any of numerous other handheld or portable communication devices, computation devices, content generation devices, content consumption devices, or combinations thereof.
  • the UE may include one or more processors that may define processing circuitry either alone or in combination with one or more memories.
  • the processing circuitry may utilize instructions stored in the memory to cause the UE to operate in a particular way or execute specific functionality when the instructions are executed by the one or more processors.
  • the UE may also include communication circuitry and corresponding hardware/software to enable communication with other devices (and/or the core network(s) via the base site of a RAN).
  • the MME 16 may include one or more processors that may define processing circuitry either alone or in combination with one or more memories that may store instructions that, when executed by the one or more processors, cause the MME to perform corresponding functions as described herein.
  • the MME may be configured to function as a control node responsible for, among other things, tracking and paging and providing control plane functions for mobility between RANs.
  • the MME may also have involvement in bearer activation and/or deactivation and handling handover functions.
  • components of the system of FIG. 1 may include or otherwise employ an apparatus configured according to an example embodiment of the present invention.
  • FIG. 2 illustrates a schematic block diagram of such an apparatus that may be configured to function as one or more of the components of the system, such as a UE 10, MME or SGSN 16, according to an example embodiment of the present invention.
  • integrated components may be supported by separate apparatus (e.g. separate MME and SGSN), or separate components may be supported by a single apparatus.
  • the apparatus 30 may include or otherwise be in communication with processing circuitry 32 that is configurable to perform actions in accordance with example embodiments described herein.
  • the processing circuitry may be configured to perform data processing, application execution and/or other processing and management services according to an example embodiment of the present invention.
  • the apparatus or the processing circuitry may be embodied as a chip or chip set.
  • the apparatus or the processing circuitry may include one or more physical packages (e.g.
  • a chip or chipset may constitute means for performing one or more operations for providing the functionalities described herein.
  • the processing circuitry 32 may include a processor 34 and memory 36 that may be in communication with or otherwise control a device interface 38 and, in some cases, a user interface 40.
  • the processing circuitry may be embodied as a circuit chip (e.g. an integrated circuit chip) configured to (e.g. with hardware, alone or in combination with software) perform operations described herein.
  • the processing circuitry may be embodied as a portion of a server, computer, workstation or other fixed or mobile computing device.
  • the user interface may be disposed at another device (e.g.
  • the processor 34 may be embodied in a number of different ways.
  • the processor may be embodied as various processing means such as one or more of a microprocessor or other processing element, a coprocessor, a controller or various other computing or processing devices including integrated circuits such as, for example, an ASIC (application specific integrated circuit), an FPGA (field programmable gate array), or the like.
  • the processor may be configured to execute instructions stored in the memory 36 or otherwise accessible to the processor. As such, whether configured by hardware or by a combination of hardware and software, the processor may represent an entity (e.g.
  • processors when the processor is embodied as an ASIC, FPGA or the like, the processor may be specifically configured hardware for conducting the operations described herein.
  • the processor when the processor is embodied as an executor of software instructions, the instructions may specifically configure the processor to perform the operations described herein.
  • the memory 36 may include one or more non- transitory memory devices such as, for example, volatile and/or non-volatile memory that may be either fixed or removable.
  • the memory may be configured to store information, data, applications, instructions or the like for enabling the apparatus 30 to carry out various functions in accordance with exemplary embodiments of the present invention.
  • the memory could be configured to buffer input data for processing by the processor 34.
  • the memory could be configured to store instructions for execution by the processor.
  • the memory may include one of a plurality of databases that may store a variety of files, contents or data sets.
  • applications may be stored for execution by the processor in order to carry out the functionality associated with each respective application.
  • the memory may be in communication with the processor via a bus for passing information among components of the apparatus.
  • the device interface 38 may include one or more interface mechanisms for enabling communication with other devices and/or networks.
  • the device interface may be any means such as a device or circuitry embodied in either hardware, or a combination of hardware and software that is configured to receive and/or transmit data from/to a network and/or any other device or module in communication with the processing circuitry 32.
  • the device interface may include, for example, an antenna (or multiple antennas) and supporting hardware and/or software for enabling communications with a wireless communication network and/or a communication modem or other hardware/software for supporting communication via cable, digital subscriber line (DSL), universal serial bus (USB), Ethernet or other methods.
  • DSL digital subscriber line
  • USB universal serial bus
  • the user interface 40 may be in communication with the processing circuitry 32 to receive an indication of a user input at the user interface and/or to provide an audible, visual, mechanical or other output to the user.
  • the user interface may include, for example, a keyboard, a mouse, a joystick, a display, a touch screen, a microphone, a speaker, and/or other input/output mechanisms.
  • the user interface may also include user interface circuitry and user interface software configured to facilitate user control of at least some functions of the apparatus through use of a display.
  • the apparatus is embodied at a server or other network device (e.g. the MME 16)
  • the user interface may be fully implemented, limited, remotely located or eliminated.
  • the UE 10 and core network including the MME 16 may communicate with one another in accordance with a protocol stack including a number of functional layers that support signalling and traffic between the respective elements. These layers may include, for example, an access stratum (AS) that may be akin to a link layer and function as a carrier or transport for a non-access stratum (NAS) that may be akin to a network layer.
  • AS access stratum
  • NAS non-access stratum
  • a number of the functions of the MME form part of the NAS, such as radio resource (RR) management, mobility management (MM) and connection management (CM) procedures - each of which may be characterized by a sublayer of the NAS. More information on these and other sublayers of the NAS of one example may be found in 3 GPP TS 24.007.
  • Mobility management may be viewed in terms of different mobility states of a UE 10, including for example, detached, active and idle.
  • the UE may be powered off or powered on but in the process of searching for and attaching to or otherwise registering with a core network (e.g. International Mobile Subscriber Identity (EVISI) attach).
  • EVISI International Mobile Subscriber Identity
  • the UE may be attached to a core network (e.g. EVISI attached) and have a radio resource control (RRC) connection with a RAN.
  • RRC radio resource control
  • the RAN and/or core network may store a UE context that includes subscription information for the UE, and the core network and UE may be able to exchange data.
  • the idle state is a power-conservation state for the UE, where the UE typically does not transmit or receive packets.
  • the UE may not have a RRC connection with a RAN.
  • the core network may locate the UE in a RAN on the level of a cell served by one or more of its base sites; but in the idle state, the core network may only locate the UE on the level of groups of multiple cells (known at times as a location area, routing area or tracking area), and the core network.
  • the core network In the idle state, the core network must therefore page a UE to locate it to a particular cell.
  • MM procedures may be performed after a RR (RRC) connection has been established between a UE 10 and core network; and in the case a RR connection has not yet been established, the MM sublayer may initiate establishment of such a connection.
  • the MM sublayer generally supports the mobility of UEs 10, such as informing the core network of its present location and providing user identity confidentiality; and it may provide connection management services to the CM sublayer.
  • MM procedures may include procedures for non-GPRS services (at times referred to as MM procedures) and procedures for GPRS services (at times referred to as GMM procedures).
  • MM procedures herein may refer to procedures for non-GPRS services or procedures for GPRS services. More information on MM procedures in accordance with 3 GPP may be found in 3 GPP TS 24.008. MM procedures may include those initiated by the UE 10 as well as those initiated by the core network. In one example embodiment, MM procedures initiated by the UE may include procedures to attach to or detach from the core network e.g. GPRS attach/detach), which may include establishing or releasing an appropriate UE context (e.g. GMM context). When a context has been established, UE-initiated MM procedures may also include a normal or periodic routing area update procedure. And the UE- initiated MM procedures may include a service request procedure to establish a secure connection to the network and/or to request the resource reservation for sending data.
  • GPRS attach/detach e.g. GMM context
  • the core network may detect network congestion (e.g. GMM signalling congestion, NAS signalling congestion, lack of processing resources) and perform congestion control (e.g. NAS-level congestion control) in mobility management.
  • this congestion control may include general mobility management control and subscribed APN-based congestion control.
  • the core network When the core network is under general overload conditions, it may reject mobility management signalling requests from UEs 10. And when subscribed APN-based congestion control is active for a particular GGSN 18, the network may reject mobility management messages from UEs subscribed to the APN of the particular GGSN.
  • the core network may receive a MM message from a UE 10.
  • This message may take the form of a request message such as a request to attach to the packet-switched domain (e.g. ATTACH REQUEST), perform a routing area update (e.g. ROUTING AREA UPDATE REQUEST), perform a tracking area update (e.g. TRACKING AREA UPDATE REQUEST) or receive a packet-switched service (e.g. SERVICE REQUEST).
  • a request message such as a request to attach to the packet-switched domain (e.g. ATTACH REQUEST), perform a routing area update (e.g. ROUTING AREA UPDATE REQUEST), perform a tracking area update (e.g. TRACKING AREA UPDATE REQUEST) or receive a packet-switched service (e.g. SERVICE REQUEST).
  • the network may respond to the UE message with a rejection message such as ATTACH REJECT, ROUTING AREA UPDATE REJECT, TRACKING AREA UPDATE REJECT or SERVICE RE
  • cause value # 22 and include one or more back-off timer (e.g. T3346) values - although the UE may be pre-configured or programmed with a back-off timer value.
  • the UE may start a back-off timer with this received value, and defer transmitting any further MM messages to the network until expiration of the back-off timer.
  • the packet-switched domain back-off timer may be triggered to begin running whenever the UE 10 receives an indication that congestion is a cause for the rejection (e.g. cause value #22) within a rejection message.
  • the UE may thereafter again send the network MM messages, such as to reinitiate its previous request.
  • the core network detects congestion in the packet-switched domain, but the circuit-switched domain has sufficient resources to provide circuit-switched services to the UE 10.
  • the SGSN 16 in the packet-switched domain may detect congestion in the packet-switched domain
  • the MSC 20 in the circuit-switched domain may have sufficient resources to provide circuit- switched services.
  • Example embodiments of the present invention therefore permit a UE to request and receive circuit-switched services in various instances in which the UE is subject to congestion control from the packet-switched domain.
  • the core network may explicitly indicate to the UE whether circuit-switched services are permitted or forbidden as congestion control is imposed for packet-switched services and the backoff timer is running.
  • a GPRS UE 10 operating in operation modes A or B that is not yet IMSI attached for circuit-switched services in the network may perform an IMSI attach for non-GPRS services while the back-off timer is running and proceed with appropriate circuit-switched MM procedures such as on request of upper layers.
  • a GPRS UE operating in operation modes A or B that is already IMSI attached for circuit-switched services in the network may remain IMSI attached for circuit-switched services in the network.
  • the UE of this other example may proceed with the appropriate MM procedure according to the MM service state while the back-off timer is running, and proceed with appropriate circuit-switched procedures such as on request of upper layers.
  • FIGS. 3 and 4 are flowcharts of a system, method and program product according to example embodiments of the invention for the case that the packet-switched domain is too congested to provide packet-switched services to the UE 10, but the circuit-switched domain has sufficient resources to provide circuit-switched services to the UE 10.
  • each block of the flowcharts, and combinations of blocks in the flowcharts may be implemented by various means, such as hardware, firmware, processor, circuitry and/or other device associated with execution of software including one or more computer program instructions.
  • one or more of the procedures described above may be embodied by computer program instructions.
  • the computer program instructions which embody the procedures described above may be stored by a memory device of an apparatus employing an embodiment of the present invention and executed by a processor in the apparatus.
  • any such computer program instructions may be loaded onto a computer or other programmable apparatus (e.g. hardware) to produce a machine, such that the resulting computer or other programmable apparatus provides for implementation of the functions specified in the flowcharts block(s).
  • These computer program instructions may also be stored in a non- transitory computer-readable storage memory that may direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable storage memory produce an article of manufacture the operation of which implements the function specified in the flowcharts block(s).
  • the computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowcharts block(s).
  • blocks of the flowcharts support combinations of means for performing the specified functions and combinations of operations for performing the specified functions. It will also be understood that one or more blocks of the flowcharts, and combinations of blocks in the flowcharts, can be implemented by special purpose hardware -based computer systems which perform the specified functions, or combinations of special purpose hardware and computer instructions.
  • FIG. 3 illustrates various operations in a method according to example embodiments of the present invention from the perspective of a UE 10.
  • the packet-switched domain component is too congested to provide packet-switched services to the UE 10, but the circuit-switched domain has sufficient resources to provide circuit-switched services to the UE 10.
  • the method includes causing transmission of a first mobility management message from a UE to a core network including a packet-switched (PS) domain and a circuit-switched (CS) domain.
  • the method may include causing transmission of the first mobility management message to a component (e.g. MME/SGSN 16) of the packet-switched domain.
  • This mobility management message may include, for example, a request to attach to the packet-switched domain, perform a routing area update, perform a tracking area update or receive a packet-switched service.
  • the method may also include receiving a rejection message at the UE 10 from the packet-switched domain component (e.g. MME/SGSN 16) in response to the first mobility management message.
  • a rejection message may be, for example, an attach reject message, a routing area update reject message, a tracking area update reject message or a service reject message.
  • the rejection message indicates congestion as a cause for rejection of the first mobility management message (e.g. cause value #22), and may also include a value of the packet-switched domain back-off timer. Consequently, the method may include running a packet-switched domain back-off timer (e.g.
  • the packet-switched domain back-off timer may be triggered to begin running whenever the UE 10 receives an indication that congestion is a cause for the rejection (e.g. cause value #22) within a rejection message.
  • the packet-switched domain back-off timer in this example indicates a time during which the UE 10 defers transmission of any further mobility management messages to the packet-switched domain component (e.g. MME/SGSN 16).
  • the rejection message also contains an indication that CS services are permitted and while the packet-switched domain back-off timer is running, the method further includes causing transmission of a second mobility management message from the UE 10 to a component of the circuit-switched domain (e.g. MSC 20), as shown at operation 48.
  • FIG. 4 illustrates various operations in a method according to example embodiments of the present invention from the perspective of a packet-switched domain component (e.g. MME/SGSN 16). Again, in this example, the packet-switched domain component is too congested to provide packet-switched services to the UE 10, but the circuit-switched domain has sufficient resources to provide circuit-switched services to the UE 10.
  • the method includes receiving a first mobility management message at a core network from a UE 10.
  • This mobility management message may include, for example, a request to attach to the packet-switched domain, perform a routing area update, perform a tracking area update or receive a packet- switched service.
  • the core network includes a packet-switched domain and a circuit- switched domain, and the first mobility management message is received at the packet- switched domain component.
  • the method also includes detecting congestion in the core network; and in response thereto, causing transmission of a rejection message from the packet-switched domain component to the UE in response to receipt of the first mobility management message, as shown in blocks 52 and 54.
  • a rejection message may be, for example, an attach reject message, a routing area update reject message, a tracking area update reject message, or a service reject message.
  • the rejection message indicates congestion as a cause for rejection of the first mobility management message (e.g. cause value # 22), and may also include a value of the packet-switched domain back-off timer. Consequently, receipt of the rejection message at the UE 10 causes the UE 10 to run a packet-switched domain back-off timer (e.g. starting at the packet-switched domain back-off timer value, or as another example, starting from zero and running up to the packet-switched domain back-off timer value) indicating a time during which the UE defers transmission of any further mobility management messages to the packet-switched domain component.
  • the packet-switched domain back-off timer may be triggered to begin running whenever the UE 10 receives an indication that congestion is a cause for the rejection (e.g. cause value #22) within a rejection message.
  • the rejection message indicates that circuit-switched services are permitted during running of the back-off timer. Receipt of the rejection message at the UE causes the UE to transmit a second mobility management message from the UE to a component of the circuit-switched domain (e.g. MSC 20) while the packet-switched domain back-off timer is running.
  • FIGS 5 and 6 are flowcharts of a system, method and program product according to example embodiments of the invention for the case that both the packet-switched domain and the circuit-switched domain are to too congested to provide services to the UE 10 at that particular time.
  • FIG. 5 illustrates various operations in a method according to example embodiments of the present invention from the perspective of a UE 10.
  • the method includes causing transmission of a first mobility management message from a UE 10 to a core network including a packet-switched domain and a circuit-switched domain.
  • This mobility management message may include, for example, a request to attach to the packet-switched domain, perform a routing area update, perform a tracking area update or receive a packet-switched service.
  • the method also includes receiving a rejection message at the UE 10 from the packet-switched domain component (e.g. MME/SGSN 16) in response to the first mobility management message.
  • a rejection message may be, for example, an attach reject message, a routing area update reject message, a service reject message or a tracking area update reject message.
  • the rejection message indicates congestion as a cause for rejection (e.g. cause value # 22) of the first mobility management message, and may also include a value of a packet-switched domain back-off timer. Consequently, the method may include running a packet-switched domain back-off timer (e.g.
  • the packet-switched domain back-off timer indicates a time during which the UE 10 defers transmission of any further mobility management messages to the packet-switched domain component (e.g. MME/SGSN 16).
  • the packet-switched domain back-off timer may be triggered to begin running whenever the UE 10 receives an indication that congestion is a cause for the rejection (e.g. cause value #22) within a rejection message.
  • the rejection message also contains an indication that circuit-switched services are forbidden.
  • the UE 10 upon receipt of an indication in the rejection message that circuit-switched services are forbidden, the UE 10 is also caused to defer transmission of any mobility management messages to the circuit- switched domain component during the running of the packet-switched domain back-off timer (as mentioned above for deferring transmission of mobility management messages to the packet-switched domain component).
  • the UE 10 upon receipt of an indication in the rejection message that circuit-switched services are forbidden, the UE 10 is caused to start a second, additional back-off timer (a circuit-switched domain back-off timer), which indicates a time during which the UE 10 is caused to defer transmission of any mobility management messages to the circuit-switched domain component (e.g. MSC 20).
  • the rejection message may include a value of the second (circuit-switched domain) back-off timer.
  • the UE 10 may be pre-configured or programmed with a circuit-switched domain back-off timer value for this second back-off timer.
  • there are separate first and second back-off timers which run to defer transmission of mobility management messages to the packet-switched domain component and the circuit-switched domain component respectively.
  • FIG. 6 illustrates various operations in a method according to example embodiments of the present invention from the perspective of a packet-switched domain component (e.g. MME/SGSN 16).
  • a packet-switched domain component e.g. MME/SGSN 16
  • the following embodiments are for use when both the circuit-switched domain component and the packet-switched domain component are too congested to provide services to the UE 10.
  • the method includes receiving at the packet-switched domain component of the core network a first mobility management message from a UE 10.
  • This mobility management message may include, for example, a request to attach to the packet- switched domain, perform a routing area update, perform a tracking area update or receive a packet-switched service.
  • the method further includes detecting congestion in the core network, as shown in block 64.
  • congestion is detected in both the packet- switched domain component and the circuit-switched domain component.
  • the packet-switched domain component is then caused to transmit a rejection message to the UE 10, as shown in block 66.
  • a rejection message may be, for example, an attach reject message, a routing area update reject message, a service reject message or a tracking area update reject message.
  • the rejection message indicates congestion as a cause for rejection of the first mobility management message (e.g. cause value # 22), and may also include a value of a packet- switched domain back-off timer. Consequently, receipt of the rejection message at the UE 10 causes the UE 10 to run a packet-switched domain back-off timer (e.g.
  • the packet-switched domain back-off timer may be triggered to begin running whenever the UE 10 receives an indication that congestion is a cause for the rejection (e.g. cause value #22) within a rejection message.
  • the rejection message also indicates that circuit-switched services are forbidden.
  • the UE 10 is caused to defer transmission of any mobility management messages to the circuit-switched domain component.
  • the UE 10 is caused to defer transmission of any mobility management messages to the circuit-switched domain component during the running of the packet-switched domain back-off timer (as mentioned above as being for deferring transmission of mobility management messages to the packet-switched domain component).
  • the UE 10 is caused to start a second, additional back-off timer (a circuit-switched domain back-off timer), and to defer transmission of any mobility management messages to the circuit-switched domain component during the running of this circuit-switched domain back-off timer.
  • the rejection message received from the packet-switched domain component may contain a value of the circuit-switched domain back-off timer.
  • the UE 10 may be preprogrammed with a value of the circuit-switched domain back-off timer, which it is configured to use only if the rejection message from the packet-switched domain component indicates that circuit-switched services are forbidden.
  • the rejection message sent from the packet-switched domain component explicitly indicates to the UE whether circuit switched services are permitted or forbidden.
  • the rejection message sent from the packet- switched domain component implicitly indicates whether circuit switched services are permitted or forbidden.
  • a rejection message including a value for the circuit-switched back-off timer implicitly indicates to the UE 10 that circuit switched services are forbidden
  • a rejection message that does not include a value for the circuit switched back-off timer implicitly indicates to the UE 10 that circuit switched services are permitted.
  • an apparatus for performing the methods of any of Figures 3 to 6 above may include processing circuitry (e.g. processing circuitry 32) configured to perform some or each of the operations (42-48,50-54, 56-60 or 62-66) described above, with or without some or all of the modifications described above.
  • the processing circuitry may, for example, be configured to perform the respective operations by performing hardware-implemented logical functions, executing stored instructions or executing algorithms for performing each of the operations.

Landscapes

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

Abstract

Selon l'invention, un premier message de gestion de mobilité est transmis d'un équipement utilisateur (10) à un réseau central comprenant des domaines à commutation de paquets et des domaines à commutation de circuits. Le premier message de gestion de mobilité est transmis (42) à une composante à domaines à commutation de paquets et un message de refus est reçu en réponse (44) de ladite composante. Ce message de refus indique comme cause du refus un encombrement lié au premier message de gestion de mobilité et indique également si des services à commutation de circuits sont autorisés ou interdits.
PCT/IB2012/052493 2011-05-19 2012-05-17 Procédés et appareil d'activation de services à commutation de circuits WO2012156943A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
DE112012002157.6T DE112012002157T5 (de) 2011-05-19 2012-05-17 Verfahren und Vorrichtung zum Ermöglichen von leitungsvermittelten Diensten

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
GB1108424.1 2011-05-19
US13/111,166 US20120294143A1 (en) 2011-05-19 2011-05-19 Enabling circuit-switched services during mobility management congestion control
US13/111,166 2011-05-19
GB1108424.1A GB2490948B (en) 2011-05-19 2011-05-19 Methods and apparatus for enabling circuit-switched services
US13/347,375 2012-01-10
US13/347,375 US8665716B2 (en) 2011-05-19 2012-01-10 Enabling circuit-switched services during mobility management congestion control

Publications (1)

Publication Number Publication Date
WO2012156943A1 true WO2012156943A1 (fr) 2012-11-22

Family

ID=47176373

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2012/052493 WO2012156943A1 (fr) 2011-05-19 2012-05-17 Procédés et appareil d'activation de services à commutation de circuits

Country Status (2)

Country Link
DE (1) DE112012002157T5 (fr)
WO (1) WO2012156943A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140003354A1 (en) * 2012-06-29 2014-01-02 Ozgur Ekici Providing a system information message having retry parameter values

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
CATT: "Discussion on APN based congestion control", 3GPP DRAFT; C1-103995 DISCUSSION ON THE APN BASED CONGESTION CONTROL, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG1, no. Barcelona; 20101011, 4 October 2010 (2010-10-04), XP050444591 *
KPN ET AL: "NAS level reject per APN with back-off timer function", 3GPP DRAFT; S2-104346_WAS_S2-104225_23401CR1726_NASBACKOFF, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Brunstad; 20100903, 3 September 2010 (2010-09-03), XP050459229 *
KPN: "NAS level attach reject in 2G-3G", 3GPP DRAFT; S2-104961, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Prague; 20101011, 6 October 2010 (2010-10-06), XP050459740 *
NTT DOCOMO: "Discussion about Call Attempt Restriction in PS domain", 3GPP DRAFT; C1-090889, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. San Antonio; 20090224, 24 February 2009 (2009-02-24), XP050311260 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140003354A1 (en) * 2012-06-29 2014-01-02 Ozgur Ekici Providing a system information message having retry parameter values

Also Published As

Publication number Publication date
DE112012002157T5 (de) 2014-02-20

Similar Documents

Publication Publication Date Title
US8665716B2 (en) Enabling circuit-switched services during mobility management congestion control
US11576088B2 (en) Method and apparatus for handling connections
AU2018449171B2 (en) Apparatus, method and computer program for connection management
EP3713258B1 (fr) Procédé et dispositif de rapport d'informations de localisation
EP2880885B1 (fr) Transmission de données
SE1300090A1 (sv) Handling wait time in a congested wireless communication network
WO2014153770A1 (fr) Procédé et appareil pour rétablir une communication avec un réseau
US20120202492A1 (en) Method and apparatus for enabling identification of a rejecting network in connection with registration area updating
JP2015531573A5 (fr)
WO2012107911A1 (fr) Procédé et appareil destinés à réagir à une erreur irréparable
US20210099912A1 (en) Rate control method, apparatus, and system
WO2018154355A1 (fr) Procédé et appareil de capture de paramètres d'utilisateur ou d'équipement utilisateur dans un système informatique de périphérie de réseau multi-accès
US20210274464A1 (en) Method for handling of network slice overload
WO2013072880A1 (fr) Procédé et appareil pour établir des communications
CN112995976B (zh) 允许用户设备从网络实体分离的方法
US11190974B2 (en) Device and method for controlling network congestion with RRC inactive
TW201448648A (zh) 用於在屬於社群網路的無線區域網路間漫遊之技術
WO2012156943A1 (fr) Procédés et appareil d'activation de services à commutation de circuits
CN108464038A (zh) 电路域回落的方法、基站、移动管理实体和终端
CN109548143B (zh) 一种寻呼处理方法及设备
GB2490948A (en) Indicating in mobility management rejection messages that circuit-switched services are permitted during congestion
US10051539B2 (en) Access network offloading method, device, and system
WO2021254434A1 (fr) Procédé et appareil de suspension d'un groupe de cellules secondaires
RU2777484C1 (ru) Аппарат, способ и компьютерная программа
JP2021516877A (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: 12727940

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 1120120021576

Country of ref document: DE

Ref document number: 112012002157

Country of ref document: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12727940

Country of ref document: EP

Kind code of ref document: A1