WO2023173360A1 - Procédé et appareil d'échange d'informations relatives à une passerelle de réseau de données par paquets - Google Patents

Procédé et appareil d'échange d'informations relatives à une passerelle de réseau de données par paquets Download PDF

Info

Publication number
WO2023173360A1
WO2023173360A1 PCT/CN2022/081437 CN2022081437W WO2023173360A1 WO 2023173360 A1 WO2023173360 A1 WO 2023173360A1 CN 2022081437 W CN2022081437 W CN 2022081437W WO 2023173360 A1 WO2023173360 A1 WO 2023173360A1
Authority
WO
WIPO (PCT)
Prior art keywords
pgw
pgws
network entity
message
type
Prior art date
Application number
PCT/CN2022/081437
Other languages
English (en)
Inventor
Lei Xia
Jian Hu
Danjiao LI
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to PCT/CN2022/081437 priority Critical patent/WO2023173360A1/fr
Publication of WO2023173360A1 publication Critical patent/WO2023173360A1/fr

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/10—Flow control between communication endpoints
    • H04W28/12—Flow control between communication endpoints using signalling between network elements

Definitions

  • the present disclosure generally relates to communication networks, and more specifically, to a method and apparatus for exchanging packet data network gateway (PGW) related information.
  • PGW packet data network gateway
  • a terminal device such as user equipment (UE) may be provided with various services by a communication network via different network nodes and/or functional entity.
  • UE user equipment
  • PGW packet data network gateway
  • MME mobility management entity
  • PCRF policy and charging rules function
  • the PCRF may respond to the MME by a Credit-Control-Answer with the PGW list.
  • the MME may treat one or more PGWs in the PGW list as the standalone PGWs with the same priority and capability.
  • the MME may randomly select a PGW from the PGW list and establish a session for the UE on the selected PGW, no matter whether the selected PGW is a standalone PGW or a combined PGW-control plane function (PGW-C) and session management function (SMF) node.
  • PGW-C PGW-control plane function
  • SMF session management function
  • the random selection of PGW by the MME may lead to resource waste and even session interruption, e.g., when a combined PGW-C and SMF node is selected for a UE without 5GS subscription data, or when a standalone PGW is selected for a N1 capable UE with 5GS subscription data, etc. Therefore, it may be desirable to implement PGW information exchange in a more efficient way.
  • Various exemplary embodiments of the present disclosure propose a solution for exchanging PGW related information, which can enable an MME to get the PGW related information (e.g., information about whether to support SMF capability, information about whether to match the PGW preference, priority information and/or capability information, etc. ) provided by PCRF, so that the MME can select a proper PGW based at least in part on the PGW related information.
  • the PGW related information e.g., information about whether to support SMF capability, information about whether to match the PGW preference, priority information and/or capability information, etc.
  • a method performed by a first network entity e.g., an MME or any other suitable network entity which may be configured to obtain PGW related information from another network entity
  • the method comprises: transmitting towards a second network entity a message for requesting information relating to one or more PGWs.
  • the method further comprises: receiving a response to the message which response is transmitted by the second network entity.
  • the response may indicate the one or more PGWs and include type information of the one or more PGWs.
  • the type information of the one or more PGWs may indicate whether the one or more PGWs are combined PGW-C and SMF nodes or standalone PGW-C nodes.
  • the message may include an indication of a preferred PGW type.
  • the indication of the preferred PGW type may indicate whether a combined PGW-C and SMF node or a standalone PGW-C node is preferred.
  • the type information of the one or more PGWs may indicate whether the one or more PGWs match the preferred PGW type.
  • the one or more PGWs indicated by the response may include: one or more PGWs matching the preferred PGW type; and/or one or more PGWs not matching the preferred PGW type.
  • the type information of the one or more PGWs may indicate priorities and/or capabilities of the one or more PGWs.
  • the method according to the first aspect of the present disclosure may further comprise: selecting a PGW from the one or more PGWs, according to the type information of the one or more PGWs.
  • the first network entity may be an MME and the second network entity may be a PCRF entity.
  • the message may be a credit control request, and the response to the message may be a credit control answer.
  • an apparatus which may be implemented as a first network entity (e.g., an MME, etc. ) .
  • the apparatus may comprise one or more processors and one or more memories storing computer program codes.
  • the one or more memories and the computer program codes may be configured to, with the one or more processors, cause the apparatus at least to perform any step of the method according to the first aspect of the present disclosure.
  • a computer-readable medium having computer program codes embodied thereon which, when executed on a computer, cause the computer to perform any step of the method according to the first aspect of the present disclosure.
  • an apparatus which may be implemented as a first network entity (e.g., an MME, etc. ) .
  • the apparatus may comprise a transmitting unit and a receiving unit.
  • the transmitting unit may be operable to carry out at least the transmitting step of the method according to the first aspect of the present disclosure.
  • the receiving unit may be operable to carry out at least the receiving step of the method according to the first aspect of the present disclosure.
  • a method performed by a second network entity e.g., a PCRF entity or any other suitable network entity which may be configured to provide PGW related information to another network entity
  • the method comprises: receiving a message for requesting information relating to one or more PGWs.
  • the message may be transmitted by a first network entity.
  • the method further comprises: transmitting a response to the message towards the first network entity.
  • the response may indicate the one or more PGWs and include type information of the one or more PGWs.
  • the type information of the one or more PGWs may indicate whether the one or more PGWs are combined PGW-C and SMF nodes or standalone PGW-C nodes.
  • the message may include an indication of a preferred PGW type.
  • the indication of the preferred PGW type may indicate whether a combined PGW-C and SMF node or a standalone PGW-C node is preferred.
  • the method according to the fifth aspect of the present disclosure may further comprise: determining the one or more PGWs, according to the indication of the preferred PGW type.
  • the type information of the one or more PGWs may indicate whether the one or more PGWs match the preferred PGW type.
  • the one or more PGWs indicated by the response may include: one or more PGWs matching the preferred PGW type; and/or one or more PGWs not matching the preferred PGW type.
  • the type information of the one or more PGWs may indicate priorities and/or capabilities of the one or more PGWs.
  • the first network entity may be an MME and the second network entity may be a PCRF entity.
  • the message may be a credit control request, and the response to the message may be a credit control answer.
  • an apparatus which may be implemented as a second network entity (e.g., a PCRF entity, etc. ) .
  • the apparatus may comprise one or more processors and one or more memories storing computer program codes.
  • the one or more memories and the computer program codes may be configured to, with the one or more processors, cause the apparatus at least to perform any step of the method according to the fifth aspect of the present disclosure.
  • a computer-readable medium having computer program codes embodied thereon which, when executed on a computer, cause the computer to perform any step of the method according to the fifth aspect of the present disclosure.
  • an apparatus which may be implemented as a second network entity (e.g., a PCRF entity, etc. ) .
  • the apparatus may comprise a receiving unit and a transmitting unit.
  • the receiving unit may be operable to carry out at least the receiving step of the method according to the fifth aspect of the present disclosure.
  • the transmitting unit may be operable to carry out at least the transmitting step of the method according to the fifth aspect of the present disclosure.
  • a first network entity such as an MME may obtain a PGW list and some PGW type information transmitted by a second network entity such as a PCRF entity, the PGW type information indicating the category, priority and/or capability of one or more PGWs in the PGW list, so that the first network entity can prioritize the one or more PGWs and select an appropriate PGW from the one or more PGWs based at least in part on the PGW type information.
  • a second network entity such as a PCRF entity
  • Fig. 1 is a diagram illustrating an exemplary PGW information exchange procedure according to an embodiment of the present disclosure
  • Fig. 2 is a diagram illustrating another exemplary PGW information exchange procedure according to an embodiment of the present disclosure
  • Fig. 3 is a flowchart illustrating a method according to an embodiment of the present disclosure
  • Fig. 4 is a flowchart illustrating another method according to an embodiment of the present disclosure.
  • Fig. 5 is a block diagram illustrating an apparatus according to an embodiment of the present disclosure.
  • Fig. 6A-6B are block diagrams illustrating various apparatus according to some embodiments of the present disclosure.
  • the term “communication network” refers to a network following any suitable communication standards, such as new radio (NR) , long term evolution (LTE) , LTE-Advanced, wideband code division multiple access (WCDMA) , high-speed packet access (HSPA) , and so on.
  • NR new radio
  • LTE long term evolution
  • WCDMA wideband code division multiple access
  • HSPA high-speed packet access
  • the communications between a terminal device and a network node in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , 4G, 4.5G, 5G communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • the terms “first” , “second” and so forth refer to different elements.
  • the singular forms “a” and “an” are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • the term “based on” is to be read as “based at least in part on” .
  • the term “one embodiment” and “an embodiment” are to be read as “at least one embodiment” .
  • the term “another embodiment” is to be read as “at least one other embodiment” .
  • Other definitions, explicit and implicit, may be included below.
  • Wireless communication networks are widely deployed to provide various telecommunication services such as voice, video, data, messaging and broadcasts.
  • Various radio access technologies such as 4G/LTE and 5G/NR may be used for cellular mobile systems to meet different service requirements related to data rate, coverage and/or capacity.
  • an MME may request a PGW list from a PCRF and randomly select a PGW for a UE from the PGW list without considering whether the type of the selected PGW matches the capability of the UE.
  • the selected PGW may not be a proper PGW for the UE.
  • the selected PGW among the PGW list from the PCRF is a standalone PGW-C node, then the session established on the selected PGW may not be able to support session continuity for later mobility or handover to the 5GS network.
  • the selected PGW is a combined PGW-C and SMF node, then it may cost unnecessary SMF resource in the customers’ network.
  • the MME can figure out whether a PGW is a combined PGW-C and SMF node or a standalone PGW-C node by domain name system (DNS) query, it may be very resource-consuming and complicated because the MME may need to perform the DNS query for each PGW, which may introduce many extra DNS queries.
  • DNS domain name system
  • the MME may not be able to know whether the PGW is a combined PGW-C and SMF node or not by DNS query.
  • the MME since the MME takes PGWs among the PGW list from the PCRF as with the same priority and capability, if the PGWs have different capabilities, then the customer may not be able to fully utilize PGW resource and customize the prioritized PGW.
  • various exemplary embodiments of the present disclosure propose solutions to enable a first network entity such as an MME to obtain a PGW list and one or more parameters indicating category, priority and/or capability of PGW (s) in the PGW list, e.g., from a second network entity such as a PCRF entity.
  • the first network entity can select a proper PGW from the PGW list in a simple and highly efficient way.
  • the first network entity can choose a combined PGW-C and SMF node to facilitate 4G/5G interworking.
  • the first network entity can prioritize some PGW candidates according to the category, priority and/or capability of the PGWs, and customize the prioritized PGW as demanded by a specific application scenario.
  • AVPs attribute-value pairs
  • MIP6-Agent-Info a message such as “Credit-Control-Answer” to indicate (i) whether each PGW is a combined PGW-C and SMF node or a standalone PGW-C node, (ii) each PGW’s priority, (iii) and/or each PGW’s capability.
  • - Solution 2 Introduce a new AVP “Preferred-PGW-Type” in a message such as “Credit-Control-Request” to indicate whether a combined PGW-C and SMF node or a standalone PGW-C node is preferred; introduce a new AVP “PGW-Match-Indication” (also called “Match Indication” ) in a message such as “Credit-Control-Answer” to indicate whether one or more PGWs in a PGW list match the required preference; and/or introduce one or more new AVPs in AVP ‘MIP6-Agent-Info’ in a message such as “Credit-Control-Answer” to indicate each PGW’s priority and/or capability.
  • AVP “Preferred-PGW-Type” in a message such as “Credit-Control-Request” to indicate whether a combined PGW-C and SMF node or a standalone PGW-C node is preferred
  • PGW-Match-Indication also called “Match
  • Fig. 1 is a diagram illustrating an exemplary PGW information exchange procedure according to an embodiment of the present disclosure.
  • the exemplary PGW information exchange procedure of Fig. 1 may be implemented by performing Solution 1.
  • Exemplary network elements such as an MME and a PCRF may be involved in the PGW information exchange procedure. It can be appreciated that network elements and signaling messages shown in Fig. 1 are just as examples, and more or less alternative network elements and signaling messages may be involved in the PGW information exchange procedure according to various embodiments of the present disclosure.
  • the MME may send a Credit-Control-Request towards the PCRF, and receive a Credit-Control-Answer transmitted by the PCRF.
  • a new AVP such as “Is-Combined-Node” may be introduced for each PGW to indicate whether the PGW is a combined PGW-C and SMF node or a standalone PGW-C node.
  • one or more new AVPs such as “Priority” and/or “Capability” may be introduced in the AVP ‘MIP6-Agent-Info’ to indicate the PGW’s priority and/or capability.
  • the AVP ‘MIP6-Agent-Info’ in the Credit-Control-Answer as described with respect to Fig. 1 may be in the following format:
  • the AVP “Is-Combined-Node” may be of type Enumerated, and indicate whether the related PGW is a combined PGW-C and SMF node or a standalone PGW-C node, e.g. by using the following defined values:
  • the AVP “Priority” may be of type Unsigned32 and indicate the priority of the related PGW.
  • the AVP “Capability” may be of type Unsigned32 and indicate the capability of the related PGW.
  • the MME can simply identify and efficiently prioritize the combined PGW-C and SMF node or a standalone PGW-C node and select a proper PGW for one or more subscribers.
  • the proposed Solution 1 can enable the MME to simply and efficiently distinguish whether a PGW in the PGW list returned by the PCRF is a combined PGW-C and SMF node or a standalone PGW node, e.g., according to indication information such as the AVP “Is-Combined-Node” provided by the PCRF. Then for N1 capable UEs with 5GS subscription data, the MME can select a combined PGW-C and SMF node adaptively to support 4G/5G interworking. Moreover, the proposed Solution 1 can prioritize some PGW candidates based at least in part on the priority/capability per PGW.
  • Fig. 2 is a diagram illustrating another exemplary PGW information exchange procedure according to an embodiment of the present disclosure.
  • the exemplary PGW information exchange procedure of Fig. 2 may be implemented by performing Solution 2.
  • Exemplary network elements such as an MME and a PCRF may be involved in the PGW information exchange procedure. It can be appreciated that network elements and signaling messages shown in Fig. 2 are just as examples, and more or less alternative network elements and signaling messages may be involved in the PGW information exchange procedure according to various embodiments of the present disclosure.
  • the MME may send a Credit-Control-Request towards the PCRF.
  • a new AVP such as “Preferred-PGW-Type” may be introduced as an indication in the Credit-Control-Request to indicate the PGW type preference by the MME.
  • the AVP “Preferred-PGW-Type” may be of type Enumerated and indicate whether a combined PGW-C and SMF node or a standalone PGW-C node is preferred, e.g. by using the following defined values:
  • the PCRF may determine a PGW list and transmit a Credit-Control-Answer including the determined PGW list towards the MME.
  • the PCRF may filter one or more PGWs by using the AVP “Preferred-PGW-Type” , and only include the matched PGWs in the Credit-Control-Answer with a new AVP such as “PGW-Match-Indication” set to “True” . If no matched PGWs, the PCRF may include unmatched PGWs in the Credit-Control-Answer with the AVP “PGW-Match-Indication” set to “False” .
  • the PCRF may filter PGWs and only include the combined PGW-C and SMF nodes in the PGW list with the AVP “PGW-Match-Indication” set to “True” . If all PGWs are standalone PGWs or standalone PGW-C nodes, the PCRF may include the standalone PGWs/PGW-C nodes in the PGW list with the AVP “PGW-Match-Indication” set to “False” .
  • the AVP “PGW-Match-Indication” may be of type Enumerated and indicate whether PGW (s) in the AVP ‘MIP6-Agent-Info’ match the required PGW type preference or not, e.g. by using the following defined values:
  • one or more new AVPs such as “Priority” and/or “Capability” may be introduced in the AVP ‘MIP6-Agent-Info’ for each PGW to indicate the PGW’s priority and/or capability.
  • the AVP “Priority” may be of type Unsigned32 and indicate the priority of the related PGW.
  • the AVP “Capability” may be of type Unsigned32 and indicate the capability of the related PGW.
  • the MME can simply identify and efficiently prioritize the PGW (s) in the PGW list provided by the PCRF and select a proper PGW for one or more subscribers.
  • the proposed Solution 2 can enable the MME to know whether one or more PGWs in the PGW list returned by the PCRF match the required PGW type preference, e.g., according to indication information such as the AVP “PGW-Match-Indication” provided by the PCRF.
  • the MME can simply and efficiently select a proper PGW type for supporting 4G/5G interworking.
  • the proposed Solution 2 can also support prioritization of some PGW candidates based at least in part on the priority/capability per PGW.
  • the PCRF may obtain information about the filtered PGW (s) as requested by the MME, the PGW list in the message “Credit-Control-Answer” may be much shorter to save bandwidth.
  • Fig. 3 is a flowchart illustrating a method 300 according to some embodiments of the present disclosure.
  • the method 300 illustrated in Fig. 3 may be performed by a first network entity or an apparatus communicatively coupled to the first network entity.
  • the first network entity may be, for example, an MME or any other suitable network entity which may be configured to obtain PGW related information from another network entity.
  • the first network entity may transmit towards a second network entity (e.g., a PCRF entity, etc. ) a message for requesting information relating to one or more PGWs, as shown in block 302.
  • the first network entity may receive a response to the message which response may be transmitted by the second network entity, as shown in block 304.
  • the response may indicate the one or more PGWs (e.g., in a PGW list, etc. ) and include type information (e.g., one or more parameters/AVPs indicating category, priority and/or capability, etc. ) of the one or more PGWs.
  • the type information (e.g., a parameter/AVP “Is-Combined-Node” , etc. ) of the one or more PGWs may indicate whether the one or more PGWs are combined PGW-C and SMF nodes or standalone PGW-C nodes.
  • the type information of the one or more PGWs may indicate priorities and/or capabilities of the one or more PGWs (e.g., by using one or more parameters/AVPs such as “Priority” , “Capability” , etc. ) .
  • the first network entity may select a PGW from the one or more PGWs, according to the type information of the one or more PGWs.
  • the message transmitted towards the second network entity may include an indication of a preferred PGW type (e.g., by using a parameter/AVP “Preferred-PGW-Type” , etc. ) .
  • the indication of the preferred PGW type may indicate whether a combined PGW-C and SMF node or a standalone PGW-C node is preferred.
  • the type information of the one or more PGWs may indicate whether the one or more PGWs match the preferred PGW type (e.g., by using a parameter/AVP “PGW-Match-Indication” , etc. ) . It can be appreciated that the type information such as “PGW-Match-Indication” of the one or more PGWs may include a single indication for all of the one or more PGWs, or include multiple indications with one for each PGW.
  • the one or more PGWs indicated by the response transmitted by the second network entity may include: one or more PGWs matching the preferred PGW type; and/or one or more PGWs not matching the preferred PGW type.
  • the message transmitted towards the second network entity may be a credit control request (e.g., the message “Credit-Control-Request” as described with respect to Fig. 1 and Fig. 2, etc. )
  • the response to the message may be a credit control answer (e.g., the message “Credit-Control-Answer” as described with respect to Fig. 1 and Fig. 2, etc. ) .
  • Fig. 4 is a flowchart illustrating a method 400 according to some embodiments of the present disclosure.
  • the method 400 illustrated in Fig. 4 may be performed by a second network entity or an apparatus communicatively coupled to the second network entity.
  • the second network entity may be a PCRF entity or any other suitable network entity which may be configured to provide PGW related information to another network entity.
  • the second network entity may receive a message for requesting information relating to one or more PGWs, as shown in block 402.
  • the message may be transmitted by a first network entity (e.g., an MME, etc. ) .
  • the second network entity may transmit a response to the message towards the first network entity, as shown in block 404.
  • the response may indicate the one or more PGWs and includes type information of the one or more PGWs.
  • the message for requesting information relating to one or more PGWs received by the second network entity according to the method 400 may correspond to the message for requesting information relating to one or more PGWs transmitted by the first network entity according to the method 300.
  • the message for requesting information relating to one or more PGWs as described with respect to Fig. 3 and Fig. 4 may have the same or similar contents and/or feature elements.
  • the response to the message for requesting information relating to one or more PGWs transmitted by the second network entity according to the method 400 may correspond to the response to the message for requesting information relating to one or more PGWs received by the first network entity according to the method 300.
  • the response to the message for requesting information relating to one or more PGWs as described with respect to Fig. 3 and Fig. 4 may have the same or similar contents and/or feature elements.
  • the type information of the one or more PGWs may indicate one or more of: whether the one or more PGWs are combined PGW-C and SMF nodes or standalone PGW-C nodes; priorities of the one or more PGWs; capabilities of the one or more PGWs, etc.
  • the message received by the second network entity may include an indication of a preferred PGW type, e.g., indicating whether a combined PGW-C and SMF node or a standalone PGW-C node is preferred.
  • the second network entity may determine the one or more PGWs and indicate the one or more PGWs in the response to the message.
  • the one or more PGWs indicated by the response may include: one or more PGWs matching the preferred PGW type; and/or one or more PGWs not matching the preferred PGW type.
  • the type information of the one or more PGWs included in the response may indicate whether the one or more PGWs match the preferred PGW type.
  • Figs. 3-4 may be viewed as method steps, and/or as operations that result from operation of computer program code, and/or as a plurality of coupled logic circuit elements constructed to carry out the associated function (s) .
  • the schematic flow chart diagrams described above are generally set forth as logical flow chart diagrams. As such, the depicted order and labeled steps are indicative of specific embodiments of the presented methods. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more steps, or portions thereof, of the illustrated methods. Additionally, the order in which a particular method occurs may or may not strictly adhere to the order of the corresponding steps shown.
  • the network node and/or the network entity 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. on a cloud infrastructure.
  • Fig. 5 is a block diagram illustrating an apparatus 500 according to various embodiments of the present disclosure.
  • the apparatus 500 may comprise one or more processors such as processor 501 and one or more memories such as memory 502 storing computer program codes 503.
  • the memory 502 may be non-transitory machine/processor/computer readable storage medium.
  • the apparatus 500 may be implemented as an integrated circuit chip or module that can be plugged or installed into a first network entity as described with respect to Fig. 3, or a second network entity as described with respect to Fig. 4. In such cases, the apparatus 500 may be implemented as a first network entity as described with respect to Fig. 3, or a second network entity as described with respect to Fig. 4.
  • the one or more memories 502 and the computer program codes 503 may be configured to, with the one or more processors 501, cause the apparatus 500 at least to perform any operation of the method as described in connection with Fig. 3.
  • the one or more memories 502 and the computer program codes 503 may be configured to, with the one or more processors 501, cause the apparatus 500 at least to perform any operation of the method as described in connection with Fig. 4.
  • the one or more memories 502 and the computer program codes 503 may be configured to, with the one or more processors 501, cause the apparatus 500 at least to perform more or less operations to implement the proposed methods according to the exemplary embodiments of the present disclosure.
  • Fig. 6A is a block diagram illustrating an apparatus 610 according to some embodiments of the present disclosure.
  • the apparatus 610 may comprise a transmitting unit 611 and a receiving unit 612.
  • the apparatus 610 may be implemented in a first network entity (e.g., an MME, etc. ) .
  • the transmitting unit 611 may be operable to carry out the operation in block 302
  • the receiving unit 612 may be operable to carry out the operation in block 304.
  • the transmitting unit 611 and/or the receiving unit 612 may be operable to carry out more or less operations to implement the proposed methods according to the exemplary embodiments of the present disclosure.
  • Fig. 6B is a block diagram illustrating an apparatus 620 according to some embodiments of the present disclosure.
  • the apparatus 620 may comprise a receiving unit 621 and a transmitting unit 622.
  • the apparatus 620 may be implemented in a second network entity (e.g., a PCRF entity, etc. ) .
  • the receiving unit 621 may be operable to carry out the operation in block 402
  • the transmitting unit 622 may be operable to carry out the operation in block 404.
  • the receiving unit 621 and/or the transmitting unit 622 may be operable to carry out more or less operations to implement the proposed methods according to the exemplary embodiments of the present disclosure.
  • the various exemplary embodiments may be implemented in hardware or special purpose chips, circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto.
  • firmware or software which may be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto.
  • While various aspects of the exemplary embodiments of this disclosure may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • the exemplary embodiments of the disclosure may be practiced in various components such as integrated circuit chips and modules. It should thus be appreciated that the exemplary embodiments of this disclosure may be realized in an apparatus that is embodied as an integrated circuit, where the integrated circuit may comprise circuitry (as well as possibly firmware) for embodying at least one or more of a data processor, a digital signal processor, baseband circuitry and radio frequency circuitry that are configurable so as to operate in accordance with the exemplary embodiments of this disclosure.
  • exemplary embodiments of the disclosure may be embodied in computer-executable instructions, such as in one or more program modules, executed by one or more computers or other devices.
  • program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types when executed by a processor in a computer or other device.
  • the computer executable instructions may be stored on a computer readable medium such as a hard disk, optical disk, removable storage media, solid state memory, random access memory (RAM) , etc.
  • RAM random access memory
  • the function of the program modules may be combined or distributed as desired in various embodiments.
  • the function may be embodied in whole or partly in firmware or hardware equivalents such as integrated circuits, field programmable gate arrays (FPGA) , and the like.

