WO2019086129A1 - Fourniture de données d'abonné à partir d'un gestionnaire de données unifié dans des contenants transparents - Google Patents

Fourniture de données d'abonné à partir d'un gestionnaire de données unifié dans des contenants transparents Download PDF

Info

Publication number
WO2019086129A1
WO2019086129A1 PCT/EP2017/078270 EP2017078270W WO2019086129A1 WO 2019086129 A1 WO2019086129 A1 WO 2019086129A1 EP 2017078270 W EP2017078270 W EP 2017078270W WO 2019086129 A1 WO2019086129 A1 WO 2019086129A1
Authority
WO
WIPO (PCT)
Prior art keywords
amf
smf
subscriber information
specific subscriber
pairs
Prior art date
Application number
PCT/EP2017/078270
Other languages
English (en)
Inventor
Harri POVELAINEN
Mikko Tirronen
Original Assignee
Nokia Technologies 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 Technologies Oy filed Critical Nokia Technologies Oy
Priority to PCT/EP2017/078270 priority Critical patent/WO2019086129A1/fr
Publication of WO2019086129A1 publication Critical patent/WO2019086129A1/fr

Links

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
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/14—Backbone network devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/24—Interfaces between hierarchically similar devices between backbone network devices

Definitions

  • 5G communication systems are expected to enable applications such as virtual reality, augmented reality, reliable remote operation of machines, factory automation, network-assisted control of traffic and self-driving vehicles, and the cellular "Internet of Things (IoT)" that supports internetworking of physical devices such as appliances, vehicles, buildings, and other items that are embedded with electronics, software, sensors, actuators, and network connectivity that enable the devices to collect and exchange data over the Internet.
  • IoT Internet of Things
  • Future 5G communication systems will therefore be required to support gigabit per second data rates (e.g., to support virtual or augmented reality applications), end-to-end latencies of at most 1 millisecond (ms) (e.g., to support factory automation applications), reliabilities of at least 99.999% (e.g., for automotive traffic control applications such as platooning), and user equipment densities of tens of millions of devices per square kilometer (e.g., to support cellular IoT applications).
  • Communication systems that operate according to the 5G standards are also expected to provide wireless access and fixed (or wired) access on an equal footing, which is referred to herein as fixed-mobile convergence. User equipment will therefore be able to perform hybrid access by connecting to the 5G communication system via concurrent fixed and wireless connections.
  • FIG. 1 is a block diagram of a communication system that supports providing subscriber data in transparent containers according to some embodiments.
  • FIG. 2 is a block diagram of a network function virtualization (NFV) architecture according to some embodiments.
  • NFV network function virtualization
  • FIG. 3 is a message flow that depicts messaging exchanged between a user equipment (UE), an access and mobility management function (AMF), an authentication service function (AUSF), and a unified data manager (UDM)according to some embodiments.
  • UE user equipment
  • AMF access and mobility management function
  • AUSF authentication service function
  • UDM unified data manager
  • FIG. 4 is a message flow that depicts messaging exchanged between a UE, an AMF, a session management function (SMF), and a UDM according to some
  • User equipment are required to register with a network in order to be authorized to receive services provided by the network, to enable mobility tracking, and to enable reachability. Registration procedures are used when the user equipment initially attaches to the network, as well as during mobility related events and in response to other events.
  • 5G Fifth Generation
  • user equipment registration involves messages exchanged between an access and mobility management function (AMF), a session management function (SMF), an authentication service function (AUSF), and a unified data manager (UDM).
  • AMF access and mobility management function
  • SMF session management function
  • AUSF authentication service function
  • UDM unified data manager
  • the AMF requests subscriber authentication information for the user equipment from AUSF over the N12 interface which communicates with the UDM over the N13 interface.
  • the AMF communicates directly with the UDM over the N8 interface to get the registration information.
  • the SMF separately requests subscription information for the user equipment over a second (N10) interface the UDM during a protocol data unit (PDU) session establishment procedure.
  • PDU protocol data unit
  • the AMF subsequently provides the SMF-specific subscriber information to the SMF over a third interface during the PDU session creation procedure.
  • the messages transmitted via the first and second transparent container pairs include messages encoded for transmission over a fourth interface between the AMF and the UDM or a fifth interface between the SMF and the UDM.
  • a third transparent container is established over a third interface (Ni l) between the AMF and the SMF for conveying the subscriber information associated with the user equipment.
  • Using transparent containers to convey subscription information for user equipment from the UDM to the AMF via the AUSF eliminates previously required signaling exchanges over the fourth interface and the fifth interface.
  • the first or second pairs of transparent containers, the third transparent container, or additional containers are used to deliver other information from UDM to AMF and SMF to reduce the amount of direct signaling with the UDM.
  • FIG. 1 is a block diagram of a communication system 100 that supports providing subscriber data in transparent containers according to some embodiments.
  • the communication system 100 provides support for both mobile and fixed access.
  • the term "mobile access” refers to accessing a communication system (e.g., the communication system 100) over an air interface. Mobile access can therefore be referred to as wireless access, mobile communication, wireless communication, or other similar terms.
  • the term "fixed access” refers to accessing to a communication system using a device that is physically connected to the communication system, e.g., accessing a communication system such as the communication system 100 via wires, optical fibers, and the like. Fixed access can therefore be referred to as wireline access, wired communication, or other similar terms.
  • the final leg of a fixed access connection can be provided by a wireless access point such as a Wi-Fi access point.
  • the communication system 100 supports hybrid access that allows devices to concurrently access the communication system 100 using mobile access and fixed access.
  • the communication system 100 includes a core network 105 that is accessible by either mobile or fixed devices using a common user plane access and a control plane that supports common authentication, authorization, and accounting (AAA) and policy control.
  • AAA authentication, authorization, and accounting
  • policy control refers to a portion of a routing architecture that performs routing of packets that arrive on an inbound interface.
  • the user plane can be implemented using routing tables to determine a path from the inbound interface through a forwarding fabric to the proper outgoing interface.
  • the user plane can also be referred to as a data plane or a forwarding plane.
  • control plane refers to a portion of the routing architecture that defines a network topology.
  • the control plane can be used to configure the routing tables that are used to forward packets on the user plane.
  • Control plane logic can also be used to establish priority or quality-of- service for the packets or to identify packets that should be discarded.
  • the core network 105 includes an access and mobility management function (AMF) 110 that manages access control and mobility for devices in the communication system 100.
  • the core network 105 also includes a session management function (SMF) 115 to set up and manage sessions in the communication system 100 according to network policies.
  • SMF session management function
  • An association between user equipment and the core network 105 can be represented as a protocol data unit (PDU) session that can be managed by the SMF 115.
  • the PDU session supports data connectivity between user equipment and a data network.
  • the core network 105 further includes an authentication service function
  • the core network 105 also includes a unified data manager (UDM) 125 that processes credentials, location management, subscription management, and the like.
  • the UDM 125 stores data including user subscription data, such as subscription identifiers, security credentials, access and mobility related subscription data, and session related subscription data.
  • the core network 105 further includes one or more user plane functions (UPF) 130 that can be deployed in the communication system 100 to provide services to users of the communication system 100.
  • the user plane function 130 can function as an endpoint for service flows that are used to broadcast, multicast, or unicast packets, as discussed herein.
  • the user plane function 130 can therefore store endpoint identifiers for the service flows.
  • Entities within the core network 105 are connected by various interfaces.
  • the AMF 110 is connected to the AUSF 120 by an interface 135, to the UDM 125 by an interface 140, and to the SMF 115 by an interface 145.
  • the AUSF 120 is connected to the UDM 125 by an interface 150.
  • the SMF 115 is connected to the UDM 125 by an interface 155.
  • the interfaces 135, 140, 145, 150, 155 are implemented according to standards such as the Third Generation Partnership Project (3GPP) Fifth Generation (5G) network architecture.
  • the interfaces 135, 140, 145, 150, 155 in a 5G system correspond to the N 12, N8, Ni l, N13, and N10 interfaces, respectively.
  • the communication system 100 defines other interfaces between entities that are disposed interior and exterior to the core network 105. The other interfaces are not indicated by a reference numeral in the interest of clarity.
  • Some embodiments of the core network 105 include other functionality such as a policy control function and a network function repository function, which are not shown in FIG. 1 in the interest of clarity. Some embodiments of the core network 105 are implemented using network function virtualization and software defined networking, as discussed herein. For example, different network slices can be used to instantiate different instances of the AMF 110, the SMF 115, the UPF 130, or the UDM 125 for different users or devices. Each protocol data unit (PDU) session is part of one network slice.
  • PDU protocol data unit
  • the core network 105 provides network access to user equipment 160 via mobile access.
  • the user equipment 160 can access the core network 105 via a base station 165 that is connected to the AMF 110 over a corresponding interface such as an N2 interface.
  • the base station 165 is also connected to the UPF 120 by a corresponding interface such as an N3 interface, which is not shown in FIG. 1 in the interest of clarity.
  • the base station 165 can be implemented as a 5G gigabit NodeB (gNB) in accordance with standards defined by the 3GPP.
  • the user equipment 160 can access the core network 105 via a base station 170 that is connected to the AMF 110 over a corresponding interface such as an N2 interface.
  • the base station 170 is also connected to the UPF 130 by a corresponding interface such as an N3 interface, which is not shown in FIG. 1 in the interest of clarity.
  • the base station 170 can be implemented as a
  • Terrestrial Broadcast 5G gNB in accordance with standards defined by the 3GPP.
  • the core network 105 also provides network access to the user equipment 160 via fixed access.
  • the user equipment 160 can establish a connection to a residential gateway 175, which has a wired connection to an Ethernet network 180.
  • a final leg of the fixed access connection between the user equipment 160 and the core network 105 is implemented using a wireless access technology.
  • a Wi-Fi access point 185 can be used to provide the final leg of the fixed access connection.
  • the user equipment 160 is connected to the residential gateway 175 using a wired connection.
  • Some embodiments of the wired connection use line termination devices such as a digital subscriber line access multiplexer (DSLAM) or a gigabit passive optical network (GPON).
  • DSLAM digital subscriber line access multiplexer
  • GPON gigabit passive optical network
  • An interworking function 190 is disposed between the Ethernet network 180 and the core network 105.
  • the interworking function 190 can also be referred to as a non- 3GPP interworking function (N3IWF).
  • the interworking function 190 is configured to modify or translate messages conveyed from the fixed access user equipment to the core network 105 so that the fixed access user equipment appears to be accessing the core network 105 according to mobile access standards or protocols from the perspective of the core network 105.
  • the interworking function 190 is also configured to modify or translate messages conveyed from the core network 105 to the fixed access user equipment so that the messages received by the fixed access user equipment conform to corresponding fixed access standards or protocols.
  • the interworking function 190 supports interfaces with the AMF 110 and the UPF 130.
  • the number of messages that are exchanged over the interfaces 135, 140, 145, 150, 155 during registration of the user equipment 160 with the core network 105 is reduced conveying registration information in transparent containers in the core network 105.
  • a first pair of transparent containers are transmitted over the interface 135 and a second pair of transparent containers are transmitted over the interface 150.
  • the AMF 110 receives AMF-specific subscriber information and SMF- specific subscriber information via the first and second pairs of transparent containers.
  • the AMF 110 decodes the AMF-specific subscriber information and forwards the SMF- specific subscriber information to the SMF 115 over the interface 145.
  • an additional transparent container is conveyed over the interface 145 and the additional transparent container is used to carry the SMF-specific subscriber information. Conveying the registration information in the transparent containers eliminates messaging exchanged between the AMF 110 and the UDM 125 over the interface 140 because the UDM 125 has previously provided this information to the AMF 110 via the transparent containers over the interfaces 135, 150. The transparent containers also eliminate messaging exchanged between the SMF 115 and the UDM 125 over the interface 155 during the PDU registration because the registration information is already available to the SMF 115 via the AMF 110.
  • FIG. 2 is a block diagram of an NFV architecture 200 according to some embodiments.
  • the NFV architecture 200 is used to implement some embodiments of the communication system 100 shown in FIG. 1.
  • instances of the AMF 110, SMF 115, AUSF 120, and UDM 125 can be instantiated as virtual functions in the NFV architecture 200.
  • the NFV architecture 200 includes hardware resources 201 including computing hardware 202, storage hardware 203, and network hardware 204.
  • the computing hardware 202 is implemented using one or more processors
  • the storage hardware 203 is implemented using one or more memories
  • the network hardware 204 is implemented using one or more transceivers, transmitters, receivers, interfaces, and the like.
  • a virtualization layer 205 provides an abstract representation of the hardware resources 201.
  • the abstract representation supported by the virtualization layer 205 can be managed using a virtualized infrastructure manager 210, which is part of the NFV management and orchestration (M&O) module 215.
  • M&O NFV management and orchestration
  • Some embodiments of the manager 210 are configured to collect and forward performance measurements and events that may occur in the NFV architecture 200. For example, performance measurements may be forwarded to an orchestrator (ORCH) 217 implemented in the NFV M&O 215.
  • ORCH orchestrator
  • the hardware resources 201 and the virtualization layer 205 may be used to implement virtual resources 220 including virtual computing resources 221, virtual storage resources 222, and virtual networking resources 223.
  • VNF1, VNF2, VNF3 Virtual networking functions (VNF1, VNF2, VNF3) run over the NFV
  • the NFV architecture 200 may include an operation support system
  • the OSS/BSS 230 deals with network management including fault management using the OSS functionality.
  • the OSS/BSS 230 also deals with customer and product management using the BSS functionality.
  • Some embodiments of the NFV architecture 200 use a set of descriptors 235 for storing descriptions of services, virtual network functions, or infrastructure supported by the NFV architecture 200. Information in the descriptors 235 may be updated or modified by the NFV M&O 215.
  • the NFV architecture 200 implements network slices that provide control plane functions or user plane functions, such as instances of the AMF 110, SMF 1 15, AUSF 120, and UDM 125 shown in FIG. 1.
  • a network slice is a complete logical network that provides communication services and network capabilities, which can vary from slice to slice.
  • User equipment can concurrently access multiple slices that support multiple service flows between a core network and the user equipment.
  • Some embodiments of user equipment provide Network Slice Selection Assistance Information (NSSAI) parameters to the network to assist in selection of a slice instance for the user equipment.
  • NSSAI Network Slice Selection Assistance Information
  • a single NSSAI may lead to the selection of several slices.
  • the NFV architecture 200 can also use device capabilities, subscription information and local operator policies to do the selection.
  • An NSSAI is a collection of smaller components, Single-NSSAIs (S- NSSAI), which each include a Slice Service Type (SST) and possibly a Slice Service Type (SST) and possibly a Slice Service Type (SST) and possibly a
  • FIG. 3 is a message flow 300 that depicts messaging exchanged between a user equipment (UE), an AMF, an AUSF, and a UDM according to some embodiments.
  • the message flow 300 is implemented in some embodiments of the communication system 100 shown in FIG. 1.
  • the UE initiates a registration procedure to register with the communication system by transmitting a registration request message 305 to the AMF.
  • the AMF transmits an information request message 310 to the AUSF to request authentication information for the UE.
  • the information request message 310 is a 5G-AIR message that optionally contains a request to establish transparent containers between the AMF and the AUSF and between the AUSF and the UDM.
  • the AUSF transmits an authentication information request message 315 to the UDM in response to receiving the information request message 310.
  • the authentication information request message 315 include information identifying the user equipment such as an international mobile subscriber identity (EVISI) that is allocated to the UE.
  • EVISI international mobile subscriber identity
  • the UDM uses the identifying information to locate authentication information such as security keys that are used to authenticate the UE to the communication system.
  • the UDM transmits an authentication information response message 320 to the AUSF.
  • the authentication information response message 320 includes authentication information for the UE such as the security keys that are used to authenticate the UE.
  • the authentication information response message 320 also includes transparent containers to carry information between the UDM and the AUSF and between the AUSF and the AMF.
  • the transparent containers are transmitted in response to receiving the authentication information request message 315 in the message flow 300, some embodiments of the UDM are configured to transmit the information containers prior to receiving the authentication information request message 315.
  • the UDM can be configured to push transparent containers including AMF- specific information and SMF-specific information to the AUSF.
  • pairs of transparent containers are used to convey information over the interfaces.
  • One of the pairs of the transparent containers on each of the interfaces carries the AMF- specific information and the other one of the pairs of transparent containers carries the SMF-specific information.
  • a first transparent container that is transmitted over the interface between the UDM and the AUSF carries AMF-specific information that is used to register the UE in an information element of the first transparent container.
  • a second transparent container in the pair that is transmitted over the interface between the UDM and the AUSF carries SMF-specific information that is used to establish a PDU session for the UE in an information element of the second transparent container.
  • the transparent containers include information identifying the container endpoints (e.g., the AMF and the UDM), information identifying the UE associated with the transparent containers, and the like.
  • the AUSF transmits an information response message 325 to the AMF in response to receiving the authentication information response message 320.
  • the information response message 325 includes the authentication information received in the authentication information response message 320, as well as the transparent containers that include the AMF-specific information for the UE and the SMF-specific information for the UE.
  • the AUSF does not access or decode the AMF-specific information or the SMF-specific information, i.e., this information is "transparent" to the AUSF when included in the transparent containers.
  • the UE is authenticated on the basis of the authentication information received from the UDM in an authentication procedure 330.
  • the AMF would be required to transmit a request for AMF-specific information over an interface between the AMF and the UDM.
  • the conventional information exchange is illustrated as a dotted line box 335 in FIG. 3.
  • the dotted lines of the box 335 indicate that this message exchange does not actually take place in the message flow 300. Instead, since the AMF-specific information has already been conveyed to the AMF in one of the transparent containers over the interfaces between the UDM, the AUSF, and the AMF as described above, the AMF can proceed directly with the authentication procedure 330.
  • FIG. 4 is a message flow 400 that depicts messaging exchanged between a user equipment (UE), an AMF, an SMF, and a UDM according to some embodiments.
  • the message flow 400 is implemented in some embodiments of the communication system 100 shown in FIG. 1.
  • the message flow 400 is used to perform a protocol data unit (PDU) session establishment of the UE with the SMF and is therefore performed after the message flow 300 shown in FIG. 3 has been performed to register the UE with the communication system.
  • PDU protocol data unit
  • the UE transmits a PDU session establishment request message 405 to begin a procedure for establishing a PDU session with the communication system.
  • the PDU session establishment request message 405 is transmitted to the AMF, which forwards a request message 410 to the SMF.
  • the request message 410 includes the transparent container that holds the SMF-specific information that was provided by the UDM, e.g., during registration of the UE using the message flow 300 shown in FIG. 3.
  • the SMF and the UE initiate a PDU session establishment procedure 415 on the basis of the SMF-specific information for the UE.
  • the SMF is required to request the SMF-specific information from the UDM using messages exchanged over an interface between the SMF and the UDM.
  • the conventional information exchange is illustrated as a dotted line box 420 in FIG. 4.
  • the dotted lines of the box 420 indicate that this message exchange does not actually take place in the message flow 400.
  • the SMF decodes the SMF-specific information conveyed in the transparent container and then proceeds with the PDU session establishment procedure 415 on the basis of the decoded SMF-specific information without sending any additional messages to the UDM.
  • certain aspects of the techniques described above may implemented by one or more processors of a processing system executing software.
  • the software comprises one or more sets of executable instructions stored or otherwise tangibly embodied on a non-transitory computer readable storage medium.
  • the software can include the instructions and certain data that, when executed by the one or more processors, manipulate the one or more processors to perform one or more aspects of the techniques described above.
  • the non-transitory computer readable storage medium can include, for example, a magnetic or optical disk storage device, solid state storage devices such as Flash memory, a cache, random access memory (RAM) or other non- volatile memory device or devices, and the like.
  • the executable instructions stored on the non- transitory computer readable storage medium may be in source code, assembly language code, object code, or other instruction format that is interpreted or otherwise executable by one or more processors.
  • a computer readable storage medium may include any storage medium, or combination of storage media, accessible by a computer system during use to provide instructions and/or data to the computer system.
  • Such storage media can include, but is not limited to, optical media (e.g., compact disc (CD), digital versatile disc (DVD), Blu- Ray disc), magnetic media (e.g., floppy disc, magnetic tape, or magnetic hard drive), volatile memory (e.g., random access memory (RAM) or cache), non-volatile memory (e.g., read-only memory (ROM) or Flash memory), or microelectromechanical systems (MEMS)-based storage media.
  • optical media e.g., compact disc (CD), digital versatile disc (DVD), Blu- Ray disc
  • magnetic media e.g., floppy disc, magnetic tape, or magnetic hard drive
  • volatile memory e.g., random access memory (RAM) or cache
  • non-volatile memory e.g., read-only memory (ROM) or Flash memory
  • MEMS microelectro
  • the computer readable storage medium may be embedded in the computing system (e.g., system RAM or ROM), fixedly attached to the computing system (e.g., a magnetic hard drive), removably attached to the computing system (e.g., an optical disc or Universal Serial Bus (USB)-based Flash memory), or coupled to the computer system via a wired or wireless network (e.g., network accessible storage (NAS)).
  • system RAM or ROM system RAM or ROM
  • USB Universal Serial Bus
  • NAS network accessible storage

