[go: up one dir, main page]

WO2014060029A1 - Sélection de cœur de réseau dans un réseau partagé pendant un transfert/relocalisation - Google Patents

Sélection de cœur de réseau dans un réseau partagé pendant un transfert/relocalisation Download PDF

Info

Publication number
WO2014060029A1
WO2014060029A1 PCT/EP2012/070554 EP2012070554W WO2014060029A1 WO 2014060029 A1 WO2014060029 A1 WO 2014060029A1 EP 2012070554 W EP2012070554 W EP 2012070554W WO 2014060029 A1 WO2014060029 A1 WO 2014060029A1
Authority
WO
WIPO (PCT)
Prior art keywords
handover
network
relocation
relocation request
operator core
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/EP2012/070554
Other languages
English (en)
Inventor
Kati Marita Vainola
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Solutions and Networks Oy
Original Assignee
Nokia Siemens 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 Siemens Networks Oy filed Critical Nokia Siemens Networks Oy
Priority to PCT/EP2012/070554 priority Critical patent/WO2014060029A1/fr
Publication of WO2014060029A1 publication Critical patent/WO2014060029A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • 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/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0066—Transmission or use of information for re-establishing the radio link of control information between different types of networks in order to establish a new radio link in the target network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node

Definitions

  • the present invention relates to core network selection in a shared network during handover/relocation.
  • Network sharing architecture allows different core network operators to connect to a shared radio access network.
  • GWCN Globalway Core Network
  • MOCN Multi-Operator Core Network
  • Fig. 1 shows a GWCN network sharing architecture in which core network operators A, B, C each connect to shared MSC/SGSN entities which connect to RNCs of a radio access network operator X via an lu interface.
  • Fig. 2 shows an MOCN network sharing architecture in which the core network operators A, B, C connect to an RNC of the radio access network operator X.
  • the subscriber distribution is typically done in the shared radio access network according to network sharing partner agreements. For example, all the CN operator A own subscribers are directed to a core network of the CN operator A and the CN operator B subscribers are directed to a core network of the CN operator B, but for incoming roamers a different distribution can be agreed, e.g.: 20% / 80% distribution of PLMN Y subscribers and 60% / 40 % distribution of PLMN Z subscribers.
  • the GWCN is able to make the corresponding subscriber distribution.
  • the subscriber After the initial access to the shared network is done, the subscriber will be served by the chosen operator as long as he stays at the shared network area.
  • the invention aims at overcoming the above problems.
  • the invention aims at enabling a preferred subscriber distribution to entities of a core network which connect to a shared radio access network also by handover/relocation from another, non-shared network, where the entities may be shared by different operators.
  • Fig. 1 shows a GWCN architecture illustrating an example of a shared network
  • Fig. 2 shows an MOCN architecture illustrating an example of a shared network configuration.
  • Fig. 3 shows a schematic diagram illustrating the handover/relocation problem for a handover/relocation from non-shared network to shared network.
  • Fig. 4 shows a schematic diagram illustrating the handover/relocation problem for a handover/relocation from SRVCC PS to CS SRVCC.
  • Fig. 5 shows a flowchart illustrating a process 1 of selecting a correct core network in a shared network during handover/relocation according to an embodiment of the invention.
  • Fig. 6 shows a flowchart illustrating a process 2 of selecting a correct core network in a shared network during handover/relocation according to an embodiment of the invention.
  • Fig. 7 shows a flowchart illustrating a process 3 of selecting a correct core network in a shared network during handover/relocation according to an embodiment of the invention.
  • Fig. 8 shows a schematic diagram illustrating selection of a correct core network in a shared network during handover/relocation for 2G/3G according to an implementation example of the invention.
  • Fig. 9 shows a schematic diagram illustrating selection of a correct core network in a shared network during handover/relocation for SRVCC according to an implementation example of the invention.
  • Fig. 10 shows a schematic block diagram illustrating a configuration of control units in which examples of embodiments of the invention are implementable. DESCRIPTION OF THE EMBODIMENTS
  • An issue in a communication network system is how to select a target operator (and a correct MSS from a pool of MSSs if MSS pooling exists) during handover (2G) or relocation (3G) of a subscriber from a non-shared network into a shared network, when the source network is not able to differentiate the target operator among the network sharing operators.
  • Target operator selection in the source network can not be mandated, because the source network may be an external network which does not belong to any of the network sharing partners and contain only legacy network elements without additional capabilities.
  • the source MSC or SGSN does not make the target core network operator selection.
  • a target MSS selection is done in a source MSS of a non-shared network based on LAI (PLMN id + LA) indicated in a target identifier in a BSSAP Handover Required message received from a source BSC or a RANAP Relocation Required received from a source RNC.
  • LAI PLMN id + LA
  • the MSS in the non-shared network can only choose either OP1 MSS or OP2 MSS based on its configuration. For example, if Common PLMN is indicated in LAI of the target identifier, then it has to be configured in the non-shared network MSS to either point only to OP1 MSS or only to OP2 MSS, which both serve the same shared RAN area.
  • a UE performs handover from a non-shared network to a shared RAN area.
  • the shared RAN area comprises a shared 2G or 3G RAN (shared RAN) in an
  • MSSs MSS1 , MSS2, MSS3 shared by operators OP1 , OP2 connect via A/lu interfaces.
  • MSS1 OP1 , MSS2 OP1 and MSS3 OP1 belong to an MSS pool managed by OP1
  • MSS1 OP2, MSS2 OP2 and MSS3 OP2 belong to another MSS pool managed by OP2.
  • a handover/relocation need is identified for the UE at a source network which is a non-shared network and comprises an RAN to which an MSS (source MSS) connects via an A/lu interface.
  • BSSAP Handover Required / RANAP Relocation Required message sent by the RAN contains either a Target Cell Identifier (handover to 2G) or Target RNC-ld (relocation to 3G). Because the target BSC or RNC is at the shared network, a PLMN identity in the Target Cell Identifier or Target RNC-ID is a Common PLMN.
  • step S2 the source MSS utilizes the source BSC/RNC indicated handover/relocation target PLMN during a handover/relocation routing decision.
  • the target BSC/RNC can be accessed via all the network sharing partner core networks at the target side, but the source MSS may only make the target network selection based on its own configuration, the subscriber distribution among the target network sharing partners is not enabled.
  • step S3a for Common PLMN + LA xxx always the Operator 2 (OP2) network is selected as handover/relocation target according to the configuration of the source MSS, and it is not possible to select MSS10P1 via a MAP-E interface (step S3b) for handling the handover/relocation request, for example.
  • OP2 Operator 2
  • the source network is not able, or mandated to, make the target network selection during handover/relocation to the shared network.
  • a source MME does not make a target core network operator selection.
  • the MME selects an MSC based on a selected target PLMN indicated by an eNodeB.
  • a setup for illustrating the SRVCC handover/relocation problem is shown in Fig. 4.
  • a VoLTE UE performs a PS to CS SRVCC relocation/handover from a non-shared network to a shared RAN area.
  • the shared RAN area comprises a shared 2G or 3G RAN (shared RAN) in an MOCN configuration, to which MSSs MSS1 , MSS2, MSS3 shared by operators OP1 , OP2 connect via A/lu interfaces.
  • MSS1 OP1 , MSS2 OP1 and MSS3 OP1 belong to an MSS pool managed by OP1
  • MSS1 OP2, MSS2 OP2 and MSS3 OP2 belong to another MSS pool managed by OP2.
  • a handover/relocation need is identified at the source network.
  • a source MME connected to an eNb of the non-shared network gets a handover target indication in form of a Target Cell Identifier (handover to 2G) or a Target RNC-ld (relocation to 3G).
  • a PLMN identity in the Target Cell Identifier or Target RNC-ID is the Common PLMN.
  • step C2 the source MME utilizes the indicated handover/relocation target PLMN during a handover/relocation routing decision.
  • the target BSC/RNC can be accessed via all the network sharing partner core networks at the target side, but the source MME may only make the target network selection based on its own configuration, the subscriber distribution among the target network sharing partners is not enabled.
  • step C3a for the Common PLMN + LA xxx always the Operator 2 (OP2) network is selected as handover/relocation target according to the configuration of the source MME, and it is not possible to select MSS10P1 via an Sv (GTP) interface (step C3b) for handling the handover/relocation request, for example.
  • OP2 Operator 2
  • a target MSS is enabled to decide e.g. based on IMSI analysis to which network sharing partner a handed over/relocated subscriber should belong to.
  • a desired amount of certain PLMN subscribers may be be directed to another MSS, which may reside in the network sharing partner's core network.
  • Fig. 5 shows a flowchart illustrating a process 1 of selecting a correct core network in a shared network during handover/relocation.
  • the process 1 may be performed by an apparatus of one of plural operator core networks of a communication network system which comprises a shared radio access network to which the plural operator core networks connect, e.g. a shared MSC/SGSN, MSS, or the like.
  • a handover/relocation request (e.g. a MAP-E interface Handover/Relocation Request, or an Sv interface SRVCC PS to CS Request) is obtained by the apparatus, e.g. from a switching device (e.g. an MSS, MME, or the like) of a non-shared network.
  • a switching device e.g. an MSS, MME, or the like
  • step S1 1 it is decided, according to a preferred subscriber distribution among the plural operator core networks, whether or not the operator core network of the apparatus is a correct target network for processing the handover/relocation request.
  • step S12 in case it is decided that the operator core network of the apparatus is not the correct target network, a message including the handover/relocation request is provided to another one of the plural operator core networks, which, according to the preferred subscriber distribution, is determined as the correct target network.
  • a handover/relocation acknowledge message (e.g. a MAP-E interface Handover Request/Relocation Request message) may be provided to the switching device in response to the handover/relocation request, in case the correct target network (or correct target apparatus at the correct target network processing the request) has no interface to the switching device.
  • step S13 in case it is decided that the operator core network of the apparatus is the correct target network, the handover/relocation request is processed in the operator core network of the apparatus.
  • a target network makes the decision to forward handover/relocation signaling to the correct target network according to the preferred subscriber distribution among the network sharing partners.
  • Fig. 6 shows a flowchart illustrating a process 2 of selecting a correct core network in a shared network during handover/relocation.
  • the process 2 may be performed by the above-mentioned switching device, e.g. an MSS or MME of a non-shared network of the communication network system.
  • step S20 it is detected that handover/relocation of the subscriber to the shared radio access network is requested.
  • step S21 the handover/relocation request is provided to a target operator core network of the plural operator core networks, for controlling the handover/relocation.
  • the handover/relocation request is provided to a target apparatus in the target operator core network for controlling the handover/relocation.
  • a home mobile network of the subscriber to be handed-over/relocated by the handover/relocation request may be identified, and the correct target network may be decided based on the home mobile network of the subscriber and mobile network specific weight factors representing the preferred subscriber distribution.
  • a correct target apparatus for processing the handover/relocation request in the correct target network may be detected based on the home mobile network of the subscriber and weight factors representing a preferred subscriber distribution in the correct target network, and the message may be provided to the correct target apparatus.
  • information elements available from the handover/relocation request are included into the message provided to the correct target network/apparatus in step S12 in process 1 , which identify the switching device from which the handover/relocation request has been obtained.
  • handover/relocation requested by the handover/relocation request may be indicated to the correct target network/apparatus in case a cancel notification message is obtained by the target apparatus from the switching device, to cancel the handover/relocation, and a cancel acknowledge message may be provided to the switching device in response to the cancel notification message.
  • Fig. 7 shows a flowchart illustrating a process 3 of selecting a correct core network in a shared network during handover/relocation.
  • the process 3 may be performed by the correct target network/apparatus in the other network (correct target network) to which the handover/relocation request is provided.
  • step S30 the message including the handover/relocation request is obtained.
  • step S31 the handover/relocation request is processed.
  • the information elements may be extracted from the message, which identify the switching device from which the handover/relocation request has been obtained, and a handover/relocation acknowledge message (e.g. SRVCC PS to CS Response message) may be provided towards the switching device e.g. via an Sv interface.
  • a handover/relocation acknowledge message e.g. SRVCC PS to CS Response message
  • the apparatus from which the message has been obtained i.e. the target apparatus
  • handover/relocation may be cancelled and a cancel acknowledge message may be provided to the switching device.
  • the correct source MME where to send the SRVCC PS to CS Response message over the Sv interface can be identified after handover/relocation forwarding at the target network has been done.
  • New information elements "MME/SGSN Sv Address for Control Plane" and "MME/SGSN Sv TEID for Control Plane” may be included in a MAP-E interface signaling in a
  • MAP_PREPARE_HANDOVER Request to indicate the source MME, when the handover/relocation message is forwarded as shown in step S12 in process 1.
  • These new information elements may be transferred in the MAP_PREPARE_HANDOVER Request as separate lEs at the MAP level message, or they may be included in an AN-APDU IE together with the whole received Sv interface SRVCC PS to CS Request message.
  • Fig. 8 shows a schematic diagram illustrating selection of a correct core network in a shared network during handover/relocation for 2G/3G according to an implementation example of the invention.
  • a UE performs handover from a non-shared network to a shared RAN area.
  • the shared RAN area comprises a shared 2G or 3G RAN (shared RAN) in an MOCN configuration, to which MSSs MSS1 , MSS2, MSS3 shared by operators OP1 , OP2 connect via A/lu interfaces.
  • MSS1 OP1 , MSS2 OP1 and MSS3 OP1 belong to an MSS pool managed by OP1
  • MSS1 OP2, MSS2 OP2 and MSS3 OP2 belong to another MSS pool managed by OP2.
  • a handover/relocation need is identified at the source network, i.e. the nonshared network comprising a RAN and an MSS (source MSS) connected to the RAN via an A lu interface.
  • a BSSAP Handover Required / RANAP Relocation Required message is sent by the source BSC/RNC (the RAN) to the MSS and it contains either a Target Cell Identifier (handover to 2G) or a Target RNC-ld (relocation to 3G). Because the target BSC or RNC (shared RAN) is at the shared network, a PLMN identity in the Target Cell Identifier or Target RNC-ID is the Common PLMN.
  • the source MSS utilizes the source BSC/RNC indicated handover/relocation target PLMN during a handover/relocation routing decision based on the received Common PLMN + LA xxx target identifier.
  • MSS1 in OP2 network MSS1 OP2 is selected as handover/relocation target during MAP_PREPARE_HANDOVER Request.
  • step S'3 when the MSS1 OP2 receives a MAP-E interface Handover
  • the Request/Relocation Request message (the MAP_PREPARE_HANDOVER Request), it evaluates if it is the correct target MSS or if the handover/relocation should be forwarded to another MSS.
  • the target evaluation in the MSS1 OP2 may be based on the subscriber PLMN in a way which enables subscriber distribution as agreed by the network sharing partners, e.g. 20% / 80% distribution of PLMN Y subscribers and 60% / 40 % distribution of PLMN Z subscribers.
  • the MSS1 OP2 identifies the need to forward the MAP-E interface Handover Request/Relocation Request message to the network sharing partner MSS1 OP1 , and in step S'4 the MAP_PREPARE_HANDOVER Request is forwarded to the MSS1 OP1.
  • step S'5 when the MSS1 OP1 receives the message, it evaluates itself as the correct target MSS for the handover/relocation.
  • the MSS1 OP1 continues the inter-MSS handover as normally for the subscriber, and sends a Handover Request Acknowledge / Relocation Request Acknowledge in MAP_PREPARE_HAN DOVER Response directly to the original source MSS in the non-shared network.
  • Fig. 9 shows a schematic diagram illustrating selection of a correct core network in a shared network during handover/relocation for SRVCC according to an implementation example of the invention.
  • a VoLTE UE performs a PS to CS SRVCC relocation/handover from a non-shared network to a shared RAN area.
  • the shared RAN area comprises a shared 2G or 3G RAN (shared RAN) in an MOCN configuration, to which MSSs MSS1 , MSS2, MSS3 shared by operators OP1 , OP2 connect via A/lu interfaces.
  • MSS1 OP1 , MSS2 OP1 and MSS3 OP1 belong to an MSS pool managed by OP1
  • MSS1 OP2, MSS2 OP2 and MSS3 OP2 belong to another MSS pool managed by OP2.
  • a PS to CS SRVCC relocation/handover need is identified at a source network, e.g. a non-shared network comprising an eNB and an MME connecting to the eNB.
  • the source eNB indicates a target identifier as either a Target Cell Identifier (handover to 2G) or a Target RNC-ld (relocation to 3G). Because a target BSC or RNC is at the shared network, a PLMN identity in the Target Cell Identifier or Target RNC-ID is the Common PLMN.
  • the source MME utilizes the source eNB indicated handover/relocation target PLMN during a PS to CS SRVCC relocation/handover routing decision based on the received Common PLMN + LA xxx target identifier.
  • MSS1 in OP2 network MSS1 OP2 is selected as
  • step C'3 when the MSS1 OP2 receives the Sv interface SRVCC PS to CS Request message, it evaluates if it is the correct target MSS or if the handover/relocation should be forwarded to another MSS.
  • the target evaluation in the MSS1 OP2 may be based on the subscriber PLMN in a way which enables a subscriber distribution as agreed by the network sharing partners, e.g. 20% / 80% distribution of PLMN Y subscribers and 60% / 40 % distribution of PLMN Z subscribers.
  • the MSS1 0P2 identifies the need to forward the Sv interface SRVCC PS to CS Request message to the network sharing partner MSS1 OP1 .
  • the MSS1 OP1 forwards the request in step C'4, it may include new lEs to the
  • MAP_PREPARE_HANDOVER Request MME/SGSN Sv Address for Control Plane and MME/SGSN Sv TEID for Control Plane at the MAP level. These lEs are available from the original SRVCC PS to CS Request message received from the MME.
  • the MAP_PREPARE_HANDOVER Request may include the information from the original Sv interface SRVCC PS to CS Request message either in an AN-APDU IE (whole original Sv interface message may be included), or as new separate lEs at the MAP level message.
  • MSS1 OP1 When MSS1 OP1 receives the message, it evaluates itself as the correct target MSS for the handover/relocation. The MSS1 OP1 continues the relocation/handover procedure as normally for the subscriber, and in step C'5 sends an Sv interface SRVCC PS to CS Response message directly to the original source MME in the non-shared network based on the MME/SGSN Sv Address for Control Plane and MME/SGSN Sv TEID for Control Plane received in the MAP_PREPARE_HANDOVER Request.
  • the MSS1 OP1 may include "MSC Server Sv Address for Control Plane” and "MSC Server Sv TEID for Control Plane” lEs, based on which the MME knows where to send the subsequent control plane messages to this GTP-C tunnel.
  • the source radio network decides to initiate a PS to CS SRVCC relocation/handover cancel procedure when the Sv interface SRVCC PS to CS Request message has been sent, but the correct target MSS has not yet responded with the Sv interface SRVCC PS to CS Response message.
  • the original target MSS MSS1 OP2
  • receives the SRVCC PS to CS Cancel Notification message the situation may be indicated also to the MSS1 OP1 using existing methods defined at MAP-E interface.
  • the original target MSS (MSS1 OP2) may also respond to the MME with a SRVCC PS to CS Cancel Acknowledge message.
  • the MSS1 OP2 may be used as an anchor MSS during the SRVCC PS to CS relocation/handover procedure.
  • the correct target MSS decision may be based on PLMN specific weight factors, for example.
  • this information combined with PLMN weight factors can be used to derive the correct target operator and the MSS element if MSS pooling is in use in the correct target operator network.
  • weight factors can also be used to choose the correct target MSS from the own network if MSS pooling in the own network is in use.
  • a control unit 10 which may execute process 1 shown in Fig. 5 and/or may be included in or be part of the MSS1 OP2 shown in Figs. 8 and 9, comprises processing resources 1 1 , memory resources 12 which may store a program, and interfaces 13, which are connected by a link 14.
  • a control unit 20 which may execute process 3 shown in Fig. 7 and/or may be included in or be part of the MSS1 OP1 shown in Figs. 8 and 9, comprises processing resources 21 , memory resources 22 which may store a program, and interfaces 23, which are connected by a link 24.
  • a control unit 30, which may execute process 2 shown in Fig. 6 and/or may be included in or be part of the MSS/MME of the non-shared network shown in Figs. 8 and 9, comprises processing resources 31 , memory resources 32 which may store a program, and interfaces 33, which are connected by a link 34.
  • control unit 10 and the control unit 20 are connected through their interfaces 13, 23 via a link 41 , e.g. for providing a MAP-E interface handover/relocation request message from the control unit 10 to the control unit 20.
  • control unit 10 and the control unit 30 are connected through their interfaces 13, 33 via a link 42, e.g. for providing a MAP-E interface handover/relocation request or an Sv interface SRVCC PS to CS request from the control unit 30 to the control unit 10.
  • link 42 e.g. for providing a MAP-E interface handover/relocation request or an Sv interface SRVCC PS to CS request from the control unit 30 to the control unit 10.
  • the control unit 20 and the control unit 30 are connected through their interfaces 23, 33 via a link 43, e.g. for providing a MAP-E interface handover/relocation response or an Sv interface SRVCC PS to CS response from the control unit 20 to the control unit 30.
  • the terms "connected,” “coupled,” or any variant thereof, mean any connection or coupling, either direct or indirect, between two or more elements, and may encompass the presence of one or more intermediate elements between two elements that are
  • connection or connection between the elements can be physical, logical, or a combination thereof.
  • two elements may be considered to be “connected” or “coupled” together by the use of one or more wires, cables and printed electrical connections, as well as by the use of electromagnetic energy, such as electromagnetic energy having wavelengths in the radio frequency region, the microwave region and the optical (both visible and invisible) region, as non-limiting examples.
  • the exemplary embodiments of this invention may be implemented by computer software stored in the memory resources 12, 22, 32 and executable by the processing resources 1 1 , 21 , 31 , or by hardware, or by a combination of software and/or firmware and hardware in any or all of the devices shown.
  • the memory resources 12, 22, 32 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.
  • the processing resources 1 1 , 21 , 31 may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on a multi-core processor architecture, as non-limiting examples.
  • an apparatus of one of plural operator core networks of a communication network system which comprises a shared radio access network to which the plural operator core networks connect which may comprise or use the control unit 10
  • the apparatus may comprise means for identifying a home mobile network of a subscriber to be handed-over/relocated by the handover/relocation request.
  • the means for deciding may decide the correct target network based on the home mobile network of the subscriber and mobile network specific weight factors representing the preferred subscriber distribution. In case several apparatuses for processing the
  • the means for deciding may decide a correct target apparatus for processing the handover/relocation request in the correct target network based on the home mobile network of the subscriber and weight factors representing a preferred subscriber distribution in the correct target network, and the means for providing may provide the message to the correct target apparatus.
  • the means for providing may including information elements available from the
  • the means for providing may include the information elements together with the handover/relocation request in an anchor node anchor packet data unit information element or as further information elements at a mobile application part level.
  • the apparatus may comprise means for, in case the message including the
  • the means for providing may provide a cancel acknowledge message in response to the cancel notification message.
  • the means for providing may provide a handover/relocation acknowledge message to a switching device from which the apparatus has obtained the handover/relocation request, in response to the handover/relocation request, in case the correct target
  • network/apparatus has no interface to the switching device.
  • the means for deciding, providing, processing, identifying and indicating may be implemented by the processing resources 1 1 , memory resources 12 and interfaces 13.
  • an apparatus of one of plural operator core networks of a communication network system which comprises a shared radio access network to which the plural operator core networks connect, which may comprise or use the control unit 20, comprises means for obtaining a message including a
  • handover/relocation request from another apparatus of one of the plural operator core networks, and means for processing the handover/relocation request.
  • the apparatus may comprise means for extracting information elements from the message, which identify a switching device from which the handover/relocation request has been obtained, and means for providing a handover/relocation acknowledge message towards the switching device.
  • the apparatus may comprise means for, upon obtaining a notification to cancel handover/relocation requested by the handover/relocation request, from the other apparatus, cancelling the handover/relocation and the means for providing may provide a cancel acknowledge message to the switching device.
  • the means for obtaining, processing, extracting, providing and cancelling may be implemented by the processing resources 21 , memory resources 22 and interfaces 23.
  • a switching device of a communication network system which may comprise or use the control unit 30, comprises means for detecting that handover/relocation of a subscriber to a shared radio access network is requested, to which plural operator core networks connect, and means for providing a
  • the means for providing may provide the handover/relocation request to a target apparatus in the target operator core network for controlling the handover/relocation.
  • the means for detecting and providing may be implemented by the processing resources 31 , memory resources 32 and interfaces 33.
  • the handover/relocation request may be at least one of a mobile application part E interface handover/relocation request and an Sv interface single radio voice call continuity packet switched to circuit switched request.
  • the message including the
  • handover/relocation request may be a mobile application part prepare handover request.