Landscapes

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

Abstract

Divers modes de réalisation de la présente divulgation concernent un procédé d'échange d'informations relatives à une passerelle de réseau de données par paquets (PGW). Le procédé qui peut être mis en œuvre par une première entité de réseau comprend : la transmission vers une seconde entité de réseau d'un message pour demander des informations relatives à une ou plusieurs PGW. Conformément à un mode de réalisation donné à titre d'exemple, le procédé comprend en outre : la réception d'une réponse au message, ladite réponse étant transmise par la seconde entité de réseau. La réponse indique la ou les PGW et comprend des informations de type de la ou des PGW.
PCT/CN2022/081437 2022-03-17 2022-03-17 Procédé et appareil d'échange d'informations relatives à une passerelle de réseau de données par paquets WO2023173360A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/081437 WO2023173360A1 (fr) 2022-03-17 2022-03-17 Procédé et appareil d'échange d'informations relatives à une passerelle de réseau de données par paquets

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/081437 WO2023173360A1 (fr) 2022-03-17 2022-03-17 Procédé et appareil d'échange d'informations relatives à une passerelle de réseau de données par paquets

Publications (1)

Publication Number Publication Date
WO2023173360A1 true WO2023173360A1 (fr) 2023-09-21

Family

ID=88021928

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/081437 WO2023173360A1 (fr) 2022-03-17 2022-03-17 Procédé et appareil d'échange d'informations relatives à une passerelle de réseau de données par paquets

