EP3412048B1 - Funknetzwerkknoten und verfahren zur ermöglichung der kommunikation in einem netzwerk - Google Patents

Funknetzwerkknoten und verfahren zur ermöglichung der kommunikation in einem netzwerk Download PDF

Info

Publication number
EP3412048B1
EP3412048B1 EP16706447.6A EP16706447A EP3412048B1 EP 3412048 B1 EP3412048 B1 EP 3412048B1 EP 16706447 A EP16706447 A EP 16706447A EP 3412048 B1 EP3412048 B1 EP 3412048B1
Authority
EP
European Patent Office
Prior art keywords
network
wireless device
node
identity
slice
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP16706447.6A
Other languages
English (en)
French (fr)
Other versions
EP3412048A1 (de
Inventor
Oscar Zee
Paul Schliwa-Bertling
Angelo Centonza
Jari Vikberg
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP3412048A1 publication Critical patent/EP3412048A1/de
Application granted granted Critical
Publication of EP3412048B1 publication Critical patent/EP3412048B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/06—Registration at serving network Location Register, VLR or user mobility server
    • 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
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H04W76/16—Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer

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.
  • the Evolved Packet System also called a Fourth Generation (4G) network
  • EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long Term Evolution (LTE) radio access network
  • EPC Evolved Packet Core
  • SAE System Architecture Evolution
  • 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.
  • E-UTRAN/LTE the functions of an RNC are distributed between the radio network nodes, e.g. eNodeBs in LTE, and the core network.
  • 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 Itf-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:
  • the purpose of the S1 Setup procedure is to exchange application level data needed for the radio network node, such as an eNB, 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 connectivity and it has been configured with at least one Tracking Area Indicator (TAI).
  • TAI Tracking Area Indicator
  • 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 RAN operator When provisioning the eNB, the RAN operator will provide a Tracking Area Identity (TAI) for each cell within the eNB.
  • the TAI consists of a network ID, such as a Public Land Mobile Network IDentifier (PLMN-ID) and a Tracking Area Code (TAC).
  • PLMN-ID Public Land Mobile Network IDentifier
  • TAC Tracking Area Code
  • the Tracking Area is a logical concept of an area covered by a core network node, such as the MME.
  • the TAC is the same for all PLMNs, i.e. that the TAIs in one cell share the same TAC.
  • the eNB During initialization of an eNB, the eNB will make a query to a Domain Name System (DNS) on all its TAI:s. For query on each TAI, the DNS will return one or several core network node, such as MME, IP addresses. After the query procedure, the eNB will setup a Stream Control Transmission Protocol (SCTP) connection towards each MME IP address received from the DNS.
  • DNS Domain Name System
  • the eNB For each SCTP connection, which corresponds to a MME instance, the eNB will initiate a S1 setup procedure by sending the S1 SETUP REQUEST message, with a list of TACs with the corresponding Broadcast PLMN (B-PLMN) lists as parameters.
  • B-PLMN Broadcast PLMN
  • the MME instance will respond with a S1 SETUP RESPONSE message with a list of the serving PLMN-IDs, which may also be referred to as S-PLMN IDs, a list of Served MME Group IDs, and a list of Served MME Codes (MMEC) as parameters.
  • S-PLMN IDs serving PLMN-IDs
  • MMEC Served MME Codes
  • the UE may request service to the network by performing an initial attach procedure.
  • the beginning of the initial attach procedure, until initial UE message is transmitted to the correct MME is shown in Figure 7 .
  • the UE When the UE is switched on, it selects and attempts to perform a Location Registration, which may also be referred to as an Attach procedure on the registered PLMN, if the UE has already been attached to the PLMN. If the UE has been out of coverage recovery from lack of coverage, the UE selects the registered PLMN, if a registered PLMN exists, and, if necessary attempts to perform a Location Registration.
  • a Location Registration which may also be referred to as an Attach procedure on the registered PLMN, if the UE has already been attached to the PLMN. If the UE has been out of coverage recovery from lack of coverage, the UE selects the registered PLMN, if a registered PLMN exists, and, if necessary attempts to perform a Location Registration.
  • the UE In case the UE has no registered PLMN, or if registration is not possible due to the PLMN being unavailable or due to a registration failure, the UE follows either manual network selection, or automatic network selection. In Automatic Network Selection, the UE selects and attempts registration on other PLMNs, if available and allowable, in all of its bands of operation in the following order:
  • the eNB is transmitting SystemlnformationBlock1 (SIB1) on each cell, for example with PLMN-IDs (up to 6), TAC, Cell Identity and Closed Subscriber Group (CSG) related information.
  • SIB1 SystemlnformationBlock1
  • the UE Once the UE has selected a PLMN for Location Registration, it initiates a RRC connection Establishment Procedure. In the end of the procedure, the UE sends a RRCConnectionSetupComplete message to the eNB, including the PLMN-ID it has selected to attach to. The eNB will then use the PLMN-ID provided by the UE for selecting the corresponding MME, according to the information received during the S1 setup procedure from different MMEs. The eNB further forwards the initial NAS message, which in this case is an Attach Request, in a S1AP Initial UE Message to the MME. The initial NAS message is received from the UE piggybacked in the RRCConnectionSetupComplete message.
  • 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:
  • 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
  • the MMEI is constructed from an MME Group ID (MMEGI) and an MME Code (MMEC).
  • 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:
  • 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. Furthermore, 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
  • VNF virtualized network functions
  • NFVI Network Functions Virtualization Infrastructure
  • vEPC elements can benefit from more agile deployment and scalability.
  • virtual resource monitoring and orchestration along with service awareness, are essential for implementing elasticity effectively.
  • 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).
  • vMME Virtualized MME
  • vPCRF Virtualized PCRF
  • vSGW Virtualized SGW
  • vPDN-GW Virtualized PDN-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. performance, security, robustness, and/or complexity.
  • 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. 9 .
  • 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.
  • 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:
  • Fig. 10 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 MME.
  • the network slice may be provided by Visited PLMN (VPLMN) totally in local breakout way, or joint provided by Home PLMN (HPLMN) and VPLMN in a home routed way, or even it could be provided by HPLMN totally and a CN of VPLMN is totally bypassed.
  • VPLMN Visited PLMN
  • HPLMN Home PLMN
  • CN CN of VPLMN
  • HPLMN the network slice types provided by HPLMN and those provided by VPLMN may be different due to different business strategy.
  • the specific network slice to be used for the roaming wireless device needs the involvement of both HPLMN and VPLMN, and it is more complex compared to a non-roaming situation.
  • NFV cloud based network service by NFV initiative at ETSI.
  • NFV will transform the way that networks are built and operated by leveraging standard virtualization technology and consolidating network equipment types onto "industry standard" servers.
  • the NFV technology will make it more flexible and efficient to provide and operate the virtual mobile network service, as well as value added service with low CAPEX and Operating Expenditures (OPEX) and reduced time to market.
  • OPEX Operating Expenditures
  • a user is roaming to a new area, in case the wireless device doesn't know the available network slice type in an area, it may select a specific network slice type/ID based on its preference. While, when the specific network slice is terminated, or out of service or overloaded, once the wireless device sets up a network connection and indicates the specific network slice type to an access network, it is highly possible that wireless device would be rejected, which would result in a negative user experience and performance of the communication network and additional signaling overhead may be required.
  • a RAN in a sliced network may be implemented with the following pre-requisites:
  • the aim of the network slicing is to provide a simple tool for cellular operators to introduce new services and features to different industries. It is therefore desired that the deployment of slices should be easy and with minimum coordination between RAN operator, CN operators (PLMNs) and other participating parties such as e.g. network slice operators.
  • PLMNs CN operators
  • An example of objects for which high coordination is currently required between networks is e.g. MME addressing and slice identification.
  • 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.
  • the object is achieved by a method, performed by 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 first network is a home network of the wireless device and the second network is a network which is visited by the wireless device.
  • the first and the second network each comprise partitioned sets of functionalities, which sets of functionalities each belong to a network slice of the network, wherein a first set of functionalities in the first network belongs to a first network slice supporting the wireless device.
  • 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 is roaming from the first network to the second network.
  • the RAN node receives a first network identity for the home network, an identity of the first network slice supporting the wireless device in the home network and a second network identity for the second network, from the wireless device.
  • the RAN node retrieves an identity of a second network slice capable of supporting the wireless device in the second network, based on the received first network identity, the first network slice identity and the second network identity.
  • the RAN node determines a second core network node based on the second network identity and the retrieved second network slice identity.
  • the RAN node transmits an initial setup message for the wireless device, which initial setup message comprises an indication of the second network identity and the identity of the second network slice capable of supporting the wireless device, to the determined second core network node.
  • the object is achieved by a method performed by a wireless device, for establishing a connection to a second network in a communication network.
  • the communication network comprises a first network and the second network.
  • the first network is a home network of the wireless device and the second network is a network which is visited by the wireless device.
  • the first and the second network each comprise partitioned sets of functionalities, which sets of functionalities each belong to a network slice of the network.
  • a first set of functionalities in the first network belongs to a first network slice supporting the wireless device in the first network.
  • 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 transmits a first network identity for the home network of the wireless device, an identity of the first network slice supporting the wireless device in the home network and a second network identity for the visited second network, to the RAN node.
  • the wireless device 10 is roaming from the first network to the second network.
  • the object is achieved by a method performed by a core network node, for enabling connection setup for a wireless device in a communication network.
  • the communication network comprises at least a first network and a second network.
  • the first and the second network each comprise partitioned sets of functionalities, which sets of functionalities each belong to a network slice of the network, and which sets of functionalities are separated from each other.
  • the core network node receives a setup request message for establishing communication between the RAN node and the core network node, from the RAN node.
  • the core network node transmits a setup response message comprising an indication of one or more networks served by the core network node and the network slices supported by each network served by the core network node, to the RAN node.
  • 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 first network is a home network of the wireless device and the second network is a network which is visited by the wireless device.
  • the first and the second network each comprise partitioned sets of functionalities, which sets of functionalities each belong to a network slice of the network.
  • a first set of functionalities in the first network belongs to a first network slice supporting the wireless device.
  • 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 is roaming from the first network to the second network.
  • the RAN node is configured to receive a first network identity for the home network, an identity of the first network slice supporting the wireless device in the home network and a second network identity for the second network from the wireless device.
  • the RAN node is configured to retrieve an identity of a second network slice capable of supporting the wireless device in the second network, based on the received first network identity, the first network slice identity and the second network identity.
  • the RAN node is further configured to determine a core network node based on the second network identity and the retrieved second network slice identity.
  • the RAN node is further configured to transmit an initial setup message for the wireless device, which initial setup message comprises an indication of the second network identity and the identity of the second network slice capable of supporting the wireless device, to the determined core network node.
  • the object is achieved by providing a core network node, for enabling connection setup for a wireless device in a communication network.
  • the communication network comprises at least a first network and a second network, wherein the first and the second network each comprise partitioned sets of functionalities.
  • the sets of functionalities each belong to a network slice of the network and the sets of functionalities are separated from each other.
  • the core network node is configured to receive a setup request message for establishing communication between the RAN node and the core network node, from the RAN node.
  • the core network node is further configured to transmit a setup response message comprising an indication of one or more networks served by the core network node and the network slices supported by each network served by the core network node, to the RAN node.
  • the object is achieved by providing a wireless device, for establishing a connection to a second network in a communication network.
  • the communication network comprises a first network and the second network.
  • the first network is a home network of the wireless device and the second network is a network which is visited by the wireless device.
  • the first and the second network each comprise partitioned sets of functionalities, which sets of functionalities each belong to a network slice of the network.
  • a first set of functionalities in the first network belongs to a first network slice supporting the wireless device in the first network.
  • 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 is configured to transmit a first network identity for the home network of the wireless device, an identity of the first network slice supporting the wireless device in the home network and a second network identity for the visited second network, to the RAN node.
  • 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.
  • Embodiments herein introduce an efficient manner of coordinating different identifiers between PLMNs when multiple PLMNs with slices are hosted in the same RAN.
  • a network identity such as a PLMN-ID
  • the slice IDs do not have to be unique across different networks, such as e.g. PLMNs, which allows a reuse of slice ID values.
  • Slice IDs do not need to be coordinated across different PLMNs cross-PLMN configurations can be minimized, thereby reducing the costs and the work load of running such networks.
  • the embodiments also introduce an efficient way of mapping home network IDs and slices in the home network to slices in a visited network.
  • Embodiments herein relate to communication networks in general.
  • Fig. 11 is a schematic overview depicting a communication network 1.
  • the communication network 1 comprises RANs and CNs.
  • 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 communications/Enhanced Data rate for GSM Evolution (GSM/EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.
  • LTE Long Term Evolution
  • WCDMA Wideband Code Division Multiple Access
  • GSM/EDGE Global System for Mobile communications/Enhanced Data rate for GSM Evolution
  • WiMax Worldwide Interoperability for Microwave Access
  • UMB Ultra Mobile Broadband
  • Embodiments herein relate to recent technology trends that are of particular interest in a 5G context, however, embodiments are applicable also in further development of the existing communication systems such as e.
  • 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 e.g. RAN
  • wireless device is a non-limiting term which means any terminal, wireless communication terminal, user equipment, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a base station communicating within a cell.
  • MTC Machine Type Communication
  • D2D Device to Device
  • the communication network 1 comprises a first radio network node 12 providing radio coverage over a geographical area, a first service area 11, of a first radio access technology (RAT), such as LTE, UMTS, Wi-Fi or similar.
  • the first 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 STA), an access controller, a base station, e.g.
  • the first radio network node 12 is comprised in a first radio access network (RAN1) of a first network.
  • RAN1 first radio access network
  • the first network or home network comprises a first core network (CN1) also denoted home core network of the wireless device 10.
  • 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.
  • the RAN1 and CN1 comprise 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.
  • the communication network 1 comprises a second network or visited network comprising a second core network (CN2), also denoted as visited core network, and a second RAN, RAN2. Also this second network may be network sliced e.g. as the first network or differently.
  • the communication network 1 further comprises a second radio network node 16 providing radio coverage over a geographical area, a second service area 17, of a second radio access technology (RAT), such as LTE, UMTS, Wi-Fi or similar.
  • the second radio network node 16 may be a radio access network node such as radio network controller or an access point such as a WLAN access point or an Access Point Station (AP STA), 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 second radio network node 16 depending e.g. on the second radio access technology and terminology used.
  • the second radio network node 16 is comprised in the second radio access network, RAN2.
  • the first and second RAT may be the same or different RATs.
  • the second network comprise 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 second radio network node 16.
  • the wireless device 10 moves into the second service area 17 of the second radio network node 16.
  • the wireless device initiates a connection establishment with a second network node 18, e.g. a RAN node associated with the second network, by performing a RRC Connection procedure.
  • the Connection procedure comprises sending the selected PLMN-ID for the network which the wireless device 10 want to establish a connection to. If slicing is introduced the wireless device may further provide a slice ID of the slice it wishes to connect to.
  • a roaming scenario such as e.g. when the wireless device is moving from a home network comprising the first network node 15 to a visited network comprising the second network nodes 18, the wireless device 10 will provide the slice ID from the home network upon connection establishment.
  • the second network will however only be able to route the request to the correct CN node if the slice IDs are correlated between the home network and the visited network.
  • this will require a lot of cross-PLMN configurations which are very time consuming and cost intensive.
  • embodiments herein provide an effective network slice selection for roaming wireless devices in the communication network that is simple and feasible from an implementation perspective, e.g. only is an enhancement on existing interfaces and network functions. This results in that less wireless devices are rejected during roaming and more are being served in the second network as served in the first network improving the performance of the communication network 1. Furthermore, the cross-PLMN configurations can be reduced which reduces the cost and effort of running the communication network 1. Hence, embodiments herein provide an effective manner to support network slice selection for roaming wireless devices.
  • Embodiments herein relate to minimizing the coordination of different identifiers, such as e.g. slice ID, between PLMNs when multiple PLMNs with slices are hosted in the same RAN.
  • identifiers such as e.g. slice ID
  • the first aspect relates to introduction of a data structure in S1 SETUP procedure related messages, for example in S1 SETUP RESPONSE, where a slice ID can be defined individually between participating PLMNs in RAN. This is a pre-requisite for independency of slice ID between participating PLMNs in RAN.
  • the second aspect relates to introduction of a "slice lookup database" node, where a mapping between slice IDs for H-PLMN and V-PLMNs is introduced.
  • MMEC coordination between participating PLMNs in RAN is still needed. It can be solved by dividing the MMEC value range into two parts. The first part is used by MMEs which need to handle legacy UEs, where MMEC coordination is needed. Such MMEs can also serve non-legacy wireless devices. The second part is used by MMEs which only handle newer UEs where MMEC coordination between PLMN can be omitted.
  • MMECs do not need to be unique across different PLMNs allows the reuse of MMEC values, which implies that the MMEs in a network can use an overall number of MMECs higher than the current limit of 256. Also, the fact that MMECs and Slice IDs do not need to be coordinated across different PLMNs allows to minimize cross-PLMN configurations and therefore to save costs of running such networks. This minimized coordination will be very beneficial for deployment of slicing in RAN once it is introduced.
  • Fig. 12 shows an enhanced S1 Setup procedure for PLMN-specific slices according to a first aspect of embodiments herein.
  • the enhanced S1 Setup procedure comprises the following actions:
  • the RAN node 12 supporting slicing is informed by the CN nodes 19, 20 connected to the RAN node 12 about the slices supported by each CN node 19, 20 and their identifiers, such as the slice ID.
  • the RAN node receives a list of Slice IDs from the CN node 19, 20 for each PLMN supported by the CN node 19, 20.
  • the eNB would receive in a list of PLMN IDs and for each PLMN ID in the list it would receive a list of Slice IDs supported by the PLMN.
  • the list of PLMN IDs and the list of Slice IDs corresponding to each PLMN ID may be transmitted from the CN node 19, 20 to the eNB in the S1 SETUP RESPONSE.
  • the eNB will be able to uniquely identify said a specific Slice amongst the Slices served by the selected PLMN ID.
  • a Slice ID only needs to be unique within its hosting PLMN, it is not necessary to coordinate Slice IDs across PLMNs but only within each PLMN.
  • two Slice IDs hosted by different PLMNs may have the same slice ID.
  • the eNB will be able to identify to which slice procedures are referring to, based on the PLMN ID and the Slice ID since the Slice ID would be unique within its own PLMN ID. Since no coordination of Slice IDs is necessary, the number of cross-PLMN configurations are reduced which saves costs and effort of running the networks.
  • the S1 SETUP RESPONSE may include an overall list of Slice IDs supported by the connected MME without an explicit association to PLMN IDs.
  • this solution implies that the eNB would need to acquire knowledge of the Slice ID to PLMN ID association, for example by an Operations and Management (OAM) configuration.
  • OAM Operations and Management
  • the wireless device 10 When the wireless device 10 is located in its home network, such as the H-PLMN, and the H-PLMN comprises a set of functionalities belonging to a network slice, the wireless device may request service of the slice in the initial attach procedure by providing a slice ID of the H-PLMN during the RRC setup procedure, e.g. in the RRCConnectionSetupComplete message.
  • a visited network such as a V-PLMN
  • the wireless device 10 will send the slice ID it is aware of in the RRCConnectionSetupComplete message.
  • this slice ID belongs to the wireless devices 10 H-PLMN and may not correspond to a slice ID in the V-PLMN capable of supporting the wireless device.
  • it is required to coordinate the slice IDs between the H-PLMN and the V-PLMN in order to give each network slice a unique identifier. Otherwise the network slice will not be selected correctly in the V-PLMN.
  • slice ID is now required to be coordinated between H-PLMN, V-PLMNs and all PLMNs handled in the core network node 19, 20, such as an MME. It is obvious that this will require a lot of cross-PLMN configurations which, as already has been discussed, is very time consuming and cost intensive.
  • a slice lookup DataBase (DB) 130 in which a mapping between slice IDs for the H-PLMN and the V-PLMNs is performed, is introduced.
  • This DB 130 may e.g. be accessed from the eNB/RAN node 12 during the initial attach procedure to translate the combination of a HPLMN ID and a H-PLMN slice ID to a V-PLMN slice ID for core network node selection based on V-PLMN selected by the wireless device 10.
  • Figure 13 shows an example of this case.
  • the result of this lookup may then be transmitted to the wireless device 10 for a later procedure, such as e.g. paging and/or service request procedures.
  • the RAN node 12 may not be necessary for the RAN node 12 to perform a lookup in the database every time the wireless device sends a service request in the visited network it has once been attached to.
  • the service request message is routed to the correct CN node based on the selected V-PLMN ID of the visited network and the V-slice ID retrieved from the DB by the RAN node.
  • the database may be located in a V-PLMN domain, since the responsibility for this database may be at the operator managing the V-PLMN, who can update the database continuously once agreements with partnering PLMNs is made without any other dependencies.
  • an operator of the slice supporting the wireless device in the H-PLMN which may also be referred to as the H-Slice, may enter an agreement with an operator of one of the network slices in the V-PLMN.
  • the operator managing the V-PLMN may enter into the lookup table in the database that the H-Slice in the H-PLMN has an agreement with, i.e. is supported by, a certain Slice ID in the V-PLMN.
  • the service request procedure according to embodiments described herein is shown in Fig. 14 , where the identifiers introduced in the embodiments herein are indicated with bold font.
  • the Service Request initiated by the wireless device 10 according to the embodiments herein comprises the following actions:
  • the communication network 1 comprises a first network and a second network.
  • the first network is a home network of the wireless device 10 and the second network is a network which is visited by the wireless device 10.
  • the first and the second network each comprise partitioned sets of functionalities, which sets of functionalities each belong to a network slice of the network.
  • a first set of functionalities in the first network belongs to a first network slice supporting the wireless device 10, 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 is roaming from the first network to the second network.
  • the RAN node 12 may further be associated with a plurality of networks, wherein each network supports a plurality of network slices.
  • the RAN node 12 may, when the RAN node is associated to a plurality of networks and each network supports a plurality of network slices, transmit a setup request message for establishing communication between the RAN node 12 and the core network node 19, 20, to a core network node 19, 20.
  • This action 1401 is similar to the action 1205 described above in relation to Fig. 12 .
  • the RAN node 12 may, when the RAN node is associated to a plurality of networks and each network supports a plurality of network slices, receive a setup response message comprising an indication of one or more networks served by the core network node 19, 20 and the network slices supported by each network served by the core network node 19, 20, from the core network node 19, 20.
  • This action 1402 is similar to the action 1206 described above in relation to Fig. 12 .
  • the RAN node 12 receives a first network identity for the home network, such as e.g. a H-PLMN ID, an identity of the first network slice supporting the wireless device in the home network, such as e.g. a H-slice ID, and a second network identity for the second network, such as e.g. a V-PLMN, from the wireless device 10.
  • a first network identity for the home network such as e.g. a H-PLMN ID
  • an identity of the first network slice supporting the wireless device in the home network such as e.g. a H-slice ID
  • a second network identity for the second network such as e.g. a V-PLMN
  • This action 1403 is similar to the action 1304 described above in relation to Fig. 13 .
  • Action 1404 The RAN node 12 retrieves an identity of a second network slice capable of supporting the wireless device 10 in the second network, based on the received first network identity for the home network, the received first network slice identity supporting the wireless device 10 in the home network and the received second network identity for the second network visited by the wireless device 10.
  • the retrieving may comprise sending the received first network identity, the received first network slice identity and the received second network identity to a DataBase (DB) 130.
  • the retrieving may further comprise receiving an identification of the second network slice capable of supporting the wireless device 10 in the second network, based on the first network identity, the first network slice identity and the second network identity from the DB 130.
  • the DB 130 may e.g. be comprised in the RAN node or in a dedicated DB node 130 being connected to the RAN node via e.g. an S1 interface or an X2 interface.
  • the DB 130 may further comprise a lookup table, where the identity of the home network for the wireless device 10, the first network slice identity supporting the wireless device 10 in the home network and the received second network identity for the second network visited by the wireless device 10 are entered as inputs to the lookup table and a slice ID supporting the wireless device 10 in the second network is received as output from the lookup table.
  • This action 1404 is similar to the actions 1305, 1306 and 1307 described above in relation to Fig. 13 .
  • the RAN node 12 determines a second core network node 20 based on the second, which may also be referred to as the selected, network identity, such as e.g. the V-PLMN ID, and the retrieved second network slice identity.
  • the determining may comprise comparing the received second network identity and the retrieved second network slice identity with the received indication of networks and network slices supported by the core network node 20.
  • This action 1405 is similar to the action 1308 described above in relation to Fig. 13 .
  • the RAN node 12 transmits an initial setup message for the wireless device 10, which initial setup message comprises an indication of the second network identity and the identity of the second network slice capable of supporting the wireless device 10, to the determined second core network node 20.
  • the initial setup message may be transmitted over the S1 protocol.
  • This action 1406 is similar to the action 1309 described above in relation to Fig. 13 .
  • action steps 1401 and 1402 may be performed separately, i.e. independently from the action steps 1403 to 1406 as a separate method for performing a S1 Setup procedure.
  • the communication network 1 comprises at least a first network and a second network.
  • the first and the second network each comprise partitioned sets of functionalities, which sets of functionalities each belong to a network slice of the network.
  • the sets of functionalities are separated from each other.
  • the core network node 20 may be associated with the second network.
  • the wireless device 10 is roaming from the first network to the second network.
  • the core network node 19, 20 receives a setup request message for establishing communication between the RAN node 12 and the core network node 19, 20, from the RAN node 12.
  • the setup request message may be transmitted over the S1 interface as e.g. an S1 SETUP REQUEST.
  • This action 1501 is similar to the action 1205 described above in relation to Fig. 12 .
  • the core network node 19, 20 transmits a setup response message comprising an indication of one or more networks served by the core network node 19, 20 and the network slices supported by each network served by the core network node 19, 20, to the RAN node 12.
  • the network slices supported by each network may be presented as a list of Slice IDs for each network ID, such as e.g. a S-PLMN ID.
  • the setup response message may be transmitted over the S1 interface as e.g. an S1 SETUP RESPONSE.
  • This action 1502 is similar to the action 1206 described above in relation to Fig. 12 .
  • the core network node 20 may receive an initial setup message for the wireless device 10, which initial setup message comprises an indication of a second network identity associated with the second network, such as e.g. a V-PLMN and an indication of a second network slice capable of supporting the wireless device 10 in the second network, from the RAN node 12.
  • a second network identity associated with the second network such as e.g. a V-PLMN
  • an indication of a second network slice capable of supporting the wireless device 10 in the second network from the RAN node 12.
  • This action 1503 is similar to the action 1309 described above in relation to Fig. 13 .
  • the core network node 20 may further transmit an attach response message comprising an indication of the second network slice supporting the wireless device 10, to the wireless device 10 via the RAN node 12.
  • the indication of the network slice may be used by the wireless device 10 in future service requests triggered by the wireless device 10.
  • This action 1504 is similar to the action 1310 described above in relation to Fig. 13 .
  • the communication network 1 comprises a first network and the second network, wherein the first network is a home network of the wireless device 10 and the second network is a network which is visited by the wireless device 10.
  • the first and the second network each comprise partitioned sets of functionalities, which sets of functionalities each belong to a network slice of the network.
  • a first set of functionalities in the first network belongs to a first network slice supporting the wireless device 10 in the first network.
  • 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 is roaming from the first network to the second network.
  • the wireless device transmits a first network identity for the home network of the wireless device 10, such as e.g. a H-PLMN ID, an identity of the first network slice supporting the wireless device 10 in the home network, such as e.g. a H-slice ID, and a second network identity for the visited second network, such as e.g. a V-PLMN ID, to the RAN node 12.
  • the transmission may be sent during a RRC Connection Setup Procedure, such as e.g. in a RRC Connection Setup Complete message.
  • This action 1601 is similar to the action 1304 described above in relation to Fig. 13 .
  • the wireless device 10 may further receive an attach response message comprising an indication of a second network slice supporting the wireless device 10 in the second network, from the second core network node 20.
  • the indication of the network slice may be used by the wireless device 10 in future service requests triggered by the wireless device 10.
  • the attach response message is transmitted from the core network node 20 to the wireless device 10 via the RAN node 12.
  • This action 1602 is similar to the action 1310 described above in relation to Fig. 13 .
  • Fig. 17 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 a first network and a second network.
  • the first network is a home network of the wireless device 10 and the second network is a network which is visited by the wireless device 10.
  • the first and the second network each comprise partitioned sets of functionalities, which sets of functionalities each belong to a network slice of the network.
  • a first set of functionalities in the first network belongs to a first network slice supporting the wireless device 10, 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 is roaming from the first network to the second network.
  • the RAN node 12 may further be associated with a plurality of networks, wherein each network supports a plurality of network slices.
  • the RAN node 12 may comprise a processing unit 1701, 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 1702 and/or the processing unit 1701 being configured to, receive a first network identity for the home network, an identity of the first network slice supporting the wireless device in the home network and a second network identity for the second network from the wireless device 10.
  • the RAN node 12 is further configured to, e.g. by means of a retrieving module 1703 and/or the processing unit 1701 being configured to, retrieve an identity of a second network slice capable of supporting the wireless device 10 in the second network, based on the received first network identity, the first network slice identity and the second network identity.
  • the RAN node 12 may further be configured to retrieve the identity of the second network slice, by being configured to, e.g. by means of a transmitting module 1705 and/or the processing unit 1701 being configured to, send the received first network identity, the first network slice identity and the second network identity, to a DataBase, DB.
  • the RAN node 12 may further be configured to retrieve the identity of the second network slice, by being configured to, e.g. by means of the receiving module 1702 and/or the processing unit 1701 being configured to, receive from the DB an identification of the second network slice capable of supporting the wireless device 10 in the second network, based on the first network identity, the first network slice identity and the second network identity.
  • the RAN node 12 is further configured to, e.g. by means of a determining module 1704 and/or the processing unit 1701 being configured to, determine a core network node 20 based on the second network identity and the retrieved second network slice identity.
  • the RAN node 12 is further configured to, e.g. by means of the transmitting module 1705 and/or the processing unit 1701 being configured to, transmit an initial setup message for the wireless device 10, which initial setup message comprises an indication of the second network identity and the identity of the second network slice capable of supporting the wireless device 10, to the determined core network node 20.
  • the RAN node 12 may, when the RAN node 12 is associated with a plurality of networks and each network supports a plurality of network slices, further be configured to, e.g. by means of the transmitting module 1705 and/or the processing unit 1701 being configured to, transmit a setup request message for establishing communication between the RAN node 12 and the core network node 19, 20, to a core network node 19, 20.
  • the RAN node 12 may, when the RAN node 12 is associated with a plurality of networks and each network supports a plurality of network slices, further be configured to, e.g. by means of the receiving module 1702 and/or the processing unit 1701 being configured to, receive a setup response message comprising an indication of one or more networks served by the core network node 19, 20 and the network slices supported by each network served by the core network node 19, 20, from the core network node 19, 20.
  • the RAN node 12 is further configured to, e.g. by means of a comparing module 1706 and/or the determining module 1704 and/or the processing unit 1701 being configured to, compare the retrieved second network identity and the second network slice identity with the received indication of networks and network slices supported by the core network node 20 in order to determine the core network node 20.
  • the RAN node 12 further comprises a memory 1705.
  • the memory comprises one or more units to be used to store data on, such as network slice information, wireless device IDs, network 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 1706 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 1706 may be stored on a computer-readable storage medium 1707, e.g. a disc or similar.
  • the computer-readable storage medium 1707, 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. 18 is a block diagram depicting the core network node 19, 20 for enabling connection setup for the wireless device 10 in the communication network 1.
  • the communication network 1 comprises at least a first network and a second network.
  • the first and the second network each comprise partitioned sets of functionalities, which sets of functionalities each belong to a network slice of the network.
  • the sets of functionalities are separated from each other.
  • the wireless device 10 is roaming from the first network to the second network.
  • the core network node 20 may be associated with the second network.
  • the core network node 19 may comprise a processing unit 1801, 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 a receiving module 1802 and/or the processing unit 1801 being configured to, receive a setup request message for establishing communication between the RAN node 12 and the core network node 19, 20, from the RAN node 12.
  • the core network node 19 is configured to, e.g. by means of a transmitting module 1803 and/or the processing unit 1801 being configured to, transmit a setup response message comprising an indication of one or more networks served by the core network node 19, 20 and the network slices supported by each network served by the core network node 19, 20, to the RAN node 12.
  • the core network node 19 may further be configured to, e.g. by means of an receiving module 1802 and/or the processing unit 1801 being configured to, receive an initial setup message for the wireless device 10, which initial setup message comprises an indication of a second network identity associated with the second network and an indication of a second network slice capable of supporting the wireless device 10, from the RAN node 12.
  • the core network node 19 further comprises a memory 1804.
  • 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 core network node 19 are respectively implemented by means of e.g. a computer program 1805 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 1805 may be stored on a computer-readable storage medium 1806, e.g. a disc or similar.
  • the computer-readable storage medium 1806, 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. 19 is a block diagram depicting the wireless device 10 for establishing a connection to a second network in a communication network 1.
  • the communication network 1 comprises a first network and the second network, wherein the first network is a home network of the wireless device 10 and the second network is a network which is visited by the wireless device 10.
  • the first and the second network each comprise partitioned sets of functionalities, which sets of functionalities each belong to a network slice of the network.
  • a first set of functionalities in the first network belongs to a first network slice supporting the wireless device 10 in the first network.
  • 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 comprise a processing unit 1901, 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 transmitting module 1902 and/or the processing unit 1901 being configured to, transmit a first network identity for the home network of the wireless device 10, an identity of the first network slice supporting the wireless device 10 in the home network and a second network identity for the visited second network to the RAN node 12.
  • the wireless device 10 may further be configured to, e.g. by means of a receiving module 1903 and/or the processing unit 1901 being configured to, receive an attach response message comprising an indication of a second network slice supporting the wireless device 10 in the second network, from the second core network node 20.
  • the indication of the network slice may be used by the wireless device 10 in future service requests triggered by the wireless device 10.
  • the attach response message is transmitted from the core network node 20 to the wireless device 10 via the RAN node 12.
  • the wireless device 10 further comprises a memory 1904.
  • 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 wireless device 10 are respectively implemented by means of e.g. a computer program 1905 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 1905 may be stored on a computer-readable storage medium 1906, e.g. a disc or similar.
  • the computer-readable storage medium 1906 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
  • 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.