Landscapes

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

Abstract

L'invention porte sur un procédé destiné à être utilisé par un appareil d'un ou plusieurs cœurs de réseau d'opérateur d'un système de réseau de communication qui comprend un réseau d'accès radio partagé auquel la pluralité de cœurs de réseau d'opérateur se connectent, consistant à décider (S11), en fonction d'une distribution d'abonnés préférée parmi les multiples cœurs de réseau d'opérateur, si le cœur de réseau d'opérateur de l'appareil est un réseau cible correct ou non pour traiter une requête de transfert/relocalisation obtenue (S10) par l'appareil. Dans le cas où il est décidé que le cœur de réseau d'opérateur de l'appareil n'est pas le réseau cible correct, un message comprenant la requête de transfert/relocalisation est fourni (S12) à un autre des multiples cœurs de réseau d'opérateur, qui, en fonction de la distribution d'abonnés préférée, est déterminé comme étant le réseau cible correct. Dans le cas où il est décidé que le cœur de réseau d'opérateur de l'appareil est le réseau cible correct, la requête de transfert/relocalisation est traitée (S13) dans le cœur de réseau d'opérateur de l'appareil.
PCT/EP2012/070554 2012-10-17 2012-10-17 Sélection de cœur de réseau dans un réseau partagé pendant un transfert/relocalisation Ceased WO2014060029A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2012/070554 WO2014060029A1 (fr) 2012-10-17 2012-10-17 Sélection de cœur de réseau dans un réseau partagé pendant un transfert/relocalisation

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2012/070554 WO2014060029A1 (fr) 2012-10-17 2012-10-17 Sélection de cœur de réseau dans un réseau partagé pendant un transfert/relocalisation

