HK1237175B - Support capability in communications networks for cs/ps coordination - Google Patents

Description

Support capabilities in communication networks for CS/PS collaboration

Technical Field

The embodiments presented herein relate to support capabilities in a communication network, and in particular to methods, core network nodes, radio access network nodes, computer programs and computer program products for providing or receiving support capabilities of a core network node.

Background Art

In communication networks, obtaining good performance and capacity for a given communication protocol, its parameters, and the physical environment in which the communication network is deployed can be a challenge.

For example, the use of Multi-Operator Radio Access Network (MORAN) (also known as Radio Access Network (RAN) sharing) and Multi-Operator Core Network (MOCN) is a way for multiple mobile phone network operators to share the radio access network infrastructure. As a result, the same network infrastructure can be used for transmission/reception for different operators. A Management Information Base (MIB) can contain a list of multiple Public Land Mobile Network (PLMN) identities. A wireless device (or User Equipment UE) can read the MIB and select a PLMN to register based on its subscription. A wireless device that does not support network sharing in the sense of ignoring additional broadcast system information specific for network sharing is denoted as a non-supporting wireless device or a network sharing non-supporting UE. A wireless device that supports network sharing in the sense of being able to select a core network operator as a serving operator within a shared network is denoted as a supporting wireless device or a network sharing supporting UE.

One of the tasks in an MOCN network is selecting the serving core network (CN) operator. In Long Term Evolution (LTE) networks, this simply means selecting a serving operator for the UE in the packet-switched (PS) domain. However, in Global System for Mobile Communications (GSM) and Wideband Code Division Multiple Access (WCDMA) networks, it is necessary to ensure that the same serving operator is selected for the UE in both the circuit-switched (CS) and PS domains, leading to so-called CS/PS collaboration.

For wireless devices in idle mode, mobility selection by the serving CN operator is performed directly or indirectly. If the UE is a supporting UE and the RAN and CN also support supporting UEs, the mobility selection by the serving CN operator is performed directly by the UE. If the UE is a non-supporting UE, or if the RAN and CN do not support supporting UEs, the mobility selection by the serving CN operator is performed indirectly by using the MOCN redirection function in the RAN and CN.

However, the current version of the 3rd Generation Partnership Project (3GPP) standard (TS 23.251 v12.1.0) does not guarantee that the same operator is selected in both the CS and PS domains for all mobility scenarios. To this end, work has been started in 3GPP (see WID SP-140168 Improvements to CS/PS Collaboration in UTRAN/GERAN Shared Networks) for the following reasons: Note that there is support for network sharing in the UTRAN/GERAN specifications, where the radio access and core network can be shared between operators without the UE being aware of this. One challenge in the context of this functionality is to ensure that the registration of a given UE to the CS and PS domains is coordinated, i.e., the subscriber is registered to the same PLMN in both domains. UTRAN is an abbreviation for Universal Terrestrial Radio Access Network, and GERAN is an abbreviation for GSM EDGE RAN, where EDGE is an abbreviation for Enhanced Data rates for GSM Evolution. In the WID SP-140168 improvements to CS/PS collaboration in UTRAN/GERAN shared networks, it should also be noted that preliminary analysis shows that there are problems with CS/PS collaboration, at least in the case of network-controlled mobility into UTRAN/GERAN shared networks, i.e., CS/PS collaboration fails resulting in the UE ultimately being registered with different operators in the CS and PS domains.

This has recently led to the formation of 3GPP TR 23.704 v 1.1.0 and the agreement therein to base a normative CR on Solution #5; see Chapter 8, Conclusion, which states that the evaluation of the solutions in Section 7 led to the conclusion that Solution #5 was selected as the basis for further normative work. Further work will be carried out through normative CRs and no further additions, alignments or corrections will be made to the Technical Report.

Solution #5 (see Section 7.5 of TR 23.704) includes, among other things, the following procedures: CS/PS collaboration in some cases is performed by the RAN node based on data (old Location Area Identity (LAI) or Routing Area Identity (RAI), CS/PS Network Resource Indication (NRI), and an indication that the UE is currently attached) provided by the CN node in both the CS and PS domains. Using this data, it can be inferred whether the UE is roaming within an operator collaboration area and can therefore be considered CS/PS collaborative. This must be applied to both the CS and PS domains when selecting a serving operator based on the operator collaboration area.

The above process will work properly when all network nodes (such as Base Station Controllers BSC, Radio Network Controllers RNC, Serving GPRS Support Nodes SGSN and Mobile Switching Centers MSC) are upgraded and are therefore able to provide data (SGSN and MSC) or to act according to the provided data (BSC or RNC). However, as mentioned above, the concept of operator cooperation areas must be applied in both CS and PS domains or not at all. And since registrations in the PS domain (for Routing Area Updates RAU) and in the CS domain (for Location Area Updates LAU) are not always concurrent, it is not possible to check the level of support during the registration process. For example, if the RAN nodes and SGSN nodes support the new procedure, but the MSC does not, and the RAU occurs first, then applying the new procedure to the PS domain will not work because it will not be possible to apply it to the CS domain.

