WO2020204097A1 - Ｕｅ、及び通信制御方法 - Google Patents

Ｕｅ、及び通信制御方法 Download PDF

Info

Publication number
WO2020204097A1
WO2020204097A1 PCT/JP2020/015083 JP2020015083W WO2020204097A1 WO 2020204097 A1 WO2020204097 A1 WO 2020204097A1 JP 2020015083 W JP2020015083 W JP 2020015083W WO 2020204097 A1 WO2020204097 A1 WO 2020204097A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu session
congestion management
identification information
information
network
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.)
Ceased
Application number
PCT/JP2020/015083
Other languages
English (en)
French (fr)
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.)
Sharp Corp
Original Assignee
Sharp 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 Sharp Corp filed Critical Sharp Corp
Priority to US17/599,902 priority Critical patent/US12256451B2/en
Publication of WO2020204097A1 publication Critical patent/WO2020204097A1/ja
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • 5GS 5th Generation mobile communication systems
  • 5GS is a system that realizes 5G mobile communication systems.
  • 5G System is being specified (see Non-Patent Document 1 and Non-Patent Document 2).
  • 5GS extracts technical issues for connecting a wide variety of terminals to cellular networks and specifies solutions.
  • the UE of the present invention is a UE (User Equipment) including a transmission / reception unit and a control unit, and the transmission / reception unit is a PDU (Protocol Data Unit) session from a control device in a PDU (Protocol Data Unit) session establishment procedure.
  • the control unit Upon receiving the establishment refusal message, the control unit includes the first information and the backoff timer value in the PDU session establishment refusal message, and the S-NSSAI (Single Network Slice Selection Assistance information) is also DNN (Data).
  • the Network Name also, if not provided during the PDU session establishment procedure, also initiates a backoff timer using the backoff timer value, the first information being a resource for a particular slice and DNN.
  • core network_A90, core network_B190, or a combination thereof may also be referred to as a core network
  • access network_A, access network_B, or a combination thereof may also be referred to as an access network or a wireless access network. It may also be referred to as DN_A5, PDN_A6 or a combination thereof.
  • the NG-RAN_A120 is a 5G access network, which may be the (R) AN shown in FIG. 4, and includes one or more NR nodes (New Radio Access Technology node) _A122 and / or ng-eNB. It is composed.
  • NR node_A122 is a radio base station to which UE_A10 is connected by 5G radio access (5G Radio Access), and is also referred to as gNB.
  • the ng-eNB may be an eNB (E-UTRA) that constitutes a 5G access network, may be connected to the core network_B190 via NR node_A, or may be directly connected to the core network_B190. You may be.
  • E-UTRA eNB
  • each NR node_A122 and / or ng-eNB may be connected to each other.
  • UE_A10 is connected to each radio access network means that it is connected to a base station device, an access point, or the like included in each radio access network, and data, signals, etc. to be transmitted and received. It also means that it goes through a base station device or an access point.
  • the control message sent and received between UE_A10 and the core network_B190 may be the same control message regardless of the type of access network. Therefore, the fact that UE_A10 and the core network_B190 send and receive messages via NR node_A122 may be the same as that UE_A10 and core network_B190 send messages via eNB_A45.
  • MME_A40 may be a relay device that transfers user data as a gateway between the core network_A90 and the access network.
  • the user data transmitted / received using MME_A40 as a gateway may be small data.
  • Assigned Session Type is information indicating the type of PDU session. Assigned Session Type may be Assigned PDN Type. The type of PDU session can be IP or non-IP. In addition, if the type of PDU session is IP, it may further include information indicating the type of PDN assigned by the network. The Assigned Session Type may be IPv4, IPv6, or IPv4 v6.
  • the DNN may be information equal to the APN or information different from the APN.
  • each device may manage the information indicating the correspondence between the DNN and the APN, or may carry out a procedure for inquiring the APN using the DNN. You may carry out the procedure to inquire about DNN using APN.
  • the second NW slice in the present embodiment is a NW slice to which another PDU session that can connect to the DN to which the PDU session belonging to the first NW slice belongs belongs.
  • the first NW slice and the second NW slice may be operated by the same operator or may be operated by different operators.
  • the 16th identification information is the information for identifying either of the 1st congestion management and the 4th congestion management, and the 4th congestion management with respect to the 16th identification information.
  • the value corresponding to is the information that can be set, and at least the 16th identification information is not received.
  • the 16th identification information is information for identifying any of the 1st congestion management, the 2nd congestion management, and the 4th congestion management, and the 16th identification information is used.
  • the 16th identification information is used.
  • UE_A10 includes at least one or more identification information from the first identification information to the fourth identification information, and / or at least one of the eleventh identification information to the eighteenth identification information.
  • the identification may be based on one identification information of the above, or a combination of two or more identification information.
  • the 16th identification information is information for identifying any of the 1st congestion management, the 2nd congestion management, and the 4th congestion management, and the 16th identification information is used. When only the value corresponding to the first congestion management and the value corresponding to the second congestion management can be set, and at least the 16th identification information is not received.
  • the seventeenth behavior in the present embodiment is the UE that identifies the congestion management to be stopped from among one or more congestion managements applied by the UE based on the reception of the control message transmitted by the core network. It may be behavior. For example, the UE may identify congestion management that suspends or modifies application based on the 21st identification information.
  • the reason value is whether the congestion management that the NW notifies the UE based on the refusal to establish the PDU session is the first congestion management, the second congestion management, the third congestion management, and the fourth. It may be information for identifying which of the congestion management of the above is the congestion management. In this case, depending on whether it is the first congestion management, the second congestion management, or one of the third congestion management and the fourth congestion management, the NW May send a different value to the UE as the reason value.
  • the UE grasps the meaning of each value transmitted as the reason value in advance, and in the fifteenth behavior, it is the first congestion management or the second congestion management based on at least the fifteenth identification information. It may be possible to identify whether it is one of the third congestion management and the fourth congestion management.
  • the exchange of various information and / or negotiation of various requests is performed in the PDU session establishment procedure and / or network-led session management. It may be carried out by the procedure.
  • the fourth condition determination may be executed based on whether or not AMF_A240 has received the SM, and may be executed based on whether or not the registration request message includes the SM message. For example, the fourth condition determination may be true if AMF_A240 receives SM and / or if the registration request message contains an SM message, if AMF_A240 does not receive SM, and / Or it may be false if the registration request message does not contain the SM message.
  • the condition for determining the truth of the fourth condition determination does not have to be limited to the above-mentioned condition.
  • SMF_A230 in the core network_B190 receives the PDU session establishment request message and executes the third condition determination.
  • the third condition determination is for determining whether or not SMF_A230 accepts the request of UE_A10.
  • SMF_A230 determines whether the third condition determination is true or false.
  • SMF_A230 starts the procedure (A) in this procedure when the third condition judgment is true, and starts the procedure (B) in this procedure when the third condition judgment is false. The step when the third condition determination is false will be described later.
  • the SMF_A230 may include one or more identification information out of the 11th to 18th identification information in the PDU session establishment refusal message, and by including these identification information, the request of UE_A10 is rejected. You may show that.
  • two or more identification information of these identification information may be configured as one or more identification information.
  • the fourth process is the process in which UE_A10 sets the value indicated by the 14th identification information as the first timer value. Alternatively, it may be a process of starting the first timer for which a timer value is set. Further, when UE_A10 receives the eleventh identification information, the fourth process may be a process of executing one or more of the first to eleventh behaviors.
  • the fifth processing example will be described below.
  • UE_A10 may include the following supplementary information in the network-led session management completion message.
  • the first congestion management for the default DNN is distinguished from the first congestion management for a specific DNN because it is applied based on the UE-led session management request that does not use the DNN information. Therefore, it is expressed as "congestion management for No DNN".
  • a UE-led session management request such as a PDU session establishment request message that does not use DNN is expressed as a UE-led session management request that uses No DNN.
  • the PDU session establishment request message using No DNN is a PDU session establishment request message not using DNN.
  • UE_A10 may perform the same processing regardless of whether the first congestion management is for a specific DNN or No DNN.
  • UE_A10 counts the backoff timer associated with the third congestion management for [No S-NSSAI, DNN] in these PLMN changes, or for [No S-NSSAI, DNN].
  • UE_A10 is set to not send the PDU session establishment request message to [No S-NSSAI, DNN] in the new PLMN. You can. Therefore, UE_10 may be restricted from sending PDU session establishment request messages to [No S-NSSAI, DNN] based on this setting.
  • the application of congestion management may be continued until the power of the terminal is turned off or USIM is taken out.
  • the processing regulated at that time may be the same as the processing regulated when the backoff timer is counted according to each type of congestion management.
  • UE_A10 is allowed to send the SM request message described in each example, which was prohibited by the PLMN before the change, depending on the backoff timer being counted. It may be set to.
  • UE_A10 changes the PLMN when the PLMN before the change is the home PLMN and the 21st identification information is received when the backoff timer is received, and / or UE_A10 changes the PLMN.
  • the PLMN before the change is the home PLMN and the 20th identification information is not received when the backoff timer is received
  • each of the PLMNs at the destination PLMN is counted according to the backoff timer.
  • the regulation of sending the SM request message described in the example may be continued.
  • UE_A10 may be set to prohibit the transmission of the SM request message described in each example according to the counting backoff timer.
  • UE_A10 counts if the backoff timer is being counted in the PLMN before the change and the backoff timer is being counted in the destination PLMN as well.
  • the regulation of sending the SM request message described in each example may be continued.
  • UE_A10 may be set to prohibit the transmission of the SM request message described in each example according to the counting backoff timer.
  • the process of UE_A10 when receiving the backoff timer at the home PLMN and then moving from the home PLMN to another PLMN in the fifth processing example will be described.
  • the processing of UE_A10 when moving from the home PLMN to another PLMN while the backoff timer is being executed will be described below.
  • UE_A10 may be set to allow the transmission of the SM request message described in each example according to the counting backoff timer.
  • UE_A10 is allowed to send the SM request message described in each example, which was prohibited by the PLMN before the change, depending on the backoff timer being counted. It may be set to.
  • the destination PLMN may be set to allow the transmission of the SM request message described in each example according to the counting backoff timer.
  • UE_A10 may be set to allow the transmission of the SM request message described in each example according to the counting backoff timer.
  • the process of UE_A10 when receiving the backoff timer at the home PLMN and then moving from the home PLMN to another PLMN in the eighth processing example will be described.
  • the processing of UE_A10 when moving from the home PLMN to another PLMN while the backoff timer is being executed will be described below.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/JP2020/015083 2019-04-01 2020-04-01 Ｕｅ、及び通信制御方法 Ceased WO2020204097A1 (ja)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US17/599,902 US12256451B2 (en) 2019-04-01 2020-04-01 UE and communication control method for controlling transmitting PDU session request message

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2019070077A JP7240227B2 (ja) 2019-04-01 2019-04-01 Ｕｅ、及び通信制御方法
JP2019-070077 2019-04-01