Landscapes

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

Abstract

Une première paire de contenants transparents est établie sur une première interface entre une fonction d'accès et de gestion de mobilité (AMF) et une fonction de service d'authentification (AUSF). Une seconde paire de contenants transparents est établie sur une seconde interface entre l'AUSF et un gestionnaire de données unifié (UDM). L'AMF reçoit des informations d'abonné spécifiques de l'AMF et des informations d'abonné spécifiques de SMF par l'intermédiaire des première et seconde paires de contenants transparents. L'AMF transfère les informations d'abonné spécifiques de SMF à la SMF. Dans certains cas, un premier conteneur dans chacune des première et seconde paires est réservé aux informations d'abonné spécifiques à l'AMF et un second conteneur dans chacune des première et seconde paires est réservé aux informations d'abonné spécifiques aux SMF.
PCT/EP2017/078270 2017-11-06 2017-11-06 Fourniture de données d'abonné à partir d'un gestionnaire de données unifié dans des contenants transparents WO2019086129A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2017/078270 WO2019086129A1 (fr) 2017-11-06 2017-11-06 Fourniture de données d'abonné à partir d'un gestionnaire de données unifié dans des contenants transparents

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2017/078270 WO2019086129A1 (fr) 2017-11-06 2017-11-06 Fourniture de données d'abonné à partir d'un gestionnaire de données unifié dans des contenants transparents