For other scenarios, the RAN node performs CS/PS collaboration based on queries sent to the CN node in both the CS and PS domains. Similarly, this must be supported in both the CS and PS domains or not at all.

Therefore, there remains a need for improved provision of support capabilities in communication networks.

Summary of the Invention

An object of embodiments herein is to provide efficient provisioning of support capabilities in a communication network.

The inventors of the accompanying embodiments have realized that the RAN node must already know the level of support in the MSC and SGSN before the first registration attempt, i.e. immediately after the connection between these nodes is established. The inventors of the accompanying embodiments have realized that this is not supported in current standards.

According to a first aspect, a method for providing support capabilities of a core network (CN) node is provided. The method is performed by the CN node. The method includes establishing a connection to a radio access network (RAN) node. The method includes, in response thereto, providing an indication to the RAN node regarding at least one of whether the CN node supports an operator collaboration area (OCA) and a query, wherein the CN node provides information to be used by the RAN node for selecting a service operator based on the indication, such that the same operator is selected for a wireless device in both a circuit switched (CS) domain and a packet switched (PS) domain.

Advantageously, this provides for efficient provision of support capabilities in the communication network.

Advantageously, this enables the use of the newly agreed CS/PS collaboration procedures without having to rely on configuration. Configuration in a shared network comprising RAN nodes and CN nodes from both the CS and PS domains and on top of that from two or more shared operators is an industrial and error-prone process as it involves extensive synchronization between the operators and between the CS and PS domains.

According to a second aspect, a core network (CN) node for providing support capabilities of a CN node is provided. The CN node includes a processing unit. The processing unit is configured to establish a connection to a radio access network (RAN) node. In response thereto, the processing unit is configured to provide an indication to the CN node regarding at least one of whether the CN node supports an operator collaboration area (OCA) and a query, wherein the CN node provides information to be used by the RAN node for selecting a service operator based on the indication, such that the same operator is selected for a wireless device in both a circuit switched (CS) domain and a packet switched (PS) domain.

According to a third aspect, a computer program for providing support capabilities of a Core Network (CN) node is proposed, the computer program comprising computer program code which, when executed on a processing unit of the CN node, causes the CN node to perform the method according to the first aspect.

According to a fourth aspect, a method for receiving supported capabilities of a core network (CN) node is provided. The method is performed by a radio access network (RAN) node. The method includes establishing a connection to the CN node. The method includes, in response thereto, receiving an indication from the CN node regarding at least one of an operator collaboration area (OCA) and a query as to whether the CN node supports the OCA, the CN node providing information to be used by the RAN node for selecting a service operator based on the indication, such that the same operator is selected for a wireless device in both a circuit switched (CS) domain and a packet switched (PS) domain. The method includes storing the received indication together with identity information of the CN node.

According to a fifth aspect, a radio access network (RAN) node for receiving supported capabilities of a core network (CN) node is provided. The RAN node comprises a processing unit. The processing unit is configured to establish a connection to the CN node. In response thereto, the processing unit is configured to receive an indication from the CN node regarding at least one of an operator collaboration area (OCA) and a query as to whether the CN node supports the OCA, and the CN node provides information to be used by the RAN node for selecting a service operator based on the indication, such that the same operator is selected for a wireless device in both a circuit switched (CS) domain and a packet switched (PS) domain. The processing unit is configured to store the received indication together with the identity information of the CN node.

According to a sixth aspect, a computer program for receiving supported capabilities of a Core Network (CN) node is proposed, the computer program comprising computer program code which, when executed on a processing unit of a RAN node, causes the RAN node to perform the method according to the fourth aspect.

According to a seventh aspect, a computer program product is proposed, comprising a computer program according to at least one of the third and sixth aspects and a computer readable component having the computer program stored thereon.

It should be noted that, where appropriate, any features of the first, second, third, fourth, fifth, sixth, and seventh aspects may be applied to any other aspect. Similarly, any advantages of the first aspect may be equally applicable to the second, third, fourth, fifth, sixth, and/or seventh aspects, respectively, and vice versa. Other objects, features, and advantages of the accompanying embodiments will be apparent from the following detailed disclosure, the accompanying dependent claims, and the accompanying drawings.

Generally, all terms used in the claims should be interpreted according to their ordinary meaning in the technical field, unless explicitly defined otherwise herein. All references to "an/an/element, means, component, part, step, etc." are to be interpreted openly as referring to at least one instance of an element, means, component, part, step, etc., unless explicitly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless explicitly stated otherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will now be described by way of example with reference to the accompanying drawings, in which:

FIG1 is a schematic diagram showing a communication network according to an embodiment;

FIG2 a is a schematic diagram illustrating functional units of a radio access network node according to an embodiment;

