[go: up one dir, main page]

WO2025069256A1 - Système de réseau cœur natif en nuage, mme et procédé - Google Patents

Système de réseau cœur natif en nuage, mme et procédé Download PDF

Info

Publication number
WO2025069256A1
WO2025069256A1 PCT/JP2023/035171 JP2023035171W WO2025069256A1 WO 2025069256 A1 WO2025069256 A1 WO 2025069256A1 JP 2023035171 W JP2023035171 W JP 2023035171W WO 2025069256 A1 WO2025069256 A1 WO 2025069256A1
Authority
WO
WIPO (PCT)
Prior art keywords
mme
udm
hss
service
processing unit
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/JP2023/035171
Other languages
English (en)
Japanese (ja)
Inventor
誠 野辺
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NEC Corp
Original Assignee
NEC Corp
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 NEC Corp filed Critical NEC Corp
Priority to PCT/JP2023/035171 priority Critical patent/WO2025069256A1/fr
Publication of WO2025069256A1 publication Critical patent/WO2025069256A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/084—Load balancing or load distribution among network function virtualisation [NFV] entities; among edge computing entities, e.g. multi-access edge computing
    • 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

  • the present disclosure relates to a cloud native core network system, an MME, and a method.
  • the MME Mobility Management Entity
  • 5GC HSS Home Subscriber Server
  • UDM Unified Data Management
  • the HSS Home Subscriber Server
  • UDM Unified Data Management
  • the objective of this disclosure is to provide a cloud native core network system, MME, and method that can connect an MME and a UDM while maintaining the benefits of a cloud native architecture.
  • a cloud native core network system includes: A containerized network function, a Mobility Management Entity (MME), a core network node connected to the MME via a service-based interface (SBI), which is a containerized network function and has a Home Subscriber Server (HSS) function and a Unified Data Management (UDM) function; Includes.
  • MME Mobility Management Entity
  • SBI service-based interface
  • HSS Home Subscriber Server
  • UDM Unified Data Management
  • a cloud native core network system includes: A containerized network function, a Mobility Management Entity (MME), A Unified Data Management (UDM) is a containerized network function connected to the MME via a Service Based Interface (SBI); Includes.
  • MME Mobility Management Entity
  • UDM Unified Data Management
  • a method performed by a cloud native core network system includes:
  • the cloud native core network system includes: A Mobility Management Entity (MME), which is a containerized network function (CNF); A core network node connected to the MME via a service-based interface (SBI), which is a containerized network function and has a Home Subscriber Server (HSS) function and a Unified Data Management (UDM) function;
  • MME Mobility Management Entity
  • SBI service-based interface
  • HSS Home Subscriber Server
  • UDM Unified Data Management
  • the MME includes a plurality of MME processing units corresponding to any of a plurality of MME services of the MME
  • the core network node includes a plurality of HSS processing units corresponding to any of a plurality of HSS services of the core network node;
  • the method comprises:
  • the method includes one of the multiple MME processing units obtaining an IP address of a target HSS processing unit corresponding to the one HSS service from a Domain Name System (DNS) based on
  • a method performed by a cloud native core network system includes: The cloud native core network system includes: A containerized network function, a Mobility Management Entity (MME), A Unified Data Management (UDM) is a containerized network function connected to the MME via a Service Based Interface (SBI); Including, The MME includes a plurality of MME processing units corresponding to any of a plurality of MME services of the MME, and a plurality of conversion processing units corresponding to the plurality of MME processing units, respectively; The UDM includes a plurality of UDM processing units corresponding to any of a plurality of UDM services of the UDM; The method includes a conversion processing unit corresponding to one of the multiple MME processing units obtaining an IP address of a target UDM processing unit corresponding to one UDM service from a Domain Name System (DNS) based on a Fully Qualified Domain Name (FQDN) corresponding to one UDM service.
  • DNS Domain Name System
  • FQDN Fully Qualified Domain Name
  • a method performed by a cloud native core network system includes:
  • the cloud native core network system includes: A Mobility Management Entity (MME), which is a containerized network function (CNF);
  • a Unified Data Management (UDM) is a containerized network function connected to the MME via a Service Based Interface (SBI); a conversion unit connected to the MME via a Diameter protocol interface and to the UDM via a service-based interface (SBI), converting a hypertext transfer protocol (HTTP)-compliant message received from the UDM into a Diameter protocol-compliant message and outputting the Diameter protocol-compliant message to the MME;
  • the MME includes a plurality of MME processing units corresponding to any of a plurality of MME services of the MME
  • the UDM includes a plurality of UDM processing units corresponding to any of a plurality of UDM services of the UDM;
  • the method includes the conversion unit obtaining an IP address of a target UDM processing unit corresponding to a UDM service from a
  • a Mobility Management Entity A containerized network function. It is a containerized network function and is connected to a core network node having a Home Subscriber Server (HSS) function and a Unified Data Management (UDM) function via a Service Based Interface (SBI).
  • HSS Home Subscriber Server
  • UDM Unified Data Management
  • MME Mobility Management Entity
  • UDM Unified Data Management
  • SBI Service-Based Interface
  • a method performed by a Mobility Management Entity includes: The MME is a containerized network function, and is connected to a core network node that is a containerized network function and has a Home Subscriber Server (HSS) function and a Unified Data Management (UDM) function via a Service Based Interface (SBI);
  • the core network node includes a plurality of HSS processing units corresponding to any of a plurality of HSS services of the core network node;
  • the MME includes a plurality of MME processing units corresponding to any of a plurality of MME services of the MME,
  • the method includes one of the plurality of MME processing units obtaining, from a Domain Name System (DNS), an IP address of a target HSS processing unit corresponding to one HSS service, based on a Fully Qualified Domain Name (FQDN) corresponding to the one HSS service.
  • DNS Domain Name System
  • FQDN Fully Qualified Domain Name
  • a method performed by a Mobility Management Entity includes: The MME is a containerized network function and is connected to a containerized network function, Unified Data Management (UDM), via a Service-Based Interface (SBI); The UDM includes a plurality of UDM processing units corresponding to any of a plurality of UDM services of the UDM; The MME includes a plurality of MME processing units corresponding to any of a plurality of MME services of the MME, and a plurality of conversion processing units corresponding to the plurality of MME processing units, respectively; The method includes a conversion processing unit corresponding to one of the multiple MME processing units obtaining an IP address of a target UDM processing unit corresponding to one UDM service from a Domain Name System (DNS) based on a Fully Qualified Domain Name (FQDN) corresponding to one UDM service.
  • DNS Domain Name System
  • FQDN Fully Qualified Domain Name
  • the present disclosure makes it possible to provide a cloud native core network system, MME, and method that can connect an MME and a UDM while maintaining the benefits of cloud native architecture.
  • FIG. 1 is a diagram illustrating container technology used in building a cloud native core network system.
  • FIG. 1 illustrates an example of a cloud native core network system of the present disclosure.
  • FIG. 2 is a diagram illustrating another example of a cloud native core network system of the present disclosure.
  • FIG. 2 is a diagram illustrating another example of a cloud native core network system of the present disclosure.
  • FIG. 2 is a diagram illustrating another example of a cloud native core network system of the present disclosure.
  • FIG. 2 is a diagram illustrating another example of a cloud native core network system of the present disclosure.
  • FIG. 1 is a diagram for explaining a container technology used to build a cloud native core network system.
  • a “server” in Fig. 1 includes one or more physical servers.
  • the “server” may have at least one memory (not shown) that holds an instruction set and at least one processor (not shown) that executes processing according to the instruction set.
  • container technology is a technology that creates a virtualized execution environment called a "container" on a host OS (operating system).
  • the container engine controls the containers that are the target of control.
  • the cloud-native core network system of the present disclosure includes multiple network function units (e.g., MME (Mobility Management Entity), HSS (Home Subscriber Server) + UDM (Unified Data Management), etc.).
  • Each network function unit provides one or more services (e.g., data processing).
  • Each service is provided by the above-mentioned containers. That is, each container corresponds to one of the services (or processes) of the corresponding network function unit.
  • the network function units of the present disclosure are containerized.
  • the network function unit of the present disclosure is realized as a cloud-native virtualized network function (CNF) by executing each service of the network function unit using containers.
  • CNF cloud-native virtualized network function
  • First Embodiment 2 is a diagram illustrating an example of a cloud native core network system according to the present disclosure.
  • a cloud native core network system 10 includes an MME 11 and an HSS+UDM 12.
  • the MME 11 is a cloud-native virtualized network function (CNF). In other words, the MME 11 is a containerized network function.
  • CNF cloud-native virtualized network function
  • HSS+UDM12 is a core network node having the functions of a Home Subscriber Server (HSS) and a Unified Data Management (UDM).
  • HSS+UDM12 is a cloud-native virtualized network function (CNF).
  • CNF cloud-native virtualized network function
  • HSS+UDM12 is a containerized network function.
  • HSS+UDM12 is connected to MME11 via a service-based interface (SBI).
  • SBI service-based interface
  • the MME 11 and the HSS+UDM 12 are each a cloud native virtualized network function (CNF).
  • CNF cloud native virtualized network function
  • the HSS+UDM 12 is connected to the MME 11 via a service based interface (SBI).
  • SBI service based interface
  • This cloud native core network system 10 configuration allows the HSS+UDM 12 and MME 11 to be connected via a service-based interface (SBI), making it possible to connect the MME 11 and HSS+UDM 12 while maintaining the benefits of cloud native architecture.
  • SBI service-based interface
  • FIG. 3 is a diagram illustrating another example of a cloud native core network system of the present disclosure.
  • the cloud native core network system 10 has an MME 11 and an HSS+UDM 12.
  • the MME 11 has MME processing units 11A-1 to 11A-M (M is an integer equal to or greater than 2).
  • M is an integer equal to or greater than 2.
  • each of the MME processing units 11A-1 to 11A-M, or the MME processing units 11A-1 to 11A-M may be collectively referred to simply as the MME processing unit 11A.
  • Each MME processing unit 11A corresponds to one of the multiple MME services of the MME 11.
  • the MME processing units 11A-1 to 11A-3 may correspond to one MME service
  • the MME processing unit 11A-M may correspond to another MME service.
  • each MME processing unit 11A corresponds to, for example, an MME pod.
  • An MME pod is a unit for managing MME containers, and may include one or more MME containers.
  • HSS+UDM12 has HSS processing units 12A-1 to 12A-N (N is an integer equal to or greater than 2).
  • N is an integer equal to or greater than 2.
  • each of the HSS processing units 12A-1 to 12A-N, or the HSS processing units 12A-1 to 12A-N collectively, may be simply referred to as HSS processing unit 12A.
  • Each HSS processing unit 12A corresponds to one of the multiple HSS services of HSS+UDM12.
  • HSS processing units 12A-1 to 12A-3 may correspond to one HSS service
  • HSS processing units 12A-(N-1) and 12A-N may correspond to another HSS service.
  • each HSS processing unit 12A corresponds to, for example, an HSS pod.
  • An HSS pod is a unit for managing HSS containers and can contain one or more HSS containers.
  • One of the multiple MME processing units 11A obtains the IP (Internet Protocol) address of the target HSS processing unit 12A corresponding to one HSS service from a DNS (Domain Name System) based on an FQDN (Fully Qualified Domain Name) corresponding to the one HSS service. Then, the one MME processing unit 11A sends a message to the target HSS processing unit 12A using the obtained IP address. For example, the one MME processing unit 11A sends a name resolution request including the FQDN corresponding to the one HSS service and the IP address of the one MME processing unit 11A to a DNS (Domain Name System) (not shown).
  • DNS Domain Name System
  • the first MME processing unit 11A receives a response message including the IP address of the target HSS processing unit 12A corresponding to the first HSS service and the IP address of the first MME processing unit 11A, which is transmitted from the DNS (not shown) in response to the name resolution request.
  • the first MME processing unit 11A then transmits a message to the target HSS processing unit 12A using the IP address included in the response message. That is, the first MME processing unit 11A transmits a message to the target HSS processing unit 12A, including the IP address of the target HSS processing unit 12A as the destination IP address and the IP address of the first MME processing unit 11A as the source address.
  • the DNS (not shown) may be included in the cloud native core network system 10, or may be a system that exists outside the cloud native core network system 10.
  • the DNS holds a second table that associates multiple FQDNs corresponding to multiple HSS services with one or more IP addresses corresponding to each FQDN (i.e., one or more HSS processing units 12A corresponding to each FQDN).
  • the DNS (not shown) then refers to the second table to select one of the one or more IP addresses (i.e., one or more HSS processing units 12A) corresponding to the FQDN included in the name resolution request.
  • the DNS (not shown) then transmits a response message including the selected IP address (i.e., the IP address of the target HSS processing unit 12A) to one MME processing unit 11A.
  • one of the multiple HSS processing units 12A acquires the IP address of the target MME processing unit 11A corresponding to one MME service from a DNS (Domain Name System) based on the FQDN corresponding to the one MME service. Then, the one HSS processing unit 12A transmits a message to the target MME processing unit 11A using the acquired IP address. For example, the one HSS processing unit 12A transmits a name resolution request including the FQDN corresponding to the one MME service and the IP address of the one HSS processing unit 12A to the DNS (not shown).
  • DNS Domain Name System
  • the one HSS processing unit 12A receives a response message including the IP address of the target MME processing unit 11A corresponding to the one MME service and the IP address of the one HSS processing unit 12A transmitted from the DNS (not shown) in response to the name resolution request. Then, the first HSS processing unit 12A transmits a message to the target MME processing unit 11A using the IP address included in the response message. That is, the first HSS processing unit 12A transmits a message to the target MME processing unit 11A, the message including the IP address of the target MME processing unit 11A as the destination IP address and the IP address of the first HSS processing unit 12A as the source address.
  • the DNS (not shown) may be included in the cloud native core network system 10, or may be a system that exists outside the cloud native core network system 10.
  • the HSS 12 holds a third table that associates multiple MME services with FQDNs corresponding to each MME service. Therefore, the first HSS processing unit 12A refers to the first table to identify an FQDN that corresponds to an MME service that the first HSS processing unit 12A wishes to receive. The first HSS processing unit 12A then transmits a name resolution request including the identified FQDN to the DNS (not shown).
  • the DNS holds a fourth table that associates multiple FQDNs corresponding to multiple MME services with one or more IP addresses corresponding to each FQDN (i.e., one or more MME processing units 11A corresponding to each FQDN).
  • the DNS (not shown) then refers to the fourth table to select one of the one or more IP addresses (i.e., one or more MME processing units 11A) corresponding to the FQDN included in the name resolution request.
  • the DNS (not shown) then transmits a response message including the selected IP address (i.e., the IP address of the target MME processing unit 11A) to one of the HSS processing units 12A.
  • an MME processing unit 11A acquires an IP address of a target HSS processing unit 12A corresponding to an HSS service from a DNS (not shown) based on an FQDN corresponding to the HSS service. Then, the MME processing unit 11A uses the acquired IP address to send a message to the target HSS processing unit 12A. For example, the MME processing unit 11A sends a name resolution request including an FQDN corresponding to an HSS service and an IP address of the MME processing unit 11A to a DNS (not shown).
  • the MME processing unit 11A receives a response message including an IP address of the target HSS processing unit 12A corresponding to the above-mentioned HSS service and an IP address of the MME processing unit 11A, which was sent from the DNS (not shown) in response to the name resolution request. Then, the first MME processing unit 11A sends a message to the target HSS processing unit 12A using the IP address included in the response message.
  • This configuration of the cloud native core network system 10 allows the MME processing units 11A-1 to 11A-M and the HSS processing units 12A-1 to 12A-N to be connected in a mesh pattern. This allows the cloud native core network system 10 to enjoy the benefits of the flexibility of cloud native architecture (e.g., ease of expanding the configuration, ease of building a redundant configuration).
  • Third Embodiment 4 is a diagram illustrating another example of the cloud native core network system of the present disclosure.
  • the cloud native core network system 20 includes an MME 21 and a UDM 22.
  • MME21 is a cloud-native virtualized network function (CNF).
  • CNF cloud-native virtualized network function
  • (Appendix 1) A containerized network function, a Mobility Management Entity (MME), A core network node connected to the MME via a service-based interface (SBI), which is a containerized network function and has a Home Subscriber Server (HSS) function and a Unified Data Management (UDM) function; Cloud native core network system including: (Appendix 2)
  • the MME includes a plurality of MME processing units corresponding to any of a plurality of MME services of the MME,
  • the core network node includes a plurality of HSS processing units corresponding to any of a plurality of HSS services of the core network node;
  • One of the MME processing units acquires an IP address of a target HSS processing unit corresponding to the one HSS service from a Domain Name System (DNS) based on a Fully Qualified Domain Name (FQDN) corresponding to the one HSS service.
  • DNS Domain Name System
  • FQDN Fully Qualified Domain Name
  • the UDM includes a plurality of UDM processing units corresponding to any of a plurality of UDM services of the UDM;
  • the MME includes a plurality of MME processing units corresponding to any of a plurality of MME services of the MME, and a plurality of conversion processing units corresponding to the plurality of MME processing units, respectively;
  • a conversion processing unit corresponding to one of the MME processing units among the plurality of MME processing units acquires an IP address of a target UDM processing unit corresponding to the one UDM service from a DNS (Domain Name System) based on a FQDN (Fully Qualified Domain Name) corresponding to the one UDM service; 37.
  • the obtaining includes: The one MME processing unit transmits a name resolution request including an FQDN corresponding to the one HSS service to the DNS; The one MME processing unit receives an IP address of a target HSS processing unit corresponding to the one HSS service transmitted from the DNS in response to the name resolution request; Including, The method of claim 42.
  • the one MME processing unit further includes sending a message to the target HSS processing unit using the acquired IP address. 44. The method according to claim 42 or 43.
  • Each MME processor corresponds to an MME pod; Each HSS processing unit corresponds to an HSS pod. The method of claim 42.
  • the obtaining includes: The one conversion processing unit transmits a name resolution request including an FQDN corresponding to the one UDM service to a DNS (Domain Name System); The one conversion processing unit receives an IP address of a target UDM processing unit corresponding to the one UDM service transmitted from the DNS in response to the name resolution request; Including, The method described in Appendix 47. (Appendix 49) The one conversion processing unit converts the Diameter protocol compliant message directed to the target UDM processing unit into an HTTP (hypertext transfer protocol) compliant message, and transmits the HTTP compliant message to the target UDM processing unit using the acquired IP address. 49. The method according to claim 47 or 48.
  • Each MME processor corresponds to an MME pod; Each UDM processing unit corresponds to a UDM pod. The method described in Appendix 47.
  • the MME pod corresponds to one or more MME containers; The UDM pod corresponds to one or more UDM containers. 51. The method of claim 50.
  • Cloud native core network system 11 MME 11A MME processing unit 12A HSS+UDM processing unit 20 Cloud native core network system 21 MME 21A Processing section 21B Conversion processing section 22 UDM 22A UDM processing unit 30 Cloud native core network system 31 MME 32 U.D.M. 33 Conversion unit

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Ce système de réseau cœur natif en nuage consiste en : une entité MME (MME) qui est une fonction de réseau conteneurisée ; et un HSS + UDM qui est connecté à la MME par l'intermédiaire d'une interface basée sur un service (SBI), est une fonction de réseau conteneurisée, et possède une fonction de serveur HSS (HSS) et une fonction de gestion de données unifiée (UDM).
PCT/JP2023/035171 2023-09-27 2023-09-27 Système de réseau cœur natif en nuage, mme et procédé Pending WO2025069256A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2023/035171 WO2025069256A1 (fr) 2023-09-27 2023-09-27 Système de réseau cœur natif en nuage, mme et procédé

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2023/035171 WO2025069256A1 (fr) 2023-09-27 2023-09-27 Système de réseau cœur natif en nuage, mme et procédé

