【5G核心网】 Deregistration procedures注销流程

    注销流程可以两种发起:

    -  UE 通知网络它不再访问 5GS

    -  网络通知 UE 它不再有权访问 5GS

     UE 的注销请求和网络的注销请求包括注销是否适用于 3GPP 接入,非 3GPP 接入或两者都适用。当 UE 在同一 PLMN 中注册了两个接入时,可以通过任何接入权限发送注销消息

 

UE-initiated Deregistration

    UE 发起的注销

  Figure 4.2.2.3.2-1: UE-initiated Deregistration

                                             

1. Deregistration Request

    UE 向 AMF 发送 NAS 消息注销请求(5G-GUTI, Deregistration type (e.g. Switch off), Access Type), UE 向 AMF 为逻辑连接关系,需要经由 RAN 

    Access type 指示注销过程是否适用于 3GPP 接入,非3GPP 接入,还是适用于两种接入由同一AMF服务(请参阅TS 23.501 [2])。AMF 将为 UE 指示的目标访问调用注销过程。

    RAN 接收 UE 封装为 NGAP 消息包括的 IE 信息如下:

 

2. Nsmf_PDUSession_ReleaseSMContext Request

    [Conditional] AMF to SMF, 包括, SUPI, PDU Session ID

    如果 UE 在步骤 1 中指示的目标接入上没有建立的 PDU 会话,则不执行步骤2至5。对于每个 PDU 会话,AMF通 过向 SMF 发送 Nsmf_PDUSession_ReleaseSMContext 请求(SUPI,PDU Session ID)消息向 SMF 释放属于 UE 的目标访问上的所有PDU 会话。

 

3. SMF 释放所有资源

    [Conditional] AMF to SMF,分配给 PDU 会话并释放相应用户平面资源的 IP 地址/前缀:

  3a. N4 Session Release Request

    [Conditional] SMF to UPF,SMF 将 N4 会话释放请求(N4 Session ID)消息发送到 PDU 会话的 UPF。UPF 将丢弃 PDU 会话的所有剩余数据包,并释放与 N4 会话相关的所有隧道资源和上下文。

  3b. N4 Session Release Response

    [Conditional] UPF to SMF,UPF 通过向 SMF 发送 N4 会话释放响应(N4 Session ID)消息来确认 N4 会话释放请求。

 

4. Nsmf_PDUSession_ReleaseSMContext Response

    [Conditional] SMF to AMF,SMF 以 Nsmf_PDUSession_ReleaseSMContext 响应消息

 

5a. SM Policy Association Termnation

    [Conditional] 如果动态 PCC 应用该会话,则 SMF 将执行第 4.16.6 节中定义的 SM 策略关联终止过程。

5b-c. Nudm_SDM_Unsubscribe Nudm_UECM Deregistration

    [Conditional]  如果它是 SMF 正在为关联的(DNN,S-NSSAI)为 UE 处理的最后一个 PDU 会话,则 SMF 通过Nudm_SDM_Unsubscribe 服务操作从 UDM 取消订阅会话管理订阅数据更改通知。   SMF 调用 Nudm_UECM_Deregistration 服务操作,以便UDM删除它存储在SMF标识与关联的DNN和PDU会话ID之间的关联。 

 

6. AMF-initiated AM Policy Association Termination

    [Conditional]    如果与此 UE 有与 PCF 的任何关联,并且该 UE不 再通过任何访问进行注册,则 AMF 执行第4.16.3.2节中定义的 AMF 启动的 AM 策略关联终止过程,删除与 PCF 的关联。

  6a. AMF-initiated UE Policy Association Termination

    [Conditional]  如果与此 UE 有与 PCF 的任何关联,并且该 UE 不再通过任何访问进行注册,则 AMF 执行第4.16.3.2节中定义的 AMF 启动的 AM 策略关联终止过程,删除与 PCF 的关联。

 

7. De-registration Accept

    [Conditional]  AMF to UE,AMF 会根据注销类型将 NAS 消息“注销接受”发送给 UE,即,如果注销类型为“关闭”,则 AMF 不会发送“注销接受”消息。

 

8. Signaling Connection Release

    [Conditional]   AMF to AN, N2 UE Context Release Request (Cause)

    

  • 3
    点赞
  • 11
    收藏
    觉得还不错? 一键收藏
  • 1
    评论