Publications (1)

Publication Number Publication Date
WO2014060029A1 true WO2014060029A1 (fr) 2014-04-24

Family

ID=47080486

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2012/070554 Ceased WO2014060029A1 (fr) 2012-10-17 2012-10-17 Sélection de cœur de réseau dans un réseau partagé pendant un transfert/relocalisation

Country Status (1)

Country Link
WO (1) WO2014060029A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106332311A (zh) * 2016-08-22 2017-01-11 广东工业大学 一种基于lte的物联网数据传输方法

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040266438A1 (en) * 2001-08-21 2004-12-30 Frode Bjelland Methods involving a core network node that is handling a mobile subscriber and initiates a request to a second core network node to handle said mobile subscriber
US20060073831A1 (en) * 2004-10-06 2006-04-06 Nokia Corporation Transfer of a user equipment in a communication system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040266438A1 (en) * 2001-08-21 2004-12-30 Frode Bjelland Methods involving a core network node that is handling a mobile subscriber and initiates a request to a second core network node to handle said mobile subscriber
US20060073831A1 (en) * 2004-10-06 2006-04-06 Nokia Corporation Transfer of a user equipment in a communication system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Network Sharing; Architecture and functional description (Release 11)", 3GPP STANDARD; 3GPP TS 23.251, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V11.3.0, 11 September 2012 (2012-09-11), pages 1 - 30, XP050649054 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106332311A (zh) * 2016-08-22 2017-01-11 广东工业大学 一种基于lte的物联网数据传输方法

