WO2015003753A1 - Redirection of m2m devices - Google Patents

Redirection of m2m devices Download PDF

Info

Publication number
WO2015003753A1
WO2015003753A1 PCT/EP2013/064832 EP2013064832W WO2015003753A1 WO 2015003753 A1 WO2015003753 A1 WO 2015003753A1 EP 2013064832 W EP2013064832 W EP 2013064832W WO 2015003753 A1 WO2015003753 A1 WO 2015003753A1
Authority
WO
WIPO (PCT)
Prior art keywords
management entity
network
message
entity
machine
Prior art date
Application number
PCT/EP2013/064832
Other languages
French (fr)
Inventor
Tuija Helena Hurtta
Original Assignee
Nokia Solutions And Networks Oy
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 Nokia Solutions And Networks Oy filed Critical Nokia Solutions And Networks Oy
Priority to PCT/EP2013/064832 priority Critical patent/WO2015003753A1/en
Publication of WO2015003753A1 publication Critical patent/WO2015003753A1/en

Links

Classifications

    • 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/06—Registration at serving network Location Register, VLR or user mobility server
    • H04W8/065—Registration at serving network Location Register, VLR or user mobility server involving selection of the user mobility server
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration

Definitions

  • the present invention relates to redirection of machine-to- machine (M2M) devices.
  • M2M machine-to- machine
  • the present invention relates to an apparatus, method and a program for redirection of M2M devices .
  • M2M optimized packet core network elements are planned with certain traffic characteristics in mind (e.g. smart meters sending small amount of data) and thus may be deployed to serve M2M devices with such traffic characteristics (and not to serve all M2M devices) .
  • M2M optimized MME/SGSN Mobility Management Entity/ Serving GPRS (General Packet Radio System) Support Node
  • 3GPP 3 rd Generation Partnership Project
  • selection of M2M optimized MME/SGSN may be done in the eNB/RNC (evolved NodeB / Radio Network Controller) with Low Access Priority Indication (LAPI) sent by the M2M device.
  • LAPI is supported by M2M devices according to 3GPP Release 10.
  • LAPI based MME/SGSN selection requires upgrade in the eNB/RNC.
  • LAPI itself does not tell much about the M2M device because it just indicates whether the M2M device is configured with "low access priority" or not. Based on customer discussions, more information is needed to determine whether or not M2M optimized packet core network elements should serve the M2M device .
  • the method further comprises causing forwarding, at the network entity, the attach request to the second management entity indicated in the received message;
  • the message is a message according to the SI application protocol ;
  • the message includes a low access priority indication for a network device, to which the attach request transmitted by the network entity belongs; - the message includes a globally unique temporary user equipment identity of the network device, to which the attach request transmitted by the network entity belongs;
  • the message includes an address of the second management entity
  • the message includes an indication for machine-to-machine communication or a category of a machine-to-machine device/subscription
  • the second management entity is a management entity optimized for machine-to-machine communication
  • the network entity is a base station according to Long Term Evolution/Long Term Evolution Advanced or a radio network controller according to 3G.
  • the method further comprises obtaining information about the network device from a register, and determining whether the network device requires reselection of the management entity based on the obtained information;
  • the message includes a low access priority indication for the network device, to which the attach request transmitted by the network entity belongs;
  • the message includes a globally unique temporary user equipment identity of the network device, to which the attach request transmitted by the network entity belongs;
  • the message includes an address of the second management entity
  • the message includes an indication for machine-to-machine communication or a category of a machine-to-machine device/subscription
  • the second management entity is a management entity optimized for machine-to-machine communication
  • the first and second management entity is a mobility management entity according to Long Term Evolution/Long Term Evolution Advanced or a Serving General Packet Radio System Support Node according to 3G.
  • an apparatus for use in a network entity comprising: at least one processor, at least one interface to at least one other network element, and at least one memory for storing instructions to be executed by the processor, wherein the at least one memory and the instructions are configured to, with the at least one processor, cause the apparatus at least to perform: causing transmission of arl attach request message to a first management entity,
  • the at least one memory and the instructions are further configured to, with the at least one processor, cause the apparatus to perform causing forwarding the attach request to the second management entity indicated in the received message ;
  • the message is a message according to the SI application protocol ;
  • the message includes a low access priority indication for a network device, to which the attach request transmitted by the network entity belongs;
  • the message includes a globally unique temporary user equipment identity of the network device, to which the attach request transmitted by the network entity belongs;
  • the message includes an address of the second management entity ;
  • the message includes an indication for machine-to-machine communication or a category of a machine-to-machine device/ subscription;
  • the second management entity is a management entity optimized for machine-to-machine communication
  • the network entity is a base station according to Long Term Evolution/Long Term Evolution Advanced or a radio network controller according to 3G.
  • an apparatus for use in a first management entity comprising:
  • At least one processor at least one interface to at least one other network element, and at least one memory for storing instructions to be executed by the processor, wherein the at least one memory and the instructions are configured to, with the at least one processor, cause the apparatus at least to perform: causing reception of an attach reguest for a network device from a network entity,
  • the network device if it is determined that the network device reguires reselection, composing a message instructing the network entity to select a second management entity for the network device .
  • the at least one memory and the instructions are further configured to, with the at least one processor, cause the apparatus to perform obtaining information about the network device from a register, and determining whether the network device requires reselection of the management entity based on the obtained information;
  • the message includes a low access priority indication for the network device, to which the attach request transmitted by the network entity belongs;
  • the message includes a globally unique temporary user equipment identity of the network device, to which the attach request transmitted by the network entity belongs;
  • the message includes an address of the second management entity
  • the message includes an indication for machine-to-machine communication or a category of a machine-to-machine device/subscription
  • the second management entity is a management entity optimized for machine-to-machine communication
  • the first and second management entity is a mobility management entity according to Long Term Evolution/Long Term Evolution Advanced or a Serving General Packet Radio System Support Node according to 3G.
  • an apparatus for use in a network entity comprising: means for causing transmission of an attach request message to a first management entity,
  • an apparatus for use in a network entity comprising: means for causing reception of an attach reguest for a network device from a network entity,
  • a computer program product comprising code means adapted to produce steps of any of the methods as described above when loaded into the memory of a computer.
  • a computer program product as defined above, wherein the computer program product comprises a computer-readable medium on which the software code portions are stored.
  • Fig. 1 is a signaling diagram illustrating an example for signaling according to certain embodiments of the present invention ;
  • Fig. 2 is a flowchart illustrating an example of a method according to certain embodiments of the present invention
  • Fig. 3 is a diagram illustrating an example of an apparatus according to certain embodiments of the present invention.
  • Fig. 4 is a flowchart illustrating another example of a method according to certain embodiments of the present invention.
  • Fig. 5 is a diagram illustrating another example of an apparatus according to certain embodiments of the present invention .
  • Basic system architecture of a communication network where examples of embodiments of the invention are applicable may comprise a commonly known architecture of one or more communication systems comprising a wired or wireless access network subsystem and a core network.
  • Such an architecture may comprise one or more access network control elements, radio access network elements, access service network gateways or base transceiver stations, such as a base station or eNB, which control a coverage area also referred to as a cell and with which one or more communication elements or terminal devices such as a UE or another device having a similar function, such as a modem chipset, a chip, a module etc., which can also be part of a UE or attached as a separate element to a UE, or the like, are capable to communicate via one or more channels for transmitting several types of data.
  • core network elements such as gateway network elements, policy and charging control network elements, mobility management entities and the like may be comprised.
  • nodes or network elements may comprise several means and components (not shown) which are reguired for control, processing and communication/signaling functionality.
  • Such means may comprise, for example, one or more processor units including one or more processing portions for executing instructions, programs and for processing data, memory means for storing instructions, programs and data, for serving as a work area of the processor or processing portion and the like (e.g.
  • processing portions should not be only considered to represent physical portions of one or more processors, but may also be considered as a logical division of the referred processing tasks performed by one or more processors .
  • Fig. 1 shows a signaling diagram according certain embodiments of the present invention.
  • a M2M device (not shown in Fig. 1), i.e. a device capable of performing machine-to-machine communication, first performs attach by sending Attach Reguest to the MME/SGSN via an eNB as shown in Step Sll in Fig. 1.
  • the Attach Reguest may be processed by a traditional MME/SGSN.
  • the traditional MME/SGSN detects in step S13 that the device is a M2M device by analyzing, e.g. APN (Access Point Name), IMSI (International Mobile Subscriber Identity) or IMEI (International Mobile Eguipment Identity).
  • the traditional MME/SGSN may also get additional information on the M2M device from the subscription data to detect M2M devices which should be served by M2M optimized MME/SGSNs (e.g. smart meters) and M2M devices which should be served by traditional MME/SGSNs (M2M devices for fleet/taxi management with high mobility).
  • Such subscription data is obtained from a HSS/HLR (Home Subscriber Server / Home Location Register) in a step S12 and thus reguires enhancements on MME/SGSN - HSS/HLR interfaces.
  • the subscription data obtained from the HSS/HLR may contain e.g. a M2M Optimized Processing Recommended attribute/flag or a M2M Subscription Category attribute (e.g. smart meter, fleet/taxi management, health, low mobility, etc.) .
  • the M2M category may indicate that the M2M device is a low mobility device. If the M2M device is not moving or has only low mobility, this means less signaling and thus it makes sense to optimize the MME/SGSN for M2M devices which are not moving, for example .
  • the traditional MME/SGSN then redirects the M2M device to a M2M optimized MME/SGSN.
  • the traditional MME/SGSN indicates to the eNB/RNC in a step S14 that another MME/SGSN needs to be selected to serve the M2M device.
  • the eNB/RNC selects an M2M optimized MME/SGSN and sends an Attach Reguest to the M2M optimized MME/SGSN in a step S15.
  • the attachment procedure continues as specified in 3GPP and as part of the attachment procedure, the M2M optimized MME/SGSN responds with an Attach Accept message in a step S16.
  • the attach reguest message is originally prepared by the M2M device. It is first forwarded from the eNB to the MME . Then from the MME back to the eNB, and from the eNB to the M2M MME.
  • the traditional MME sends a new SlAP (SI Application Protocol) signaling message (e.g. NAS (Network Access Server) Node Reselection Required or Reroute Required, as shown in step S14 in Fig. 1) to the eNB .
  • SlAP Sesion Initiation Protocol
  • the MME indicates with LAPI that NAS node (MME) reselection is required for a M2M device.
  • MME NAS node
  • the MME sends also other information elements to the eNB (e.g.
  • the eNB performs NAS node (MME) reselection with LAPI and selects a M2M optimized MME to serve the M2M device.
  • MME NAS node
  • the eNB signals with the M2M optimized MME and sends IMSI, original Attach Request from the M2M device and other relevant information elements to the M2M optimized MME, as shown in step S15 in Fig. 1.
  • This first option allows re-using LAPI based NAS node selection function in the eNB.
  • the LAPI comes from the M2M devices.
  • the LAPI does not come from M2M devices but is rather indicated towards the eNB from the MME based on M2M detection in the MME (e.g. with APN, IMSI, IMEI or new subscription information coming from the HSS) .
  • the procedure is similar as in the first option described above, but instead of sending LAPI, the traditional MME sends a special M2M GUTI (Globally Unique Temporary UE Identifier) to the eNB in step S14.
  • M2M GUTI Globally Unique Temporary UE Identifier
  • the eNB selects a M2M optimized MME.
  • This second option allows re-using GUTI based NAS node selection functionality in the eNB (basic eNB functionality) .
  • the 3GPP standard TS 23.003, Vll.5.0 (2013-03) describes GUTI as follows :
  • the GUTI has two main components:
  • the GUTI shall be constructed from the GUMMEI (Globally Unigue MME Identifier) and the M-TMSI.”
  • the traditional MME determines GUMMEI of a M2M optimized MME. This may happen e.g. with information configured in the traditional MME or by other means .
  • information may be configured in various ways, e.g. by configuring GUMMEI of a M2M optimized MME for all M2M devices, GUMMEI of a M2M optimized MME for M2M devices with a specific APN, GUMMEI of a M2M optimized MME for M2M devices with a specific M2M subscription category, etc.
  • the eNB after receiving the special M2M GUTI (Globally Unigue Temporary UE Identifier) from the traditional MME in step S14, the eNB selects a M2M optimized MME and sends an Attach Reguest to the M2M optimized MME/SGSN in a step S15.
  • the attachment procedure continues as specified in 3GPP and as part of the attachment procedure, the M2M optimized MME/SGSN responds with an Attach Accept message in a step S16.
  • the traditional MME sends a M2M Optimized MME Address to the eNB in step S14. Then, the eNB signals with the M2M optimized MME in steps S15 and S16 in a similar manner as described above.
  • the traditional MME sends a M2M Indication (or M2M Category) to the eNB in step S14.
  • the eNB selects a M2M optimized MME and signals with the M2M optimized MME in steps S15 and S16 in a similar manner as described above.
  • a new SlAP signaling message is proposed.
  • an existing SlAP signaling message may also be used if/when done in a backward compatible way (i.e. not confusing the eNB) .
  • an Attach Reguest from a traditional UE is processed by the M2M optimized MME, similar NAS Node Reselection is triggered from the M2M optimized MME to the eNB.
  • the methods according to certain embodiments of the present invention apply in a similar manner in this case for redirecting the traditional UE from the M2M optimized MME to the traditional MME.
  • attach procedure was described only as an example but the solutions above may also be used during other procedures (e.g. during mobility) if/when applicable .
  • the M2M optimized MME/SGSN allows M2M devices to be served with capacities and features reguired for M2M use cases .
  • Fig. 2 is a flowchart illustrating an example of a method according to certain embodiments of the present invention.
  • the method may be implemented in a network element, like e.g. a base station in a communication network, and comprises causing transmission, at the network entity, of an attach request message to a first management entity in a step S21, causing reception, at the network entity, of a message from the first management entity including an indication to select a second management entity in a step S22, and determining, at the network entity, in a step S23 to forward the attach request message to the second management entity based on the indication included in the received message.
  • a network element like e.g. a base station in a communication network, and comprises causing transmission, at the network entity, of an attach request message to a first management entity in a step S21, causing reception, at the network entity, of a message from the first management entity including an indication to select a second management entity in a step S22, and determining, at the network entity, in a step S23 to forward the attach request message to the second management entity based on the indication included in the received message.
  • the method further comprises causing forwarding, at the network entity, the attach request to the second management entity indicated in the received message.
  • the message is a message according to the SI application protocol.
  • the message includes a low access priority indication for a network device, to which the attach request transmitted by the network entity belongs .
  • the message includes a globally unique temporary user equipment identity of the network device, to which the attach request transmitted by the network entity belongs.
  • the message includes an address of the second management entity. According to certain embodiments of the present invention, the message includes an indication for machine-to-machine communication or a category of a machine-to-machine device/subscription .
  • the second management entity is a management entity optimized for machine-to-machine communication .
  • the network entity is a base station according to Long Term Evolution/Long Term Evolution Advanced or a radio network controller according to 3G
  • the network device is a M2M device like a user eguipment capable of performing machine-to- machine communication.
  • Fig. 3 is a block diagram showing an example of an apparatus according to certain embodiments of the present invention.
  • FIG. 3 a block circuit diagram illustrating a configuration of an apparatus 30, such as of a base station or a network entity, is shown, which is configured to implement the above described aspects of the invention.
  • the apparatus 30 shown in Fig. 3 may comprise several further elements or functions besides those described herein below, which are omitted herein for the sake of simplicity as they are not essential for understanding the invention.
  • the apparatus may be also another device having a similar function, such as a chipset, a chip, a module etc., which can also be part of a base station or attached as a separate element to a base station, or the like .
  • the apparatus 30 may comprise a processing function or processor 31, such as a CPU or the like, which executes instructions given by programs or the like related to the flow control mechanism.
  • the processor 31 may comprise one or more processing portions dedicated to specific processing as described below, or the processing may be run in a single processor. Portions for executing such specific processing may be also provided as discrete elements or within one or more further processors or processing portions, such as in one physical processor like a CPU or in several physical entities, for example.
  • Reference sign 32 denotes transceiver or input/output (I/O) units (interfaces) connected to the processor 31.
  • the I/O units 32 may be used for communicating with one or more management entities and or user eguipments.
  • the I/O units 32 may be a combined unit comprising communication eguipment towards several network elements, or may comprise a distributed structure with a plurality of different interfaces for different network elements .
  • Reference sign 33 denotes a memory usable, for example, for storing data and programs to be executed by the processor 31 and/or as a working storage of the processor 31.
  • the processor 31 is configured to execute processing related to the above described aspects.
  • the processor 31 is configured to cause transmission of an attach reguest message to a first management entity, cause reception of a message from the first management entity including an indication to select a second management entity, and determine to forward the attach reguest message to the second management entity based on the indication included in the received message .
  • Fig. 4 is a flowchart illustrating an example of a method according to certain embodiments of the present invention.
  • the method may be implemented in a network element, like e.g. a mobility management entity or serving GPRS support node in a communication network, and comprises causing reception, at a first management entity, of an attach reguest for a network device from a network entity in a step S41, determining, at the management entity, whether the network device reguires reselection of the management entity in a step S42, and, if it is determined that the network device reguires reselection, composing a message instructing the network entity to select a second management entity for the network device in a step S43.
  • a network element like e.g. a mobility management entity or serving GPRS support node in a communication network, and comprises causing reception, at a first management entity, of an attach reguest for a network device from a network entity in a step S41, determining, at the management entity, whether the network device reguires reselection of the management entity in a step S42, and,
  • the method further comprises obtaining information about the network device from a register, and determining whether the network device requires reselection of the management entity based on the obtained information.
  • the message includes a low access priority indication for the network device, to which the attach request transmitted by the network entity belongs .
  • the message includes a globally unique temporary user equipment identity of the network device, to which the attach request transmitted by the network entity belongs.
  • the message includes an address of the second management entity.
  • the message includes an indication for machine-to-machine communication or a category of a machine-to-machine device/subscription .
  • the second management entity is a management entity optimized for machine-to-machine communication .
  • the first and second management entity is a mobility management entity according to Long Term Evolution/Long Term Evolution Advanced or a Serving General Packet Radio System Support Node according to 3G.
  • Fig. 5 is a block diagram showing another example of an apparatus according to certain embodiments of the present invention .
  • FIG. 5 a block circuit diagram illustrating a configuration of an apparatus 50, such as of a management entity, is shown, which is configured to implement the above described aspects of the invention.
  • the apparatus 50 shown in Fig. 5 may comprise several further elements or functions besides those described herein below, which are omitted herein for the sake of simplicity as they are not essential for understanding the invention.
  • the apparatus may be also another device having a similar function, such as a chipset, a chip, a module etc., which can also be part of a management entity or attached as a separate element to a management entity, or the like.
  • the apparatus 50 may comprise a processing function or processor 51, such as a CPU or the like, which executes instructions given by programs or the like related to the flow control mechanism.
  • the processor 51 may comprise one or more processing portions dedicated to specific processing as described below, or the processing may be run in a single processor. Portions for executing such specific processing may be also provided as discrete elements or within one or more further processors or processing portions, such as in one physical processor like a CPU or in several physical entities, for example.
  • Reference sign 52 denotes transceiver or input/output (I/O) units (interfaces) connected to the processor 51.
  • the I/O units 52 may be used for communicating with one or more management entities, base stations, registers, other network elements, or the like.
  • the I/O units 52 may be a combined unit comprising communication eguipment towards several network elements, or may comprise a distributed structure with a plurality of different interfaces for different network elements.
  • Reference sign 53 denotes a memory usable, for example, for storing data and programs to be executed by the processor 51 and/or as a working storage of the processor 51.
  • the processor 51 is configured to execute processing related to the above described aspects.
  • the processor 51 is configured to cause reception of an attach reguest for a network device from a network entity, determine whether the network device reguires reselection of the management entity, and, if it is determined that the network device reguires reselection, compose a message instructing the network entity to select a second management entity for the network device.
  • the apparatus may comprise further units/means that are necessary for its respective operation as base station or management entity, respectively. However, a description of these units/means is omitted in this specification.
  • the arrangement of the functional blocks of the apparatus is not construed to limit the invention, and the functions may be performed by one block or further split into sub-blocks .
  • the apparatus (or some other means) is configured to perform some function
  • this is to be construed to be eguivalent to a description stating that a (i.e. at least one) processor or corresponding circuitry, potentially in cooperation with computer program code stored in the memory of the respective apparatus, is configured to cause the apparatus to perform at least the thus mentioned function.
  • function is to be construed to be eguivalently implementable by specifically configured circuitry or means for performing the respective function (i.e. the expression "unit configured to” is construed to be eguivalent to an expression such as "means for”) .
  • any method step is suitable to be implemented as software or by hardware without changing the idea of the aspects/embodiments and its modification in terms of the functionality implemented;
  • CMOS Complementary MOS
  • BiMOS Bipolar MOS
  • BiCMOS Bipolar CMOS
  • ECL emitter Coupled Logic
  • TTL Transistor-Transistor Logic
  • ASIC Application Specific IC
  • FPGA Field-programmable Gate Arrays
  • CPLD Complex Programmable Logic Device
  • DSP Digital Signal Processor
  • - devices, units or means can be implemented as individual devices, units or means, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device, unit or means is preserved;
  • an apparatus may be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of an apparatus or module, instead of being hardware implemented, be implemented as software in a (software) module such as a computer program or a computer program product comprising executable software code portions for execution/being run on a processor;
  • a device may be regarded as an apparatus or as an assembly of more than one apparatus, whether functionally in cooperation with each other or functionally independently of each other but in a same device housing, for example.
  • respective functional blocks or elements according to above-described aspects can be implemented by any known means, either in hardware and/or software, respectively, if it is only adapted to perform the described functions of the respective parts.
  • the mentioned method steps can be realized in individual functional blocks or by individual devices, or one or more of the method steps can be realized in a single functional block or by a single device .
  • any method step is suitable to be implemented as software or by hardware without changing the idea of the present invention.
  • Devices and means can be implemented as individual devices, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device is preserved. Such and similar principles are to be considered as known to a skilled person .
  • Software in the sense of the present description comprises software code as such comprising code means or portions or a computer program or a computer program product for performing the respective functions, as well as software (or a computer program or a computer program product) embodied on a tangible medium such as a computer-readable (storage) medium having stored thereon a respective data structure or code means /portions or embodied in a signal or in a chip, potentially during processing thereof.

Landscapes

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

Abstract

The present invention provides a method, apparatus and computer program product relating to redirection of M2M devices. The present invention includes causing transmission, at a network entity, of an attach request message to a first management entity, causing reception, at the network entity, of a message from the first management entity including an indication to select a second management entity, and determining, at the network entity, to forward the attach request message to the second management entity based on the indication included in the received message.

Description

DESCRIPTION
Redirection of M2M devices
Field of the invention
The present invention relates to redirection of machine-to- machine (M2M) devices. In particular, the present invention relates to an apparatus, method and a program for redirection of M2M devices .
Background of the invention
Recently, some operators are planning to use cellular accesses for M2M communications. Some operators plan to deploy an overlay packet core network for M2M communications. Traditional packet core network elements continue serving traditional subscribers whereas M2M optimized packet core network elements are planned to be deployed to serve M2M devices. The M2M optimized packet core elements are planned with certain traffic characteristics in mind (e.g. smart meters sending small amount of data) and thus may be deployed to serve M2M devices with such traffic characteristics (and not to serve all M2M devices) .
Some solutions to select M2M optimized MME/SGSN (Mobility Management Entity/ Serving GPRS (General Packet Radio System) Support Node) has already been discussed/agreed in 3GPP (3rd Generation Partnership Project). In 3GPP, it has been agreed that selection of M2M optimized MME/SGSN may be done in the eNB/RNC (evolved NodeB / Radio Network Controller) with Low Access Priority Indication (LAPI) sent by the M2M device. LAPI is supported by M2M devices according to 3GPP Release 10.
LAPI based MME/SGSN selection requires upgrade in the eNB/RNC.
LAPI itself does not tell much about the M2M device because it just indicates whether the M2M device is configured with "low access priority" or not. Based on customer discussions, more information is needed to determine whether or not M2M optimized packet core network elements should serve the M2M device .
There are already millions of M2M devices in the market which can not send LAPI to the network. Thus, other MME/SGSN selection solutions need to be considered when LAPI is not supported by the M2M devices.
In addition to LAPI based MME/SGSN selection, another proposal has also been discussed, where the traditional MME/SGSN requests the M2M device to perform detach with "re-attach required" and during re-attach a M2M optimized MME/SGSN is selected. This, however, is not an optimal solution as the M2M device is first detached and then needs to re-attach to the network . Summary of the Invention
It is therefore an object of the present invention to overcome the above mentioned problems and to provide methods, apparatuses and a program for redirection of M2M devices.
According to an aspect of the present invention there is provided a method comprising:
causing transmission, at a network entity, of an attach request message to a first management entity,
causing reception, at the network entity, of a message from the first management entity including an indication to select a second management entity, and
determining, at the network entity, to forward the attach request message to the second management entity based on the indication included in the received message.
According to further refinements of the present invention as defined under the above aspect
- the method further comprises causing forwarding, at the network entity, the attach request to the second management entity indicated in the received message;
- the message is a message according to the SI application protocol ;
- the message includes a low access priority indication for a network device, to which the attach request transmitted by the network entity belongs; - the message includes a globally unique temporary user equipment identity of the network device, to which the attach request transmitted by the network entity belongs;
- the message includes an address of the second management entity;
- the message includes an indication for machine-to-machine communication or a category of a machine-to-machine device/subscription;
- the second management entity is a management entity optimized for machine-to-machine communication;
- the network entity is a base station according to Long Term Evolution/Long Term Evolution Advanced or a radio network controller according to 3G.
According to another aspect of the present invention there is provided a method comprising:
causing reception, at a first management entity, of an attach request for a network device from a network entity,
determining, at the management entity, whether the network device requires reselection of the management entity, and
if it is determined that the network device requires reselection, composing a message instructing the network entity to select a second management entity for the network device .
According to further refinements of the present invention as defined under the above aspect
- the method further comprises obtaining information about the network device from a register, and determining whether the network device requires reselection of the management entity based on the obtained information;
- the message includes a low access priority indication for the network device, to which the attach request transmitted by the network entity belongs;
- the message includes a globally unique temporary user equipment identity of the network device, to which the attach request transmitted by the network entity belongs;
- the message includes an address of the second management entity;
- the message includes an indication for machine-to-machine communication or a category of a machine-to-machine device/subscription;
- the second management entity is a management entity optimized for machine-to-machine communication;
- the first and second management entity is a mobility management entity according to Long Term Evolution/Long Term Evolution Advanced or a Serving General Packet Radio System Support Node according to 3G.
According to another aspect of the present invention there is provided an apparatus for use in a network entity, comprising: at least one processor, at least one interface to at least one other network element, and at least one memory for storing instructions to be executed by the processor, wherein the at least one memory and the instructions are configured to, with the at least one processor, cause the apparatus at least to perform: causing transmission of arl attach request message to a first management entity,
causing reception of a mes sage from the first management entity including an indication to select a second management entity, and
determining to forward the attach request message to the second management entity based on the indication included in the received message.
According to further refinements of the present invention as defined under the above aspect
- the at least one memory and the instructions are further configured to, with the at least one processor, cause the apparatus to perform causing forwarding the attach request to the second management entity indicated in the received message ;
- the message is a message according to the SI application protocol ;
- the message includes a low access priority indication for a network device, to which the attach request transmitted by the network entity belongs;
- the message includes a globally unique temporary user equipment identity of the network device, to which the attach request transmitted by the network entity belongs;
- the message includes an address of the second management entity ;
- the message includes an indication for machine-to-machine communication or a category of a machine-to-machine device/ subscription;
- the second management entity is a management entity optimized for machine-to-machine communication; - the network entity is a base station according to Long Term Evolution/Long Term Evolution Advanced or a radio network controller according to 3G.
According to another aspect of the present invention there is provided an apparatus for use in a first management entity, comprising :
at least one processor, at least one interface to at least one other network element, and at least one memory for storing instructions to be executed by the processor, wherein the at least one memory and the instructions are configured to, with the at least one processor, cause the apparatus at least to perform: causing reception of an attach reguest for a network device from a network entity,
determining whether the network device reguires reselection of the management entity, and
if it is determined that the network device reguires reselection, composing a message instructing the network entity to select a second management entity for the network device .
According to further refinements of the present invention as defined under the above aspect
- the at least one memory and the instructions are further configured to, with the at least one processor, cause the apparatus to perform obtaining information about the network device from a register, and determining whether the network device requires reselection of the management entity based on the obtained information;
- the message includes a low access priority indication for the network device, to which the attach request transmitted by the network entity belongs;
- the message includes a globally unique temporary user equipment identity of the network device, to which the attach request transmitted by the network entity belongs;
- the message includes an address of the second management entity;
- the message includes an indication for machine-to-machine communication or a category of a machine-to-machine device/subscription;
- the second management entity is a management entity optimized for machine-to-machine communication;
- the first and second management entity is a mobility management entity according to Long Term Evolution/Long Term Evolution Advanced or a Serving General Packet Radio System Support Node according to 3G.
According to another aspect of the present invention there is provided an apparatus for use in a network entity, comprising: means for causing transmission of an attach request message to a first management entity,
means for causing reception of a message from the first management entity including an indication to select a second management entity, and
means for determining to forward the attach request message to the second management entity based on the indication included in the received message. According to another aspect of the present invention there is provided an apparatus for use in a network entity, comprising: means for causing reception of an attach reguest for a network device from a network entity,
means for determining whether the network device reguires reselection of the management entity, and
means for composing, if it is determined that the network device reguires reselection, a message instructing the network entity to select a second management entity for the network device .
According to another aspect of the present invention there is provided a computer program product comprising code means adapted to produce steps of any of the methods as described above when loaded into the memory of a computer.
According to a still further aspect of the invention there is provided a computer program product as defined above, wherein the computer program product comprises a computer-readable medium on which the software code portions are stored.
According to a still further aspect of the invention there is provided a computer program product as defined above, wherein the program is directly loadable into an internal memory of the processing device.
Brief Description of the Drawings These and other objects, features, details and advantages will become more fully apparent from the following detailed description of aspects /embodiments of the present invention which is to be taken in conjunction with the appended drawings, in which:
Fig. 1 is a signaling diagram illustrating an example for signaling according to certain embodiments of the present invention ;
Fig. 2 is a flowchart illustrating an example of a method according to certain embodiments of the present invention;
Fig. 3 is a diagram illustrating an example of an apparatus according to certain embodiments of the present invention;
Fig. 4 is a flowchart illustrating another example of a method according to certain embodiments of the present invention;
Fig. 5 is a diagram illustrating another example of an apparatus according to certain embodiments of the present invention .
Detailed Description
In the following, examples and embodiments of the present invention are described with reference to the drawings. For illustrating the present invention, the examples and embodiments will be described in connection with a cellular communication network based on a 3GPP based communication system, for example an LTE/LTE-A based system or a system according to 3G. However, it is to be noted that the present invention is not limited to an application using such types of communication system, but is also applicable in other types of communication systems and the like.
Basic system architecture of a communication network where examples of embodiments of the invention are applicable may comprise a commonly known architecture of one or more communication systems comprising a wired or wireless access network subsystem and a core network. Such an architecture may comprise one or more access network control elements, radio access network elements, access service network gateways or base transceiver stations, such as a base station or eNB, which control a coverage area also referred to as a cell and with which one or more communication elements or terminal devices such as a UE or another device having a similar function, such as a modem chipset, a chip, a module etc., which can also be part of a UE or attached as a separate element to a UE, or the like, are capable to communicate via one or more channels for transmitting several types of data. Furthermore, core network elements such as gateway network elements, policy and charging control network elements, mobility management entities and the like may be comprised.
The general functions and interconnections of the described elements, which also depend on the actual network type, are known to those skilled in the art and described in corresponding specifications, so that a detailed description thereof is omitted herein. However, it is to be noted that several additional network elements and signaling links may be employed for a communication to or from a communication element or terminal device like a UE and a communication network control element like a base transceiver station or eNB, besides those described in detail herein below.
Furthermore, the described network elements, such as communication network control elements, like an eNB, management entities such as a MME, and the like, as well as corresponding functions as described herein may be implemented by software, e.g. by a computer program product for a computer, and/or by hardware. In any case, for executing their respective functions, correspondingly used devices, nodes or network elements may comprise several means and components (not shown) which are reguired for control, processing and communication/signaling functionality. Such means may comprise, for example, one or more processor units including one or more processing portions for executing instructions, programs and for processing data, memory means for storing instructions, programs and data, for serving as a work area of the processor or processing portion and the like (e.g. ROM, RAM, EEPROM, and the like), input means for inputting data and instructions by software (e.g. floppy disc, CD-ROM, EEPROM, and the like), user interface means for providing monitor and manipulation possibilities to a user (e.g. a screen, a keyboard and the like), interface means for establishing links and/or connections under the control of the processor unit or portion (e.g. wired and wireless interface means, an antenna, etc.) and the like. It is to be noted that in the present specification processing portions should not be only considered to represent physical portions of one or more processors, but may also be considered as a logical division of the referred processing tasks performed by one or more processors .
Fig. 1 shows a signaling diagram according certain embodiments of the present invention.
According to certain embodiments of the present invention, a M2M device (not shown in Fig. 1), i.e. a device capable of performing machine-to-machine communication, first performs attach by sending Attach Reguest to the MME/SGSN via an eNB as shown in Step Sll in Fig. 1. When the MME/SGSN selection happens as today, the Attach Reguest may be processed by a traditional MME/SGSN.
The traditional MME/SGSN detects in step S13 that the device is a M2M device by analyzing, e.g. APN (Access Point Name), IMSI (International Mobile Subscriber Identity) or IMEI (International Mobile Eguipment Identity). The traditional MME/SGSN may also get additional information on the M2M device from the subscription data to detect M2M devices which should be served by M2M optimized MME/SGSNs (e.g. smart meters) and M2M devices which should be served by traditional MME/SGSNs (M2M devices for fleet/taxi management with high mobility). Such subscription data is obtained from a HSS/HLR (Home Subscriber Server / Home Location Register) in a step S12 and thus reguires enhancements on MME/SGSN - HSS/HLR interfaces. The subscription data obtained from the HSS/HLR may contain e.g. a M2M Optimized Processing Recommended attribute/flag or a M2M Subscription Category attribute (e.g. smart meter, fleet/taxi management, health, low mobility, etc.) . For example, the M2M category may indicate that the M2M device is a low mobility device. If the M2M device is not moving or has only low mobility, this means less signaling and thus it makes sense to optimize the MME/SGSN for M2M devices which are not moving, for example .
The traditional MME/SGSN then redirects the M2M device to a M2M optimized MME/SGSN. The traditional MME/SGSN indicates to the eNB/RNC in a step S14 that another MME/SGSN needs to be selected to serve the M2M device.
Then, the eNB/RNC selects an M2M optimized MME/SGSN and sends an Attach Reguest to the M2M optimized MME/SGSN in a step S15. The attachment procedure continues as specified in 3GPP and as part of the attachment procedure, the M2M optimized MME/SGSN responds with an Attach Accept message in a step S16.
Thus, in short, as an example, the attach reguest message is originally prepared by the M2M device. It is first forwarded from the eNB to the MME . Then from the MME back to the eNB, and from the eNB to the M2M MME.
In the following, some options for signaling between the traditional MME and eNB are described (same or similar signaling applies between the traditional SGSN and RNC) . In a first option, the traditional MME sends a new SlAP (SI Application Protocol) signaling message (e.g. NAS (Network Access Server) Node Reselection Required or Reroute Required, as shown in step S14 in Fig. 1) to the eNB . In the SlAP signaling message, the MME indicates with LAPI that NAS node (MME) reselection is required for a M2M device. In the SlAP signaling message, the MME sends also other information elements to the eNB (e.g. IMSI, original Attach Request from the M2M device and other relevant information elements) . The eNB performs NAS node (MME) reselection with LAPI and selects a M2M optimized MME to serve the M2M device. The eNB signals with the M2M optimized MME and sends IMSI, original Attach Request from the M2M device and other relevant information elements to the M2M optimized MME, as shown in step S15 in Fig. 1.
This first option allows re-using LAPI based NAS node selection function in the eNB.
As described above, in the known LAPI based MME/SGSN selection, the LAPI comes from the M2M devices. In this first option according to certain embodiments of the present invention, the LAPI does not come from M2M devices but is rather indicated towards the eNB from the MME based on M2M detection in the MME (e.g. with APN, IMSI, IMEI or new subscription information coming from the HSS) .
According to a second option of certain embodiments of the present invention, the procedure is similar as in the first option described above, but instead of sending LAPI, the traditional MME sends a special M2M GUTI (Globally Unique Temporary UE Identifier) to the eNB in step S14. With the special M2M GUTI, the eNB selects a M2M optimized MME.
This second option allows re-using GUTI based NAS node selection functionality in the eNB (basic eNB functionality) .
The 3GPP standard TS 23.003, Vll.5.0 (2013-03) describes GUTI as follows :
"The GUTI has two main components:
- one that uniguely identifies the MME which allocated the GUTI; and
- one that uniguely identifies the UE within the MME that allocated the GUTI .
The GUTI shall be constructed from the GUMMEI (Globally Unigue MME Identifier) and the M-TMSI."
In this second option, the traditional MME determines GUMMEI of a M2M optimized MME. This may happen e.g. with information configured in the traditional MME or by other means . To the MME, information may be configured in various ways, e.g. by configuring GUMMEI of a M2M optimized MME for all M2M devices, GUMMEI of a M2M optimized MME for M2M devices with a specific APN, GUMMEI of a M2M optimized MME for M2M devices with a specific M2M subscription category, etc.
Thus, according to the second option, after receiving the special M2M GUTI (Globally Unigue Temporary UE Identifier) from the traditional MME in step S14, the eNB selects a M2M optimized MME and sends an Attach Reguest to the M2M optimized MME/SGSN in a step S15. The attachment procedure continues as specified in 3GPP and as part of the attachment procedure, the M2M optimized MME/SGSN responds with an Attach Accept message in a step S16.
In a third option of certain embodiments of the present invention, which is similar to the first option, the traditional MME sends a M2M Optimized MME Address to the eNB in step S14. Then, the eNB signals with the M2M optimized MME in steps S15 and S16 in a similar manner as described above.
In a fourth option of certain embodiments of the present invention, which is similar to the first option, the traditional MME sends a M2M Indication (or M2M Category) to the eNB in step S14. The eNB selects a M2M optimized MME and signals with the M2M optimized MME in steps S15 and S16 in a similar manner as described above.
According to the above described first to fourth options according to certain embodiments of the present invention, a new SlAP signaling message is proposed. However, it is noted that also an existing SlAP signaling message may also be used if/when done in a backward compatible way (i.e. not confusing the eNB) .
If for any reason, an Attach Reguest from a traditional UE is processed by the M2M optimized MME, similar NAS Node Reselection is triggered from the M2M optimized MME to the eNB. In this case, parameters mentioned in the first to fourth options described above are used in a different way to indicate that a traditional MME needs to be selected (e.g. LAPI = 0, LAPI is not present, GUTI points to a traditional MME, traditional MME Address is given, M2M Indication/Category = 0, etc.) . This way, it is ensured that the M2M optimized MME is not used to serve traditional UEs.
Hence, the methods according to certain embodiments of the present invention apply in a similar manner in this case for redirecting the traditional UE from the M2M optimized MME to the traditional MME.
The examples above are given for LTE access but the solutions above are applicable also for SGSN - RNC signaling according to 3G. In this regard, "MME" is then replaced with "SGSN", "eNB" is replaced with "RNC" and "HSS" is replaced with "HLR" in the descriptions above and the signaling is similar to the one described above.
Further, it is noted that the attach procedure was described only as an example but the solutions above may also be used during other procedures (e.g. during mobility) if/when applicable .
The M2M optimized MME/SGSN allows M2M devices to be served with capacities and features reguired for M2M use cases .
Fig. 2 is a flowchart illustrating an example of a method according to certain embodiments of the present invention.
According to certain embodiments of the present invention, the method may be implemented in a network element, like e.g. a base station in a communication network, and comprises causing transmission, at the network entity, of an attach request message to a first management entity in a step S21, causing reception, at the network entity, of a message from the first management entity including an indication to select a second management entity in a step S22, and determining, at the network entity, in a step S23 to forward the attach request message to the second management entity based on the indication included in the received message.
According to certain embodiments of the present invention, the method further comprises causing forwarding, at the network entity, the attach request to the second management entity indicated in the received message.
According to certain embodiments of the present invention, the message is a message according to the SI application protocol.
According to certain embodiments of the present invention, the message includes a low access priority indication for a network device, to which the attach request transmitted by the network entity belongs .
According to certain embodiments of the present invention, the message includes a globally unique temporary user equipment identity of the network device, to which the attach request transmitted by the network entity belongs.
According to certain embodiments of the present invention, the message includes an address of the second management entity. According to certain embodiments of the present invention, the message includes an indication for machine-to-machine communication or a category of a machine-to-machine device/subscription .
According to certain embodiments of the present invention, the second management entity is a management entity optimized for machine-to-machine communication .
According to certain embodiments of the present invention, the network entity is a base station according to Long Term Evolution/Long Term Evolution Advanced or a radio network controller according to 3G, and the network device is a M2M device like a user eguipment capable of performing machine-to- machine communication.
Fig. 3 is a block diagram showing an example of an apparatus according to certain embodiments of the present invention.
In Fig. 3, a block circuit diagram illustrating a configuration of an apparatus 30, such as of a base station or a network entity, is shown, which is configured to implement the above described aspects of the invention. It is to be noted that the apparatus 30 shown in Fig. 3 may comprise several further elements or functions besides those described herein below, which are omitted herein for the sake of simplicity as they are not essential for understanding the invention. Furthermore, even though reference is made to a base station or network entity, the apparatus may be also another device having a similar function, such as a chipset, a chip, a module etc., which can also be part of a base station or attached as a separate element to a base station, or the like .
The apparatus 30 may comprise a processing function or processor 31, such as a CPU or the like, which executes instructions given by programs or the like related to the flow control mechanism. The processor 31 may comprise one or more processing portions dedicated to specific processing as described below, or the processing may be run in a single processor. Portions for executing such specific processing may be also provided as discrete elements or within one or more further processors or processing portions, such as in one physical processor like a CPU or in several physical entities, for example. Reference sign 32 denotes transceiver or input/output (I/O) units (interfaces) connected to the processor 31. The I/O units 32 may be used for communicating with one or more management entities and or user eguipments. The I/O units 32 may be a combined unit comprising communication eguipment towards several network elements, or may comprise a distributed structure with a plurality of different interfaces for different network elements . Reference sign 33 denotes a memory usable, for example, for storing data and programs to be executed by the processor 31 and/or as a working storage of the processor 31.
The processor 31 is configured to execute processing related to the above described aspects. In particular, the processor 31 is configured to cause transmission of an attach reguest message to a first management entity, cause reception of a message from the first management entity including an indication to select a second management entity, and determine to forward the attach reguest message to the second management entity based on the indication included in the received message .
For further functions of the apparatus according to further example embodiments of the present invention, reference is made to the above description of methods according to certain embodiments of the present invention, as described in connection with Fig. 2.
Fig. 4 is a flowchart illustrating an example of a method according to certain embodiments of the present invention.
According to certain embodiments of the present invention, the method may be implemented in a network element, like e.g. a mobility management entity or serving GPRS support node in a communication network, and comprises causing reception, at a first management entity, of an attach reguest for a network device from a network entity in a step S41, determining, at the management entity, whether the network device reguires reselection of the management entity in a step S42, and, if it is determined that the network device reguires reselection, composing a message instructing the network entity to select a second management entity for the network device in a step S43.
According to certain embodiments of the present invention, the method further comprises obtaining information about the network device from a register, and determining whether the network device requires reselection of the management entity based on the obtained information.
According to certain embodiments of the present invention, the message includes a low access priority indication for the network device, to which the attach request transmitted by the network entity belongs .
According to certain embodiments of the present invention, the message includes a globally unique temporary user equipment identity of the network device, to which the attach request transmitted by the network entity belongs.
According to certain embodiments of the present invention, the message includes an address of the second management entity.
According to certain embodiments of the present invention, the message includes an indication for machine-to-machine communication or a category of a machine-to-machine device/subscription .
According to certain embodiments of the present invention, the second management entity is a management entity optimized for machine-to-machine communication .
According to certain embodiments of the present invention, the first and second management entity is a mobility management entity according to Long Term Evolution/Long Term Evolution Advanced or a Serving General Packet Radio System Support Node according to 3G. Fig. 5 is a block diagram showing another example of an apparatus according to certain embodiments of the present invention .
In Fig. 5, a block circuit diagram illustrating a configuration of an apparatus 50, such as of a management entity, is shown, which is configured to implement the above described aspects of the invention. It is to be noted that the apparatus 50 shown in Fig. 5 may comprise several further elements or functions besides those described herein below, which are omitted herein for the sake of simplicity as they are not essential for understanding the invention. Furthermore, even though reference is made to a management entity, the apparatus may be also another device having a similar function, such as a chipset, a chip, a module etc., which can also be part of a management entity or attached as a separate element to a management entity, or the like.
The apparatus 50 may comprise a processing function or processor 51, such as a CPU or the like, which executes instructions given by programs or the like related to the flow control mechanism. The processor 51 may comprise one or more processing portions dedicated to specific processing as described below, or the processing may be run in a single processor. Portions for executing such specific processing may be also provided as discrete elements or within one or more further processors or processing portions, such as in one physical processor like a CPU or in several physical entities, for example. Reference sign 52 denotes transceiver or input/output (I/O) units (interfaces) connected to the processor 51. The I/O units 52 may be used for communicating with one or more management entities, base stations, registers, other network elements, or the like. The I/O units 52 may be a combined unit comprising communication eguipment towards several network elements, or may comprise a distributed structure with a plurality of different interfaces for different network elements. Reference sign 53 denotes a memory usable, for example, for storing data and programs to be executed by the processor 51 and/or as a working storage of the processor 51.
The processor 51 is configured to execute processing related to the above described aspects. In particular, the processor 51 is configured to cause reception of an attach reguest for a network device from a network entity, determine whether the network device reguires reselection of the management entity, and, if it is determined that the network device reguires reselection, compose a message instructing the network entity to select a second management entity for the network device.
For further functions of the apparatus according to further example embodiments of the present invention, reference is made to the above description of methods according to certain embodiments of the present invention, as described in connection with Fig. 4.
In the foregoing exemplary description of the apparatus, only the units/means that are relevant for understanding the principles of the invention have been described using functional blocks. The apparatus may comprise further units/means that are necessary for its respective operation as base station or management entity, respectively. However, a description of these units/means is omitted in this specification. The arrangement of the functional blocks of the apparatus is not construed to limit the invention, and the functions may be performed by one block or further split into sub-blocks .
When in the foregoing description it is stated that the apparatus (or some other means) is configured to perform some function, this is to be construed to be eguivalent to a description stating that a (i.e. at least one) processor or corresponding circuitry, potentially in cooperation with computer program code stored in the memory of the respective apparatus, is configured to cause the apparatus to perform at least the thus mentioned function. Also, such function is to be construed to be eguivalently implementable by specifically configured circuitry or means for performing the respective function (i.e. the expression "unit configured to" is construed to be eguivalent to an expression such as "means for") .
For the purpose of the present invention as described herein above, it should be noted that
- method steps likely to be implemented as software code portions and being run using a processor at an apparatus (as examples of devices, apparatuses and/or modules thereof, or as examples of entities including apparatuses and/or modules therefore), are software code independent and can be specified using any known or future developed programming language as long as the functionality defined by the method steps is preserved;
- generally, any method step is suitable to be implemented as software or by hardware without changing the idea of the aspects/embodiments and its modification in terms of the functionality implemented;
- method steps and/or devices, units or means likely to be implemented as hardware components at the above-defined apparatuses, or any module(s) thereof, (e.g., devices carrying out the functions of the apparatuses according to the aspects/embodiments as described above) are hardware independent and can be implemented using any known or future developed hardware technology or any hybrids of these, such as MOS (Metal Oxide Semiconductor), CMOS (Complementary MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter Coupled Logic), TTL (Transistor-Transistor Logic), etc., using for example ASIC (Application Specific IC (Integrated Circuit)) components, FPGA (Field-programmable Gate Arrays) components, CPLD (Complex Programmable Logic Device) components or DSP (Digital Signal Processor) components;
- devices, units or means (e.g. the above-defined apparatuses, or any one of their respective units/means) can be implemented as individual devices, units or means, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device, unit or means is preserved;
- an apparatus may be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of an apparatus or module, instead of being hardware implemented, be implemented as software in a (software) module such as a computer program or a computer program product comprising executable software code portions for execution/being run on a processor;
- a device may be regarded as an apparatus or as an assembly of more than one apparatus, whether functionally in cooperation with each other or functionally independently of each other but in a same device housing, for example.
In general, it is to be noted that respective functional blocks or elements according to above-described aspects can be implemented by any known means, either in hardware and/or software, respectively, if it is only adapted to perform the described functions of the respective parts. The mentioned method steps can be realized in individual functional blocks or by individual devices, or one or more of the method steps can be realized in a single functional block or by a single device .
Generally, any method step is suitable to be implemented as software or by hardware without changing the idea of the present invention. Devices and means can be implemented as individual devices, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device is preserved. Such and similar principles are to be considered as known to a skilled person . Software in the sense of the present description comprises software code as such comprising code means or portions or a computer program or a computer program product for performing the respective functions, as well as software (or a computer program or a computer program product) embodied on a tangible medium such as a computer-readable (storage) medium having stored thereon a respective data structure or code means /portions or embodied in a signal or in a chip, potentially during processing thereof.
It is noted that the aspects/embodiments and general and specific examples described above are provided for illustrative purposes only and are in no way intended that the present invention is restricted thereto. Rather, it is the intention that all variations and modifications which fall within the scope of the appended claims are covered.

Claims

1. A method, comprising:
causing transmission, at a network entity, of an attach request message to a first management entity,
causing reception, at the network entity, of a message from the first management entity including an indication to select a second management entity, and
determining, at the network entity, to forward the attach request message to the second management entity based on the indication included in the received message.
2. The method according to claim 1, further comprising:
causing forwarding, at the network entity, the attach request to the second management entity indicated in the received message.
3. The method according to claim 1 or 2, wherein
the message is a message according to the SI application protocol .
4. The method according to any one of claims 1 to 3, wherein the message includes a low access priority indication for a network device, to which the attach request transmitted by the network entity belongs.
5. The method according to any one of claims 1 to 3, wherein the message includes a globally unique temporary user equipment identity of the network device, to which the attach request transmitted by the network entity belongs.
6. The method according to any one of claims 1 to 3, wherein the message includes an address of the second management entity .
7. The method according to any one of claims 1 to 3, wherein the message includes an indication for machine-to-machine communication or a category of a machine-to-machine device/subscription .
8. The method according to any one of claims 1 to 7, wherein the second management entity is a management entity optimized for machine-to-machine communication .
9. The method according to any one of claims 1 to 8, wherein the network entity is a base station according to Long Term Evolution/Long Term Evolution Advanced or a radio network controller according to 3G.
10. A method, comprising:
causing reception, at a first management entity, of an attach request for a network device from a network entity,
determining, at the management entity, whether the network device requires reselection of the management entity, and
if it is determined that the network device requires reselection, composing a message instructing the network entity to select a second management entity for the network device .
11. The method according to claim 10, further comprising obtaining information about the network device from a register, and
determining whether the network device requires reselection of the management entity based on the obtained information .
12. The method according to claim 10 or 11, wherein
the message includes a low access priority indication for the network device, to which the attach request transmitted by the network entity belongs.
13. The method according to claim 10 or 11, wherein
the message includes a globally unique temporary user equipment identity of the network device, to which the attach request transmitted by the network entity belongs.
14. The method according to claim 10 or 11, wherein
the message includes an address of the second management entity .
15. The method according to claim 10 or 11, wherein
the message includes an indication for machine-to-machine communication or a category of a machine-to-machine device/subscription .
16. The method according to any one of claims 10 to 15, wherein
the second management entity is a management entity optimized for machine-to-machine communication.
17. The method according to any one of claims 10 to 16, wherein the first and second management entity is a mobility management entity according to Long Term Evolution/Long Term Evolution Advanced or a Serving General Packet Radio System Support Node according to 3G.
18. An apparatus for use in a network entity, comprising:
at least one processor, at least one interface to at least one other network element, and at least one memory for storing instructions to be executed by the processor, wherein the at least one memory and the instructions are configured to, with the at least one processor, cause the apparatus at least to perform: causing transmission of an attach reguest message to a first management entity,
causing reception of a message from the first management entity including an indication to select a second management entity, and
determining to forward the attach reguest message to the second management entity based on the indication included in the received message.
19. The apparatus according to claim 18, wherein the at least one memory and the instructions are further configured to, with the at least one processor, cause the apparatus to perform :
causing forwarding the attach reguest to the second management entity indicated in the received message.
20. The apparatus according to claim 18 or 19, wherein
the message is a message according to the SI application protocol .
21. The apparatus according to any one of claims 18 to wherein
the message includes a low access priority indication a network device, to which the attach request transmitted the network entity belongs.
22. The apparatus according to any one of claims 18 to 20, wherein
the message includes a globally unique temporary user equipment identity of the network device, to which the attach request transmitted by the network entity belongs.
23. The apparatus according to any one of claims 18 to 20, wherein
the message includes an address of the second management entity .
24. The apparatus according to any one of claims 18 to 20, wherein
the message includes an indication for machine-to-machine communication or a category of a machine-to-machine device/subscription .
25. The apparatus according to any one of claims 18 to 24, wherein
the second management entity is a management entity optimized for machine-to-machine communication.
26. The method according to any one of claims 18 to 25, wherein
the network entity is a base station according to Long Term Evolution/Long Term Evolution Advanced or a radio network controller according to 3G.
27. An apparatus for use in a first management entity, comprising :
at least one processor, at least one interface to at least one other network element, and at least one memory for storing instructions to be executed by the processor, wherein the at least one memory and the instructions are configured to, with the at least one processor, cause the apparatus at least to perform: causing reception of an attach reguest for a network device from a network entity,
determining whether the network device reguires reselection of the management entity, and
if it is determined that the network device reguires reselection, composing a message instructing the network entity to select a second management entity for the network device .
28. The apparatus according to claim 27, wherein the at least one memory and the instructions are further configured to, with the at least one processor, cause the apparatus to perform : obtaining information about the network device from a register, and
determining whether the network device requires reselection of the management entity based on the obtained information .
29. The apparatus according to claim 27 or 28, wherein
the message includes a low access priority indication for the network device, to which the attach request transmitted by the network entity belongs.
30. The apparatus according to claim 27 or 28, wherein
the message includes a globally unique temporary user equipment identity of the network device, to which the attach request transmitted by the network entity belongs.
31. The apparatus according to claim 27 or 28, wherein
the message includes an address of the second management entity .
32. The apparatus according to claim 27 or 28, wherein
the message includes an indication for machine-to-machine communication or a category of a machine-to-machine device/subscription .
33. The apparatus according to any one of claims 27 to 32, wherein
the second management entity is a management entity optimized for machine-to-machine communication.
34. The apparatus according to any one of claims 27 to 33, wherein the first and second management entity is a mobility management entity according to Long Term Evolution/Long Term Evolution Advanced or a Serving General Packet Radio System Support Node according to 3G.
35. An apparatus for use in a network entity, comprising:
means for causing transmission of an attach reguest message to a first management entity,
means for causing reception of a message from the first management entity including an indication to select a second management entity, and
means for determining to forward the attach reguest message to the second management entity based on the indication included in the received message.
36. An apparatus for use in a network entity, comprising:
means for causing reception of an attach reguest for a network device from a network entity,
means for determining whether the network device reguires reselection of the management entity, and
means for composing, if it is determined that the network device reguires reselection, a message instructing the network entity to select a second management entity for the network device .
37. A computer program product including a program for a processing device, comprising software code portions for performing the steps of any one of claims 1 to 17 when the program is run on the processing device.
38. The computer program product according to claim 37, wherein the computer program product comprises a computer- readable medium on which the software code portions are stored .
39. The computer program product according to claim 37, wherein the program is directly loadable into an internal memory of the processing device.
PCT/EP2013/064832 2013-07-12 2013-07-12 Redirection of m2m devices WO2015003753A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2013/064832 WO2015003753A1 (en) 2013-07-12 2013-07-12 Redirection of m2m devices

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2013/064832 WO2015003753A1 (en) 2013-07-12 2013-07-12 Redirection of m2m devices

Publications (1)

Publication Number Publication Date
WO2015003753A1 true WO2015003753A1 (en) 2015-01-15

Family

ID=48790463

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2013/064832 WO2015003753A1 (en) 2013-07-12 2013-07-12 Redirection of m2m devices

Country Status (1)

Country Link
WO (1) WO2015003753A1 (en)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3046390A4 (en) * 2013-09-13 2016-08-10 Ntt Docomo Inc Mobile communication system, network node, and mobile communication method
JP2017038323A (en) * 2015-08-13 2017-02-16 株式会社Ｎｔｔドコモ Base station, management device and connection method
WO2017029795A1 (en) * 2015-08-14 2017-02-23 Nec Corporation Communication system
WO2017079074A1 (en) * 2015-11-06 2017-05-11 Interdigital Patent Holdings, Inc. Methods, core network entity and wireless transmit/receive unit (wtru) using enhanced dedicated core network (dcn) selection
WO2018006985A1 (en) * 2016-07-08 2018-01-11 Nec Corporation System, devices, and methods for interworking between a legacy 3gpp mobile telecommunications network (4g) and a next generation network (5g)
CN112075051A (en) * 2018-03-02 2020-12-11 日东电工株式会社 System and method for securing data communications between computers
US11356708B2 (en) 2012-09-28 2022-06-07 Interdigital Madison Patent Holdings, Sas Cross-plane filtering for chroma signal enhancement in video coding
US11438605B2 (en) 2015-07-08 2022-09-06 Interdigital Madison Patent Holdings, Sas Enhanced chroma coding using cross plane filtering

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003037021A1 (en) * 2001-10-19 2003-05-01 Nokia Corporation Forwarding a terminal identity between core network nodes
US20100080186A1 (en) * 2007-03-20 2010-04-01 Guo Xiaolong Method and system for selecting network equipment
EP2584805A2 (en) * 2010-06-17 2013-04-24 Samsung Electronics Co., Ltd Wireless communication system and method for establishing a connection between user equipment and a mobility management entity thereof

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003037021A1 (en) * 2001-10-19 2003-05-01 Nokia Corporation Forwarding a terminal identity between core network nodes
US20100080186A1 (en) * 2007-03-20 2010-04-01 Guo Xiaolong Method and system for selecting network equipment
EP2584805A2 (en) * 2010-06-17 2013-04-24 Samsung Electronics Co., Ltd Wireless communication system and method for establishing a connection between user equipment and a mobility management entity thereof

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System improvements for Machine-Type Communications (MTC) (Release 11)", 3GPP STANDARD; 3GPP TR 23.888, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V11.0.0, 18 September 2012 (2012-09-18), pages 1 - 165, XP050649142 *
3GPP STANDARD TS 23.003, V11.5.0, March 2013 (2013-03-01)
NTT DOCOMO: "Use of Low Access Priority Indication to select MME", vol. SA WG2, no. Busan, South Korea; 20130527 - 20130531, 21 May 2013 (2013-05-21), XP050709034, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_97_Busan/Docs/> [retrieved on 20130521] *

Cited By (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11356708B2 (en) 2012-09-28 2022-06-07 Interdigital Madison Patent Holdings, Sas Cross-plane filtering for chroma signal enhancement in video coding
EP3046390A4 (en) * 2013-09-13 2016-08-10 Ntt Docomo Inc Mobile communication system, network node, and mobile communication method
US10172056B2 (en) 2013-09-13 2019-01-01 Ntt Docomo, Inc. Mobile communication system, network node, and mobile communication method
US11438605B2 (en) 2015-07-08 2022-09-06 Interdigital Madison Patent Holdings, Sas Enhanced chroma coding using cross plane filtering
JP2017038323A (en) * 2015-08-13 2017-02-16 株式会社Ｎｔｔドコモ Base station, management device and connection method
WO2017026531A1 (en) * 2015-08-13 2017-02-16 株式会社Ｎｔｔドコモ Base station, management device, and connection method
CN107925862B (en) * 2015-08-14 2022-02-08 日本电气株式会社 Communication system
WO2017029795A1 (en) * 2015-08-14 2017-02-23 Nec Corporation Communication system
CN107925862A (en) * 2015-08-14 2018-04-17 日本电气株式会社 Communication system
US11317273B2 (en) 2015-08-14 2022-04-26 Nec Corporation Communication system for establishing a connection with a mobility management entity
WO2017079074A1 (en) * 2015-11-06 2017-05-11 Interdigital Patent Holdings, Inc. Methods, core network entity and wireless transmit/receive unit (wtru) using enhanced dedicated core network (dcn) selection
US11071031B2 (en) 2015-11-06 2021-07-20 Interdigital Patent Holdings, Inc. Methods, apparatus, and systems using enhanced dedicated core network (DCN) selection
EP3944671A1 (en) * 2015-11-06 2022-01-26 Interdigital Patent Holdings, Inc. Method and wireless transmit/receive unit (wtru) registering with a changed or new dedicated network (dcn) type
TWI701954B (en) * 2015-11-06 2020-08-11 美商內數位專利控股公司 Methods, apparatus, and systems using enhanced dedicated core network (dcn) selection
US10667190B2 (en) 2015-11-06 2020-05-26 Interdigital Patent Holdings, Inc. Methods, apparatus, and systems using enhanced dedicated core network (DCN) selection
CN108464036A (en) * 2015-11-06 2018-08-28 交互数字专利控股公司 Use enhanced special core network（DNC）Method, core-network entities and the wireless transmitter/receiver unit of selection（WTRU）
US11689979B2 (en) 2015-11-06 2023-06-27 Interdigital Patent Holdings, Inc. Methods, apparatus, and systems using enhanced dedicated core network (DCN) selection
WO2018006985A1 (en) * 2016-07-08 2018-01-11 Nec Corporation System, devices, and methods for interworking between a legacy 3gpp mobile telecommunications network (4g) and a next generation network (5g)
CN112075051A (en) * 2018-03-02 2020-12-11 日东电工株式会社 System and method for securing data communications between computers

Similar Documents

Publication Publication Date Title
US11653296B2 (en) Isolated network slice selection
WO2015003753A1 (en) Redirection of m2m devices
US9585084B2 (en) Dynamic control of network selection
EP4178284A1 (en) Network entity, user equipment and method for the control and use of network slices
CN112312418A (en) Method and device for acquiring user plane data and storage medium
EP2664176B1 (en) Terminal measurement configuration in carrier aggregation
EP3910973A1 (en) Label management method and apparatus for terminal device
US11765791B2 (en) Systems and methods for providing low latency services via an evolved packet core network
CN108029150B (en) Method and device for data transmission
US10075821B2 (en) Subscriber group based cell broadcast
WO2015113597A1 (en) Dynamic adjustments of measurement conditions along with additional trigger methods for reporting
JP7448047B2 (en) NWDAF nodes and methods
WO2015115782A1 (en) Method and apparatus for supporting minimization of drive tests for radio access network sharing in wireless communication system
US20220369402A1 (en) Methods and apparatus to support access to services for multiple subscriber identity modules
US20220346052A1 (en) Support of network slicing for sms
WO2018000439A1 (en) Method and device for wireless communication
CN103458429A (en) Method of minimization of drive test (MDT), network management system and base station
WO2012019652A1 (en) Method and apparatus for restricting collection of minimization of drive -tests data in a roaming network
US20230126999A1 (en) Method for wireless communication and network device
CN109314943B (en) Allowing allocation of registration areas
CN110731119A (en) Network rollback method, terminal equipment and access network equipment
US20230292275A1 (en) Transceiver device, network entity and base station
EP2860892A1 (en) Method and apparatuses for identifying a mobile device in wireless networks
FI126799B (en) Procedure for combining user-reported information and MDT tracking records
WO2022078575A1 (en) Mechanism for direct event exposure

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

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

Country of ref document: EP

Kind code of ref document: A1