Claims (16)

  1. Verfahren, das von einem Funkzugangsnetz-Knoten, RAN-Knoten, (12) durchgeführt wird, um den Verbindungsaufbau für eine drahtlose Vorrichtung (10) in einem Kommunikationsnetz (1) zu ermöglichen, wobei das Kommunikationsnetz (1) ein erstes Netzwerk und ein zweites Netzwerk umfasst, wobei das erste Netzwerk ein Heimnetzwerk der drahtlosen Vorrichtung (10) ist und das zweite Netzwerk ein Netzwerk ist, das von der drahtlosen Vorrichtung (10) besucht wird, und wobei das erste und das zweite Netzwerk jeweils partitionierte Sätze von Funktionalitäten umfassen, wobei die Sätze von Funktionalitäten jeweils zu einem Netzwerk-Slice des Netzwerks gehören, wobei ein erster Satz von Funktionalitäten im ersten Netzwerk zu einem ersten Netzwerk-Slice gehört, der die drahtlose Vorrichtung (10) unterstützt, und wobei der erste Satz von Funktionalitäten von einem anderen Satz von Funktionalitäten aus einem gesamten Satz von Funktionalitäten im ersten Netzwerk getrennt ist, wobei die drahtlose Vorrichtung (10) vom ersten Netzwerk zum zweiten Netzwerk roamt, wobei das Verfahren umfasst:
    - Empfangen (1403),
    von der drahtlosen Vorrichtung (10), einer ersten Netzwerkidentität für das Heimnetzwerk, einer Identität des ersten Netzwerk-Slice, der die drahtlose Vorrichtung in dem Heimnetzwerk unterstützt, und einer zweiten Netzwerkidentität für das zweite Netzwerk;
    - Abrufen (1404)
    einer Identität eines zweiten Netzwerk-Slice, der in der Lage ist, die drahtlose Vorrichtung (10) im zweiten Netzwerk basierend auf der empfangenen ersten Netzwerkidentität, der ersten Netzwerk-Slice-Identität und der zweiten Netzwerkidentität zu unterstützen,
    - Bestimmen (1405)
    eines zweiten Kernnetzknotens (20), basierend auf der zweiten Netzwerkidentität und der abgerufenen zweiten Netzwerk-Slice-Identität,
    - Übertragen (1406),
    an den bestimmten zweiten Kernnetzknoten (20), einer anfänglichen Setup-Nachricht für die drahtlose Vorrichtung (10), wobei die anfängliche Setup-Nachricht eine Anzeige der zweiten Netzwerkidentität und der Identität des zweiten Netzwerk-Slice umfasst, der in der Lage ist, die drahtlose Vorrichtung (10) zu unterstützen.
  2. Verfahren nach Anspruch 1, wobei das Abrufen das Senden der empfangenen ersten Netzwerkidentität, der ersten Netzwerk-Slice-Identität und der zweiten Netzwerkidentität an eine Datenbank, DB, und das Empfangen einer Identifizierung des zweiten Netzwerk-Slice von der DB umfasst, der in der Lage ist, die drahtlose Vorrichtung im zweiten Netzwerk basierend auf der ersten Netzwerkidentität, der ersten Netzwerk-Slice-Identität und der zweiten Netzwerkidentität zu unterstützen.
  3. Verfahren nach Anspruch 1 oder 2, wobei der RAN-Knoten (12) weiterhin einer Vielzahl von Netzwerken zugeordnet ist und wobei jedes Netzwerk eine Vielzahl von Netzwerk-Slices unterstützt, wobei das Verfahren ferner umfasst:
    - Übertragen einer Setup-Anforderungsnachricht an einen Kernnetzknoten (19, 20) zum Herstellen einer Kommunikation zwischen dem RAN-Knoten (12) und dem Kernnetzknoten (19, 20),
    - Empfangen einer Setup-Antwortnachricht von dem Kernnetzknoten (19, 20), die eine Anzeige von einem oder mehreren Netzwerken, die von dem Kernnetzknoten (19, 20) bedient werden, und der Netzwerk-Slices umfasst, die von jedem Netzwerk unterstützt werden, das von dem Kernnetzknoten (19, 20) bedient wird.
  4. Verfahren nach Anspruch 3, wobei das Bestimmen (1405) das Vergleichen der abgerufenen zweiten Netzwerkidentität und der zweiten Netzwerk-Slice-Identität mit der empfangenen Anzeige von Netzwerken und Netzwerk-Slices, die von dem Kernnetzknoten (20) unterstützt werden, umfasst.
  5. Verfahren, das von einem Kernnetzknoten (19, 20) durchgeführt wird, um den Verbindungsaufbau für eine drahtlose Vorrichtung (10) in einem Kommunikationsnetz (1) zu ermöglichen, wobei das Kommunikationsnetz (1) mindestens ein erstes Netzwerk und ein zweites Netzwerk umfasst, wobei das erste und das zweite Netzwerk jeweils partitionierte Sätze von Funktionalitäten umfassen, wobei die Sätze von Funktionalitäten jeweils zu einem Netzwerk-Slice des Netzwerks gehören und wobei die Sätze von Funktionalitäten voneinander getrennt sind, wobei das Verfahren umfasst:
    - Empfangen (1501),
    von dem RAN-Knoten (12), einer Setup-Anforderungsnachricht zum Herstellen einer Kommunikation zwischen dem RAN-Knoten (12) und dem Kernnetzknoten (19, 20),
    - Übertragen (1502),
    an den RAN-Knoten (12), einer Setup-Antwortnachricht, die eine Anzeige eines oder mehrerer Netzwerke, die von dem Kernnetzknoten (19, 20) bedient werden, und der Netzwerk-Slices umfasst, die von jedem Netzwerk unterstützt werden, das von dem Kernnetzknoten (19, 20) bedient wird.
  6. Verfahren nach Anspruch 5, wobei der Kernnetzknoten (19, 20) dem zweiten Netzwerk zugeordnet ist und wobei die drahtlose Vorrichtung (10) vom ersten Netzwerk zum zweiten Netzwerk roamt, wobei das Verfahren ferner umfasst:
    - Empfangen (1503),
    von dem RAN-Knoten (12), einer anfänglichen Setup-Nachricht für die drahtlose Vorrichtung (10), wobei die anfängliche Setup-Nachricht eine Anzeige einer dem zweiten Netzwerk zugeordneten zweiten Netzwerkidentität und eine Anzeige eines zweiten Netzwerk-Slice umfasst, der in der Lage ist, die drahtlose Vorrichtung (10) zu unterstützen.
  7. Verfahren, das von einer drahtlosen Vorrichtung (10) durchgeführt wird, um eine Verbindung zu einem zweiten Netzwerk in einem Kommunikationsnetz (1) herzustellen, wobei das Kommunikationsnetz (1) ein erstes Netzwerk und das zweite Netzwerk umfasst, wobei das erste Netzwerk ein Heimnetzwerk der drahtlosen Vorrichtung (10) ist und das zweite Netzwerk ein Netzwerk ist, das von der drahtlosen Vorrichtung (10) besucht wird, und wobei das erste und das zweite Netzwerk jeweils partitionierte Sätze von Funktionalitäten umfassen, wobei die Sätze von Funktionalitäten jeweils zu einem Netzwerk-Slice des Netzwerks gehören, wobei ein erster Satz von Funktionalitäten im ersten Netzwerk zu einem ersten Netzwerk-Slice gehört, der die drahtlose Vorrichtung (10) im ersten Netzwerk unterstützt, und wobei der erste Satz von Funktionalitäten von einem anderen Satz von Funktionalitäten aus einem gesamten Satz von Funktionalitäten im ersten Netzwerk getrennt ist, wobei die drahtlose Vorrichtung (10) vom ersten Netzwerk zum zweiten Netzwerk roamt, wobei das Verfahren umfasst:
    - Übertragen, an den RAN-Knoten (12), einer ersten Netzwerkidentität für das Heimnetzwerk der drahtlosen Vorrichtung (10), einer Identität des ersten Netzwerk-Slice, der die drahtlose Vorrichtung (10) im Heimnetzwerk unterstützt, und einer zweiten Netzwerkidentität für das besuchte zweite Netzwerk.
  8. Funkzugangsnetz-, RAN, -Knoten (12), zum Ermöglichen des Verbindungsaufbaus für eine drahtlose Vorrichtung (10) in einem Kommunikationsnetz (1), wobei das Kommunikationsnetz (1) ein erstes Netzwerk und ein zweites Netzwerk umfasst,
    wobei das erste Netzwerk ein Heimnetzwerk der drahtlosen Vorrichtung (10) ist und das zweite Netzwerk ein Netzwerk ist, das von der drahtlosen Vorrichtung (10) besucht wird, und wobei das erste und das zweite Netzwerk jeweils partitionierte Sätze von Funktionalitäten umfassen, wobei die Sätze von Funktionalitäten jeweils zu einem Netzwerk-Slice des Netzwerks gehören, wobei ein erster Satz von Funktionalitäten im ersten Netzwerk zu einem ersten Netzwerk-Slice gehört, der die drahtlose Vorrichtung (10) unterstützt, und wobei der erste Satz von Funktionalitäten von einem anderen Satz von Funktionalitäten aus einem gesamten Satz von Funktionalitäten im ersten Netzwerk getrennt ist, wobei die drahtlose Vorrichtung (10) vom ersten Netzwerk zum zweiten Netzwerk roamt, wobei der RAN-Knoten (12) konfiguriert ist zum:
    - Empfangen, von der drahtlosen Vorrichtung (10), einer ersten Netzwerkidentität für das Heimnetzwerk, einer Identität des ersten Netzwerk-Slice, der die drahtlose Vorrichtung im Heimnetzwerk unterstützt, und einer zweiten Netzwerkidentität für das zweite Netzwerk;
    - Abrufen einer Identität eines zweiten Netzwerk-Slice, der in der Lage ist, die drahtlose Vorrichtung (10) im zweiten Netzwerk zu unterstützen, basierend auf der empfangenen ersten Netzwerkidentität, der ersten Netzwerk-Slice-Identität und der zweiten Netzwerkidentität,
    - Bestimmen eines Kernnetzknotens (20) basierend auf der zweiten Netzwerkidentität und der abgerufenen zweiten Netzwerk-Slice-Identität,
    - Übertragen, an den bestimmten Kernnetzknoten (20), einer anfänglichen Setup-Nachricht für die drahtlose Vorrichtung (10), wobei die anfängliche Setup-Nachricht eine Anzeige der zweiten Netzwerkidentität und die Identität des zweiten Netzwerk-Slice umfasst, der in der Lage ist, die drahtlose Vorrichtung (10) zu unterstützen.
  9. RAN-Knoten (12) nach Anspruch 8, wobei der RAN-Knoten (12) zum Abrufen der Identität des zweiten Netzwerk-Slice dazu konfiguriert ist, die empfangene erste Netzwerkidentität, die erste Netzwerk-Slice-Identität und die zweite Netzwerk-Identität an eine Datenbank, DB, zu senden und von der DB eine Kennung des zweiten Netzwerk-Slice zu empfangen, der in der Lage ist, die drahtlose Vorrichtung () im zweiten Netzwerk zu unterstützen, basierend auf der ersten Netzwerkidentität, der ersten Netzwerk-Slice-Identität und der zweiten Netzwerk-Identität.
  10. RAN-Knoten (12) nach Anspruch 8 oder 9, wobei der RAN-Knoten (12) ferner einer Vielzahl von Netzwerken zugeordnet ist und wobei jedes Netzwerk eine Vielzahl von Netzwerk-Slices unterstützt, wobei der RAN-Knoten ferner konfiguriert ist zum:
    - Übertragen, an einen Kernnetzknoten (19, 20), einer Setup-Anforderungsnachricht zum Aufbau einer Kommunikation zwischen dem RAN-Knoten (12) und dem Kernnetzknoten (19, 20),
    - Empfangen, von dem Kernnetzknoten (19, 20), einer Setup-Antwortnachricht, die eine Anzeige eines oder mehrerer Netzwerke, die von dem Kernnetzknoten (19, 20) bedient werden, und der von jedem Netzwerk, das von dem Kernnetzknoten (19, 20) bedient wird, unterstützten Netzwerk-Slices umfasst.
  11. RAN-Knoten (12) nach Anspruch 10, wobei der RAN-Knoten (12) ferner dazu konfiguriert ist, die abgerufene zweite Netzwerkidentität und die zweite Netzwerk-Slice-Identität mit der empfangenen Anzeige von Netzwerken und Netzwerk-Slices zu vergleichen, die von dem Kernnetzknoten (20) unterstützt werden, um den Kernnetzknoten (20) zu bestimmen.
  12. Kernnetzknoten (19, 20), zum Ermöglichen des Verbindungsaufbaus für eine drahtlose Vorrichtung (10) in einem Kommunikationsnetz (1), wobei das Kommunikationsnetz (1) mindestens ein erstes Netzwerk und ein zweites Netzwerk umfasst, wobei das erste und das zweite Netzwerk jeweils partitionierte Sätze von Funktionalitäten umfassen, wobei diese Sätze von Funktionalitäten jeweils zu einem Netzwerk-Slice des Netzwerks gehören, wobei jeder Satz von Funktionalitäten zu einem Netzwerk-Slice gehört und wobei die Sätze von Funktionalitäten voneinander getrennt sind, wobei der Kernnetzknoten (19, 20) konfiguriert ist zum:
    - Empfangen einer Setup-Anforderungsnachricht vom RAN-Knoten (12) zum Herstellen einer Kommunikation zwischen dem RAN-Knoten (12) und dem Kernnetzknoten (19, 20),
    - Übertragen, an den RAN-Knoten (12), einer Setup-Antwortnachricht, die eine Anzeige eines oder mehrerer Netzwerke, die von dem Kernnetzknoten (19, 20) bedient werden, und der Netzwerk-Slices umfasst, die von jedem Netzwerk unterstützt werden, das von dem Kernnetzknoten (19, 20) bedient wird.
  13. Kernnetzknoten (19, 20) nach Anspruch 12, wobei der Kernnetzknoten (20) dem zweiten Netzwerk zugeordnet ist und die drahtlose Vorrichtung (10) vom ersten Netzwerk zum zweiten Netzwerk roamt, wobei der Kernnetzknoten (20) ferner konfiguriert ist zum:
    - Empfangen, von dem RAN-Knoten (12), einer anfänglichen Setup-Nachricht für die drahtlose Vorrichtung (10), wobei die anfängliche Setup-Nachricht eine Anzeige über eine dem zweiten Netzwerk zugeordnete zweiten Netzwerkidentität und eine Anzeige über einen zweiten Netzwerk-Slice umfasst, der in der Lage ist, die drahtlose Vorrichtung (10) zu unterstützen.
  14. Drahtlose Vorrichtung (10) zum Aufbau einer Verbindung mit einem zweiten Netzwerk in einem Kommunikationsnetz (1), wobei das Kommunikationsnetz (1) ein erstes Netzwerk und das zweite Netzwerk umfasst, wobei das erste Netzwerk ein Heimnetzwerk der drahtlosen Vorrichtung (10) ist und das zweite Netzwerk ein Netzwerk ist, das von der drahtlosen Vorrichtung (10) besucht wird, und wobei das erste und das zweite Netzwerk jeweils partitionierte Sätze von Funktionalitäten umfassen, wobei diese Sätze von Funktionalitäten jeweils zu einem Netzwerk-Slice des Netzwerks gehören, wobei ein erster Satz von Funktionalitäten in dem ersten Netzwerk zu einem ersten Netzwerk-Slice gehört, der die drahtlose Vorrichtung (10) in dem ersten Netzwerk unterstützt, und wobei der erste Satz von Funktionalitäten von einem anderen Satz von Funktionalitäten aus einem gesamten Satz von Funktionalitäten in dem ersten Netzwerk getrennt ist, wobei die drahtlose Vorrichtung (10) konfiguriert ist zum:
    - Übertragen, an den RAN-Knoten (12), einer ersten Netzwerkidentität für das Heimnetzwerk der drahtlosen Vorrichtung (10), einer Identität des ersten Netzwerk-Slice, der die drahtlose Vorrichtung (10) im Heimnetzwerk unterstützt, und einer zweiten Netzwerkidentität für das besuchte zweite Netzwerk.
  15. Computerprogramm, umfassend Anweisungen, die, wenn sie auf mindestens einem Prozessor ausgeführt werden, bewirken, dass der mindestens eine Prozessor eines der Verfahren nach einem der Ansprüche 1 bis 7 ausführt, wie es von dem Kernnetzknoten (19), dem RAN-Knoten (12) oder der drahtlosen Vorrichtung (10) ausgeführt wird.
  16. Computerlesbares Speichermedium, auf dem ein Computerprogramm gespeichert ist, das Anweisungen umfasst, die, wenn sie auf mindestens einem Prozessor ausgeführt werden, bewirken, dass der mindestens eine Prozessor das Verfahren nach einem der Ansprüche 1 bis 7 ausführt, wie es von dem Kernnetzknoten (19), dem RAN-Knoten (12) oder der drahtlosen Vorrichtung (10) ausgeführt wird.