Similar Documents

Publication Publication Date Title
US20200296634A1 (en) Method and device for accessing and obtaining user equipment context and user equipment identity
CN101978767B (zh) 移动端接的呼叫的电路交换回退
US8259673B2 (en) System and method for providing voice service in a mobile network with multiple wireless technologies
CN102804853B (zh) 管理从2g/3g网络到lte网络的cs irat切换的方法
EP2648459B1 (fr) Sélection de réseau dans un environnement de réseau partagé
EP2613596B1 (fr) Sélection de réseau dans un environnement de réseau partagé
US8175601B2 (en) Method of detecting incorrect cell identity in wireless communication systems
US20060073831A1 (en) Transfer of a user equipment in a communication system
US20160174285A1 (en) Method for maintaining service continuity in heterogeneous communications system
US9961596B2 (en) Determination of a capability of a user equipment
US20140274059A1 (en) Plmn selection at handover to a target shared location being shared between core network operators
US20140177599A1 (en) Method and system for enabling circuit switched fallback service in evolved packet system
KR102200821B1 (ko) 작은 셀 아키텍처에서 로컬 브레이크아웃을 지원하기 위한 방법, 시스템 및 장치
CN105992293B (zh) 一种进行网络间切换的方法和设备
CN102036325A (zh) 一种建立或修改本地ip接入承载的方法和设备
US10334640B2 (en) Systems, methods, and devices for facilitating wireless communication
US9301214B2 (en) Method and device in a telecommunications system
CN108811006B (zh) 一种信息处理方法及装置
CN106063327B (zh) 一种处理语音业务的方法、终端
EP3280178A1 (fr) Procédé, dispositif de réseau et système permettant un repli sur commutation de circuits
WO2014184349A1 (fr) Redirection étendue dans une configuration mocn
EP2871874B1 (fr) Procédé, dispositif et système de mise à jour de zone de localisation
KR20170018453A (ko) 네트워크 요소 선택 엔티티 및 사용자 장비 등록 방법
CN106454943A (zh) 一种节点管理范围的控制方法与设备
US9516623B2 (en) Enabling CDMA2000 system sharing in LTE

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

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

Country of ref document: EP

Kind code of ref document: A1