WO2019145036A1 - Procédure de commande de connexion de communication sélectionnant une tranche de connexion de communication - Google Patents

Procédure de commande de connexion de communication sélectionnant une tranche de connexion de communication Download PDF

Info

Publication number
WO2019145036A1
WO2019145036A1 PCT/EP2018/051850 EP2018051850W WO2019145036A1 WO 2019145036 A1 WO2019145036 A1 WO 2019145036A1 EP 2018051850 W EP2018051850 W EP 2018051850W WO 2019145036 A1 WO2019145036 A1 WO 2019145036A1
Authority
WO
WIPO (PCT)
Prior art keywords
function
communication
control element
request
network
Prior art date
Application number
PCT/EP2018/051850
Other languages
English (en)
Inventor
Harri POVELAINEN
Mikko Tirronen
Original Assignee
Nokia Solutions And Networks Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Solutions And Networks Oy filed Critical Nokia Solutions And Networks Oy
Priority to PCT/EP2018/051850 priority Critical patent/WO2019145036A1/fr
Publication of WO2019145036A1 publication Critical patent/WO2019145036A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration

Definitions

  • an apparatus for use by a core network control element or function configured to execute a communication connection related control for access and mobility management
  • the apparatus comprising at least one processing circuitry, and at least one memory for storing instructions to be executed by the processing circuitry, wherein the at least one memory and the instructions are configured to, with the at least one processing circuitry, cause the apparatus at least: to receive a request for establishing a communication connection for a communication element, wherein the request includes session management information comprising at least one of an access point name and a quality of service requirement indication, to select a core network control element or function for session management serving the communication element, to forward the request for establishing the communication connection to selected core network control element or function for session management, to receive, from the selected core network control element or function for session management, a rerouting indication, wherein the rerouting indication comprises network slice specific information for a specific network slice dedicated for the at least one of the access point name and the quality of service requirement indication, and an indication to
  • a computer program product for a computer including software code portions for performing the steps of the above defined methods, when said product is run on the computer.
  • the computer program product may include a computer-readable medium on which said software code portions are stored.
  • the computer program product may be directly loadable into the internal memory of the computer and/or transmittable via a network by means of at least one of upload, download and push procedures.
  • Fig. 4 shows a signaling diagram illustrating a processing for selecting a network slice for a communication connection according to some examples of embodiments
  • Fig. 6 shows a flow chart of a communication connection control procedure executed by a core network control element or function for access and mobility management like an AMF according to some examples of embodiments;
  • Fig. 7 shows a diagram of a network element or function acting as a core network control element for session management according to some examples of embodiments
  • Fig. 8 shows a diagram of a network element or function acting as a core network control element for access and mobility management according to some examples of embodiments.
  • Fig. 9 shows a diagram illustrating a communication network configuration in which examples of embodiments of the invention are implementable.
  • communication networks e.g. of wire based communication networks, such as the Integrated Services Digital Network (ISDN), DSL, or wireless communication networks, such as the cdma2000 (code division multiple access) system, cellular 3 rd generation (3G) like the Universal Mobile Telecommunications System (UMTS), fourth generation (4G) communication networks or enhanced communication networks based e.g.
  • wire based communication networks such as the Integrated Services Digital Network (ISDN), DSL
  • wireless communication networks such as the cdma2000 (code division multiple access) system, cellular 3 rd generation (3G) like the Universal Mobile Telecommunications System (UMTS), fourth generation (4G) communication networks or enhanced communication networks based e.g.
  • cdma2000 code division multiple access
  • 3G cellular 3 rd generation
  • UMTS Universal Mobile Telecommunications System
  • 4G fourth generation
  • enhanced communication networks based e.g.
  • one or more network elements or functions e.g. virtualized network functions
  • communication network control elements for example access network elements like access points, radio base stations, relay stations, eNBs, gNBs etc.
  • core network elements or functions for example control nodes, support nodes, service nodes, gateways etc., may be involved, which may belong to one communication network system or different communication network systems.
  • Next-generation (also referred to as 5G) networks will provide significant improvements for achieving a fully mobile and connected society.
  • 5G networks will provide services capable for eMBB (enhanced Mobile Broadband), mMTC (massive Machine Type Communications) and URLLC (Ultra-Reliable and Low Latency Communications), which have differing requirements for resources.
  • eMBB enhanced Mobile Broadband
  • mMTC massive Machine Type Communications
  • URLLC Ultra-Reliable and Low Latency Communications
  • Network slicing describes the idea of providing multiple isolated network slices for a variety of services on a common infrastructure in order to scale the network and guarantee best possible service efficient usage of resources. For example, slicing is based on using virtualization technology to architect, partition and organize computing and communication resources of a physical infrastructure to enable flexible support of diverse use case realizations. With network slicing, one physical network is sliced into multiple virtual networks, each architected and optimized for a specific requirement and/or specific application/service.
  • a network slice represents a logical end-to-end network that can be dynamically created.
  • a UE as a communication element can have access to multiple network slices over different or the same access network.
  • a network slice is defined within a PLMN and includes the core network control plane a user plane network functions as well as an access network, such as a NG access network or another type of access network (e.g. Wi-Fi based).
  • NSSAI in 5G networks is used for establishing PDU session (e.g. when the AMF receives a session management message from the UE), for discovering and selecting a suitable candidate SMF, and selecting a suitable user plane function (UPF) by the SMF.
  • a network repository function (NRF) is used for the discovery of the required network functions. Data transmission can take place after a PDU session to a data network is established in the network slice.
  • slice selection of devices according to the 5G specification protocols is specified by using the NSSAI.
  • legacy devices i.e. devices such as UEs or other terminal devices which are configured according to former standards, such as 4G (LTE) standards
  • LTE 4G
  • NSSAI is not provided via RRC and NAS signalling as stated in the 5G specifications.
  • 5G core network architecture is based on the concept to separate mobility management and session management functions to different network functions (i.e. AMF and SMF, respectively). Therefore, a network slice selection using information such as an APN is not directly available as the required information is not available in the AMF which is the network function performing the SMF selection, as described above.
  • a process which enables that the AMF can make the network slice selection for a UE even when no NSSAI or other slice type information is obtained from the UE (e.g. in case the UE is a LTE based UE).
  • a process is executed where an SMF asks for slice type information at a UDM. If there is a specific slice dedicated for this APN, the first SMF is able to reject the AMF request and force the AMF to reselect another SMF, wherein the slice type information received from the UDM are used as the basis for the reselection.
  • a communication network architecture as being considered in examples of embodiments may also be able to communicate with other networks, such as a public switched telephone network or the Internet.
  • the communication network may also be able to support the usage of cloud services for virtual network elements or functions thereof, wherein it is to be noted that the virtual network part of the telecommunication network can also be provided by non-cloud resources, e.g. an internal network or the like.
  • network elements of an access system, of a core network etc., and/or respective functionalities may be implemented by using any node, host, server, access node or entity etc. being suitable for such a usage.
  • a network element such as communication elements, like a UE, a terminal device, control elements or functions, such as access network elements, like a base station (BS), an gNB, a radio network controller, a core network control element or function, such as a SMF, an AMF, an UDM, a gateway element, or other network elements or functions, as described herein, and any other elements, functions or applications may be implemented by software, e.g. by a computer program product for a computer, and/or by hardware.
  • nodes, functions or network elements may include several means, modules, units, components, etc. (not shown) which are required for control, processing and/or communication/signaling functionality.
  • Such means, modules, units and components may include, for example, one or more processors or processor units including one or more processing portions for executing instructions and/or programs and/or for processing data, storage or memory units or means for storing instructions, programs and/or data, for serving as a work area of the processor or processing portion and the like (e.g. ROM, RAM, EEPROM, and the like), input or interface means for inputting data and instructions by software (e.g. floppy disc, CD- ROM, EEPROM, and the like), a user interface for providing monitor and manipulation possibilities to a user (e.g. a screen, a keyboard and the like), other interface or means for establishing links and/or connections under the control of the processor unit or portion (e.g.
  • radio interface means including e.g. an antenna unit or the like, means for forming a radio communication part etc.) and the like, wherein respective means forming an interface, such as a radio communication part, can be also located on a remote site (e.g. a radio head or a radio station etc.).
  • a remote site e.g. a radio head or a radio station etc.
  • a so-called“liquid” or flexible network concept may be employed where the operations and functionalities of a network element, a network function, or of another entity of the network, may be performed in different entities or functions, such as in a node, host or server, in a flexible manner.
  • a“division of labor” between involved network elements, functions or entities may vary case by case.
  • Fig. 1 and Fig. 9 show a respective diagram illustrating a communication network configuration in which examples of embodiments of the invention are implementable. Specifically, Figs. 1 and 9 show a respective architecture of a communication network including a next generation (5G) core network structure.
  • 5G next generation
  • next generation networks like 5G networks protocols and reference points are defined for network functions (NF) and reference points connecting NFs.
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • P-GW Packet Data Network Gateway
  • a point-to-point architecture which is the basis of the configuration of Fig. 1.
  • a service-based architecture as shown in Fig. 9. Both types of architecture comprise, more or less, the same functional elements wherein a splitting of control and user plane is considered. Furthermore, several interfaces are the same.
  • the point-to-point architecture shown in Fig. 1 is similar a traditional 3GPP architecture, as it defines functions and interfaces between them.
  • a services model is used in which components query a network repository function NRF to discover and communicate with each other.
  • This approach is more related to a cloud-native networking concept in which libraries of functions can be requested from a virtualized network function catalog and composed into end-to-end service chains on demand.
  • a network function can be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., a cloud infrastructure.
  • a communication element such as a user equipment (UE) 10 is connected to a RAN or access network (AN) 20 and to an access and mobility function (AMF) 50.
  • the RAN 20 represents a base station (BS or NB) using a NR RAT and/or an evolved LTE base station, while AN 20 is a general base station including e.g. non-3GPP access, e.g., Wi-Fi.
  • the core network architecture shown in Fig. 1 applied for a 5G network comprises various NFs.
  • the CN NFs comprises the AMF 50, a session management function (SMF) 40, a policy control function (PCF) 60, an application function (AF) 90, an authentication server function (AUSF) 70, a network slice selection function (NSSF) 75, a user plane function (UPF) 30, and a user data management (UDM) 80.
  • Further elements, which are not shown in Fig. 1 , belonging to the CN NFs include, for example, an NRF and the like which is used for providing network function related information.
  • the AMF 50 provides UE-based authentication, authorization, mobility management, etc.
  • a UE e.g. UE 10
  • a UE even using multiple access technologies is basically connected to a single AMF because the AMF 50 is independent of the access technologies.
  • the SMF 40 sets up and manages sessions according to network policy.
  • the SMF 40 is responsible, for example, for session management and allocates IP addresses to UEs. Furthermore, it selects and controls the UPF 30 for data transfer.
  • the UPF 30 can be deployed in various configurations and locations, according to the service type. Functions of the UPF 30 are e.g. QoS handling for user plane, packet routing and forwarding, packet inspection and policy rule enforcement, traffic accounting and reporting.
  • the PCF 60 provides a policy framework incorporating network slicing, roaming and mobility management, similar to a policy and charging rules function in a 4G network.
  • the AF 90 provides information on the packet flow to the PCF 60 in order to support QoS. Based on the information, the PCF 60 determines policies about mobility and session management to make the AMF 50 and the SMF 40 operate properly.
  • the AUSF 70 stores and provides data for authentication of the UE 10.
  • the NSSF 75 selects network slice instances.
  • the UDM 80 stores and provides subscription data of the UE 10, similar to a home subscriber server (FISS) in 4G networks, and also network slice specific information.
  • FISS home subscriber server
  • a data network 100 (e.g. the Internet) is shown in Fig. 1 which are not part of the core network architecture, for providing access to the Internet or to operator services.
  • N1 is defined to carry signaling between the UE 10 and the AMF 50.
  • the reference point for connecting between the RAN/AN 20 and the AMF 50 is defined as N2, and the reference point between RAN/AN 20 and the UPF 30/35 is defined as N3, respectively.
  • a reference point N11 is defined between the AMF 50 and the SMF 40 so that SMF 40 is controllable by the AMF 50.
  • Reference point N22 is defined between the AMF 50 and the NSSF 75.
  • Reference point N4 is used by the SMF 40 and the UPF 30 so that the UPF 30 can be set using the control signal generated by the SMF 40, and the UPF 30 can report its state to the SMF 40.
  • Reference point N9 is the reference point for the connection between different UPFs
  • reference point N14 is the reference point connecting between different AMFs, respectively.
  • Reference point N15 and N7 are defined for connecting the PCF 60 to the AMF 50 and the SMF 40, respectively, so that the PCF 60 can apply policy to the AMF 50 and the SMF 40, respectively.
  • Reference point N12 to AUSF 70 is required for the AMF 50 to perform authentication of the UE 10.
  • Reference points N8 and N10 are defined because the subscription data of the UE 10 is required for the AMF 50 and the SMF 40, respectively.
  • Reference point N5 is defined for connecting between the AF 90 and the PCF 60
  • reference point N13 is defined for connecting between the AUSF 70 and the UDM 80.
  • Reference points N6 are defined for connecting between the UPF 30 and the DN 100.
  • the service-based architecture shown in Fig. 9 basically the same functional elements and the same user-plane processing path between the UE 10 and external data network 100 are provided.
  • the major difference of the architecture according to Fig. 9 is in the control plane, where, instead of predefined interfaces between the elements/functions, a services model is used in which the components query the NRF to discover and communicate with each other. That is, in the configuration according to Fig. 9, the NRF 77 and a NEF 76 are illustrated.
  • NRF 77 and the NSSF 75 can be the same or separate elements or functions. Furthermore, even though NEF 76 and NRF 77 are not illustrated in the point-to-point architecture as shown in Fig. 1 , NEF and NRF elements or functions can be also included therein; all depicted network functions can interact with the NEF and NRF as necessary.
  • the network function NSSF 75 is linked to other network functions via Nnssf interface
  • the network function NEF 76 is linked to other network functions via Nnef interface
  • the network function NRF 76 is linked to other network functions via Nnrf interface
  • the network function PCF 60 is linked to other network functions via Npcf interface
  • the network function UDM 80 is linked to other network functions via Nudm interface
  • the network function AF 90 is linked to other network functions via Naf interface
  • the network function AUSF 70 is linked to other network functions via Nausf interface
  • the network function AMF 50 is linked to other network functions via Namf interface
  • the network function SMF 40 is linked to other network functions via Nsmf interface.
  • a separation of control plane and the user plane is considered.
  • the user plane carries user traffic while the control plane carries signaling in the network.
  • the UPF 30 is in the user plane and the AMF 50, the SMF 40, the PCF 60, the AF 90, the AUSF 70, the NSSF and the UDM 80 are in the control plane (the same applies for the NRF (not shown).
  • Separating the user and control planes guarantees each plane resources to be scaled independently. It also allows UPFs to be deployed separately from control plane functions in a distributed fashion. For example, UPFs can be deployed very close to RAN or UEs to shorten a round trip time (RTT) between the UE and data network for some applications requiring low latency.
  • RTT round trip time
  • each NF interacts with another NF directly, but it is also possible that an intermediate function is used for routing messages from one NF to another NF.
  • an intermediate function is used for routing messages from one NF to another NF.
  • a set of interactions between two NFs is defined as service so that its reuse is possible.
  • the user plane supports interactions such as forwarding operations between different UPFs.
  • the core network control elements and functions are able to handle also messages being configured according to non-5G specifications, such as LTE S1 AP and NAS messages.
  • non-5G specifications such as LTE S1 AP and NAS messages.
  • This is beneficial to be able to gain the benefit of the 5G network functions (i.e. scaling, slicing, etc.) also for non-5G devices, such as LTE devices.
  • Fig. 2 shows a signaling diagram illustrating a processing for selecting a network slice for a communication connection according to some examples of embodiments.
  • a situation is illustrated where the UE 10 initially requests for establishing a communication connection with the communication network as depicted in Fig. 1 (or Fig. 9), i.e. with the 5G network.
  • the UE 10 is, for example, an LTE device, i.e. the communication network is of a first type (e.g. 5G) and the communication device is configured for a second type of communication network, e.g. an LTE network or another network type.
  • examples of embodiments of the invention are related to a case where the UE is not prepared to provide information assisting in the network slice selection, such as NSSAI, when requesting to establish a communication connection.
  • the UE 10 requests for a new PDN connection in an initial attach.
  • a UE has to register with the network to receive services that require registration. This registration is also referred to as initial network attachment.
  • the UE 10 e.g. an LTE UE
  • the core network control element or function communicating with the UE 10 on the control plane is the AMF 50. That is, the UE 10 requests in S10 for a new PDN connection in the initial attach.
  • This request is accompanied by session management information; for example, the UE 10 sends also a request that it is to be connected to a specific APN.
  • the request should be decoded in the SMF 40.
  • the AMF 50 conducts a selection processing for selecting the SMF to which the request is to be forwarded.
  • Fig. 2 is related to a case where an initial attach is conducted. Because of this, the AMF 50 selects a default SMF as the target for forwarding the initial PDN Connectivity Request.
  • S30 information related to the request received from the UE 10 in S10 are forwarded to the selected SMF (e.g. SMF 40) via N11 interface.
  • the session management information contained in the request e.g. ESM
  • the APN information is retrieved.
  • the (default) SMF 40 conducts a processing for checking whether there is a specific network slice allocated to this APN.
  • the SMF 40 sends to the UDM 80 a signaling being, for example, the 5G equivalent to an ULR signaling which includes the information retrieved from the session management information, i.e. the APN in this example.
  • the UDM is asked whether there is a specific slice allocated for the APN the UE has requested.
  • the UDM 80 responds in S55 to the ULR by sending a signaling being, for example, the 5G equivalent to an ULA signaling.
  • a signaling being, for example, the 5G equivalent to an ULA signaling.
  • the SMF 40 can determine whether there is a specific network slice allocated to the APN.
  • the SMF 40 When the ULA in S55 indicates that there is no network slice allocated to the APN, the SMF 40 continue with a processing related to the attach request as the serving SMF. That is, a connection establishing procedure is conducted in a normal manner. A corresponding example of such a processing is discussed in connection with S90, for example.
  • the processing in the (default) SMF is different.
  • the ULA in S55 contains information indicating the target slice type.
  • the ULA includes subscriber profile information.
  • the AMF When receiving the rerouting indication, the AMF starts a processing for forwarding the request to the correct SMF (in the example of Fig. 2 this is for example a network element or function for session management in a eMBB scenario, which is referred to as SMF for eMBB).
  • the slice type information received from the SMF 40 in S60 are used to request from the NRF_NSSF slice specific SMF information, i.e. the AMF requests information allowing to contact the SMF for eMBB.
  • the AMF 50 sends a discover request to the NRF_NSSF which includes the target slice type.
  • the NRF_NSSF answers in S75 with a discover response signaling in which the slice specific SMF information is included. That is, in the processing of S70 and S75, the AMF 50 request for information about the SMF (for eMBB) for this specific slice type from the NRF NSSF.
  • the AMF 50 When having received the information in S75, the AMF 50 continues the attach procedure with the slice specific SMF (SMF for eMBB) by forwarding in S80 the request for establishing the communication connection.
  • This request in S80 contains also the subscriber information; that is, it is not necessary to obtain (once more) the subscriber information (e.g. by using an ULR/ULA signaling with the UDM) since the required information is available already in the signaling of S60.
  • the attach procedure started in S10 is continued, wherein the SMF for eMBB is now acting as the serving SMF.
  • an initial context is setup and a RRC connection is configured between the UE 10, the RAN 20 and the core network control elements or functions (e.g. the AMF/SMF and the UPF), so that a data transfer (i.e. uplink data and downlink data) can be started.
  • Fig. 3 shows a signaling diagram illustrating another processing for selecting a network slice for a communication connection according to some examples of embodiments.
  • a situation is illustrated where after the initial attach (e.g. processing of Fig. 2) the UE 10 requests for additional PDN connections for different APNs.
  • the network is a communication network is of a first type (e.g. 5G) and the communication device (UE 10) is configured for a second type of communication network, e.g. an LTE network or another network type.
  • the UE 10 requests for an additional PDN connectivity to an additional APN including allocation of a default bearer.
  • the UE 10 requests, after the initial attach, for additional PDN connections for different APNs.
  • the UDM allocate the new slice type and includes corresponding target slice type information (together with subscriber profile information) in the ULA in S155.
  • Fig. 4 shows a signaling diagram illustrating another processing for selecting a network slice for a communication connection according to some examples of embodiments.
  • a situation is illustrated where the UE 10 requests for a dedicated bearer with specific QoS requirements. That is, in the example according to Fig. 4, QoS information instead of APN information are provided by the UE 10 for the further processing.
  • the network in the example of Fig. 4 is a communication network is of a first type (e.g. 5G) and the communication device (UE 10) is configured for a second type of communication network, e.g. an LTE network or another network type.
  • a first type e.g. 5G
  • the communication device UE 10
  • a second type of communication network e.g. an LTE network or another network type.
  • the UE 10 sends a bearer resource allocation request to the core network via the access network, e.g. via the RAN 20, i.e. to the AMF 50 as the core network control element or function communicating with the UE 10 on the control plane.
  • This request comprises session management information, i.e. QoS requirements which the UE 10 is requesting, which should be decoded in the SMF.
  • the AMF 50 selects the serving SMF to which the request is to be forwarded.
  • the serving SMF can be e.g. the default SMF 40 or the slice specific SMF ( SMF for eMBB).
  • the serving SMF is the SMF for eMBB.
  • information related to the request received from the UE 10 in S210 is forwarded to the serving SMF via N11 interface.
  • the session management information contained in the request e.g. ESM
  • the QoS requirement information is retrieved.
  • the SMF for eMBB conducts a processing for checking whether the there is a different network slice type for the QoS requirement, compared to the one the UE 10 is already connected to (via the SMF for eMBB).
  • the UDM 80 responds in S255 to the ULR by sending an ULA.
  • the SMF for eMBB can determine whether there is a different network slice allocated to the QoS in question.
  • the UDM allocates the new slice type and includes corresponding target slice type information (together with subscriber profile information) in the ULA in S255.
  • the UDM uses QoS information instead of APN to make selection of the slice type.
  • the AMF 50 When receiving the rerouting indication, the AMF 50 starts a processing for forwarding the request to the correct SMF (in the example of Fig. 4 this is referred to as SMF for URLLC). That is, the slice type information received from the SMF in S260 are used to request from the NRF_NSSF slice specific SMF information, i.e. the AMF 50 requests information allowing to contact the SMF for URLLC. For example, in S270, the AMF 50 sends a discover request to the NRF NSSF which includes the target slice type. The NRF_NSSF answers in S275 with a discover response signaling in which the slice specific SMF information is included. That is, in the processing of S270 and S275, the AMF 50 requests information about the SMF for URLLC for the new slice type from the NRF NSSF.
  • the AMF 50 continues the procedure with the slice specific SMF (SMF for URLLC) by forwarding in S280 the request for establishing the communication connection.
  • This request in S280 contains also the subscriber information; that is, it is not necessary to obtain (once more) the subscriber information (e.g. by using an ULR/ULA signaling with the UDM) since the required information is available already in the signaling of S260.
  • the procedure started in S210 is continued for creating a dedicated bearer, wherein the SMF for URLLC is now acting as the serving SMF.
  • this bearer creation procedure for example, RRC connection is reconfigured between the UE 10, the RAN 20 and the core network control elements or functions (e.g. the AMF/SMF and the UPF), and a bearer is setup.
  • a container may be used for AMF-specific subscriber information and another container may be used for SMF-specific subscriber information.
  • These containers can be requested by the AMF or pushed by the UDM.
  • Subscriber information for a UE is transported from the UDM to the AMF by using such transparent containers.
  • the AMF decodes the AMF-specific subscriber information received via the transparent containers during a registration procedure, and subsequently provides the SMF-specific subscriber information to the SMF over an interface, e.g. during a PDU session creation procedure.
  • a transparent container can be established over N11 interface between the AMF and the SMF for conveying the subscriber information associated with the UE.
  • Fig. 5 shows a flow chart of a communication connection control procedure executed by a core network control element or function for session management like the SMF 40 shown in Fig. 1 (or Fig. 9), according to some examples of embodiments.
  • a request for establishing a communication connection for a communication element is received, for example, from a core network control element or function for access and mobility management, like the AMF 50.
  • the request includes session management information comprising at least one of an access point name and a QoS requirement indication.
  • the request for establishing the communication connection comprises one of an initial attach request of the UE, a PDN connectivity request, and a request for allocating a communication network resource, such as a dedicated bearer.
  • the request is processed by decoding the session management information for obtaining the at least one of the access point name and the quality of service requirement indication.
  • a specific network slice dedicated for the obtained at least one of the access point name and the QoS requirement indication is present by means of the following processing.
  • the obtained at least one of the access point name and the QoS requirement indication is sent to a control element or function for unified data management, such as UDM 80.
  • an answer from the UDM 80 is received which is processed for determining the presence of such a specific network slice.
  • the specific network slice dedicated for the obtained at least one of the access point name and the QoS requirement indication is determined to be present when the answer includes corresponding target slice information and subscriber information. That is, in S330, based on S320, in case it is determined that a specific network slice is present for the obtained at least one of the access point name and the QoS requirement indication, the process is directed to S340.
  • a rerouting indication is sent to the AMF 50, wherein the rerouting indication comprises network slice specific information and an indication to reroute the request for establishing the communication connection. That is, according to some examples of embodiments, the target slice information and the subscriber information received from the UDM 80 are included in the rerouting indication to be sent to the AMF 50.
  • a communication with the control element or function for unified data management is executed by using an update location related signaling (i.e. ULR and ULA, for example).
  • ULR and ULA update location related signaling
  • a signaling between the UDM 80 and the SMF 40 (or the AMF 50) for providing subscriber information by using a signaling container is executed.
  • the process when it is determined in S320 and S330 that there is no specific network slice dedicated for the obtained at least one of the access point name and the QoS requirement indication, e.g. when the answer includes no target slice information, the process is directed from S330 to S350.
  • the SMF 40 conducts a processing for establishing the communication connection according to the request (i.e. the SMF receiving the request in S300 is the serving SMF for the communication establishment, such as initial attach, PDN connectivity, etc.).
  • the above described processing according to S300 to S350 is executed by a core network control element or function for session management like the SMF 40 which is configured to control a communication connection in a communication network of a first type, such as in a 5G network.
  • the communication element like the UE 10 for which the communication connection is established is configured for a communication in a communication network of a second type being different to the first type, such as in a 4G or LTE based network (i.e. an LTE UE).
  • Fig. 6 shows a flow chart of a communication connection control procedure executed by a core network control element or function for access and mobility management like the AMF 50 according to some examples of embodiments.
  • a request for establishing a communication connection for a communication element is received, wherein the request includes session management information comprising at least one of an access point name and a QoS requirement indication.
  • the request for establishing the communication connection comprises one of an initial attach request of the UE 10, a PDN connectivity request, and request for allocating a communication network resource, such as a dedicated bearer.
  • a core network control element or function for session management i.e. an SMF for serving the UE 10 is selected.
  • the request for establishing the communication connection is forwarded to the selected core network control element or function for session management.
  • a core network control element or function for session management serving the UE 10 one of a default core network control element or function for session management (e.g. SMF 40) and a previously determined core network control element or function for session management related to a network slice (such as the SMF for eMBB shown in Figs. 2 to 4) is selected by the AMF 50.
  • a default core network control element or function for session management e.g. SMF 40
  • a previously determined core network control element or function for session management related to a network slice such as the SMF for eMBB shown in Figs. 2 to 4
  • the AMF 50 receives from the selected core network control element or function for session management a rerouting indication.
  • the rerouting indication comprises network slice specific information for a specific network slice dedicated for the at least one of the access point name and the QoS requirement indication, and an indication to reroute the request for establishing the communication connection.
  • the AMF 50 is forced to reselect another SMF.
  • the AMF 50 conducts a processing for establishing the communication connection with the new core network control element or function for session management related to the dedicated network slice.
  • a processing for establishing the communication connection with the (currently) serving core network control element or function for session management. is executed, which is similar to the processing of S450.
  • the above described processing according to S400 to S450 is executed by a core network control element or function for access and mobility management like the AMF 50 which is configured to control a communication connection in a communication network of a first type, such as in a 5G network.
  • the communication element like the UE 10 for which the communication connection is established is configured for a communication in a communication network of a second type being different to the first type, such as in a 4G or LTE based network (i.e. an LTE UE).
  • Fig. 7 shows a diagram of a network element or function acting as a core network control element for session management according to some examples of embodiments, e.g. the SMF 40 of Fig. 1 (or Fig.
  • control element or function like the SMF 40 of Fig. 1 (or Fig. 9), may include further elements or functions besides those described herein below.
  • the element or function may be also another device or function having a similar task, such as a chipset, a chip, a module, an application etc., which can also be part of a network element or attached as a separate element to a network element, or the like.
  • each block and any combination thereof may be implemented by various means or their combinations, such as hardware, software, firmware, one or more processors and/or circuitry.
  • the network control element like the SMF 40 shown in Fig. 7 may include a processing circuitry, a processing function, a control unit or a processor 401 , such as a CPU or the like, which is suitable for executing instructions given by programs or the like related to the communication connection control procedure.
  • the processor 401 may include one or more processing portions or functions dedicated to specific processing as described below, or the processing may be run in a single processor or processing function. Portions for executing such specific processing may be also provided as discrete elements or within one or more further processors, processing functions or processing portions, such as in one physical processor like a CPU or in one or more physical or virtual entities, for example.
  • Reference signs 402 and 403 denote input/output (I/O) units or functions (interfaces) connected to the processor or processing function 401.
  • the I/O units 402 may be used for communicating with the AMF, as described in connection with Fig. 1 (or Fig. 9), for example.
  • the I/O units 403 may be used for communicating with the UDM, as described in connection with Fig. 1 (or Fig. 9), for example.
  • the I/O units 402 and 403 may be a combined unit including communication equipment towards several entities, or may include a distributed structure with a plurality of different interfaces for different entities.
  • Reference sign 404 denotes a memory usable, for example, for storing data and programs to be executed by the processor or processing function 401 and/or as a working storage of the processor or processing function 401. It is to be noted that the memory 404 may be implemented by using one or more memory portions of the same or different type of memory.
  • the processor or processing function 401 is configured to execute processing related to the above described communication connection control processing.
  • the processor or processing circuitry or function 401 includes one or more of the following sub-portions.
  • Sub-portion 4011 is a processing portion which is usable as a portion for receiving a connection establishing request.
  • the portion 4011 may be configured to perform processing according to S300 of Fig. 5.
  • the processor or processing circuitry or function 401 may include a sub-portion 4012 usable as a portion for processing the request.
  • the portion 4012 may be configured to perform a processing according to S310 of Fig. 5.
  • the processor or processing circuitry or function 401 may include a sub-portion 4013 usable as a portion for checking the presence of a dedicated network slice.
  • the portion 4013 may be configured to perform a processing according to S320 and S330 of Fig. 5.
  • the processor or processing circuitry or function 401 may include a sub-portion 4014 usable as a portion for sending the rerouting indication.
  • the portion 4014 may be configured to perform a processing according to S340 of Fig. 5.
  • the processor or processing circuitry or function 401 may include a sub-portion 4015 usable as a portion for conducting a processing for establishing a communication connection.
  • the portion 4015 may be configured to perform a processing according to S350 of Fig. 5.
  • Fig. 8 shows a diagram of a network element or function acting as a core network control element for access and mobility management according to some examples of embodiments, e.g. the AMF 50 of Fig. 1 (or Fig. 9), which is configured to conduct a communication connection control procedure as described in connection with some of the examples of embodiments.
  • the network element or function like the AMF 50 of Fig. 1 (or Fig. 9), may include further elements or functions besides those described herein below.
  • the element or function may be also another device or function having a similar task, such as a chipset, a chip, a module, an application etc., which can also be part of a network element or attached as a separate element to a network element, or the like.
  • each block and any combination thereof may be implemented by various means or their combinations, such as hardware, software, firmware, one or more processors and/or circuitry.
  • the network element 50 like the AMF shown in Fig. 8 may include a processing circuitry, a processing function, a control unit or a processor 501 , such as a CPU or the like, which is suitable for executing instructions given by programs or the like related to the communication connection control procedure.
  • the processor 501 may include one or more processing portions or functions dedicated to specific processing as described below, or the processing may be run in a single processor or processing function. Portions for executing such specific processing may be also provided as discrete elements or within one or more further processors, processing functions or processing portions, such as in one physical processor like a CPU or in one or more physical or virtual entities, for example.
  • Reference signs 502 and 503 denotes input/output (I/O) units or functions (interfaces) connected to the processor or processing function 501.
  • the I/O units 502 may be used for communicating with the UE and RAN, as described in connection with Fig. 1 (or Fig. 9), for example.
  • the I/O units 503 may be used for communicating with the CN control elements and functions, such as the SMF 40 and the NRF/NSSF, as described in connection with Fig. 1 (or Fig. 9), for example.
  • the I/O units 502 and 503 may be a combined unit including communication equipment towards several entities, or may include a distributed structure with a plurality of different interfaces for different entities.
  • Reference sign 504 denotes a memory usable, for example, for storing data and programs to be executed by the processor or processing function 501 and/or as a working storage of the processor or processing function 301. It is to be noted that the memory 504 may be implemented by using one or more memory portions of the same or different type of memory.
  • the processor or processing function 501 is configured to execute processing related to the above described communication connection control processing.
  • the processor or processing circuitry or function 501 includes one or more of the following sub-portions.
  • Sub-portion 5011 is a processing portion which is usable as a portion for receiving a connection establishing request.
  • the portion 5011 may be configured to perform processing according to S400 of Fig. 6.
  • the processor or processing circuitry or function 5010 may include a sub-portion 5012 usable as a portion for conducting a SMF selection and forwarding the request.
  • the portion 5012 may be configured to perform a processing according to S410 or S440 of Fig. 6.
  • the processor or processing circuitry or function 5010 may include a sub-portion 5013 usable as a portion for receiving and processing a rerouting indication.
  • the portion 5013 may be configured to perform a processing according to S420 of Fig. 6.
  • the processor or processing circuitry or function 5010 may include a sub-portion 5014 usable as a portion for obtaining SMF information.
  • the portion 5014 may be configured to perform a processing according to S430 of Fig. 6.
  • the processor or processing circuitry or function 5010 may include a sub-portion 5015 usable as a portion for conducting a connection establishing processing.
  • the portion 5015 may be configured to perform a processing according to S450 of Fig. 6.
  • a method which uses the access and mobility management function (AMF) for making a slice selection without NSSAI or other slice type information from the UE (e.g. LTE UE).
  • LTE UE requests for new packet data network (PDN) connection in the initial attach it also requests to be connected to a specific APN which is decoded in the session management function (SMF).
  • SMF session management function
  • QoS quality of service
  • APN access point name
  • SMF can ask slice type information from the unified data management (UDM). If there is a specific slice dedicated for this APN or specific QoS requirements, then the SMF delivers this information to the AMF.
  • the AMF can request an SMF for this specific slice type from the NRF and continue the attach procedure with the slice specific SMF, so that the AMF is forced to do an SMF reselection with slice type information received from the UDM.
  • an apparatus for use by a core network control element or function configured to execute a communication connection related control for session management comprising means configured to receive a request for establishing a communication connection for a communication element, wherein the request includes session management information comprising at least one of an access point name and a quality of service requirement indication, means configured to process the request by decoding the session management information for obtaining the at least one of the access point name and the quality of service requirement indication, means configured to check whether a specific network slice dedicated for the obtained at least one of the access point name and the quality of service requirement indication is present, and means configured send, in case a specific network slice is dedicated for the obtained at least one of the access point name and the quality of service requirement indication, a rerouting indication to a communication network control element or function for access and mobility management, wherein the rerouting indication comprises network slice specific information and an indication to reroute the request for establishing the communication connection.
  • the above defined apparatus may further comprise means for conducting at least one of the processing defined in the above described methods, for example a method according that described in connection with Fig 5.
  • an apparatus for use by a core network control element or function configured to execute a communication connection related control for access and mobility management comprising means configured to receive a request for establishing a communication connection for a communication element, wherein the request includes session management information comprising at least one of an access point name and a quality of service requirement indication, means configured to select a core network control element or function for session management serving the communication element, means configured to forward the request for establishing the communication connection to selected core network control element or function for session management, means configured to receive, from the selected core network control element or function for session management, a rerouting indication, wherein the rerouting indication comprises network slice specific information for a specific network slice dedicated for the at least one of the access point name and the quality of service requirement indication, and an indication to reroute the request for establishing the communication connection, means configured to obtain information indicating a new core network control element or function for session management related to a dedicated network slice, means configured forward the request for establishing
  • the above defined apparatus may further comprise means for conducting at least one of the processing defined in the above described methods, for example a method according that described in connection with Fig 6.
  • an access technology via which traffic is transferred to and from an entity in the communication network may be any suitable present or future technology, such as WLAN (Wireless Local Access Network), WiMAX (Worldwide Interoperability for Microwave Access), LTE, LTE-A, 5G, Bluetooth, Infrared, and the like may be used; additionally, embodiments may also apply wired technologies, e.g. IP based access technologies like cable networks or fixed lines.
  • WLAN Wireless Local Access Network
  • WiMAX Worldwide Interoperability for Microwave Access
  • LTE Long Term Evolution
  • LTE-A Fifth Generation
  • 5G Fifth Generation
  • Bluetooth Infrared
  • wired technologies e.g. IP based access technologies like cable networks or fixed lines.

Landscapes

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

Abstract

La présente invention concerne un appareil destiné à être utilisé par un élément de commande de réseau central ou une fonction configurée pour exécuter une connexion de communication associée à une commande pour une gestion de session, l'appareil comprenant au moins un ensemble de circuits de traitement, et au moins une mémoire pour stocker des instructions à exécuter au moyen de l'ensemble de circuits de traitement, ladite mémoire et les instructions étant configurées pour, avec ledit ensemble de circuits de traitement, entraîner l'appareil à au moins : recevoir une demande pour établir une connexion de communication pour un élément de communication, la demande comprenant des informations de gestion de session comprenant au moins un élément parmi un nom de point d'accès et une qualité d'indication d'exigence de service, traiter la demande en décodant les informations de gestion de session pour obtenir ledit élément parmi le nom de point d'accès et la qualité d'indication d'exigence de service, vérifier si une tranche de réseau spécifique dédiée pour ledit élément obtenu parmi le nom de point d'accès et la qualité d'indication d'exigence de service est présente, et dans le cas où une tranche de réseau spécifique est dédiée pour ledit élément obtenu parmi le nom de point d'accès et la qualité d'indication d'exigence de service, envoyer une indication de réacheminement à un élément de commande de réseau de communication ou une fonction pour accéder et une gestion de mobilité, l'indication de réacheminement comprenant des informations spécifiques de tranche de réseau et une indication pour réacheminer la demande pour établir la connexion de communication.
PCT/EP2018/051850 2018-01-25 2018-01-25 Procédure de commande de connexion de communication sélectionnant une tranche de connexion de communication WO2019145036A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2018/051850 WO2019145036A1 (fr) 2018-01-25 2018-01-25 Procédure de commande de connexion de communication sélectionnant une tranche de connexion de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2018/051850 WO2019145036A1 (fr) 2018-01-25 2018-01-25 Procédure de commande de connexion de communication sélectionnant une tranche de connexion de communication

Publications (1)

Publication Number Publication Date
WO2019145036A1 true WO2019145036A1 (fr) 2019-08-01

Family

ID=61132417

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2018/051850 WO2019145036A1 (fr) 2018-01-25 2018-01-25 Procédure de commande de connexion de communication sélectionnant une tranche de connexion de communication

Country Status (1)

Country Link
WO (1) WO2019145036A1 (fr)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021096222A1 (fr) * 2019-11-14 2021-05-20 Samsung Electronics Co., Ltd. Appareil et procédé pour réaliser l'interfonctionnement de tranches de réseau dans un système de communication sans fil
CN113316098A (zh) * 2021-04-20 2021-08-27 新华三技术有限公司 一种建立业务通道、公网对讲的方法和公网对讲设备
CN113365285A (zh) * 2020-03-03 2021-09-07 华为技术有限公司 一种确定策略控制网元的方法、装置和系统
CN113498117A (zh) * 2020-03-20 2021-10-12 中国电信股份有限公司 切换网络切片的方法、装置、通信系统及存储介质
CN113596909A (zh) * 2020-04-30 2021-11-02 华为技术有限公司 通信方法、装置及系统
CN113872981A (zh) * 2021-09-30 2021-12-31 阿里巴巴达摩院(杭州)科技有限公司 核心网和通信网络
WO2022155853A1 (fr) * 2021-01-21 2022-07-28 华为技术有限公司 Procédé de communication sans fil, appareil de communication et système de communication
WO2022238910A1 (fr) * 2021-05-11 2022-11-17 Telefonaktiebolaget Lm Ericsson (Publ) Cadriciel pour une gestion dynamique de ressources dans une tranche partagée
US11516677B2 (en) * 2018-04-09 2022-11-29 Huawei Technologies Co., Ltd. Communication method, apparatus, and system

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170070892A1 (en) * 2015-09-07 2017-03-09 Electronics And Telecommunications Research Institute Mobile communication network system and method for composing network component configurations
US20170367036A1 (en) * 2016-06-15 2017-12-21 Convida Wireless, Llc Network Slice Discovery And Selection

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170070892A1 (en) * 2015-09-07 2017-03-09 Electronics And Telecommunications Research Institute Mobile communication network system and method for composing network component configurations
US20170367036A1 (en) * 2016-06-15 2017-12-21 Convida Wireless, Llc Network Slice Discovery And Selection

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 15)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 23.502, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V15.0.0, 22 December 2017 (2017-12-22), pages 1 - 258, XP051392102 *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 23.501, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V15.0.0, 22 December 2017 (2017-12-22), pages 1 - 181, XP051392101 *

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11516677B2 (en) * 2018-04-09 2022-11-29 Huawei Technologies Co., Ltd. Communication method, apparatus, and system
US11558910B2 (en) 2019-11-14 2023-01-17 Samsung Electronics Co., Ltd. Apparatus and method for providing interworking of network slices in wireless communication system
WO2021096222A1 (fr) * 2019-11-14 2021-05-20 Samsung Electronics Co., Ltd. Appareil et procédé pour réaliser l'interfonctionnement de tranches de réseau dans un système de communication sans fil
CN113365285A (zh) * 2020-03-03 2021-09-07 华为技术有限公司 一种确定策略控制网元的方法、装置和系统
CN113498117A (zh) * 2020-03-20 2021-10-12 中国电信股份有限公司 切换网络切片的方法、装置、通信系统及存储介质
WO2021218244A1 (fr) * 2020-04-30 2021-11-04 华为技术有限公司 Procédé, appareil et système de communication
CN113596909A (zh) * 2020-04-30 2021-11-02 华为技术有限公司 通信方法、装置及系统
CN113596909B (zh) * 2020-04-30 2023-04-04 华为技术有限公司 通信方法、装置及系统
WO2022155853A1 (fr) * 2021-01-21 2022-07-28 华为技术有限公司 Procédé de communication sans fil, appareil de communication et système de communication
CN113316098A (zh) * 2021-04-20 2021-08-27 新华三技术有限公司 一种建立业务通道、公网对讲的方法和公网对讲设备
WO2022238910A1 (fr) * 2021-05-11 2022-11-17 Telefonaktiebolaget Lm Ericsson (Publ) Cadriciel pour une gestion dynamique de ressources dans une tranche partagée
CN113872981A (zh) * 2021-09-30 2021-12-31 阿里巴巴达摩院(杭州)科技有限公司 核心网和通信网络
CN113872981B (zh) * 2021-09-30 2023-11-07 阿里巴巴达摩院(杭州)科技有限公司 核心网和通信网络

Similar Documents

Publication Publication Date Title
WO2019145036A1 (fr) Procédure de commande de connexion de communication sélectionnant une tranche de connexion de communication
EP3709711B1 (fr) Obtenir et transmettre des informations sur une correspondance entre une session pdu et une tranche de réseau
JP6724232B2 (ja) 無線通信システムにおけるネットワークスライスベースのｎｒのためのセル特定手順を実行する方法及び装置
US11265808B2 (en) Adaptive network slice selection
US10979886B2 (en) UE configuration and update with network slice selection policy
EP3777340A1 (fr) Sélection de tranches de réseau isolées
CN112313980A (zh) 动态rfsp
CN110662274A (zh) 存取网络切片的方法及使用其方法的用户装置
JP7135122B2 (ja) リダイレクション方法、通信システム及び通信装置
CN111567082A (zh) Lte与nr之间的业务引导
EP4042830A1 (fr) Sessions pdu commandées par l'équipement d'utilisateur dans une tranche de réseau
US11979943B2 (en) PCI configuration and mobility robustness optimization son functionality for 5G networks
US11516645B2 (en) Cross-agency communication through an ad-hoc network slice
JP2023015240A (ja) コアネットワークノード及び冗長ｕｒｌｌｃ接続に対応する方法
EP4222992A1 (fr) Influence de la fonction d'application dans la relocalisation d'un contexte d'application
US11641602B2 (en) Systems and methods for handover of dual connectivity user equipment
CN113785613A (zh) Vplmn策略控制
CN107079047A (zh) 用于网络辅助的域选择的装置和方法
WO2019122497A1 (fr) Procédure de commande de connexion de communication utilisant des tranches de connexion de communication sélectionnées
WO2020049347A1 (fr) Transfert de session vocale de réseau local sans fil (wlan) à cellulaire déclenché par l'utilisateur
EP4255001A1 (fr) Mécanisme d'accès à des données d'abonnement
CN113473564B (zh) 网络切片切换的方法、建立pdu会话的方法及装置
EP4262244A1 (fr) Procédé et dispositif de détermination de point d'accès mec
WO2022078575A1 (fr) Mécanisme pour exposition directe d'événement
WO2023041174A1 (fr) Coordination dccf-dccf

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18702458

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18702458

Country of ref document: EP

Kind code of ref document: A1