EP16706447.6A 2016-02-05 2016-02-12 Funknetzwerkknoten und verfahren zur ermöglichung der kommunikation in einem netzwerk Active EP3412048B1 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662291572P 2016-02-05 2016-02-05
PCT/SE2016/050107 WO2017135860A1 (en) 2016-02-05 2016-02-12 Network nodes and methods performed therein for enabling communication in a communication network

Publications (2)

Publication Number Publication Date
EP3412048A1 EP3412048A1 (de) 2018-12-12
EP3412048B1 true EP3412048B1 (de) 2019-09-25

Family

ID=55436142

Family Applications (1)

Application Number Title Priority Date Filing Date
EP16706447.6A Active EP3412048B1 (de) 2016-02-05 2016-02-12 Funknetzwerkknoten und verfahren zur ermöglichung der kommunikation in einem netzwerk

Country Status (3)

Country Link
US (1) US10893405B2 (de)
EP (1) EP3412048B1 (de)
WO (1) WO2017135860A1 (de)

Families Citing this family (67)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3378254B1 (de) * 2015-11-18 2019-10-02 Telefonaktiebolaget LM Ericsson (PUBL) Netzwerkknoten, funkzugangsknoten und darin durchgeführte verfahren
EP3403448B1 (de) * 2016-01-11 2020-03-04 Telefonaktiebolaget LM Ericsson (PUBL) Funknetzknoten, kommunikationsnetzwerk und damit durchgeführte verfahren
WO2017143047A1 (en) * 2016-02-16 2017-08-24 Idac Holdings, Inc. Network slicing operation
JP6884156B2 (ja) * 2016-02-29 2021-06-09 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． 制御プレーンノードを判定する方法、装置、および無線通信システム
KR102078189B1 (ko) * 2016-03-11 2020-02-20 주식회사 케이티 무선 액세스 망 슬라이싱 제어 장치와 그 장치가 무선 베어러 전송을 제어하는 방법
WO2017173404A1 (en) 2016-04-01 2017-10-05 Idac Holdings, Inc. Methods for service slice selection and separation
JP2019096918A (ja) 2016-04-05 2019-06-20 シャープ株式会社 端末装置、基地局装置、ＭＭＥ（Ｍｏｂｉｌｉｔｙ Ｍａｎａｇｅｍｅｎｔ Ｅｎｔｉｔｙ）および通信制御方法
CN116113014A (zh) * 2016-04-23 2023-05-12 华为技术有限公司 一种无线接入网切片的生成方法、无线接入网及切片管理器
US11153744B2 (en) * 2016-05-16 2021-10-19 Samsung Electronics Co., Ltd. Roaming support for next generation slice architecture
JP6480641B2 (ja) * 2016-05-26 2019-03-13 京セラ株式会社 ネットワーク装置
CN111479297B (zh) * 2016-07-29 2023-04-18 中兴通讯股份有限公司 公共流程实现方法、装置及系统
CN113630849B (zh) 2016-08-12 2022-09-09 华为技术有限公司 网络切片的选择方法、无线接入设备和终端
CN109565785B (zh) * 2016-08-12 2023-11-03 华为技术有限公司 一种寻呼方法和寻呼设备
US11363435B2 (en) * 2016-10-11 2022-06-14 Telefonaktiebolaget Lm Ericsson (Publ) Network slicing-aware access network
CN108024314B (zh) * 2016-11-03 2021-07-16 华为技术有限公司 一种选择网络的方法及装置
CN108616959B (zh) 2017-01-06 2022-01-04 荣耀终端有限公司 一种通信方法、接入网设备、核心网设备和用户设备
CN108347751B (zh) * 2017-01-25 2021-08-03 华为技术有限公司 通信方法和通信装置
US10764785B2 (en) * 2017-03-07 2020-09-01 Htc Corporation Device and method of handling network slice information
US10582432B2 (en) 2017-05-04 2020-03-03 Comcast Cable Communications, Llc Communications for network slicing using resource status information
US10820185B2 (en) 2017-05-08 2020-10-27 Qualcomm Incorporated Mobility between areas with heterogeneous network slices
US10264506B2 (en) 2017-05-13 2019-04-16 Qualcomm Incorporated Enable a network-trigger change of network slices
CN110679199B (zh) * 2017-05-23 2024-04-02 瑞典爱立信有限公司 为用户平面会话获得cn/ran端点对的决定的网络节点及方法
CN110679179B (zh) * 2017-06-02 2021-10-29 鸿颖创新有限公司 用于服务驱动的移动性管理的方法、装置及系统
RU2731121C1 (ru) * 2017-06-19 2020-08-31 Хуавей Текнолоджиз Ко., Лтд. Способ регистрации, способ установки сеанса, оконечное устройство и объект функции управления доступом и мобильностью
US11012929B2 (en) * 2017-07-13 2021-05-18 Qualcomm Incorporated Techniques for determining public land mobile network support of different core networks
US10764789B2 (en) 2017-08-11 2020-09-01 Comcast Cable Communications, Llc Application-initiated network slices in a wireless network
CN111491345B (zh) * 2017-08-11 2021-04-20 华为技术有限公司 通信方法、接入网设备及计算机可读存储介质
US11153813B2 (en) 2017-08-11 2021-10-19 Comcast Cable Communications, Llc Network slice for visited network
KR102425675B1 (ko) 2017-08-14 2022-07-28 삼성전자 주식회사 5g 시스템에서 네트워크와 단말 간 제공 기능 협상 및 슬라이스 정보 맵핑 방법
US11115838B2 (en) * 2017-08-15 2021-09-07 Telefonaktiebolaget Lm Ericsson (Publ) Service area definition at network slicing
CN109429272B (zh) * 2017-08-31 2022-02-11 华为技术有限公司 一种漫游场景下的分流方法及相关设备
EP3689032A1 (de) 2017-09-28 2020-08-05 Telefonaktiebolaget LM Ericsson (publ) Auswahl einer frequenz oder funkzugangstechnologie (rat) auf der basis der slice verfügbarkeit
CN114745728A (zh) * 2017-09-30 2022-07-12 华为技术有限公司 网络资源部署及评估的方法、和设备
CN111279751A (zh) 2017-11-09 2020-06-12 华为技术有限公司 用于获取切片支持信息的装置和方法
CN109802809B (zh) 2017-11-17 2021-02-09 华为技术有限公司 网络接入的方法、终端设备和网络设备
CN109862579B (zh) * 2017-11-30 2022-05-17 华为技术有限公司 通信方法和通信装置
EP3972347A1 (de) 2017-12-08 2022-03-23 Comcast Cable Communications LLC Funktionsauswahl auf benutzerebene für isolierte netzwerk-slice
KR102014101B1 (ko) * 2017-12-15 2019-10-21 에스케이 텔레콤주식회사 네트워크 슬라이싱을 이용한 로밍 서비스 제공방법 및 장치
CN110035461B (zh) * 2018-01-12 2020-12-15 华为技术有限公司 通信方法、接入网设备和终端设备
CN110100481B (zh) * 2018-01-19 2020-09-08 Oppo广东移动通信有限公司 一种接入控制的方法、设备及计算机存储介质
US10813078B2 (en) * 2018-02-23 2020-10-20 Hughes Network Systems, Llc Satellite paging efficiency
US11271846B2 (en) 2018-10-22 2022-03-08 Oracle International Corporation Methods, systems, and computer readable media for locality-based selection and routing of traffic to producer network functions (NFs)
US10778527B2 (en) * 2018-10-31 2020-09-15 Oracle International Corporation Methods, systems, and computer readable media for providing a service proxy function in a telecommunications network core using a service-based architecture
US11159359B2 (en) 2019-06-26 2021-10-26 Oracle International Corporation Methods, systems, and computer readable media for diameter-peer-wide egress rate limiting at diameter relay agent (DRA)
US10819636B1 (en) 2019-06-26 2020-10-27 Oracle International Corporation Methods, systems, and computer readable media for producer network function (NF) service instance wide egress rate limiting at service communication proxy (SCP)
US11252093B2 (en) 2019-06-26 2022-02-15 Oracle International Corporation Methods, systems, and computer readable media for policing access point name-aggregate maximum bit rate (APN-AMBR) across packet data network gateway data plane (P-GW DP) worker instances
US10833938B1 (en) 2019-07-31 2020-11-10 Oracle International Corporation Methods, systems, and computer readable media for network function (NF) topology synchronization
US11323413B2 (en) 2019-08-29 2022-05-03 Oracle International Corporation Methods, systems, and computer readable media for actively discovering and tracking addresses associated with 4G service endpoints
US11082393B2 (en) 2019-08-29 2021-08-03 Oracle International Corporation Methods, systems, and computer readable media for actively discovering and tracking addresses associated with 5G and non-5G service endpoints
US11102138B2 (en) 2019-10-14 2021-08-24 Oracle International Corporation Methods, systems, and computer readable media for providing guaranteed traffic bandwidth for services at intermediate proxy nodes
US11018971B2 (en) 2019-10-14 2021-05-25 Oracle International Corporation Methods, systems, and computer readable media for distributing network function (NF) topology information among proxy nodes and for using the NF topology information for inter-proxy node message routing
US11425598B2 (en) 2019-10-14 2022-08-23 Oracle International Corporation Methods, systems, and computer readable media for rules-based overload control for 5G servicing
US11224009B2 (en) 2019-12-30 2022-01-11 Oracle International Corporation Methods, systems, and computer readable media for enabling transport quality of service (QoS) in 5G networks
CN114025349B (zh) * 2020-07-16 2024-01-26 中国电信股份有限公司 网络服务方法、装置、系统和存储介质
US11528334B2 (en) 2020-07-31 2022-12-13 Oracle International Corporation Methods, systems, and computer readable media for preferred network function (NF) location routing using service communications proxy (SCP)
US11290549B2 (en) 2020-08-24 2022-03-29 Oracle International Corporation Methods, systems, and computer readable media for optimized network function (NF) discovery and routing using service communications proxy (SCP) and NF repository function (NRF)
US11483694B2 (en) 2020-09-01 2022-10-25 Oracle International Corporation Methods, systems, and computer readable media for service communications proxy (SCP)-specific prioritized network function (NF) discovery and routing
US11570262B2 (en) 2020-10-28 2023-01-31 Oracle International Corporation Methods, systems, and computer readable media for rank processing for network function selection
US11470544B2 (en) 2021-01-22 2022-10-11 Oracle International Corporation Methods, systems, and computer readable media for optimized routing of messages relating to existing network function (NF) subscriptions using an intermediate forwarding NF repository function (NRF)
US11496954B2 (en) 2021-03-13 2022-11-08 Oracle International Corporation Methods, systems, and computer readable media for supporting multiple preferred localities for network function (NF) discovery and selection procedures
US11895080B2 (en) 2021-06-23 2024-02-06 Oracle International Corporation Methods, systems, and computer readable media for resolution of inter-network domain names
US11805463B2 (en) * 2021-07-23 2023-10-31 T-Mobile Innovations Llc User equipment (UE) handover in wireless communication networks
US11950178B2 (en) 2021-08-03 2024-04-02 Oracle International Corporation Methods, systems, and computer readable media for optimized routing of service based interface (SBI) request messages to remote network function (NF) repository functions using indirect communications via service communication proxy (SCP)
US11792634B2 (en) 2021-08-16 2023-10-17 Cisco Technology, Inc. Facilitating visited network selection by a user equipment based on slice considerations
US11849506B2 (en) 2021-10-08 2023-12-19 Oracle International Corporation Methods, systems, and computer readable media for routing inter-public land mobile network (inter-PLMN) messages related to existing subscriptions with network function (NF) repository function (NRF) using security edge protection proxy (SEPP)
US20230171099A1 (en) * 2021-11-27 2023-06-01 Oracle International Corporation Methods, systems, and computer readable media for sharing key identification and public certificate data for access token verification
CN117014889A (zh) * 2022-04-28 2023-11-07 华为技术有限公司 通信方法以及通信装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160353367A1 (en) * 2015-06-01 2016-12-01 Huawei Technologies Co., Ltd. System and Method for Virtualized Functions in Control and Data Planes
CN106375987B (zh) * 2015-07-22 2021-08-20 中兴通讯股份有限公司 一种网络切片的选择方法及系统
US10425830B2 (en) * 2015-09-07 2019-09-24 Electronics And Telecommunications Research Institute Mobile communication network system and method for composing network component configurations
KR102058234B1 (ko) * 2015-11-10 2019-12-20 후아웨이 테크놀러지 컴퍼니 리미티드 서비스 네트워크를 선택하는 방법 및 네트워크, 및 관리 장치
US10536946B2 (en) * 2015-12-08 2020-01-14 Huawei Technologies Co., Ltd. Method and system for performing network slicing in a radio access network
KR102066188B1 (ko) * 2015-12-30 2020-01-14 도이체 텔레콤 악티엔 게젤샤프트 로밍 연결을 확립하기 위한 방법

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
US20190045351A1 (en) 2019-02-07
US10893405B2 (en) 2021-01-12
EP3412048A1 (de) 2018-12-12
WO2017135860A1 (en) 2017-08-10