Publications (1)

Publication Number Publication Date
WO2019086129A1 true WO2019086129A1 (fr) 2019-05-09

Family

ID=60320860

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2017/078270 WO2019086129A1 (fr) 2017-11-06 2017-11-06 Fourniture de données d'abonné à partir d'un gestionnaire de données unifié dans des contenants transparents

Country Status (1)

Country Link
WO (1) WO2019086129A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110167088A (zh) * 2019-05-29 2019-08-23 中国联合网络通信集团有限公司 一种会话的管理方法及装置
CN112105021A (zh) * 2019-06-17 2020-12-18 华为技术有限公司 一种认证方法、装置及系统
CN115022877A (zh) * 2022-07-14 2022-09-06 中国联合网络通信集团有限公司 终端鉴权方法、装置、电子设备及计算机可读存储介质

Non-Patent Citations (3)

* 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)", 22 September 2017 (2017-09-22), XP051359408, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/Latest_SA2_Specs/Latest_draft_S2_Specs/> [retrieved on 20170922] *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on the security aspects of the next generation system (Release 14)", 27 September 2017 (2017-09-27), XP051361245, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG3_Security/TSGS3_LI/2017_66bis_Sophia/Docs/> [retrieved on 20170927] *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15)", 26 July 2017 (2017-07-26), XP051312202, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/Latest_SA2_Specs/Latest_draft_S2_Specs/> [retrieved on 20170726] *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110167088A (zh) * 2019-05-29 2019-08-23 中国联合网络通信集团有限公司 一种会话的管理方法及装置
CN112105021A (zh) * 2019-06-17 2020-12-18 华为技术有限公司 一种认证方法、装置及系统
CN112105021B (zh) * 2019-06-17 2022-05-10 华为技术有限公司 一种认证方法、装置及系统
CN115022877A (zh) * 2022-07-14 2022-09-06 中国联合网络通信集团有限公司 终端鉴权方法、装置、电子设备及计算机可读存储介质

