WO2017135859A1 - Nœuds de réseau et procédés réalisés dans ces derniers - Google Patents

Nœuds de réseau et procédés réalisés dans ces derniers Download PDF

Info

Publication number
WO2017135859A1
WO2017135859A1 PCT/SE2016/050106 SE2016050106W WO2017135859A1 WO 2017135859 A1 WO2017135859 A1 WO 2017135859A1 SE 2016050106 W SE2016050106 W SE 2016050106W WO 2017135859 A1 WO2017135859 A1 WO 2017135859A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
wireless device
node
core network
functionalities
Prior art date
Application number
PCT/SE2016/050106
Other languages
English (en)
Inventor
Angelo Centonza
Jari Vikberg
Oscar Zee
Paul Schliwa-Bertling
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2017135859A1 publication Critical patent/WO2017135859A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/12—Inter-network notification
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events

Definitions

  • Embodiments herein relate to a Radio Access Network, RAN, node, a core network node, a wireless device and methods performed therein for communication. Furthermore, a computer program and a computer readable storage medium are also provided herein. In particular, embodiments herein relate to enabling connection setup for a wireless device in a communication network.
  • wireless devices also known as wireless communication devices, mobile stations, stations (STA) and/or user equipments (UE), communicate via a Radio Access Network (RAN) to one or more core networks (CN).
  • the RAN covers a geographical area which is divided into service areas or cell areas, with each service area or cell area being served by a radio network node such as a radio access node e.g., a Wi-Fi access point or a radio base station (RBS), which in some networks may also be denoted, for example, a "NodeB" or "eNodeB".
  • a service area or cell area is a geographical area where radio coverage is provided by the radio network node.
  • the radio network node communicates over an air interface operating on radio frequencies with the wireless device within range of the radio network node.
  • a Universal Mobile Telecommunications System is a third generation telecommunication network, which evolved from the second generation (2G) Global System for Mobile Communications (GSM).
  • the UMTS terrestrial radio access network is essentially a RAN using wideband code division multiple access (WCDMA) and/or High Speed Packet Access (HSPA) for user equipments.
  • WCDMA wideband code division multiple access
  • HSPA High Speed Packet Access
  • 3GPP Third Generation Partnership Project
  • telecommunications suppliers propose and agree upon standards for third generation networks, and investigate enhanced data rate and radio capacity.
  • 3GPP Third Generation Partnership Project
  • radio network nodes may be connected, e.g., by landlines or microwave, to a controller node, such as a radio network controller (RNC) or a base station controller (BSC), which supervises and coordinates various activities of the plural radio network nodes connected thereto.
  • RNC radio network controller
  • BSC base station controller
  • This type of connection is sometimes referred to as a backhaul connection.
  • the RNCs and BSCs are typically connected to one or more core networks.
  • EPS Evolved Packet System
  • the EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network.
  • E-UTRAN/LTE is a variant of a 3GPP radio access network wherein the radio network nodes are directly connected to the EPC core network rather than to RNCs.
  • SAE System Architecture Evolution
  • the RAN of an EPS has an essentially "flat" architecture comprising radio network nodes connected directly to one or more core networks, i.e. they are not connected to RNCs.
  • the E-UTRAN specification defines a direct interface between the radio network nodes, this interface being denoted the X2 interface.
  • EPS is the Evolved 3GPP Packet Switched Domain.
  • Figure 1 is an overview of the EPC architecture.
  • E-UTRAN comprises one or more eNBs.
  • Figure 2 shows the overall E-UTRAN architecture and is further defined in for example 3GPP TS 36.300 v.13.1.0.
  • the E-UTRAN comprises eNBs, providing a user plane comprising the protocol layers Packet Data Convergence Protocol (PDCP)/Radio Link Control (RLC)/Medium Access Control (MAC)/Physical layer (PHY), and a control plane comprising Radio Resource Control (RRC) protocol in addition to the user plane protocols towards the wireless device.
  • the radio network nodes are interconnected with each other by means of the X2 interface.
  • the radio network nodes are also connected by means of the S1 interface to the EPC, more specifically to the MME by means of an S1- MME interface and to the S-GW by means of an S1-U interface.
  • FIG. 3 shows a management system architecture in the communications network.
  • the node elements also referred to as eNodeB, are managed by a domain manager (DM), also referred to as the operation and support system (OSS).
  • a DM may further be managed by a network manager (NM).
  • NM network manager
  • Two NEs are interfaced by X2, whereas the interface between two DMs is referred to as ltf-P2P.
  • the management system may configure the network elements, as well as receive observations associated to features in the network elements. For example, DM observes and configures NEs, while NM observes and configures DM, as well as NE via DM.
  • NM and related interfaces By means of configuration via the DM, NM and related interfaces, functions over the X2 and S1 interfaces can be carried out in a coordinated way throughout the RAN, eventually involving the Core Network, i.e. MMEs and S-GWs.
  • the S1-MME interface is used for control plane between eNodeB/E-UTRAN and MME.
  • the main protocols used in this interface are S1 Application Protocol (S1AP) and Stream Control Transmission Protocol (SCTP).
  • S1AP is the application Layer Protocol between the radio network node and the MME and SCTP for example guarantees delivery of signaling messages between MME and the radio network node.
  • the transport network layer is based on Internet Protocol (IP).
  • a subset of the S1 interface provided functions are:
  • S1-interface management functions such as S1 setup, error indication, reset and the radio network node and MME configuration update.
  • UE Context Management functionality such as Initial Context Setup Function and UE Context Modification Function.
  • E-UTRAN Radio Access Bearer Service Management functions e.g. Setup, Modify, Release.
  • ECM Intra-LTE Handover and inter-3GPP-Radio Access Technology (RAT) Handover.
  • RAT Radio Access Technology
  • Non Access Stratum (NAS) Signaling Transport function NAS
  • the purpose of the S1 Setup procedure is to exchange application level data needed for the radio network node and the MME to correctly interoperate on the S1 interface.
  • the radio network node may initiate the procedure by sending an S1 SETUP REQUEST message to the MME once it has gained IP
  • the TAI(s) are used by the radio network node to locate IP-addresses of the different MMEs, possibly in different MME pools.
  • the radio network node includes its global radio network node identity and other information in the S1 SETUP REQUEST message.
  • the MME responds with an S1 SETUP RESPONSE message.
  • This S1 SETUP RESPONSE message includes for example the Globally Unique MME identifier(s) (GUMMEI) of the MME.
  • An Initial Context Setup process is shown in Figure 5.
  • An INITIAL CONTEXT SETUP REQUEST message is sent by the MME to request the setup of a UE context or context of a wireless device.
  • This INITIAL CONTEXT SETUP REQUEST message comprises information related to both the UE context and different E-RABs to be established.
  • the MME includes E-RAB Quality of Service (QoS) parameters such as QoS Class Identifier (QCI) and Allocation and Retention Priority (ARP).
  • QCI Quality of Service
  • QCI QoS Class Identifier
  • ARP Allocation and Retention Priority
  • the QCI is a scalar that is used as a reference to radio access node-specific parameters that control bearer level packet forwarding treatment, e.g.
  • the purpose of the Globally Unique Temporary UE Identity is to provide an unambiguous identification of the UE that does not reveal the UE or the user's permanent identity in the Evolved Packet System (EPS).
  • the GUTI also allows the identification of the MME and the network. It can be used by the network and the UE to establish the UE's identity during signaling between the UE and the network in the EPS.
  • the GUTI may have a length of 76 to 80 bits.
  • the GUTI comprises two main components:
  • GUMMEI Globally Unique MME Identifier
  • M-TMSI Temporary Mobile Subscriber Identity
  • the mobile is identified by the M-TMSI.
  • the GUMMEI may be constructed from a Mobile Country Code (MCC), a Mobile Network Code (MNC) and an MME Identifier (MMEI).
  • MCC Mobile Country Code
  • MNC Mobile Network Code
  • MMEI MME Identifier
  • MMEGI MME Group ID
  • MMEC MME Code
  • the GUTI is constructed from the GUMMEI and the M-TMSI.
  • the mobile is paged with an S-TMSI, which S-TMSI is constructed from the MMEC and the M-TMSI.
  • An operator will need to ensure that the MMEC is unique within the MME pool area and, if overlapping pool areas are in use, unique within the area of overlapping MME pools. If the MMEC is not unique within the MME pool, the transmission in the network might be directed to the wrong MME
  • the UE may signal to the RAN, during a service request or paging response procedure, an S-TMSI or a GUMMEI. A detection of the right CN node may then be performed based on these parameters.
  • the GUTI supports subscriber identity confidentiality, and, in the shortened S-
  • TMSI form enables more efficient radio signalling procedures, e.g. during Paging and/or Service Request.
  • the format and size of the GUTI is therefore the following:
  • ⁇ GUTI> ⁇ GUMMEI> ⁇ M-TMSI>
  • ⁇ GUMMEI> ⁇ MCC> ⁇ MNC> ⁇ MME Identifier
  • ⁇ MME Identifier ⁇ MME Group ID> ⁇ MME Code>.
  • the wireless communication industry is at the verge of a unique business crossroads. The growing gap between capacity and demand is an urgent call for new approaches and alternative network technologies to enable mobile operators to achieve more with less.
  • mobile broadband data is growing at an annual rate of 40-50 percent per year in the U.S. and other regions globally. Mobile service providers address these rapidly expanding traffic volumes through deployment of additional network functions, which will be a significant capital expenditure (CAPEX) challenge.
  • CAEX capital expenditure
  • the nature of the mobile broadband data traffic is also evolving with new services including new video applications, connected cars and the Internet of Things (loT). This rapid capacity growth and increasing traffic diversity in LTE networks stresses the assumptions of existing network architectures and operational paradigms. As expected by leading operators and vendors in Next Generation Mobile
  • 5G Networks (NGMN) association, diverse applications or services are expected to be provided by 5G networks.
  • 5G will support countless emerging use cases with a high variety of applications and variability of their performance attributes: from delay-sensitive video applications to ultra-low latency, from high speed entertainment applications in a vehicle to mobility on demand for connected objects, and from best effort applications to reliable and ultra-reliable ones such as health and safety.
  • use cases will be delivered across a wide range of devices, e.g., smartphones, wearables, MTCs, and across a fully heterogeneous environment.
  • NFV Network Functions Virtualization
  • COTS Commercial Off-the- Shelf
  • vEPC Virtualized EPC
  • NFVI Network Functions Virtualization Infrastructure
  • SLA Service Level Agreements
  • VNF is a virtualized network function which serves as a VNF Software for providing virtual network capabilities.
  • a VNF could be decomposed and instantiated in roles such as Virtualized MME (vMME), Virtualized PCRF (vPCRF), Virtualized SGW (vSGW) or Virtualized PDN-GW (vPDN-GW).
  • NFV is seen as an enabler for network slicing and network sharing that is described herein.
  • Network slicing is about creating logically separated partitions of the network, which may also be referred to as slices or network slices, addressing different business purposes. These network slices are logically separated to a degree that they can be regarded and managed as networks of their own.
  • Network slicing is a new concept that applies to both LTE Evolution and New 5G RAT, which herein is referred to as NX.
  • the key driver for introducing network slicing is business expansion, i.e. improving the operator's ability to serve other industries, by offering connectivity services with different network characteristics, such as e.g.
  • the current main working assumption is that there will be one shared RAN infrastructure that will connect to several EPC instances, where one EPC instance relates to a network slice.
  • EPC functions are being virtualized, it is assumed that an operator will instantiate a new CN when a new slice should be supported.
  • RAN sharing is based on the possibility for operators to share the same RAN and optionally the same spectrum by means of two standardized architectures, which are shown in Fig. 7.
  • the first architecture is called Mobile Operator Core Network (MOCN) and consists of different participating operators to connect their CN infrastructure to a commonly shared RAN. In this case each participating operator can run CN-RAN procedures from its own managed RAN.
  • a second architecture option is called Gateway Core Network (GWCN) and it consists of the shared RAN connecting to a single shared CN. Participating operators would therefore share the CN as well as the RAN.
  • MOCN Mobile Operator Core Network
  • GWCN Gateway Core Network
  • the RAN may be managed by one of the participating operators or may be managed by a third party. It may also be possible that the CN infrastructure is managed by one of the participating operators or by a third party or it may be managed in part, i.e. for some nodes, by a third party and in part by the participating operator. Each participating operator has access to a set of resources both in the CN and in the RAN.
  • a network slice supports the communication service of a particular connection type with a specific way of handling C- plane and U-plane for the service.
  • a 5G slice could be composed by a collection of 5G network functions and possibly specific RAT with specific settings that are combined together for the specific use case or business model. It should be noted that not all slices contain the same network functions.
  • a specific network service can be instantiated according to on demand requirements for third party users/operators and the business policy between the network service providers and network the service consumers.
  • an operator may have one physical network infrastructure and one pool of frequency bands, which may support many separate virtualized networks, also called network slices.
  • Each network slice may have unique characteristics for meeting the specific requirements of the use case/s it serves.
  • a key function of 5G Core network is to allow for flexibility in network service creation, making use of different network functions suitable for the offered service in a specific network slice, e.g. Evolved Mobile Broadband (MBB), Massive Machine Type Communication (MTC), Critical MTC, Enterprise, etc.
  • MBB Evolved Mobile Broadband
  • MTC Massive Machine Type Communication
  • Critical MTC Critical MTC
  • Enterprise etc.
  • the network slices can also provide resource isolation between each other. Thus introduction of a new isolated network slice will not impact the existing operator services and therefore only provide low risk
  • TTM Short Time To Market
  • the operators are concerned about the time it takes to set up the network for a new service.
  • Slicing of the network for different services/operator use cases provides a separation of concern that can result in a faster setup of a network slice for a certain service as it is separately managed and with limited impact on other network slices
  • Optimized use of resources Today the network is supporting many different services but with new use cases and more diverging requirements there is a need for optimize the network for the specific type use case. Network slicing allows to match services to optimized network instances, and it also allows for a more optimized use of those specific resources
  • Slicing can also be used to isolate different services in an operator's network. Future networks are expected to support new use cases going beyond the basic support for voice services and mobile broadband currently supported by existing cellular network, e.g. 2G/3G/4G. Some example use cases include:
  • Government services e.g. national and/or public safety
  • Fig. 8 shows an example of a network slicing for a case when there exists different network slices in the core network for MBB, Massive MTC and Critical MTC.
  • the network slices may comprise separate core network instances supporting the different network slices.
  • parts of the EPC are shared between the different network slices.
  • shared EPC functionality may be a core network node, such as a MME.
  • a RAN in a sliced network may be implemented with the following pre-requisites:
  • a RAN operator manages a number of eNBs which are comprised in the operators own transport network in the RAN.
  • the RAN operator, CN operators and other participating parties in the shared system have mutual Service Level Agreements (SLA).
  • SLA Service Level Agreement
  • the shared network supports a number of coexisting network slices
  • each slice is served by part of the overall RAN/CN infrastructure.
  • Each core network node such as an MME, in the CN can handle one or several slices.
  • the maximum number of core network nodes which can be addressed within a CN operator will be 256 as long as 8-bits MMEC is used, since each core network node requires a unique MMEC.
  • the aim of the network slicing is therefore to provide a simple tool for cellular operators to introduce new services and features to different industries.
  • An object of embodiments herein is to provide a mechanism for improving capacity and reducing the coordination effort of the communication network in an efficient manner. According to an aspect the object is achieved by a method, performed by a Radio
  • the communication network comprises a first network and a second network.
  • the RAN node is associated with the first and with the second network.
  • a first core network node is associated with the first network and a second core network node is associated with the second network.
  • the RAN node receives a paging request from a core network node, which paging request comprises an indication of a network identity for the network associated with the core network node, an indication of a core network node IDentity (ID) associated with the core network node and a wireless device ID of the wireless device which is being paged.
  • ID core network node IDentity
  • the RAN node further transmits the paging request to the wireless device associated with the wireless device ID, wherein the paging request indicates the network identity for the network associated with the core network node, the core network node ID associated with the core network node, and the wireless device identity.
  • the object is achieved by a method performed by a first core network node, for enabling connection setup for a wireless device in a communication network.
  • the communication network comprises a first network and a second network.
  • the first core network node is associated with the first network and a second core network node is associated with the second network.
  • the first core network node is being identified by a first core network node IDentity (ID) and the second core network node is being identified by a second core network node ID.
  • the first and the second core network node IDs are uncoordinated between the first network and the second network.
  • the core network node initiates a connection establishment for the wireless device by transmitting a paging request to a Radio Access Network (RAN) node.
  • the paging request comprises an indication of a network identity for the first network associated with the core network node, the core network node ID and a wireless device identity of the wireless device which is being paged.
  • RAN Radio Access Network
  • the object is achieved by a method performed by a wireless device, for establishing a connection to a communication network.
  • the communication network comprises a first network and a second network.
  • the first network is associated with a first core network node and the second network is associated with a second core network node.
  • the first and the second network are further associated to a Radio Access Network (RAN) node.
  • the wireless device receives a paging request from the RAN node.
  • the paging request comprises an indication of a network identity (ID) of the network associated with the core network node, a core network node ID identifying the first core network node 19 and the wireless device identity of the wireless device.
  • the wireless device further transmits a response to the RAN node.
  • the response comprises the network ID of the first network indicated in the paging request, the core network node ID for the core network node indicated in the paging request and the wireless device identity of the wireless device.
  • the object is achieved by providing a Radio Access Network (RAN) node for enabling connection setup for a wireless device in a communication network.
  • the communication network comprises a first network and a second network.
  • the RAN node is associated with the first and the second network.
  • a first core network node is associated with the first network and a second core network node is associated with the second network.
  • the RAN node is configured to receive a paging request from a core network node, which paging request comprises an indication of a network identity for the network associated with the core network node, a core network node IDentity (ID) associated with the core network node and a wireless device identity of the wireless device which is being paged.
  • ID core network node IDentity
  • the RAN node is further configured to transmit the paging request to the wireless device which is associated with the wireless device identity.
  • the paging request indicates the network identity for the network associated with the core network node, the core network node ID associated with the core network node and the wireless device identity.
  • the object is achieved by providing a first core network node, for enabling connection setup for a wireless device in a communication network.
  • the communication network comprises a first network and a second network.
  • the first core network node is associated with the first network and a second core network node is associated with the second network.
  • the first core network node is being identified by a first core network node IDentity (ID) and the second core network node is being identified by a second core network node ID.
  • the first and the second core network node IDs are uncoordinated between the first network and the second network.
  • the core network node is configured to initiate a connection establishment for the wireless device by transmitting a paging request to a Radio Access Network (RAN) node.
  • the paging request comprises an indication of a network identity for the first network associated with the core network node, the core network node ID and a wireless device identity of the wireless device which is being paged.
  • RAN Radio Access Network
  • the object is achieved by providing a wireless device, for establishing a connection to a communication network.
  • the communication network comprises a first network and a second network.
  • the first network is associated with a first core network node and the second network is associated with a second core network node.
  • the first and the second network are further associated to a Radio Access Network (RAN) node.
  • the wireless device is configured to receive a paging request from the RAN node.
  • the paging request comprises an indication of a network identity (ID) of the network associated with the core network node, a core network node ID identifying the first core network node and a wireless device identity of the wireless device.
  • the wireless device is further configured to transmit a response to the RAN node.
  • the response comprises the network ID of the first network indicated in the paging request, the core network node ID for the core network node indicated in the paging request and the wireless device identity of the wireless device.
  • a computer program comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out any of the methods above, as performed by the first network node or the second network node.
  • a computer-readable storage medium having stored thereon a computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the methods above, as performed by the first network node or the second network node.
  • the MMECs do not have to be unique across different networks, such as e.g. PLMNs. This allows a reuse of MMEC values. Thereby, a communications network can handle an overall number of MMECs higher than the current limit of 256, which increases the capacity of the network. Further, since MMECs and Slice IDs do not need to be coordinated across different PLMNs cross-PLMN configurations can be minimized, thereby reducing coordination between RAN operator, CN operators (PLMNs) and other participating parties such as e.g. network slice operators. A further advantage is that M-TMSI does not need to be coordinated between core network nodes in different networks. By minimizing the coordination of the different identifiers between the participating parties the costs of running such networks can be reduced.
  • Fig. 1 is a schematic overview depicting a communication network according to prior art
  • Fig. 2 is a schematic overview depicting a radio access network in connection with a core network
  • Fig. 3 is a schematic overview depicting a management system architecture for a
  • Fig. 4 is a signalling scheme according to prior art
  • Fig. 5 is a signalling scheme according to prior art
  • Fig. 6 is a schematic overview of identities used for distinguishing elements within the network
  • Fig. 7 is a schematic overview depicting examples of standardized architectures for sharing Radio Access Networks
  • Fig. 8 is a schematic overview depicting an example of network slicing with slice specific core network instances according to prior art
  • Fig. 9 is a schematic overview depicting a communication network according to
  • Fig. 10 is a signaling diagram depicting a paging procedure according to embodiments herein.
  • Fig. 11 is a schematic flowchart depicting a method performed by a RAN node according to a first aspect of embodiments herein;
  • Fig. 12 is a schematic flowchart depicting a method performed by a core network node according to a first aspect of embodiments herein;
  • Fig. 13 is a schematic flowchart depicting a method performed by a wireless device
  • Fig. 14 is a signaling diagram depicting a service request procedure according to embodiments herein.
  • Fig. 15 is a schematic flowchart depicting a method performed by a wireless device
  • Fig. 16 is a schematic flowchart depicting a method performed by a RAN node according to a second aspect of embodiments herein;
  • Fig. 17 is a schematic flowchart depicting a method performed by a core network node according to a second aspect of embodiments herein;
  • Fig. 18 is a block diagram depicting a RAN node according to embodiments herein;
  • Fig. 19 is a block diagram depicting a core network node according to embodiments
  • Fig. 20 is a block diagram depicting a wireless device according to embodiments herein.
  • Fig. 9 is a schematic overview depicting a communication network 1.
  • the communication network 1 comprises a RAN and a CN.
  • the communication network 1 may use a number of different technologies, such as Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, 5G, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile
  • GSM/EDGE Global System for GSM Evolution
  • Embodiments herein relate to recent technology trends that are of particular interest in a 5G context, however, embodiments are
  • wireless devices e.g. a wireless device 10 such as a mobile station, a non-access point (non-AP) STA, a STA, a User Equipment (UE) and/or a wireless terminals, communicate via one or more Access Networks (AN), e.g. RAN, to one or more CNs.
  • AN Access Networks
  • wireless device is a non-limiting term which means any terminal, wireless
  • the communication network 1 comprises a radio network node 12 providing radio coverage over a geographical area, a service area 11 , of a radio access technology (RAT), such as LTE, UMTS, Wi-Fi or similar.
  • the radio network node 12 may be a radio access network node such as radio network controller or an access point such as a wireless local area network (WLAN) access point or an Access Point Station (AP ST A), an access controller, a base station, e.g.
  • a radio base station such as a NodeB, an evolved Node B (eNB, eNodeB), a base transceiver station, Access Point Base Station, base station router, a transmission arrangement of a radio base station, a stand-alone access point or any other network unit capable of serving a wireless device within the service area served by the radio network node 12 depending e.g. on the first radio access technology and terminology used.
  • the radio network node 12 is comprised in a first radio access network (RAN1) of a first network.
  • RAN1 radio access network
  • the communication network 1 comprises a first core network (CN1) and a second core network (CN2).
  • the radio network node 12 may communicate with both the CN1 and the CN2.
  • the first network comprises the first core network CN1.
  • the first network is a virtual network sliced into a number of network slices, the CN1 and/or the RAN1 may be a virtual network sliced into CN slices and/or RAN slices, each network slice or core network slice supports one or more type of wireless devices and/or one or more type of services i.e. each network slice supports a different set of functionalities.
  • Network slicing introduces the possibility that the network slices are used for different services and use cases and these services and use cases may introduce differences in the functionality supported in the different network slices.
  • Each network slice may comprise one or more network nodes or elements of network nodes providing the services/functionalities for the respective network slice.
  • Each slice may comprise a network node such as a core network slice node or a RAN slice node.
  • a first network slice for e.g. MTC devices may comprise a first network slice node 13.
  • a second network slice for e.g. MBB devices may comprise a second network slice node 14.
  • Each network slice supports a set of functionalities out of a total set of functionalities in the communication network.
  • the first network slice node 13 supports a first set of functionalities out of the total set of functionalities in the communication network 1.
  • the first set of functionalities is separated from a different set of functionalities out of the total set of functionalities in the communication network 1.
  • the first set of functionalities being associated with MTC devices is separated or logically separated, e.g. using separated data storage or processing resources, from a second set of functionalities of the second network slice being associated with MBB devices.
  • the first set of functionalities may use one or more resources in a core or RAN network of the communication network, which one or more resources are separated from other resources used by a different set of functionalities, i.e. different network slices, out of the total set of functionalities in the communication network 1.
  • the resources may then be dedicated or virtually dedicated for each set of functionalities or network slice.
  • the network slice node may be separated from other network slice nodes supporting a second set of functionalities out of the total set of functionalities in the communication network.
  • the network slice nodes may be executed on different hardware platforms and therefore using different resources of the hardware, and/or logically separated wherein the network slice nodes may be executed on a same hardware platform and use different resources such as memory parts or resources of processor capacity but may also use some same resources of the hardware e.g. a single physical network slice node may be partitioned into multiple virtual network slice nodes.
  • the first network slice node 13 supports the first set of functionalities out of the total set of functionalities in the first network of the communication network, which first set of functionalities belongs to the first network slice of the first network, and is separated from another set of functionalities out of the total set of functionalities in the first network.
  • a first network comprises one or more first network nodes 15, such as first core network nodes 19 e.g. Radio Software Defined Networking (SDN) nodes, MMEs, S-GWs, Serving GPRS Support Nodes (SGSN), or corresponding nodes in e.g. a 5G network or similar.
  • the GPRS meaning General Packet Radio Services.
  • the first network node 15 may further be a radio access network node such as the first radio network node 12.
  • a second network comprises one or more second network nodes 18, such as second core network nodes 20 e.g. Radio SDN nodes, MMEs, S-GWs, SGSNs, or corresponding nodes in e.g. a 5G network or similar.
  • the second network node 18 may further be a radio access network node such as the first radio network node 12.
  • the CN1 may assign the same MMEC to the first network node 19 as the CN2 assigns the second network node 20.
  • the radio network node will transmit an S-TMSI to the UEs in the RAN which does not uniquely identify a single UE.
  • the UE 10 may be paged by the first network node 19 with a S-TMSI.
  • paging request are transmitted to UEs using broadcasting all UEs comprised in the RAN will listen to the transmitted S-TMSI.
  • the second UE 10' will listen to the S-TMSI and determine that the transmitted S-TMSI is intended for the second UE 10'.
  • the second UE 10' will therefore try to send an erroneous paging response to the CN2.
  • the first radio network node 12 receives the paging response it will not know if the response is intended for the first network node 19 or the second network node 20 and may also forward the message to the wrong CN node.
  • paging may originate from one of the multiplicity of slices that the wireless device 10 is registered with.
  • the S-TMSI included in the paging message that includes a single MMEC identifying a single core network node 19 will not be enough for the wireless device 10 to identify the specific slice in the core network node 19 that issued the paging message.
  • the slice identifiers are not coordinated between core networks within the communication network 1 supporting multiple slices it may not be possible to identify from the identities in a service request message, such as e.g. a paging message, which slice the paging request concerns. The latter may generate a number of problems such as e.g. erroneous service request from the wireless device to a wrong slice as response to a reception of a paging message.
  • a service request message such as e.g. a paging message
  • the latter may generate a number of problems such as e.g. erroneous service request from the wireless device to a wrong slice as response to a reception of a paging message.
  • Embodiments herein therefore provide a cost effective and easy way of identifying an intended sending and/or a receiving logical node in a communications network comprising a plurality of networks, such as PLMNs, that is simple and feasible from an implementation perspective, e.g. only enhancement on existing interfaces and network functions.
  • the PLMNs comprise multiple network slices and multiple slices are configured in a core network node
  • some of the embodiments described herein enable routing of a NAS message to the NAS instance associated with the slice instance in the network that triggered paging, when a paging message is received by the wireless device.
  • the embodiments herein enable a correct identification of logical nodes during service request initiated by either the wireless device or by the core network node, by using not only S-TMSI but also a network ID for identification of the logical nodes. Thereby the dependencies of MMEC and/or slice ID between PLMNs are removed. Hence, by minimizing the coordination of identifiers across different PLMNs, the number of cross- PLMN configurations may be reduced which saves costs of running such networks.
  • a first aspect of embodiments herein therefore relate to a Network Initiated Service Request procedure, which may also be referred to as paging, for enabling connection setup for a wireless device 10 in the communication network 1.
  • a Network Initiated Service Request procedure which may also be referred to as paging
  • a wireless device 10 When a wireless device 10 is attached to a network, which may be referred to as
  • EMM REGISTERED it may enter RRC IDLE (ECM IDLE) mode, due to e.g. inactivity.
  • ECM IDLE RRC IDLE
  • the core network can initiate a Network Initiated Service Request by transmitting a paging message to the wireless device 10 through S1AP and RRC protocols and related signalling.
  • S-TMSI which comprises the MMEC for identifying a core network node and the M-TMSI for identifying a wireless device, is used as an identifier for the wireless device 10 and the core network node 19 in paging and service request procedures.
  • the S-TMSI consists of MMEC for identifying the core network node 19 and the M-TMSI generated by the core network node 19 for identifying the wireless device 10.
  • FIG. 10 where the identifiers introduced in the embodiments herein are indicated with bold font.
  • the Network Initiated Service Request comprises the following actions:
  • the core network node 19 transmits a paging message over the S1 interface to the RAN node 12.
  • the paging message comprises a network ID, such as a
  • the paging message may further comprise a slice identification, such as a slice ID, of the network slice transmitting the paging message.
  • Action 1002 The RAN node 12 forwards the paging message to the wireless device 10 over the RRC connection.
  • the paging message is broadcasted in the RAN which allows all wireless devices located in the RAN to listen to the message.
  • the wireless device 10 may determine that it is the intended receiver of the paging message based on the network ID, such as the PLMN-ID, and the MMEC and M-TMSI comprised in the S-TMSI.
  • the wireless device 10 may respond to the paging message by sending a RRC paging response to the RAN node 12.
  • the response comprises the received PLMN-ID of the network paging the wireless device 10, the S-TMSI indicating the MMEC of the core network node 19 paging the wireless device 10 and a NAS- Protocol Data Unit (PDU).
  • the response message may further comprise the slice identification, such as the slice ID, of the network slice transmitting the paging message.
  • the different identifiers may be transmitted to the RAN node 12 in one single message or may be transmitted in a plurality of messages, such as e.g. transmitting the S-TMSI in a RRC Connection Request message and the PLMN-ID, the slice ID and the NAS-PDU in a RRC Connection Setup Complete message.
  • the RAN node 12 may determine the receiving core network node based on the network ID and the core network node ID received in the paging response from the wireless device 10.
  • the RAN node 12 may further transmit an initial setup message, such as a S1AP Initial UE message, to the determined core network node 19.
  • the initial setup message comprises the S-TMSI and the NAS-PDU.
  • the response message may further comprise the slice identification, such as the slice ID, of the network slice transmitting the paging message.
  • the core network node 19 may identify a specific wireless device
  • the core network node 19 may further identify a specific wireless device 10 slice instance based on the M-TMSI and the slide ID indicated in the initial setup message received from the RAN node.
  • the RAN is hosting multiple PLMNs
  • current 3GPP standards require that the MMECs are coordinated between the participating PLMNs in the RAN for avoiding false paging, since the S-TMSI is generated independently between the core network node instances. If the MMECs would not be coordinated between networks, there would be a risk that core network nodes in different networks would have the same MMEC.
  • the method is therefore enhanced to enable a correct delivery of paging messages for uncoordinated MMECs.
  • An un-coordination of MMECs implies that there could be more than one wireless device 10 with the same S-TMSI. To avoid this, a PLMN ID for the network to which the paged wireless device 10 is attached to is added to the paging message.
  • the PLMN ID and the S-TMSI will not be sufficient to provide information about which slice has triggered the paging when the paging message is received by the wireless device 10. If the wireless device 10 has a NAS entity per slice to which it is registered, the lack of the slice identifier (Slice ID) makes it impossible for the AS layer to inform the right NAS entity about the paging.
  • the wireless device 10 would not be able to derive the Slice ID for which a service request is needed, following a paging request. Therefore, in a further embodiment the paging message may further contain a Slice ID.
  • a core network node 19 such as e.g. an MME, which is identified by a single MMEC, is serving multiple slices
  • the core network node 19 may use the same M-TMSI for both slices, an indication of the slice sending the paging message may be included. Since the correct core network itself is identified by the MMEC code and the network ID, it is sufficient to only coordinate the slice ID within each core network node. Hence, the slice ID may be reused in the
  • the MMEC range may be divided into two parts, where one part is used for legacy wireless devices, where the MMEC in this range needs to be coordinated between participating PLMNs in RAN network, and the second 5 part of MMEC range is used by wireless device type supporting shared RAN, paged according to the methods above, where MMEC coordination is not required.
  • the communication network 1 comprises the first network and the second network.
  • the RAN node 12 is associated with the first and the second network.
  • the first network may further comprise partitioned sets of functionalities wherein a first set of functionalities belongs to a first network slice supporting the wireless device 10, and which first set of functionalities is separated from another set of functionalities out of a total set of functionalities in the first
  • the RAN node 12 receives a paging request from a core network node 19.
  • the paging request comprises an indication of a network identity, such as e.g. a PLMN-ID, for the network associated with the core network node 19, a core network node IDentity (ID), such as a MMEC, associated with the core network node 19 and a wireless 25 device identity, such as S-TMSI or a M-TMSI, of the wireless device 10 which is being paged.
  • a network identity such as e.g. a PLMN-ID
  • ID core network node IDentity
  • MMEC wireless 25 device identity
  • the paging request may further comprise an indication of the first network slice supporting the wireless device 10.
  • the indication may indicate
  • paging originating from different slices managed by a single core network node can be uniquely identified in the paging message. Furthermore, if multiple slices are configured in the core network node 19, embodiments herein enable routing of a NAS message to the NAS instance
  • the combination of the parameters ⁇ PLMN ID> ⁇ S-TMSI> ⁇ Slice ID> allows the RAN node 12 to unequivocally identify a single network device and the slice for which the UE is paged, since the S-TMSI and optionally the Slice ID are unique within a PLMN ID.
  • the paging request may be received from the core network node over the S1 interface.
  • the MMEC range may be divided into two parts.
  • a first part may be used for legacy wireless devices, wherein the MMEC in this first part of the range is coordinated between participating networks, such as PLMNs in the RAN network.
  • a second part of the MMEC range is used by new wireless device types, which may be paged according to the methods above, where a coordination of MMEC is not required between participating networks.
  • This action 1 101 is similar to the action 1001 described above in relation to Fig. 10.
  • Action 1102 The RAN node 12 transmits the paging request to the wireless device 10 associated with the wireless device identity, such as S-TMSI.
  • the paging request is transmitted as a broadcasted message in the RAN, thereby every wireless device 10 in the RAN may listen to the paging request.
  • the paging request indicates the network identity for the network associated with the core network node, the core network node ID associated with the core network node, and the wireless device identity. Based on the network identity, the core network node ID and the wireless device ID the wireless device 10 may determine that it is the intended receiver of the paging request. Thereby only the wireless device 10 camping on the network identified by the network ID in the paging message, and associated to the wireless device identity, such as an S-TMSI, in the paging message will respond to the paging message.
  • the wireless device 10 camping on the network identified by the network ID in the paging message, and
  • the paging request may further comprise an indication of the first network slice paging the wireless device.
  • Such an indication may also be referred to as a slice ID.
  • the indication may indicate that the first network slice of the core network node 19 is paging the wireless device 10. By including the slice ID the wireless device 10 will know that it has been paged for a specific slice ID of the network, hence it may perform a page response for the Slice ID indicated in the paging message.
  • the RAN node 12 may transmit the paging request to the wireless device 10 using a RRC protocol.
  • This action 1 102 is similar to the action 1002 described above in relation to Fig. 10.
  • the RAN node 12 may receive a response from the wireless device 10, which response comprises the network ID of the first network selected for
  • the core network node ID for the core network node associated with the selected network and a wireless device identity of the wireless device 10 which is being paged.
  • the network selected for communication is the network which has sent the paging request.
  • the response may further comprise an indication of the first network slice paging the wireless device.
  • the wireless device can indicate which network slice the response is directed to.
  • the response may be a connection request such as a RRC Connection
  • the RAN node 12 may determine, which may also be referred to as identify, a core network node based on the received network ID and the received core network node ID from the wireless device 10. Since the core network node ID is unique for each core network node within each network ID, the RAN node 12 will be able to unequivocally identify an intended receiving core network node for the response received from the wireless device 10.
  • This action 1104 corresponds to the action 1005 described above in relation to Fig.
  • the RAN node 12 may transmit an initial setup message for the wireless device 10 to the determined core network node.
  • the initial setup message comprises the wireless device identity of the wireless device 10 which is being paged. If the first network comprises partitioned sets of functionalities the initial setup message may further comprises an indication of the network slice paging the wireless device 10.
  • the communication network 1 comprises a first network and a second network, which first core network node 19 is associated with the first network and wherein a second core network node 19 is associated with the second network.
  • the first core network node 19 is being identified by a first core network node IDentity, ID, and the second core network node is being identified by a second core network node ID.
  • the first and the second core network node IDs are uncoordinated between the first network and the second network.
  • the first network may further comprise partitioned sets of functionalities wherein a first set of functionalities belongs to a first network slice supporting the wireless device 10.
  • the first set of functionalities is separated from another set of functionalities out of a total set of functionalities in the first network.
  • the core network node may further comprise partitioned sets of functionalities wherein a first set of functionalities belongs to the first network slice.
  • the core network node 19 initiates a connection establishment for the wireless device 10 by transmitting a paging request to the RAN node 12.
  • the paging request comprises an indication of a network identity for the first network associated with the core network node 19, the core network node ID and a wireless device identity of the wireless device 10 which is being paged by the core network node.
  • the paging request may further indicate the first network slice paging the wireless device 10. This indication indicates which network slice of the core network node is paging the wireless device.
  • the paging request may be transmitted to the RAN node 12 over the S1 interface.
  • the MMEC range comprised in the S-TMSI may be divided into two parts.
  • a first part may be used for legacy wireless devices, wherein the MMEC in this first part of the range is coordinated between participating networks, such as PLMNs in the RAN network.
  • a second part of the MMEC range is used by new wireless device types, which may be paged according to the methods above, where a coordination of MMEC is not required between participating networks.
  • the core network node 19 may receive an initial setup message for the wireless device 10 from the RAN node 12.
  • the initial setup message may comprise a wireless device identity of the wireless device 10 which is being paged and an indication of the network slice paging the wireless device 10.
  • This action 1202 is similar to the action 1006 described above in relation to Fig. 10.
  • the core network node 19 may identify a specific wireless device instance based on the received wireless device identity and the received network slice indication.
  • This action 1203 is similar to the action 1007 described above in relation to Fig. 10.
  • the communication network 1 comprises a first network and a second network.
  • the first network is associated with a first core network node 19 and the second network is associated with a second core network node 20.
  • the first and the second networks are further associated to the RAN node 12.
  • the first network may further comprise partitioned sets of functionalities, wherein a first set of functionalities belongs to a first network slice supporting the wireless device 10.
  • the first set of functionalities is separated from another set of functionalities out of a total set of functionalities in the first network.
  • the wireless device 10 may further comprise partitioned sets of functionalities.
  • a first set of functionalities may belong to the first network slice supporting the wireless device 10 and a second set of functionalities may belong to a second network slice supporting the wireless device 10, wherein the first set of functionalities is separated from the second set of functionalities in the wireless device 10.
  • Action 1301 The wireless device receives a paging request from the RAN node
  • the paging request is transmitted as a broadcasted message in the RAN, thereby every wireless device 10 in the RAN may listen to the paging request.
  • the paging request comprises an indication of a network identity, ID, of the network associated with the core network node 19 transmitting the paging request, a core network node ID identifying the first core network node 19 and the wireless device identity of the wireless device 10. This allows the wireless device 10 to identify the network and the core network node 19 in the network which has transmitted the paging request.
  • the paging request may further indicate the first network slice paging the wireless device 10.
  • This action 1301 is similar to the action 1002 described above in relation to Fig. 10.
  • the wireless device 10 may determine that the wireless device is the intended receiver of the paging message based on the received network ID of the network associated with the core network node 19 transmitting the paging request, a core network node ID identifying the first core network node 19 and the wireless device identity.
  • This action 1302 corresponds to the action 1003 described above in relation to Fig.
  • the wireless device 10 may further determine, when the wireless device and the network comprise partitioned sets of functionalities, the first set of functionalities belonging to the first network slice indicated in the paging request, based on the indication of the network slice.
  • the wireless device 10 may further forward the paging request to the determined set of functionalities in the wireless device 10.
  • the wireless device 10 transmits a response to the RAN node 12.
  • the response comprises the network ID of the first network indicated in the paging request, the core network node ID for the core network node 19 indicated in the paging request and the wireless device identity of the wireless device 10.
  • the RAN node 12 is able to determine which core network node 19 is the receiving node for the response, even if two core network nodes 19, 20 in two separate networks would have the same core network node ID.
  • the transmitting may be initiated by the determined set of functionalities belonging to the first network slice indicated in the paging request.
  • the response may further comprise an indication of the network slice paging the wireless device, which allows the receiving core network node 19 to determine which network slice, i.e. which set of functionalities in the core network node 19 the wireless device 10 shall be connected to.
  • the response may be a connection request such as a RRC Connection
  • This action 1305 is similar to the action 1004 described above in relation to Fig. 10.
  • a similar scenario as described above may occur when the wireless device initiates a service request procedure.
  • the wireless device is attached to a core network node but has entered RRC IDLE, due to e.g. inactivity.
  • the wireless device 10 will initiate a RRC Connection
  • the wireless device will send a request to the RAN node comprising an indication of the core network node which it is attached to. According to current standard the wireless device 10 will indicate the core network node by sending the S-TMSI to the RAN node 12. If the MMECs for core network nodes in different networks, such as PLMNs, hosted by the RAN are uncoordinated, the RAN node may not be able to identify the correct core network node 12.
  • the S-TMSI included in a RRCConnectionRequest message that includes a single MMEC identifying a single core network node can't be used to identify a specific slice in the core network node.
  • a second aspect of embodiments herein relate to a Service Request procedure initiated by the wireless device 10.
  • it relates to CN node selection and wireless device 10 slice instance identification performed during service request.
  • the wireless device 10 indicates a network, a core network node and a network slice for which a service request, or in general for which attachment to the network, is to be initiated. This indication may be performed as part of an RRC connection establishment procedure.
  • the wireless device may indicate the network based on a PLMN-ID, the core network node based on S-TMSI comprising MMEC, and the network slice based on a slice ID.
  • the receiving core network node may be identified by other nodes, such as the RAN node 12, based on PLMN-ID and MMEC information.
  • the service request initiated by the wireless device 10 comprises the following actions:
  • the RAN node may transmit a System Information Block 1 (SIB1) message to the wireless device 10, comprising an indication of the supported PLMN-IDs, a Tracking Area Code (TAC) and a Closed Subscriber Group (CSG) for assisting the wireless device 10 in evaluating a cell access.
  • SIB1 System Information Block 1
  • TAC Tracking Area Code
  • CSG Closed Subscriber Group
  • Action 1402 The wireless device 10 initiates the setup request by transmitting a RRC Connection Request (RRCConnReq) to the RAN node 12 comprising S-TMSI and the reason for the setup request.
  • RRCConnReq RRC Connection Request
  • the RAN node 12 may transmit a RRC Connection Setup
  • RRCConnSetup message to the wireless device 10 in response to the RRC Connection Request, which may comprise an indication of a configuration used for the connection with the wireless device 10.
  • Action 1404 The wireless device 10 transmits a RRC Connection Setup
  • RRCConnSetupComp RRCConnSetupComp
  • the RAN node 12 comprising an indication of the selected network, such as a PLMN-ID, an indication of the network slice, such as a slice ID, supporting the wireless device 10 in the selected network and the NAS-PDU.
  • the RAN node 12 may determine the receiving core network node 19 based on the selected network ID, such as the PLMN-ID, and the core network node ID, such as the MMEC, comprised in the S-TMSI received from the wireless device 10.
  • the RAN node 12 may transmits an initial setup message, such as a S1AP Initial UE message, to the determined core network node 19.
  • the initial setup message comprises the S-TMSI, the slice identification, such as the slice ID, of the network slice supporting the wireless device 10 in the selected network and the NAS-PDU.
  • the core network node 19 identifies a specific wireless device 10 slice instance based on the M-TMSI comprised in the S-TMSI and the slide ID indicated in the initial setup message received from the RAN node.
  • the communication network 1 comprises a first network and a second network, which first network is associated with a first core network node and which second network is associated with a second core network node.
  • the first and the second network are further associated to a Radio Access Network (RAN) node 12.
  • the first network further comprises partitioned sets of functionalities wherein a first set of functionalities belongs to a first network slice supporting the wireless device 10. The first set of functionalities is separated from another set of functionalities out of a total set of functionalities in the first network.
  • the wireless device 10 initiates a connection establishment by transmitting a service request to the RAN node 12.
  • the service request comprises a network ID, such as a PLMN-ID, of the first network associated with the first network slice, a core network node ID, such as a MMEC, for the core network node associated with the first network slice, a wireless device ID, such as a S-TMSI or M-TMSI, of the wireless device and an indication of the network slice, such as a slice ID, to which the wireless device is initiating the connection establishment.
  • the wireless device 10 may comprise partitioned sets of functionalities, wherein a first set of functionalities belongs to the first network slice supporting the wireless device 10 and a second set of functionalities belongs to a second network slice supporting the wireless device 10.
  • the first set of functionalities may be separated from the second set of functionalities in the wireless device 10.
  • the wireless device comprises partitioned set of functionalities the initiating of the connection establishment may be initiated, which may also be referred to as performed, by the first set of functionalities of the wireless device 10.
  • the initiating may be performed over the RRC protocol as part of a RRC
  • This action 1501 is similar to the actions 1402 and 1404 described above in relation to Fig. 14.
  • the communication network 1 comprises a first network and a second network, which RAN node 12 is associated with the first and the second network.
  • a first core network node 19 is associated with the first network and a second core network node 20 is associated with the second network.
  • the first network further comprises partitioned sets of functionalities wherein a first set of functionalities belongs to a first network slice supporting the wireless device 10, and which first set of functionalities is separated from another set of functionalities out of a total set of functionalities in the first network.
  • the RAN node 12 receives a service request or a paging response from the wireless device 10.
  • the service request comprises a network ID, such as a PLMN-ID of the first network associated with a first network slice supporting the wireless device 10, a core network node ID, such as a MMEC, for the core network node associated with the first network slice, a wireless device ID, such as a M-TMSI, of the wireless device 10 and an indication of the network slice supporting the wireless device 10, such as a slice ID.
  • This action 1601 is similar to the actions 1402 and 1404 described above in relation to Fig. 14.
  • the RAN node 12 determines a core network node based on the received network ID and the received core network node ID. Since the core network IDs are unique within each network and the RAN node 12 can determine the correct network based on the network ID the correct core network node can be determined without having to coordinate the core network node IDs between networks. Thereby an unequivocal routing of the service request can be performed.
  • This action 1602 corresponds to the action 1405 described above in relation to Fig.
  • the RAN node 12 transmits an initial setup message for the wireless device 12 to the determined core network node.
  • the initial setup message comprises an indication of a wireless device ID of the wireless device 10 and an indication of the network slice supporting the wireless device 10.
  • the core network node 19 can, when the core network node comprises partitioned sets of functionalities, determine the set of functionalities of the core network node responsible for the
  • the communication network 1 comprises a first network and a second network, which first core network node 19 is associated with the first network and wherein a second core network node 20 is associated with the second network.
  • the first core network node is being identified by a first core network node IDentity, ID, and the second core network node is being identified by a second core network node ID.
  • the first and the second core 5 network node IDs are uncoordinated between the first network and the second network.
  • the first network further comprises partitioned sets of functionalities wherein a first set of functionalities belongs to a first network slice supporting the wireless device 10, and which first set of functionalities is separated from another set of functionalities out of a total set of functionalities in the first network.
  • the core network node 19 receives an initial setup message for the wireless device 10 from the RAN node 12.
  • the initial setup message comprises a wireless device identity of the wireless device 10 performing the setup request and an indication of the network slice supporting the wireless device 10.
  • the wireless device identity may be a S-TMSI or a M-TMSI and the indication of
  • the network slice may be a slice ID.
  • the initial setup message may be received from the RAN node 12 over the S1 interface.
  • Action 1701 is similar to the action 1406 described above in relation to Fig. 14.
  • Action 1702 The core network node identifies a specific wireless device instance, 20 which identification is based on the received wireless device identity and the network slice indication.
  • the identification of the wireless device instance may comprise determining a set of functionalities belonging to the received indication of the network slice supporting the wireless device.
  • the identification of the wireless device instance may further comprise forwarding the initial setup message to the determined set of functionalities in the core network node for enabling a connection between the wireless device 10 and the set of functionalities in the core network node supporting the wireless device 10.
  • This action 1702 corresponds to the action 1407 described above in relation to Fig.
  • Fig. 18 is a block diagram depicting the RAN node 12 for enabling connection setup for the wireless device 10 in the communication network 1.
  • the communication network 1 comprises the first network and the second network, which RAN node 12 is associated with the first and the second network.
  • a first core network node 19 is
  • the first network may further comprise partitioned sets of functionalities, wherein a first set of functionalities belongs to a first network slice supporting the wireless device 10, and which first set of functionalities is separated from another set of functionalities out of a total set of functionalities in the first network.
  • the RAN node 12 may comprise a processing unit 1801 , e.g. one or more processors, configured to perform the methods described herein.
  • the RAN node 12 is configured to, e.g. by means of a receiving module 1802 and/or the processing unit 1801 being configured to, receive a paging request from a core network node 19, which paging request comprises an indication of a network identity for the network associated with the core network node 19, a core network node ID associated with the core network node 19 and a wireless device identity of the wireless device 10 which is being paged.
  • the RAN node 12 may further be configured to, e.g. by means of the receiving module 1802 and/or the processing unit 1801 being configured to, receive the paging request further comprising an indication of the first network slice supporting the wireless device 10, wherein the indication is indicating that the first network slice is paging the wireless device 10.
  • the RAN node 12 is configured to, e.g. by means of a transmitting module 1803 and/or the processing unit 1801 being configured to, transmit the paging request to the wireless device 10 associated to the wireless device ID, which paging request indicates the network ID for the network associated with the core network node 19, the core network node ID associated with the core network node 19, and the wireless device ID.
  • the RAN node may further be configured to, e.g. by means of a transmitting module 1803 and/or the processing unit 1801 being configured to, transmit the paging request as a broadcasted message in the RAN.
  • the RAN node 12 may further be configured to, e.g. by means of the receiving module 1802 and/or the processing unit 1801 being configured to, receive a response from the wireless device 10, which response comprises the network ID of the first network selected for communication with the wireless device 10, the core network node ID for the core network node 19 associated with the selected network and the wireless device ID of the wireless device 10.
  • the response may further comprise an indication of the first network slice supporting the wireless device 10.
  • the RAN node 12 may further be configured to, e.g. by means of the receiving module 1802 and/or the processing unit 1801 being configured to, receive a service request from the wireless device 10, which service request comprises the network ID of the first network selected for communication with the wireless device 10, the core network node ID for the core network node 19 associated with the selected network and the wireless device ID of the wireless device 10.
  • the RAN node 12 may further be configured to, e.g. by means of a determining module 1804 and/or the processing unit 1801 being configured to, determine a core network node 19 based on the received network ID and the received core network node ID.
  • the RAN node 12 may further be configured to, e.g. by means of the transmitting module 1803 and/or the processing unit 1801 being configured to, transmit an initial setup message for the wireless device 10 to the determined core network node 19, which initial setup message comprises the wireless device identity of the wireless device 10 transmitting the response to the paging request and/or the wireless device 10 transmitting the service request.
  • the initial setup message may further comprise an indication of the network slice supporting the wireless device 10.
  • the RAN node 12 further comprises a memory 1805.
  • the memory comprises one or more units to be used to store data on, such as network slice information, wireless device IDs, network slice and roaming policies, Slice IDs applications to perform the methods disclosed herein when being executed, and similar.
  • the methods according to the embodiments described herein for the RAN node 12 are respectively implemented by means of e.g. a computer program 1806 or a computer program product, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the RAN node 12.
  • the computer program 1806 may be stored on a computer-readable storage medium 1807, e.g. a disc or similar.
  • the computer-readable storage medium 1807, having stored thereon the computer program may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the RAN node 12.
  • the computer-readable storage medium may be a non-transitory computer-readable storage medium.
  • Fig. 19 is a block diagram depicting the core network node 19 for enabling connection setup for the wireless device 10 in the communication network 1.
  • the communication network 1 comprises a first network and a second network, which first core network node 19 is associated with the first network and wherein a second core network node 20 is associated with the second network.
  • the first core network node 19 is being identified by a first core network node ID and the second core network node 20 is being identified by a second core network node ID, wherein the first and the second core network node IDs are uncoordinated between the first network and the second network.
  • the first network may further comprise partitioned sets of functionalities wherein a first set 5 of functionalities belongs to a first network slice supporting the wireless device 10, and which first set of functionalities is separated from another set of functionalities out of a total set of functionalities in the first network.
  • the core network node 19 may comprise a processing unit 1901 , e.g. one or more processors, configured to perform the methods described herein.
  • the core network node 19 is configured to, e.g. by means of an initiating module
  • a transmitting module 1903 and/or the processing unit 1901 being configured to, initiate a connection establishment for the wireless device 10 by
  • paging request comprises an indication of a network identity for the first network associated with the core network node
  • the paging request may further indicate the first network slice supporting the wireless device 10.
  • the core network node 19 may further be configured to, e.g. by means of an receiving module 1904 and/or the processing unit 1901 being configured to, receive an
  • initial setup message for the wireless device 10 from the RAN node 12 which initial setup message comprises a wireless device identity of the wireless device 10 which is being paged and an indication of the network slice supporting the wireless device 10.
  • the core network node 19 may further be configured to, e.g. by means of an identification module 1905 and/or the processing unit 1901 being configured to, identify
  • the core network node 19 may further be configured to, e.g. by means of a determining module 1906 and/or the identification module 1904 and/or the processing unit 1901 being configured to, determining a set of functionalities in the core network node
  • the core network node 19 may further be configured to, e.g. by means of a forwarding module 1907 and/or the identification module 1904 and/or the processing unit 1901 being configured to, forward the initial setup message to the determined set of functionalities.
  • the core network node 19 further comprises a memory 1908.
  • the memory comprises one or more units to be used to store data on, such as network slice
  • the methods according to the embodiments described herein for the core network node 19 are respectively implemented by means of e.g. a computer program 1909 or a computer program product, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the core network node 19.
  • the computer program 1909 may be stored on a computer-readable storage medium 1910, e.g. a disc or similar.
  • the computer-readable storage medium 1910, having stored thereon the computer program may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the core network node 19.
  • the computer-readable storage medium may be a non-transitory computer-readable storage medium.
  • Fig. 20 is a block diagram depicting the wireless device 10 for establishing a connection to the communication network 1.
  • the communication network comprises a first network and a second network, which first network is associated with a first core network node 19 and which second network is associated with a second core network node 20.
  • the first and the second networks are further associated to a RAN node 12.
  • the first network may further comprise partitioned sets of functionalities wherein a first set of functionalities belongs to a first network slice supporting the wireless device 10, and which first set of functionalities is separated from another set of functionalities out of a total set of functionalities in the first network.
  • the wireless device 10 may further comprise partitioned sets of functionalities wherein a first set of functionalities belongs to the first network slice supporting the wireless device 10 and a second set of functionalities belongs to a second network slice supporting the wireless device 10. The first set of functionalities is separated from the second set of functionalities in the wireless device 10.
  • the wireless device 10 may comprise a processing unit 2001 , e.g. one or more processors, configured to perform the methods described herein.
  • the wireless device 10 is configured to, e.g. by means of a receiving module 2002 and/or the processing unit 2001 being configured to, receive a paging request from the RAN node 12, which paging request comprises an indication of a network ID of the network associated with the core network node 19, a core network node ID identifying the first core network node 19 and a wireless device identity of the wireless device 10.
  • the paging request may further indicate the first network slice supporting the wireless device 10.
  • the wireless device 10 is configured to, e.g. by means of a transmitting module 5 2003 and/or the processing unit 2001 being configured to, transmit a response to the RAN node 12, which response comprises the network ID of the first network indicated in the paging request, the core network node ID for the core network node 19 indicated in the paging request and the wireless device identity of the wireless device 10.
  • the wireless device 10 may further be configured to, e.g. by means of the transmitting module 2003
  • the processing unit 2001 being configured to, transmit a service request to the RAN node 12, which service request comprises the network ID of the first network indicated in the paging request, the core network node ID for the core network node 19 indicated in the paging request and the wireless device identity of the wireless device 10.
  • the response and/or the service request may further comprise an indication of the
  • the wireless device 10 may further be configured to, e.g. by means of a determining module 2004 and/or the processing unit 2001 being configured to, determine that the wireless device 10 is the intended receiver of the paging message based on the received network ID of the network associated with the core network node
  • the wireless device 10 may further be configured to, e.g. by means of a determining module 2004 and/or the processing unit 2001 being configured to, determining a set of functionalities, in the wireless device 10, belonging to the first
  • the wireless device 10 may further be configured to, e.g. by means of a forwarding module 2005 and/or the processing unit 2001 being configured to, forward the paging request to the determined set of functionalities.
  • the wireless device 10 further comprises a memory 2006.
  • the memory
  • Network slice information comprises one or more units to be used to store data on, such as network slice information, wireless device IDs, network slice and roaming policies, Slice IDs
  • 35 device 10 are respectively implemented by means of e.g. a computer program 2007 or a computer program product, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the wireless device 10.
  • the computer program 2007 may be stored on a computer-readable storage medium 2008, e.g. a disc or similar.
  • the computer-readable storage medium 2008 having stored thereon the computer program, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the wireless device 10.
  • the computer-readable storage medium may be a non-transitory computer-readable storage medium.
  • Embodiments herein relate to a network with network slices i.e. a (core or RAN or both) network with partitioned sets of functionalities wherein the core network node 19, the wireless device 10 and/or the RAN node 12 may support the first set of functionalities out of the total set of functionalities in the network of the communication network.
  • the first set of functionalities belongs to the first network slice of the network, and is separated from another set of functionalities out of the total set of functionalities in the network.
  • ASIC application-specific integrated circuit
  • Several of the functions may be implemented on a processor shared with other functional components of a network node, for example.
  • processors or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and/or program or application data, and non-volatile memory.
  • DSP digital signal processor
  • ROM read-only memory
  • RAM random-access memory
  • non-volatile memory non-volatile memory
  • Other hardware conventional and/or custom, may also be included. Designers of network nodes will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