FIG2 b is a schematic diagram illustrating functional modules of a radio access network node according to an embodiment;

FIG3 a is a schematic diagram illustrating functional units of a core network node according to an embodiment;

FIG3 b is a schematic diagram illustrating functional modules of a core network node according to an embodiment;

FIG4 shows an example of a computer program product including computer readable components according to an embodiment;

5 , 6 , 7 and 8 are flow charts of methods according to embodiments;

FIG9 is a signaling diagram of a method according to an embodiment; and

FIG10 schematically shows some fields of an extended feature bitmap message according to an embodiment.

DETAILED DESCRIPTION

The inventive concept will now be described more fully hereinafter with reference to the accompanying drawings, which illustrate certain embodiments of the inventive concept. However, the inventive concept can be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided as examples so that this disclosure will be thorough and complete and fully convey the scope of the inventive concept to those skilled in the art. Throughout the description, like numbers refer to like elements. Any steps or features shown in dashed lines should be considered optional.

FIG1 shows a schematic diagram of an exemplary communications network 10. Communications network 10 includes a first radio access network (RAN) 11 in the form of a UTRAN and a second RAN 12 in the form of a GERAN. First RAN 11 includes radio access network nodes in the form of NodeBs and RNCs 11b. Second RAN 12 includes radio access network nodes in the form of base transceiver stations (BTSs) 12a and BSCs 12b. RANs 11 and 12 are operatively connected to a core network (CN) 13. While the schematic diagram shows only one CN 13, it will be readily understood that in a multi-operator core network (MOCN) scenario, at least two CNs 13 (one for each operator or service provider) are operatively connected to RANs 11 and/or 12. CN 13 includes core network nodes in the form of mobile switching centers 13a, 13b, SGSNs 13c, 13d, and GGSNs 13e. In this regard, in the case of using the S3/S4 architecture, a serving gateway (SGW) and/or a packet data network gateway (PGW) may replace the GGSN. The CN 13 is in turn operatively connected to an Internet Protocol (IP)-based service and data provision network 14. Thus, wireless devices 15a, 15b, such as user equipment (UE), mobile stations (MS), and wireless devices (WD), are enabled to access services and data provided by the network 14 by establishing a wireless connection to one of the RANs 11, 12.

The GGSN 13e is responsible for interworking between the GPRS core network 13 and external packet data networks 14 (such as the Internet and X.25 networks) that provide the operator's IP services. The GGSN 13e is the anchor point that enables mobility for wireless devices 15a, 15b within the GPRS/UMTS network and can be considered the GPRS equivalent of a home agent in Mobile IP. It maintains the routing necessary to tunnel protocol data units (PDUs) to the SGSN 13c, 13d serving a specific wireless device 15a, 15b. The GGSN 13e converts GPRS packets from the SGSNs 13c, 13d into the appropriate packet data protocol (PDP) format (e.g., IP or X.25) and sends them out over the corresponding packet data network 14. In the other direction, the PDP address of incoming data packets is converted to the destination user's GSM address. The re-addressed packets are then sent to the responsible SGSN 13c, 13d. The GGSN 13e is responsible for IP address allocation and is the default router for connected wireless devices 15a, 15b. The GGSN 13e also performs authentication and billing functions. Other functions include subscriber screening, IP pool management and address mapping, QoS, and PDP context enforcement.

The SGSN 13c, 13d is responsible for the delivery of data packets to and from wireless devices 15a, 15b within its geographic service area. Its tasks include packet routing and transfer, mobility management (attachment/detachment and location management), logical link management, and authentication and billing functions. The location register of the SGSN 13c, 13d stores location information (e.g., current cell, current visitor location register (VLR)) and user profiles (e.g., International Mobile Station Identity (IMSI), address used in packet data networks) for all GPRS users registered with that SGSN 13c, 13d.

Mobile Switching Centres 13a, 13b (often abbreviated as MSC Servers or MSSs) are GSM core network elements that control the network switching subsystem elements.

RNC 11b is a node in the UMTS Radio Access Network (UTRAN) 11 and is responsible for controlling the NodeB 11a to which it is operationally connected. RNC 11b performs radio resource management, some mobility management functions, and is the point at which user data is encrypted before being sent to and from wireless devices 15a. RNC 11b is operationally connected to the circuit-switched domain of the core network via a media gateway (MGW) and to the SGSN 13c in the packet-switched core network.

The BSC 12b is a node in the GSM Radio Access Network (GERAN) 12 and is responsible for controlling the BTSs 12a connected thereto. The BSC 12b performs radio resource management and some mobility management functions.