Similar Documents

Publication Publication Date Title
EP3412048B1 (de) Funknetzwerkknoten und verfahren zur ermöglichung der kommunikation in einem netzwerk
US10893455B2 (en) Handover in a wireless communication network with network slices
US11070967B2 (en) Network nodes and methods performed therein for enabling communication in a communication network
EP3417648B1 (de) Netzwerkknoten und darin ausgeführte verfahren zur ermöglichung der kommunikation in einem kommunikationsnetzwerk
US11026165B2 (en) Radio network node, network node, database, configuration control node, and methods performed thereby
US10820241B2 (en) Network nodes and methods performed therein for enabling communication in a communication network
EP3417657B1 (de) Funknetzwerkknoten, drahtlose vorrichtung und darin ausgeführte verfahren
EP3403464B1 (de) Sendende kommunikationsvorrichtung, empfangende kommunikationsvorrichtung, darin ausgeführte verfahren im kontext des netzwerk-slicing und computerprogramm
US10506552B2 (en) Core network node, radio network node, wireless device and methods performed therein
US10863560B2 (en) First network node, receiving network node and methods performed therein
WO2017135859A1 (en) Network nodes and methods performed therein
KR102497696B1 (ko) 무선 네트워크 노드, 사용자 평면 기능(upf) 및 페이징 정책 차별화를 위한 내부에서 수행된 방법

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20180528

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 76/11 20180101ALI20190515BHEP

Ipc: H04W 76/16 20180101ALI20190515BHEP

Ipc: H04W 8/06 20090101ALI20190515BHEP

Ipc: H04W 8/02 20090101AFI20190515BHEP

Ipc: H04W 48/18 20090101ALI20190515BHEP

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

INTG Intention to grant announced

Effective date: 20190722

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1185047

Country of ref document: AT

Kind code of ref document: T

Effective date: 20191015

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602016021197

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20190925

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190925

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190925

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191225

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191225

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190925

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190925

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190925

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191226

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190925

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1185047

Country of ref document: AT

Kind code of ref document: T

Effective date: 20190925

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190925

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190925

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190925

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190925

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190925

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190925

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190925

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190925

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200127

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190925

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190925

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200224

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190925

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602016021197

Country of ref document: DE

PG2D Information on lapse in contracting state deleted

Ref country code: IS

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190925

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200126

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20200626

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20200229

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200212

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190925

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200229

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200229

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190925

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200212

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200229

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20220225

Year of fee payment: 7

Ref country code: DE

Payment date: 20220225

Year of fee payment: 7

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190925

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190925

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190925

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20220223

Year of fee payment: 7

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190925

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602016021197

Country of ref document: DE

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20230212

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230212

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230212

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230228

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230901