Landscapes

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

Abstract

Conformément à des modes de réalisation, la présente invention concerne un procédé réalisé par un nœud de réseau d'accès radio (RAN) (12), pour permettre une configuration de connexion pour un dispositif sans fil (10) dans un réseau de communication (1). Le réseau de communication (1) comprend un premier réseau et un second réseau. Le nœud de RAN (12) est associé au premier et au second réseau. Un premier nœud de réseau central (19) est associé au premier réseau et un second nœud de réseau central (20) est associé au second réseau. Le nœud de RAN reçoit une requête de radiomessagerie à partir d'un nœud de réseau central (19), laquelle requête de radiomessagerie comprend une indication d'une identité de réseau pour le réseau associé au nœud de réseau central, une identité (ID) de nœud de réseau central associée au nœud de réseau central (19) et une identité de dispositif sans fil du dispositif sans fil (10) qui est recherché. Le nœud de RAN transmet la requête de radiomessagerie au dispositif sans fil (10) associé à l'identité de dispositif sans fil, laquelle requête de radiomessagerie indique l'identité de réseau pour le réseau associé au nœud de réseau central (19), l'ID de nœud de réseau central associée au nœud de réseau central (19), et l'identité de dispositif sans fil.
PCT/SE2016/050106 2016-02-05 2016-02-12 Nœuds de réseau et procédés réalisés dans ces derniers WO2017135859A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662291563P 2016-02-05 2016-02-05
US62/291,563 2016-02-05