Similar Documents

Publication Publication Date Title
US11184842B2 (en) Conveying non-access stratum messages over ethernet
US20230216754A1 (en) Packet Processing Method, Forwarding Plane Device and Network Device
EP3659358B1 (fr) Service de minimessages sécurisé sur strate de non-accès
EP3656174B1 (fr) Interactions entre une passerelle de réseau à large bande et un coeur de cinquième génération
CN106464534B (zh) 配设和管理用户驻地设备装置的片
CN110417840B (zh) 一种信息处理方法及装置
CN112449315B (zh) 一种网络切片的管理方法及相关装置
JP7296993B2 (ja) 通信方法及び通信装置
US11985585B2 (en) Downlink signaling to user equipment in non-3GPP idle state
KR20210044831A (ko) 사용자 그룹에 대한 세션 관리 방법 및 장치
CN110166414B (zh) 一种通信方法、装置及系统
US11647452B2 (en) Application-driven user slice selection for mobile networks
JP6775683B2 (ja) 次世代システムの認証
JP5679343B2 (ja) クラウドシステム、ゲートウェイ装置、通信制御方法、及び通信制御プログラム
CN111193644A (zh) 一种vBRAS业务传输方法、装置、终端设备和介质
WO2019086129A1 (fr) Fourniture de données d&#39;abonné à partir d&#39;un gestionnaire de données unifié dans des contenants transparents
CN110278095A (zh) 一种消息传输方法和装置
WO2021244356A1 (fr) Procédé et appareil de transmission de données
WO2015100585A1 (fr) Dispositif à fibre reliée au point de distribution et procédé de communication associé
JP7374139B2 (ja) 接続モードのユーザ機器のアクセス制御
US20230291607A1 (en) System and method for ursp-based tunneling through fixed wireless access
US20230292230A1 (en) System and method for ursp-based tunneling through fixed wireless access
KR102076121B1 (ko) 제 2 계층을 기반으로 네트워크 서비스를 제공하는 장치 및 시스템

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

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

Country of ref document: EP

Kind code of ref document: A1