Those skilled in the art who have the benefit of this disclosure will recognize that a large number of well-known wireless devices 15a, 15b can be used in various embodiments of the present disclosure. The wireless devices 15a, 15b can be, for example, cellular telephone devices or the like defined by standards provided by 3GPP, such as mobile phones, cell phones, wireless local loop phones, smart phones, laptop computers, tablet computers, etc. Therefore, the wireless devices 15a, 15b themselves do not need to be described in detail. However, it should be emphasized that the wireless devices 15a, 15b can be embedded (for example, as a card or circuit arrangement or the like) in various other devices and/or attached to various other devices, such as various laptop computers or tablet computers or the like or other mobile consumer electronic products or the like, or vehicles or ships or aircraft or other mobile devices intended for transportation purposes. In fact, the wireless devices 15a, 15b can even be embedded in and/or attached to various semi-fixed devices, such as household appliances or the like, or consumer electronic products with semi-fixed mobile characteristics such as printers or the like.

Embodiments disclosed herein relate to supporting capabilities in a communication network. To provide supporting capabilities in a communication network, a CN node 13a, 13b, 13c, 13d is provided, as is a method performed by the CN node 13a, 13b, 13c, 13d, such as a computer program in the form of a computer program product including code that, when executed on a processing unit of the CN node 13a, 13b, 13c, 13d, causes the CN node 13a, 13b, 13c, 13d to perform the method. To receive supporting capabilities in a communication network, a RAN node 11b, 12b is provided, as is a method performed by the RAN node 11b, 12b, such as a computer program in the form of a computer program product including code that, when executed on a processing unit of the RAN node 11b, 12b, causes the RAN node 11b, 12b to perform the method.

Figure 2a schematically illustrates the components of a RAN node 11b, 12b according to an embodiment, in terms of multiple functional units. The processing unit 21 is provided using any combination of one or more of the following suitable options: a central processing unit (CPU), a multiprocessor, a microcontroller, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), etc., capable of executing software instructions stored, for example, in the form of a computer program product 41a (as shown in Figure 4) in the form of a storage medium 23. The processing unit 21 is thus arranged to perform the methods disclosed herein. The storage medium 23 may also include a persistent storage device, which may be, for example, any single memory or combination of magnetic memory, optical memory, solid-state memory, or even remotely mounted memory. The RAN node 11b, 12b may also include a communication interface 22 for communicating with the CN nodes 13a, 13b, 13c, 13d and other RAN nodes 11a, 12a. The processing unit 21 controls the general operation of the RAN nodes 11 b, 12 b, for example, by sending data and control signals to the communication interface 22 and the storage medium 23, by receiving data and reports from the communication interface 22, and by retrieving data and instructions from the storage medium 23. Other components of the RAN nodes 11 b, 12 b and related functions are omitted to avoid obscuring the concepts presented herein.

Figure 2b schematically illustrates the components of a RAN node 11b, 12b according to an embodiment, in terms of multiple functional modules. The RAN node 11b, 12b of Figure 2b includes multiple functional modules: a setup module 21a, a receiving module 21b, and a storage module 21c. The RAN node 11b, 12b of Figure 2b may also include multiple optional functional modules, such as a sending module 21d and any of the register modules 21e. The functionality of each functional module 21a-21e will be further disclosed below in the context of how the functional modules 21a-21e may be used. In general, each functional module 21a-21e may be implemented in hardware or software. Preferably, one or more or all functional modules 21a-21e may be implemented by a processing unit 21, possibly in cooperation with functional units 22 and/or 23. The processing unit 21 may therefore be arranged to retrieve instructions provided by the functional modules 21a-21e from a storage medium 23 and execute these instructions, thereby performing any of the steps disclosed below.

FIG3 a schematically illustrates components of CN nodes 13a, 13b, 13c, and 13d according to an embodiment, in terms of multiple functional units. Processing unit 31 is provided using any combination of one or more of the following suitable options: a central processing unit (CPU), a multiprocessor, a microcontroller, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), etc., capable of executing software instructions stored, for example, in the form of a computer program product 41a (as shown in FIG4 ) in the form of a storage medium 33. Processing unit 31 is thus arranged to perform the methods disclosed herein. Storage medium 33 may also include permanent storage, which may be, for example, any single or combination of magnetic, optical, solid-state, or even remotely mounted storage. CN nodes 13a, 13b, 13c, and 13d may also include a communication interface 32 for communicating with RAN nodes 11b, 12b and other CN nodes 13a, 13b, 13c, 13d, and 13e. The processing unit 31 controls the general operation of the CN nodes 13a, 13b, 13c, 13d, for example, by sending data and control signals to the communication interface 22 and the storage medium 33, by receiving data and reports from the communication interface 32, and by retrieving data and instructions from the storage medium 33. Other components of the CN nodes 13a, 13b, 13c, 13d and related functions are omitted to avoid obscuring the concepts presented herein.