Publications (1)

Publication Number Publication Date
WO2025069256A1 true WO2025069256A1 (fr) 2025-04-03

Family

ID=95202408

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2023/035171 Pending WO2025069256A1 (fr) 2023-09-27 2023-09-27 Système de réseau cœur natif en nuage, mme et procédé

Country Status (1)

Country Link
WO (1) WO2025069256A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013047200A1 (fr) * 2011-09-30 2013-04-04 日本電気株式会社 Système, procédé et programme de communication
CN111246478A (zh) * 2020-01-20 2020-06-05 广州爱浦路网络技术有限公司 一种基于hss的5g核心网信息处理装置及方法
JP2020528221A (ja) * 2018-06-27 2020-09-17 株式会社Ｎｔｔドコモ 通信システムコアネットワーク及びハートビートメッセージを提供するための方法
WO2022201395A1 (fr) * 2021-03-24 2022-09-29 楽天モバイル株式会社 Système de commande et procédé de commande

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013047200A1 (fr) * 2011-09-30 2013-04-04 日本電気株式会社 Système, procédé et programme de communication
JP2020528221A (ja) * 2018-06-27 2020-09-17 株式会社Ｎｔｔドコモ 通信システムコアネットワーク及びハートビートメッセージを提供するための方法
CN111246478A (zh) * 2020-01-20 2020-06-05 广州爱浦路网络技术有限公司 一种基于hss的5g核心网信息处理装置及方法
WO2022201395A1 (fr) * 2021-03-24 2022-09-29 楽天モバイル株式会社 Système de commande et procédé de commande

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "One core - the best of two worlds Ericsson's dual-mode 5G Core solution", THE CLOUD-NATIVE 5G CORE NETWORK GUIDE SERIES 2.0, ERICSSON, pages 1 - 15, XP009564044, Retrieved from the Internet <URL:https://www.ericsson.com/assets/local/core-network/guides/dualmode-5g-core-solution.pdf> *
GANJI SEPEHR, BEHNAMINIA SHIRIN, AHANGARPOUR ALI, MAZAHERI ERFAN, BARADARAN SARA, ZALI ZEINAB, HEIDARPOUR MOHAMMAD REZA, RAKHSHAN : "CN2F: A Cloud-Native Cellular Network Framework", ARXIV2305.18778V1, 30 May 2023 (2023-05-30), XP093296860, Retrieved from the Internet <URL:https://arxiv.org/pdf/2305.18778> *
MIRKO CANO SOVERI, GOOGLE INC., CABLELABS, CHARTER COMMUNICATIONS, TELEFONICA, DEUTSCHE TELEKOM: "Proposal Solution #XX ACME use in 3GPP", 3GPP DRAFT; S3-231489; TYPE PCR; FS_ACM_SBA, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG3, no. Athens, GR; 20230220 - 20230224, 24 February 2023 (2023-02-24), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052253237 *
TSG WG RAN5: "Maintenance for closed WIs/SIs for REL-15 (batch 7)", 3GPP DRAFT; RP-230979, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. TSG RAN, no. Taipei; 20230612 - 20230614, 7 June 2023 (2023-06-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052505380 *

Similar Documents

Publication Publication Date Title
JP3903014B2 (ja) インターネットプロトコルアドレス変換装置及びこれを用いたホームネットワークシステム並びにその通信方法
US9419940B2 (en) IPv4 data center support for IPv4 and IPv6 visitors
US20120324063A1 (en) Method, network device, and system for automatically configuring network device in ipv6 network
CN102938735B (zh) 使用路由通告携带选项下发nat64地址前缀的方法
CN101656737B (zh) 一种实现多协议接入的方法及接口平台
WO2011147353A1 (fr) Procédé et appareil de transmission de message
CN104283979A (zh) 组播域名系统中报文传输的方法、装置及系统
CN115225606B (zh) 一种容器云平台的跨网络协议的域名访问方法和系统
JP5424007B2 (ja) 情報を提供するための方法、ホームゲートウェイおよびホームネットワークシステム
US11202252B2 (en) Inclusion of a message proxy in a service based architecture
WO2014047919A1 (fr) Procédé, dispositif et système d&#39;attribution d&#39;adresse
CN102025799A (zh) 一种发现及自动配置设备的ip地址的方法
CN102405629B (zh) 用于将用户设备连接到支持IPv6的聚合网络的方法和装置
TW201414253A (zh) 網路位址轉換系統及方法
CN102244687B (zh) 获取多地址信息的方法、装置和系统
CN112968965A (zh) Nfv网络节点的元数据服务方法、服务器及存储介质
WO2025069256A1 (fr) Système de réseau cœur natif en nuage, mme et procédé
TWI715054B (zh) 網路位址轉譯方法及系統
CN118200331A (zh) 数据传输方法、系统和电子设备及存储介质
CN102143239B (zh) 实现在不同网络间进行通信的方法及装置
WO2020168363A2 (fr) Système et procédé de transfert de paquets dans une architecture de réseau hiérarchique à l&#39;aide d&#39;adresses de longueur variable
JP5293559B2 (ja) 通信システム
KR101515853B1 (ko) Most 디바이스와 tcp 디바이스 간의 데이터 통신을 위한 게이트웨이 및 그 동작 방법
CN111654390B (zh) 一种数据传输方法、装置、终端设备和存储介质
JP2011019007A (ja) ネットワークアドレス重複回避方法、装置、システムおよびプログラム

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

Country of ref document: EP

Kind code of ref document: A1