Publications (1)

Publication Number Publication Date
WO2017135859A1 true WO2017135859A1 (fr) 2017-08-10

Family

ID=55436141

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2016/050106 WO2017135859A1 (fr) 2016-02-05 2016-02-12 Nœuds de réseau et procédés réalisés dans ces derniers

Country Status (1)

Country Link
WO (1) WO2017135859A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2569989A (en) * 2018-01-08 2019-07-10 Tcl Communication Ltd Paging in cellular communication systems
EP3503619A4 (fr) * 2016-09-30 2019-10-16 Huawei Technologies Co., Ltd. Procédé et dispositif de reconnaissance de message
CN111034273A (zh) * 2017-08-14 2020-04-17 Idac控股公司 从非3gpp接入网络请求网络切片能力的终端
CN112514446A (zh) * 2018-08-10 2021-03-16 索尼公司 用于处理网络切片过载的方法
JP2021511695A (ja) * 2018-01-12 2021-05-06 パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカＰａｎａｓｏｎｉｃ Ｉｎｔｅｌｌｅｃｔｕａｌ Ｐｒｏｐｅｒｔｙ Ｃｏｒｐｏｒａｔｉｏｎ ｏｆ Ａｍｅｒｉｃａ ページング手順のためのユーザ機器、基地局、および方法
WO2022237671A1 (fr) * 2021-05-10 2022-11-17 华为技术有限公司 Procédé et appareil de radiomessagerie de groupe

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070259675A1 (en) * 2006-05-02 2007-11-08 Ipwireless, Inc. Network-initiated communication establishment in a cellular system
WO2012050842A1 (fr) * 2010-09-28 2012-04-19 Research In Motion Limited Gestion de connexion de réseau résidentiel/d'entreprise et scénarios de repli à commutation de circuits (csfb)

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070259675A1 (en) * 2006-05-02 2007-11-08 Ipwireless, Inc. Network-initiated communication establishment in a cellular system
WO2012050842A1 (fr) * 2010-09-28 2012-04-19 Research In Motion Limited Gestion de connexion de réseau résidentiel/d'entreprise et scénarios de repli à commutation de circuits (csfb)

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ZTE CORPORATION ET AL: "update the network slicing use case in SMARTER", vol. SA WG1, no. Belgrade, Serbia; 20150817 - 20150821, 24 August 2015 (2015-08-24), XP051033547, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG1_Serv/TSGS1_71_Belgrade/Docs/> [retrieved on 20150824] *

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3503619A4 (fr) * 2016-09-30 2019-10-16 Huawei Technologies Co., Ltd. Procédé et dispositif de reconnaissance de message
US11895617B2 (en) 2016-09-30 2024-02-06 Huawei Technologies Co., Ltd. Message identification method and apparatus
CN111034273A (zh) * 2017-08-14 2020-04-17 Idac控股公司 从非3gpp接入网络请求网络切片能力的终端
CN111034273B (zh) * 2017-08-14 2024-03-29 交互数字专利控股公司 从非3gpp接入网络请求网络切片能力的终端
GB2569989A (en) * 2018-01-08 2019-07-10 Tcl Communication Ltd Paging in cellular communication systems
GB2569989B (en) * 2018-01-08 2020-01-15 Tcl Communication Ltd Paging in cellular communication systems
JP2021511695A (ja) * 2018-01-12 2021-05-06 パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカＰａｎａｓｏｎｉｃ Ｉｎｔｅｌｌｅｃｔｕａｌ Ｐｒｏｐｅｒｔｙ Ｃｏｒｐｏｒａｔｉｏｎ ｏｆ Ａｍｅｒｉｃａ ページング手順のためのユーザ機器、基地局、および方法
JP7274483B2 (ja) 2018-01-12 2023-05-16 パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカ ページング手順のためのユーザ機器、基地局、および方法
CN112514446A (zh) * 2018-08-10 2021-03-16 索尼公司 用于处理网络切片过载的方法
CN112514446B (zh) * 2018-08-10 2024-08-06 索尼公司 用于处理网络切片过载的方法
WO2022237671A1 (fr) * 2021-05-10 2022-11-17 华为技术有限公司 Procédé et appareil de radiomessagerie de groupe