Figure 3b schematically illustrates the components of CN nodes 13a, 13b, 13c, and 13d according to an embodiment, in terms of multiple functional modules. The CN nodes 13a, 13b, 13c, and 13d of Figure 3b include multiple functional modules: a setup module 31a and a provision module 31b. The CN nodes 13a, 13b, 13c, and 13d of Figure 3b may also include multiple optional functional modules. The functions of each functional module 31a-31b will be further disclosed below in the context of how these functional modules 31a-31b may be used. Generally speaking, each functional module 31a-31b can be implemented in hardware or software. Preferably, one or more or all of the functional modules 31a-31b can be implemented by a processing unit 31, possibly in conjunction with functional units 32 and/or 33. The processing unit 31 can therefore be arranged to retrieve instructions provided by the functional modules 31a-31c from a storage medium 33 and execute these instructions, thereby performing any of the steps disclosed below.

Figure 4 shows an example of a computer program product 41a, 41b comprising computer-readable components 43. Computer-readable components 43 may store a computer program 42a that causes processing unit 21 and entities and devices operatively coupled thereto, such as communication interface 22 and storage medium 23, to perform methods performed by RAN nodes 11b, 12b according to embodiments described herein. Computer-readable components 43 may also store a computer program 42b that causes processing unit 31 and entities and devices operatively coupled thereto, such as communication interface 32 and storage medium 33, to perform methods performed by CN nodes 13a, 13b, 13c, 13d according to embodiments described herein. Computer programs 42a, 42b and/or computer program products 41a, 41b may thus provide means for performing any of the steps disclosed herein.

In the example of FIG4 , the computer program products 41 a, 41 b are shown as optical discs such as CDs (Compact Discs), DVDs (Digital Versatile Discs), or Blu-ray Discs. The computer program products 41 a, 41 b may also be embodied as memories such as random access memories (RAMs), read-only memories (ROMs), erasable programmable read-only memories (EPROMs), or electrically erasable programmable read-only memories (EEPROMs), and more specifically as non-volatile storage media in devices such as USB (Universal Serial Bus) memories or flash memories (such as Compact Flash). Thus, although the computer programs 42 a, 42 b are schematically shown here as tracks on the depicted optical discs, the computer programs 42 a, 42 b may be stored in any manner suitable for the computer program products 41 a, 41 b.

Figures 5 and 6 are flow charts illustrating embodiments of methods for providing supported capabilities of CN nodes 13a, 13b, 13c, and 13d. These methods are performed by CN nodes 13a, 13b, 13c, and 13d. Figures 7 and 8 are flow charts illustrating embodiments of methods for receiving supported capabilities of CN nodes 13a, 13b, 13c, and 13d. These methods are performed by RAN nodes 11b and 12b. Advantageously, these methods are provided as computer programs 42a and 42b.

Reference is now made to Figure 5 which illustrates a method performed by the CN nodes 13a, 13b, 13c, 13d for providing support capabilities of the CN nodes 13a, 13b, 13c, 13d according to an embodiment. Reference is made in parallel to the signalling diagram of Figure 9 .

S102: The CN node 13a, 13b, 13c, 13d establishes a connection to a Radio Access Network (RAN) node 11b, 12b. Either the CN node 13a, 13b, 13c, 13d or the RAN node 11b, 12b may initiate the connection to be established.

S104: The CN nodes 13a, 13b, 13c, 13d provide, in response to the connection being established in step S102, an indication to the RAN nodes 11b, 12b as to whether the CN nodes 13a, 13b, 13c, 13d support at least one of an operator cooperation area (OCA) and a query. Based on the indication, the CN nodes provide information to be used by the RAN nodes for selecting a service operator, such that the same operator is selected for the wireless device in both the circuit switched (CS) domain and the packet switched (PS) domain.

At this point, the OCA and query may be defined as the old LAI/CS-NRI (for CS domain) and old RAI/PS-NRI (for PS domain) from the sharing partner network may always be mapped to the operator's area in the shared network.

Furthermore, in terms of queries, for a (combined or non-combined) registration attempt in the PS domain, the RAN nodes 11b, 12b may query the CN nodes 13a, 13b in the CS domain to determine whether the wireless device 15a, 15b is registered with any shared operator in the CS domain. Similarly, for a registration attempt in the CS domain, the RAN nodes 11b, 12b may query the CN nodes 13c, 13d in the PS domain to determine whether the wireless device 15a, 15b is registered with any shared operator in the PS domain. For a registration attempt in the CS domain, and if the wireless device 15a, 15b is not registered with any CN node in the PS domain in the shared network 10, the RAN nodes 11b, 12b may query all possible Mobility Management Entities (MMEs) of the shared operators via the CN nodes 13c, 13d in the PS domain to determine whether the wireless device 15a, 15b is registered with any MME of the shared operator. When reselecting a cell from LTE for a wireless device 15a, 15b that is not registered with a CN node 13c, 13d, registration in the MME but not in the CS domain may occur.

Thus, the embodiments disclosed herein enable the CN nodes (SGSN 13c, 13d and MSC 13a, 13b) to provide the RAN nodes (BSC 12b or RNC 11b) with the ability to query whether they each support the concept of an Operator Collaboration Area (OCA). As described above, this capability is provided immediately after the connection between the network nodes is established.