Table of Contents Title Page Copyright and Credits Mastering Spring Cloud Packt Upsell Why subscribe? PacktPub.com Contributors About the author About the reviewer Packt is searching for authors like you Preface Who this book is for What this book covers To get the most out of this book Download the example code files Conventions used Get in touch Reviews Introduction to Microservices The blessings of microservices Building microservices with Spring Framework Cloud-native development Learning the microservices architecture Understanding the need for service discovery Communication between services Failures and circuit breakers Summary Spring for Microservices Introducing Spring Boot Developing applications with Spring Boot Customizing configuration files Creating RESTful Web Services API Documentation Using Swagger 2 together with Spring Boot Testing API with Swagger UI Spring Boot Actuator features Application information Health information Metrics Developer tools Integrating application with database Building a sample application Running the application Summary Spring Cloud Overview Beginning with the basics Netflix OSS Service discovery with Eureka Routing with Zuul Load balancing with Ribbon Writing Java HTTP clients Latency and fault tolerance with Hystrix Configuration management with Archaius Discovery and distributed configuration An alternative – Consul Apache Zookeeper Miscellaneous projects Distributed tracing with Sleuth Messaging and integration Cloud platform support Other useful libraries Security Automated testing Cluster features Projects overview  Release trains Summary Service Discovery Running Eureka on the server side Enabling Eureka on the client side Deregistration on shutdown Using discovery client programmatically Advanced configuration settings Refreshing the registry Changing the instance identificator  Preferring the IP address Response cache Enabling secure communication between client and server Registering a secure service Eureka API Replication and high availability Architecture of the sample solution Building the example application Failover Zones Zones with a standalone server Building an example application Summary Distributed Configuration with Spring Cloud Config Introduction to HTTP API resources Native profile support Building a server-side application Building a client-side application Adding a Eureka Server Client-side bootstrap approaches Config Server discovery Repository backend types Filesystem backend Git backend Different protocols Using placeholders in URIs Building a server application Client-side configuration Multiple repositories Vault backend Getting started with Vault Integration with Spring Cloud Config Client-side configuration Additional features Fail on start and retry Secure client Reload configuration automatically Solution architecture Reload configuration with @RefreshScope Consuming events from a message broker Monitoring repository changes on a Config Server Simulating change events manually Testing locally with a GitLab instance  Summary Communication Between Microservices Different styles of communication  Synchronous communication with Spring Cloud Load balancing with Ribbon Enabling communication between microservices using the Ribbon client Static load balancing configuration Calling other services Using RestTemplate together with service discovery Building example application Using Feign client Support for different zones Enabling Feign for an application Building Feign interfaces Launching microservices Inheritance support Creating a client manually Client customization Summary Advanced Load Balancing and Circuit Breakers Load balancing rules The WeightedResponseTime rule Introducing Hoverfly for testing Testing the rule Customizing the Ribbon client The circuit breaker pattern with Hystrix Building an application with Hystrix Implementing Hystrix's commands Implementing fallback with cached data The tripping circuit breaker Monitoring latency and fault tolerance Exposing Hystrix's metrics stream Hystrix dashboard Building an application with the dashboard Monitoring metrics on the dashboard Aggregating Hystrix's streams with Turbine Enabling Turbine Enabling Turbine with streaming Failures and the circuit breaker pattern with Feign Retrying the connection with Ribbon Hystrix's support for Feign Summary Routing and Filtering with API Gateway Using Spring Cloud Netflix Zuul Building a gateway application Integration with service discovery Customizing route configuration Ignoring registered services Explicity set service name  Route definition with the Ribbon client Adding a prefix to the path Connection settings and timeouts Secure headers Management endpoints Providing Hystrix fallback Zuul filters Predefined filters Custom implementations Using Spring Cloud Gateway Enable Spring Cloud Gateway for a project Built-in predicates and filters Gateway for microservices Integration with service discovery Summary Distributed Logging and Tracing Best logging practices for microservices Logging with Spring Boot Centralizing logs with ELK Stack Setting up ELK Stack on the machine Integrating an application with ELK Stack Using LogstashTCPAppender Using AMQP appender and a message broker Spring Cloud Sleuth Integrating Sleuth with an application Searching events using Kibana Integrating Sleuth with Zipkin Running the Zipkin server Building the client application Analyze data with the Zipkin UI Integration via message broker Summary Additional Configuration and Discovery Features Using Spring Cloud Consul Running Consul agent Integration on the client side Service discovery Health check Zones Client settings customization Running in clustered mode Distributed configuration Managing properties in Consul Client customization Watching configuration changes Using Spring Cloud Zookeeper Running Zookeeper Service discovery Client implementation Zookeeper dependencies Distributed configuration Summary Message-Driven Microservices Learning about Spring Cloud Stream Building a messaging system Enabling Spring Cloud Stream Declaring and binding channels Customizing connectivity with the RabbitMQ broker Integration with other Spring Cloud projects The publish/subscribe model Running a sample system Scaling and grouping Running multiple instances Consumer groups Partitioning Configuration options Spring Cloud Stream properties Binding properties The consumer The producer The advanced programming model Producing messages Transformation Consuming messages conditionally Using Apache Kafka Running Kafka Customizing application settings Kafka Streams API support Configuration properties Multiple binders Summary Securing an API Enabling HTTPS for Spring Boot Secure discovery Registering a secure application Serving Eureka over HTTPS Keystore generation Configurating SSL for microservices and Eureka server Secure configuration server Encryption and decryption Configuring authentication for a client and a server Authorization with OAuth2 Introduction to OAuth2 Building an authorization server Client configuration Using the JDBC backend store Inter-service authorization Enabling SSO on the API gateway Summary Testing Java Microservices Testing strategies Testing Spring Boot applications Building the sample application Integration with the database Unit tests Component tests Running tests with an in-memory database Handling HTTP clients and service discovery Implementing sample tests Integration tests Categorizing tests Capturing HTTP traffic Contract tests Using Pact Consumer side Producer side Using Spring Cloud Contract Defining contracts and generating stubs Verifying a contract on the consumer side Scenarios Performance testing Gatling Enabling Gatling Defining the test scenario Running a test scenario Summary Docker Support Introducing Docker Installing Docker Commonly used Docker commands Running and stopping a container Listing and removing containers Pulling and pushing images Building an image Networking Creating a Docker image with microservices Dockerfiles Running containerized microservices Building an image using the Maven plugin Advanced Docker images Continuous Delivery Integrating Jenkins with Docker Building pipelines Working with Kubernetes Concepts and components Running Kubernetes locally via Minikube Deploying an application Maintaining a cluster Summary Spring Microservices on Cloud Platforms Pivotal Cloud Foundry Usage models Preparing the application Deploying the application Using CLI Binding to services Using the Maven plugin Maintenance Accessing deployment details Managing application life cycles Scaling Provisioning brokered services The Heroku platform Deployment methods Using the CLI Connecting to the GitHub repository Docker Container Registry Preparing an application Testing deployments Summary
MIPv6(移动IPv6)机制可以分为5个阶段,这5个阶段的功能如下: 1. 发现阶段(Discovery):移动节点(MN)发现并识别它所在的网络是否具有对MIPv6的支持。该阶段涉及到的实体包括MN、家庭代理(HA)和路由器。消息包括Router Advertisement(RA)和Router Solicitation(RS)。 2. 注册阶段(Registration):MN向HA注册,并告知HA其新的位置。该阶段涉及到的实体包括MN、HA和AAA服务器。消息包括Home Agent Discovery Request(HADISCO_REQ)、Home Agent Discovery Reply(HADISCO_REP)、Authentication Request(AAR)、Authentication Reply(AAR)、Binding Update(BU)和Binding Acknowledgment(BA)。 3. 隧道设置阶段(Tunnel Establishment):MN和HA建立隧道,以便将MN的数据包转发到正确的位置。该阶段涉及到的实体包括MN和HA。消息包括Binding Update(BU)和Binding Acknowledgment(BA)。 4. 隧道更新阶段(Tunnel Update):MN和HA周期性地更新隧道,以确保隧道的有效性,同时也可以更新MN的位置信息。该阶段涉及到的实体包括MN和HA。消息包括Binding Update(BU)和Binding Acknowledgment(BA)。 5. 解除注册阶段(Deregistration):MN从HA处注销,并告知HA其新的位置。该阶段涉及到的实体包括MN和HA。消息包括Binding Update(BU)和Binding Acknowledgment(BA)。 总的来说,MIPv6机制的这5个阶段涵盖了移动节点的注册、位置更新、数据传输等方面的功能,同时也涉及到了多个实体之间的通信和消息的交换。

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 1
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值