Country Status (1)

Country Link
WO (1) WO2023173360A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110096750A1 (en) * 2009-10-27 2011-04-28 Cisco Technology, Inc. Dynamic gateway selection process
CN110461013A (zh) * 2018-05-08 2019-11-15 华为技术有限公司 一种网元选择方法及装置
US20200053636A1 (en) * 2017-03-21 2020-02-13 Telefonaktiebolaget Lm Ericsson (Publ) SMF Selection Based On Supported DNN
US20200163008A1 (en) * 2018-11-19 2020-05-21 Telefonaktiebolaget Lm Ericsson (Publ) Selecting a network slice identifier
WO2021023299A1 (fr) * 2019-08-08 2021-02-11 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et appareil de gestion d'interopérabilité 5gs

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110096750A1 (en) * 2009-10-27 2011-04-28 Cisco Technology, Inc. Dynamic gateway selection process
US20200053636A1 (en) * 2017-03-21 2020-02-13 Telefonaktiebolaget Lm Ericsson (Publ) SMF Selection Based On Supported DNN
CN110461013A (zh) * 2018-05-08 2019-11-15 华为技术有限公司 一种网元选择方法及装置
US20200163008A1 (en) * 2018-11-19 2020-05-21 Telefonaktiebolaget Lm Ericsson (Publ) Selecting a network slice identifier
WO2021023299A1 (fr) * 2019-08-08 2021-02-11 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et appareil de gestion d'interopérabilité 5gs

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "EPS to 5GS with network slices", 3GPP DRAFT; 23502_CR0824R2_5GS_PH1_(REL-15)_S2-1813286_WAS13019_WAS11924_23502_EPS_TO_5GS_WITH_NETWORK_SLICES, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. West Palm Beach, USA; 20181126 - 20181130, 4 December 2018 (2018-12-04), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051497894 *