Embodiments will now be disclosed relating to further details of providing support capabilities of the CN nodes 13a, 13b, 13c, 13d.

There are different examples of RAN nodes. For example, a RAN node may be a Base Station Controller (BSC) 12b or a Radio Network Controller (RNC) 11b.

There are different examples of CN nodes. For example, a CN node may be a Serving General Packet Radio Service Support Node (SGSN) 13c, 13d or a Mobile Switching Center (MSC) 13a, 13b.

Reference is now made to Figure 6 which illustrates a method performed by the CN nodes 13a, 13b, 13c, 13d for providing support capabilities of the CN nodes 13a, 13b, 13c, 13d according to a further embodiment. Continuing in parallel reference is the signalling diagram of Figure 9 .

There are different ways to provide the indication. Now, different embodiments related thereto will be described in turn.

The indication may be provided upon initialization of the CN node. Additionally or alternatively, the indication is provided upon initialization of the RAN node.

For GSM in the PS domain, the SGSN capability can be indicated by using one of the spare bits in the extended feature bitmap message. Therefore, according to an embodiment, the indication is provided using a spare bit in the extended feature bitmap message. Figure 10 provides a schematic diagram of the fields of the extended feature bitmap message 100. Generally speaking, the extended feature bitmap information element indicates optional features supported by the underlying network service entity (NSE).

The extended feature bitmap message may be sent within the BVC-RESET and BVC-RESET-ACK messages between the SGSN 13d and the BSC 12b as part of the connection establishment process. Therefore, according to an embodiment, an indication is provided in the BVC-RESET message, and the method further comprises the following optional step S104a:

S104a: The CN nodes 13a, 13b, 13c, 13d provide a BVC-RESET message to the RAN node. The BVC-RESET message may include an indication.

For GSM in the CS domain, and for WCDMA (in both the CS and PS domains), new messages indicating the capabilities of the MSC 13a, 13b and SGSN 13c, 13d, respectively, may be introduced. This message and the corresponding confirmation message may be sent upon initialization of the node. Both the initialization message and the confirmation message may include an OCA capability indication.

Another possible approach is to multiplex the RESET and RESET ACKNOWLEDGE messages. These messages are currently defined to be sent only after a network node (BSC 12b, RNC 11b, MSC 13a, 13b, or SGSN 13c, 13d) is restarted, but the BSC 12b and RNC 11b may also be required to send a RESET message upon network node initialization (compared to BVC-RESET). The MSC 13a, 13b and SGSN 13c, 13d can then reply with a RESET ACKNOWLEDGE message. Therefore, in this context, in step S104a, it is the CN node that sends the RESET message, and it is the RAN node that responds with the RESET ACK. The CN node may also need to send a RESET upon initialization. Both the RESET message and the RESET ACKNOWLEDGE message may include parameters indicating the network node's OCA capabilities.

Therefore, according to an embodiment, the indication is provided in a RESET message sent during initialization, and the method further comprises the following optional step S104b:

S104b: The CN nodes 13a, 13b, 13c, 13d provide a RESET message to the RAN nodes 11b, 12b. The RESET message may include an indication.

The indication may be provided to the RAN node 11b, 12b before the CN node 13a, 13b, 13c, 13d receives any registration request from the wireless device 15a, 15b via the RAN node 11b, 12b.

Reference is now made to Figure 7 which illustrates a method performed by a RAN node 11b, 12b for receiving supported capabilities of a CN node 13a, 13b, 13c, 13d according to an embodiment. Continuing in parallel reference is made to the signalling diagram of Figure 9 .

S202: RAN nodes 11b, 12b establish connections to CN nodes 13a, 13b, 13c, 13d. The CN nodes 13a, 13b, 13c, 13d or the RAN nodes 11b, 12b may initiate the connection to be established.

S204: The RAN nodes 11b, 12b receive, in response to the connection established in step S202, an indication from the CN nodes 13a, 13b, 13c, 13d as to whether the CN nodes 13a, 13b, 13c, 13d support at least one of an Operator Cooperation Area (OCA) and a query. Based on the indication, the CN nodes provide information to be used by the RAN nodes for selecting a service operator, such that the same operator is selected for the wireless device in both the circuit switched CS domain and the packet switched PS domain.

S206: The RAN node stores the received indication together with the identity information of the CN nodes 13a, 13b, 13c, 13d.

Thus, the embodiments disclosed herein ensure that the CN nodes (SGSN 13c, 13d and MSC 13a, 13b) provide the RAN nodes (BSC 12b or RNC 11b) with the capability of whether each supports the concept of an Operator Collaboration Area (OCA). As described above, this capability is received immediately after the connection between the network nodes is established. RAN nodes 11b, 12b will then only apply this functionality if both the SGSN 13c, 13d and the MSC 13a, 13b support it.