Publications (1)

Publication Number Publication Date
WO2020204097A1 true WO2020204097A1 (ja) 2020-10-08

Family

ID=72668968

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2020/015083 Ceased WO2020204097A1 (ja) 2019-04-01 2020-04-01 Ｕｅ、及び通信制御方法

Country Status (3)

Country Link
US (1) US12256451B2 (enExample)
JP (1) JP7240227B2 (enExample)
WO (1) WO2020204097A1 (enExample)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7336239B2 (ja) * 2019-04-01 2023-08-31 シャープ株式会社 Ｕｅ、及び通信制御方法
WO2021132096A1 (ja) * 2019-12-26 2021-07-01 日本電気株式会社 Ａｍｆノード及びその方法
CN116234057A (zh) * 2022-12-30 2023-06-06 中国电信股份有限公司 通信方法、通信装置、电子设备及可读存储介质

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2019004410A (ja) * 2017-06-19 2019-01-10 シャープ株式会社 端末装置、コアネットワーク内の装置、データネットワーク内の装置、及び通信制御方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11457403B2 (en) * 2018-05-08 2022-09-27 Lg Electronics Inc. Method and user equipment for performing access control in 5GS
EP3892035A4 (en) * 2018-12-05 2022-08-03 INTEL Corporation CONGESTION CONTROL IN DIFFERENT PUBLIC LAND MOBILE NETWORKS

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2019004410A (ja) * 2017-06-19 2019-01-10 シャープ株式会社 端末装置、コアネットワーク内の装置、データネットワーク内の装置、及び通信制御方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CATT: "Update the 5GSM procedure related to 5GSM congestion control [ online", 3GPP TSG CT WG1 #115, 2019.03.01 , C1-191548, 1 March 2019 (2019-03-01), XP051592531, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/tsg_ct/WG1_mm-cc-sm_ex-CN1/TSGC1_115_Montreal/Docs/C1-191548.zip> [retrieved on 20200609] *