Similar Documents

Publication Publication Date Title
US20210274436A1 (en) Resource information sending method, first network element and system
US11736981B2 (en) Method, apparatus and computer readable media for enforcing a rule related to traffic routing
US20220014475A1 (en) Packet delay parameter obtaining method, system, and apparatus
KR101654258B1 (ko) 네트워크 선택의 동적 제어
US11057865B1 (en) Apparatus and methods for enhanced paging in wireless networks
US20210168151A1 (en) Method for implementing user plane security policy, apparatus, and system
US20150003253A1 (en) Method and apparatus for offloading traffic
JP2014511090A (ja) インテリジェントな輻輳存在通知サービス
CN109429366B (zh) 一种pdu会话处理方法及设备
US20230061152A1 (en) Communication method, apparatus, and system
WO2020252710A1 (fr) Procédé et dispositif de communication sans fil
JP2020506625A (ja) 持続可能なサービスの選択
EP4154497A1 (fr) Amélioration de la précision de classification dans des scénarios de resélection de fonction de plan utilisateur
US11147039B2 (en) Paging strategy determination method, device, RAN network element and core network element
WO2023173360A1 (fr) Procédé et appareil d'échange d'informations relatives à une passerelle de réseau de données par paquets
JP2021508418A (ja) ネットワークコンポーネント、通信端末、通信端末を接続する方法及び通信ネットワークを使用する方法
US20230336369A1 (en) Methods supporting usage reporting rules with and without associated reporting rules and related network nodes
CN115175117A (zh) 多接入下的数据冗余传输方法及其相关设备
WO2020156460A1 (fr) Procédés et nœuds de surveillance d'événements d'ue à ue
US9125167B1 (en) System and method of increasing paging accuracy
WO2022100844A1 (fr) Appareil, procédé, et programme informatique de découverte de groupe de véhicules aériens sans pilote
WO2024087776A1 (fr) Procédé et appareil d'itinérance
CN114287169B (zh) 用于改进的分组检测规则提供的方法和装置
WO2022084093A1 (fr) Procédé et appareil de formation de boucle de routage dans le domaine scp
WO2020147038A1 (fr) Procédé et appareil de sélection d'un réseau central dédié

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

Country of ref document: EP

Kind code of ref document: A1