Embodiments will now be disclosed relating to further details of the supported capabilities of the receiving CN nodes 13a, 13b, 13c, 13d.

As mentioned above, there are different examples of RAN nodes. For example, a RAN node may be a Base Station Controller (BSC) 12b or a Radio Network Controller (RNC) 11b.

As mentioned above, there are different examples of CN nodes. For example, a CN node may be a Serving General Packet Radio Service Support Node (SGSN) 13c, 13d or a Mobile Switching Center (MSC) 13a, 13b.

Reference is now made to Figure 8 which illustrates a method performed by a RAN node 11b, 12b for receiving supported capabilities of a CN node 13a, 13b, 13c, 13d according to a further embodiment. Continuing in parallel reference is made to the signalling diagram of Figure 9 .

There are different ways to receive the indication, and different embodiments related thereto will now be described in sequence.

As mentioned above, the indication may be provided upon initialisation of the CN node. Additionally or alternatively, the indication may be provided upon initialisation of the RAN node.

As described above, the indication may be provided in a BVC-RESET message (step S104a), and according to an embodiment, the method therefore further comprises the following optional step S204a:

S204a: The RAN nodes 11b, 12b receive a BVC-RESET message from the CN node. The BVC-RESET message may include an indication.

The RAN nodes 11b, 12b may respond to the BVC-RESET message by sending a BVC-RESET-ACK message, and according to an embodiment, the method therefore further comprises the following optional step S208a:

S208a: The RAN nodes 11b, 12b send a BVC-RESET-ACK message to the CN nodes 13a, 13b, 13c, 13d. The BVC-RESET-ACK message may include the indication.

As described above, the indication may be provided in a RESET message (step S104b). Thus, according to an embodiment, the indication is received in a RESET message sent during initialization of the CN node, and the method further comprises the following optional step S204b:

S204b: The RAN nodes 11b and 12b receive a RESET message from the CN node. The RESET message may include an indication.

The RAN node 11b, 12b may respond to the RESET message by sending a RESET-ACK message, and according to an embodiment, the method therefore further comprises an optional step S208b as follows:

S208b: The RAN nodes 11b and 12b send a RESET-ACK message to the CN nodes 13a, 13b, 13c and 13d. The RESET-ACK message may include an indication.

The RAN nodes 11b, 12b may use this capability during registration of the wireless devices 15a, 15b. Therefore, according to an embodiment, the method further comprises the following optional steps S210 and S212:

S210: The RAN node 11b, 12b receives a registration request for the wireless device 15a, 15b.

S212: The RAN node 11b, 12b registers the wireless device 15a, 15b based on the stored indication.In other aspects, the registration may follow the procedure as outlined in 3GPP TS 23.704.

The inventive concept has been primarily described above with reference to several embodiments. However, as will be readily appreciated by those skilled in the art, other embodiments than those disclosed are equally feasible within the scope of the inventive concept as defined by the appended patent claims. Furthermore, while the embodiments presented so far relate to indications of capabilities provided by CN nodes 13a, 13b, 13c, 13d to RAN nodes 11b, 12b, the corresponding capabilities of CN nodes 13a, 13b, 13c, 13d may also be provided to RAN nodes 11b, 12b. Furthermore, in at least some embodiments, it is typically a network node (either a RAN node or a CN node) that initiates the communication of sending a BVC-RESET message, and another network node responds with a BVC-RESET-ACK. The BVC-RESET message may therefore be sent by either RAN node 11b, 12b or CN node 13a, 13b, 13c, 13d.

Claims (27)