Similar Documents

Publication Publication Date Title
EP3412048B1 (fr) Noeuds de réseau radio et procédés associés permettant une communication dans un réseau de communication sans fil
US10893455B2 (en) Handover in a wireless communication network with network slices
EP3417648B1 (fr) Noeuds de réseau et procédés exécutés dans ceux-ci pour permettre une communication dans un réseau de communication
US10506552B2 (en) Core network node, radio network node, wireless device and methods performed therein
US11070967B2 (en) Network nodes and methods performed therein for enabling communication in a communication network
EP3403464B1 (fr) Dispositif de communication émetteur, dispositif de communication récepteur, procédés réalisés par ces dispositifs dans le contexte de tranches de réseau et programme informatique
EP3417657B1 (fr) Noeud de réseau radio, dispositif sans fil et procédés réalisés dans ces derniers
US10820241B2 (en) Network nodes and methods performed therein for enabling communication in a communication network
US10979998B2 (en) Radio network node, communication device and methods performed therein
US11026165B2 (en) Radio network node, network node, database, configuration control node, and methods performed thereby
US10863560B2 (en) First network node, receiving network node and methods performed therein
WO2017086848A1 (fr) Nœud de réseau radioélectrique, nœud de réseau et procédés correspondants
WO2017135859A1 (fr) Nœuds de réseau et procédés réalisés dans ces derniers
US11006309B2 (en) Network node, radio network node and methods performed therein

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

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

Country of ref document: EP

Kind code of ref document: A1