Also Published As

Publication number Publication date
JP7240227B2 (ja) 2023-03-15
JP2020170900A (ja) 2020-10-15
US20220201787A1 (en) 2022-06-23
US12256451B2 (en) 2025-03-18

Similar Documents

Publication Publication Date Title
JP6884731B2 (ja) Ｕｅ通信制御方法
JP6869908B2 (ja) Ｕｅ及びｕｅの通信制御方法
JP6855431B2 (ja) Ｕｅ及びｕｅの通信制御方法
JP6884730B2 (ja) Ｕｅ通信制御方法
WO2020071502A1 (ja) Ｕｅ
JP7079141B2 (ja) Ｕｅ通信制御方法
JP7390798B2 (ja) Ｕｅ、及び通信制御方法
WO2020100636A1 (ja) Ｕｅ及び通信制御方法
JP7216553B2 (ja) Ｕｅ、コアネットワーク装置、及び通信制御方法
JP6901413B2 (ja) Ｕｅ及びｕｅの通信制御方法
WO2020204097A1 (ja) Ｕｅ、及び通信制御方法
JP7712875B2 (ja) Ｕｅ、及び通信制御方法
CN113678496B (zh) Ue以及通信控制方法
JP2019186718A (ja) Ｕｅ、制御装置、及び通信制御方法
JP7652710B2 (ja) Ｕｅ、及び通信制御方法
JP7336239B2 (ja) Ｕｅ、及び通信制御方法
JP7362344B2 (ja) Ｕｅ、及び通信制御方法
WO2020153126A1 (ja) Ｕｅ
JP2019145935A (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: 20785120

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

Country of ref document: EP

Kind code of ref document: A1

WWG Wipo information: grant in national office

Ref document number: 17599902

Country of ref document: US