1. A method for providing support capabilities for core network CN nodes (13a, 13b, 13c, 13d), the method being executed by the CN nodes, the method comprising: Establish (S102) a connection to the radio access network RAN nodes (11b, 12b), and immediately after the establishment of the connection: The RAN node is provided with (S104) an indication relating to at least one of whether the CN node supports the Operator Cooperation Area (OCA) and a query, and the CN node provides information to be used by the RAN node to select a service operator based on the indication, such that the same operator is selected for the radio device in both the circuit-switched (CS) domain and the packet-switched (PS) domain. 2. The method according to claim 1, wherein the RAN node is a base station controller (BSC) (12b) or a radio network controller (RNC) (11b). 3. The method according to claim 1, wherein the CN node is a Serving General Packet Radio Service Support Node (SGSN) (13c, 13d) or a Mobile Switching Center (MSC) (13a, 13b). 4. The method of claim 1, wherein the indication is provided using spare bits in the extended feature bitmap message (100). 5. The method of claim 1, wherein the indication is provided in the BVC-RESET message, the method further comprising: Provide the BVC-RESET message (S104a) to the RAN node. 6. The method according to claim 5, further comprising: Receive a BVC-RESET-ACK message from the RAN node, wherein the BVC-RESET-ACK message includes the indication. 7. The method of claim 1, wherein the indication is provided during the initialization of the CN node. 8. The method of claim 1, wherein the indication is provided during the initialization of the RAN node. 9. The method of claim 7 or 8, wherein the indication is provided in a RESET message sent during the initialization, the method further comprising: Provide the RESET message (S104b) to the RAN node. 10. The method of claim 9, wherein the RESET-ACK message includes the indication. 11. The method of claim 1, wherein the indication is provided to the RAN node before the CN node receives any registration request from the wireless device (15a, 15b) via the RAN node. 12. A method for receiving support capabilities of core network CN nodes (13a, 13b, 13c, 13d), the method being performed by radio access network RAN nodes (11b, 12b), the method comprising: Establish (S202) a connection to the core network CN node, and immediately after the establishment of the connection: The CN node receives (S204) an indication relating to at least one of whether the CN node supports Operator Cooperation Area (OCA) and a query, and the CN node provides information to be used by the RAN node for selecting a serving operator based on the indication, such that the same operator is selected for the radio device in both the circuit-switched (CS) and packet-switched (PS) domains; and The stored (S206) instruction received is accompanied by the identity information of the CN node. 13. The method of claim 12, wherein the RAN node is a base station controller (BSC) (12b) or a radio network controller (RNC) (11b). 14. The method of claim 12, wherein the CN node is a Serving General Packet Radio Service Support Node (SGSN) (13c, 13d) or a Mobile Switching Center (MSC) (13a, 13b). 15. The method of claim 12, further comprising: Receive (S204a) BVC-RESET message from the CN node. 16. The method of claim 15, wherein the BVC-RESET message includes the indication. 17. The method according to claim 15 or 16, further comprising: Send a (S208a) BVC-RESET-ACK message to the CN node. 18. The method of claim 17, wherein the BVC-RESET-ACK message includes the indication. 19. The method of claim 12, wherein the indication is received in a RESET message sent during the initialization of the CN node, the method further comprising: Receive (S204b) RESET message from the CN node. 20. The method of claim 19, wherein the RESET message includes the indication. 21. The method according to claim 19 or 20, further comprising: Send a (S208b) RESET-ACK message to the CN node. 22. The method of claim 21, wherein the RESET-ACK message includes the indication. 23. The method of claim 12, further comprising: Receive (S210) registration request (15a, 15b); and Register the wireless device based on the stored instructions (S212). 24. A core network CN node (13a, 13b, 13c, 13d) for providing support capabilities for the CN node, the CN node including a processing unit (21), the processing unit (21) being configured to: Establish a connection to the radio access network (RAN) nodes (11b, 12b), and immediately after the establishment of the connection: The RAN node is provided with an indication of whether the CN node supports at least one of the Operator Cooperation Area (OCA) and queries, and the CN node provides information to be used by the RAN node to select a service operator based on the indication, such that the same operator is selected for the radio device in both the circuit-switched (CS) domain and the packet-switched (PS) domain. 25. A radio access network (RAN) node (11b, 12b) for receiving support capabilities from core network (CN) nodes (13a, 13b, 13c, 13d), the RAN node comprising a processing unit (31) configured to: Establish a connection to the core network (CN) node, and immediately after the establishment of the connection: The CN node receives an indication relating to at least one of whether it supports Operator Cooperation Area (OCA) and a query, and the CN node provides information to be used by the RAN node for selecting a serving operator based on the indication, such that the same operator is selected for the radio device in both the circuit-switched (CS) and packet-switched (PS) domains; and The received instruction is stored along with the identity information of the CN node. 26. A computer-readable storage medium storing a computer program (42b) for providing support capabilities for core network CN nodes (13a, 13b, 13c, 13d), the computer program including computer program code, which, when executed on a processing unit (31) of the CN node, causes the processing unit to: Establish (S102) a connection to the radio access network RAN nodes (11b, 12b), and immediately after the establishment of the connection: The RAN node is provided with (S104) an indication relating to at least one of whether the CN node supports the Operator Cooperation Area (OCA) and a query, and the CN node provides information to be used by the RAN node to select a service operator based on the indication, such that the same operator is selected for the radio device in both the circuit-switched (CS) domain and the packet-switched (PS) domain. 27. A computer-readable storage medium storing a computer program (42a) for receiving support capabilities of core network CN nodes (13a, 13b, 13c, 13d), the computer program including computer program code, which, when executed on a processing unit (21) of a radio access network RAN node (11b, 12b), causes the processing unit to: Establish (S202) a connection to the core network CN node, and immediately after the establishment of the connection: The CN node receives (S204) an indication relating to at least one of whether the CN node supports Operator Cooperation Area (OCA) and a query, and the CN node provides information to be used by the RAN node for selecting a serving operator based on the indication, such that the same operator is selected for the radio device in both the circuit-switched (CS) and packet-switched (PS) domains; and The stored (S206) instruction received is accompanied by the identity information of the CN node.