US20200113009A1 - Handling Of Invalid Mandatory Information In Mobile Communications - Google Patents

Handling Of Invalid Mandatory Information In Mobile Communications Download PDF

Info

Publication number
US20200113009A1
US20200113009A1 US16/593,502 US201916593502A US2020113009A1 US 20200113009 A1 US20200113009 A1 US 20200113009A1 US 201916593502 A US201916593502 A US 201916593502A US 2020113009 A1 US2020113009 A1 US 2020113009A1
Authority
US
United States
Prior art keywords
message
pdu session
5gsm
error
handling
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.)
Abandoned
Application number
US16/593,502
Other languages
English (en)
Inventor
Chien-Chun Huang-Fu
Yu-Chieh Tien
Chi-Hsien Chen
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.)
MediaTek Inc
Original Assignee
MediaTek Inc
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 MediaTek Inc filed Critical MediaTek Inc
Priority to US16/593,502 priority Critical patent/US20200113009A1/en
Assigned to MEDIATEK INC. reassignment MEDIATEK INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: CHEN, CHI-HSIEN, HUANG-FU, CHIEN-CHUN, TIEN, Yu-Chieh
Priority to TW108136184A priority patent/TWI734209B/zh
Priority to CN201980003921.4A priority patent/CN111295928A/zh
Priority to PCT/CN2019/109910 priority patent/WO2020069677A1/fr
Publication of US20200113009A1 publication Critical patent/US20200113009A1/en
Priority to IL282397A priority patent/IL282397A/en
Abandoned 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/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • 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/04—Error control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • 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
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/34—Selective release of ongoing connections
    • H04W76/36—Selective release of ongoing connections for reassigning the resources associated with the released connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/30—Network data restoration; Network data reliability; Network data fault tolerance
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/12—Application layer protocols, e.g. WAP [Wireless Application Protocol]

Definitions

  • the present disclosure is generally related to mobile communications and, more particularly, to handling of invalid mandatory information in mobile communications.
  • non-access stratum (NAS) procedures in a 5th Generation system can be used for 5GS mobility management between a user equipment (UE) and an Access and Mobility Management Function (AMF) for both 3GPP access and non-3GPP access.
  • the NAS procedures can also be used for 5GS session management between the UE and a Session Management Function (SMF) for both 3GPP access and non-3GPP access.
  • SMF Session Management Function
  • 5GSM 5G Session Management
  • the 5G Session Management (5GSM) protocol defined in the 3GPP specifications e.g., TS 24.301
  • PDU 5GS protocol data unit
  • the 5GSM protocol is used for the control of user plane (UP) bearers, as the 5G Session Management Function (SMF) is responsible for interacting with the decoupled data plane, creating, updating and removing PDU sessions and managing session context with the User Plane Function (UPF).
  • SMF 5G Session Management Function
  • a method may involve a processor of an apparatus receiving a 5GSM message from a network node of a wireless network. The method may also involve the processor determining that there is an error encountered with a mandatory information element (IE) in the 5GSM message. The method may further involve the processor handing the error in a way specific to a PDU session procedure corresponding to the 5GSM message.
  • IE mandatory information element
  • a method may involve a processor of an apparatus determining that there is an error encountered with a mandatory IE in a 5GSM message from a network node of a wireless network. The method may also involve the processor handling the error in a way depending on to which PDU session procedure the 5GSM message corresponds.
  • the PDU session procedure to which the 5GSM message corresponds may be a PDU session establishment procedure, a PDU session modification procedure, or a PDU session release procedure.
  • an apparatus may include a transceiver and a processor coupled to the transceiver.
  • the transceiver may be configured to wirelessly communicate with a network node of a wireless network.
  • the processor may be configured to receive, via the transceiver, a 5GSM message from the network node.
  • the processor may be also configured to determine that there is an error encountered with a mandatory IE in the 5GSM message.
  • the processor may be further configured to handle the error in a way specific to a PDU session procedure corresponding to the 5GSM message.
  • FIG. 1 is a diagram of an example network environment in which various proposed schemes in accordance with the present disclosure may be implemented.
  • FIG. 2 is a block diagram of an example communication system in accordance with an implementation of the present disclosure.
  • FIG. 3 is a flowchart of an example process in accordance with an implementation of the present disclosure.
  • FIG. 4 is a flowchart of an example process in accordance with an implementation of the present disclosure.
  • Implementations in accordance with the present disclosure relate to various techniques, methods, schemes and/or solutions pertaining to handling of invalid mandatory information in mobile communications.
  • a number of possible solutions may be implemented separately or jointly. That is, although these possible solutions may be described below separately, two or more of these possible solutions may be implemented in one combination or another.
  • FIG. 1 illustrates an example network environment 100 in which various solutions and schemes in accordance with the present disclosure may be implemented.
  • network environment 100 may involve a UE 110 in wireless communication with a wireless network 120 (e.g., a 5G NR mobile network or an NB-IoT network) via a network node 125 (e.g., a base station such as an eNB, a gNB or a transmit-receive point (TRP)).
  • a wireless network 120 e.g., a 5G NR mobile network or an NB-IoT network
  • a network node 125 e.g., a base station such as an eNB, a gNB or a transmit-receive point (TRP)
  • UE 110 and wireless network 120 may implement various schemes pertaining handling of invalid mandatory information in mobile communications in accordance with the present disclosure.
  • UE 110 may receive a 5GSM message for a PDU session-related procedure from wireless network 120 via network node 125 and may determine that there is an error encountered with a mandatory IE in the 5GSM message. Accordingly, UE 110 may handle the error in a way specific to the PDU session-related procedure, which may be a PDU session establishment procedure, a PDU session modification procedure, or a PDU session release procedure.
  • the PDU session-related procedure may be a PDU session establishment procedure, a PDU session modification procedure, or a PDU session release procedure.
  • UE 110 may handle the error by initiating a PDU session release procedure. For instance, UE 110 may send a PDU SESSION RELEASE REQUEST message to network node 125 with a 5GSM cause #96 to indicate invalid mandatory information.
  • UE 110 may handle the error by sending a PDU SESSION MODIFICATION COMMAND REJECT message to network node 125 with a 5GSM cause #96 to indicate invalid mandatory information.
  • UE 110 may handle the error by sending a PDU SESSION RELEASE COMPLETE message to network node 125 with a 5GSM cause #96 to indicate invalid mandatory information.
  • FIG. 2 illustrates an example communication system 200 having an example apparatus 210 and an example apparatus 220 in accordance with an implementation of the present disclosure.
  • apparatus 210 and apparatus 220 may perform various functions to implement schemes, techniques, processes and methods described herein pertaining to handling of invalid mandatory information in mobile communications, including various schemes described above as well as process 400 described below.
  • Each of apparatus 210 and apparatus 220 may be a part of an electronic apparatus, which may be a UE such as a portable or mobile apparatus, a wearable apparatus, a wireless communication apparatus or a computing apparatus.
  • each of apparatus 210 and apparatus 220 may be implemented in a smartphone, a smartwatch, a personal digital assistant, a digital camera, or a computing equipment such as a tablet computer, a laptop computer or a notebook computer.
  • Each of apparatus 210 and apparatus 220 may also be a part of a machine type apparatus, which may be an IoT or NB-IoT apparatus such as an immobile or a stationary apparatus, a home apparatus, a wire communication apparatus or a computing apparatus.
  • each of apparatus 210 and apparatus 220 may be implemented in a smart thermostat, a smart fridge, a smart door lock, a wireless speaker or a home control center.
  • each of apparatus 210 and apparatus 220 may be implemented in the form of one or more integrated-circuit (IC) chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, one or more complex-instruction-set-computing (CISC) processors, or one or more reduced-instruction-set-computing (RISC) processors.
  • CISC complex-instruction-set-computing
  • RISC reduced-instruction-set-computing
  • Each of apparatus 210 and apparatus 220 may include at least some of those components shown in FIG. 2 such as a processor 212 and a processor 222 , respectively.
  • Each of apparatus 210 and apparatus 220 may further include one or more other components not pertinent to the proposed scheme of the present disclosure (e.g., internal power supply, display device and/or user interface device), and, thus, such component(s) of each of apparatus 210 and apparatus 220 are neither shown in FIG. 2 nor described below in the interest of simplicity and brevity.
  • components not pertinent to the proposed scheme of the present disclosure e.g., internal power supply, display device and/or user interface device
  • At least one of apparatus 210 and apparatus 220 may be a part of an electronic apparatus, which may be a network node or base station (e.g., eNB, gNB or TRP), a small cell, a router or a gateway.
  • a network node or base station e.g., eNB, gNB or TRP
  • a small cell e.g., a router or a gateway.
  • at least one of apparatus 210 and apparatus 220 may be implemented in an eNodeB in an LTE, LTE-Advanced or LTE-Advanced Pro network or in a gNB in a 5G, NR, IoT or NB-IoT network.
  • apparatus 210 and apparatus 220 may be implemented in the form of one or more IC chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, or one or more CISC or RISC processors.
  • each of processor 212 and processor 222 may be implemented in the form of one or more single-core processors, one or more multi-core processors, or one or more CISC or RISC processors. That is, even though a singular term “a processor” is used herein to refer to processor 212 and processor 222 , each of processor 212 and processor 222 may include multiple processors in some implementations and a single processor in other implementations in accordance with the present disclosure.
  • each of processor 212 and processor 222 may be implemented in the form of hardware (and, optionally, firmware) with electronic components including, for example and without limitation, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors and/or one or more varactors that are configured and arranged to achieve specific purposes in accordance with the present disclosure.
  • each of processor 212 and processor 222 is a special-purpose machine specifically designed, arranged and configured to perform specific tasks including handling of invalid mandatory information in mobile communications in accordance with various implementations of the present disclosure.
  • apparatus 210 may also include a transceiver 216 , as a communication device, coupled to processor 212 and capable of wirelessly transmitting and receiving data.
  • apparatus 210 may further include a memory 214 coupled to processor 212 and capable of being accessed by processor 212 and storing data therein.
  • apparatus 220 may also include a transceiver 226 , as a communication device, coupled to processor 222 and capable of wirelessly transmitting and receiving data.
  • apparatus 220 may further include a memory 224 coupled to processor 222 and capable of being accessed by processor 222 and storing data therein. Accordingly, apparatus 210 and apparatus 220 may wirelessly communicate with each other via transceiver 216 and transceiver 226 , respectively.
  • apparatus 210 is implemented in or as a UE (e.g., UE 110 ) and apparatus 220 is implemented in or as a network node (e.g., network node 125 ) of a wireless network (e.g., wireless network 120 ).
  • UE e.g., UE 110
  • network node e.g., network node 125
  • wireless network e.g., wireless network 120
  • processor 212 of apparatus 210 may receive, via transceiver 216 , a 5GSM message from apparatus 220 as a network node of a wireless network. Additionally, processor 212 may determine that there is an error encountered with a mandatory IE in the 5GSM message. Moreover, processor 212 may handle the error in a way specific to a PDU session procedure corresponding to the 5GSM message.
  • the 5GSM message may include a PDU SESSION ESTABLISHMENT ACCEPT message.
  • processor 212 may initiate a PDU session release procedure.
  • processor 212 may send, via transceiver 216 , a PDU SESSION RELEASE REQUEST message to apparatus 220 with a 5GSM cause #96 to indicate invalid mandatory information.
  • the 5GSM message may include a PDU SESSION MODIFICATION COMMAND message.
  • processor 212 may send, via transceiver 216 , a PDU SESSION MODIFICATION COMMAND REJECT message to apparatus 220 with a 5GSM cause #96 to indicate invalid mandatory information.
  • the 5GSM message may include a PDU SESSION RELEASE COMMAND message.
  • processor 212 may send, via transceiver 216 , a PDU SESSION RELEASE COMPLETE message to apparatus 220 with a 5GSM cause #96 to indicate invalid mandatory information.
  • processor 212 of apparatus 210 may determine that there is an error encountered with a mandatory IE in a 5GSM message from apparatus 220 as a network node of a wireless network. Furthermore, processor 212 may handle the error in a way depending on to which PDU session procedure the 5GSM message corresponds.
  • the PDU session procedure to which the 5GSM message corresponds may include a PDU session establishment procedure, a PDU session modification procedure, or a PDU session release procedure.
  • the 5GSM message may include a PDU SESSION ESTABLISHMENT ACCEPT message.
  • processor 212 may initiate a PDU session release procedure.
  • processor 212 may send, via transceiver 216 , a PDU SESSION RELEASE REQUEST message to apparatus 220 with a 5GSM cause #96 to indicate invalid mandatory information.
  • the 5GSM message may include a PDU SESSION MODIFICATION COMMAND message.
  • processor 212 may send, via transceiver 216 , a PDU SESSION MODIFICATION COMMAND REJECT message to apparatus 220 with a 5GSM cause #96 to indicate invalid mandatory information.
  • the 5GSM message may include a PDU SESSION RELEASE COMMAND message.
  • processor 212 may send, via transceiver 216 , a PDU SESSION RELEASE COMPLETE message to apparatus 220 with a 5GSM cause #96 to indicate invalid mandatory information.
  • FIG. 3 illustrates an example process 300 in accordance with an implementation of the present disclosure.
  • Process 300 may be an example implementation of the proposed schemes described above with respect to handling of invalid mandatory information in mobile communications in accordance with the present disclosure.
  • Process 300 may represent an aspect of implementation of features of apparatus 210 and apparatus 220 .
  • Process 300 may include one or more operations, actions, or functions as illustrated by one or more of blocks 310 , 320 and 330 . Although illustrated as discrete blocks, various blocks of process 300 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks of process 300 may executed in the order shown in FIG. 3 or, alternatively, in a different order. Process 300 may also be repeated partially or entirely.
  • Process 300 may be implemented by apparatus 210 , apparatus 220 and/or any suitable wireless communication device, UE, base station or machine type devices. Solely for illustrative purposes and without limitation, process 300 is described below in the context of apparatus 210 in or as a UE and apparatus 220 in or as a network node of a wireless network (e.g., 5G NR mobile network). Process 300 may begin at block 310 .
  • a wireless network e.g., 5G NR mobile network
  • process 300 may involve processor 212 of apparatus 210 receiving, via transceiver 216 , a 5GSM message from apparatus 220 as a network node of a wireless network. Process 300 may proceed from 310 to 320 .
  • process 300 may involve processor 212 determining that there is an error encountered with a mandatory information element (IE) in the 5GSM message.
  • Process 300 may proceed from 320 to 330 .
  • IE mandatory information element
  • process 300 may involve processor 212 handling the error in a way specific to a PDU session procedure corresponding to the 5GSM message.
  • the 5GSM message may include a PDU SESSION ESTABLISHMENT ACCEPT message.
  • process 300 may involve processor 212 initiating a PDU session release procedure.
  • process 300 may involve processor 212 sending, via transceiver 216 , a PDU SESSION RELEASE REQUEST message to apparatus 220 with a 5GSM cause #96 to indicate invalid mandatory information.
  • the 5GSM message may include a PDU SESSION MODIFICATION COMMAND message.
  • process 300 may involve processor 212 sending, via transceiver 216 , a PDU SESSION MODIFICATION COMMAND REJECT message to apparatus 220 with a 5GSM cause #96 to indicate invalid mandatory information.
  • the 5GSM message may include a PDU SESSION RELEASE COMMAND message.
  • process 300 may involve processor 212 sending, via transceiver 216 , a PDU SESSION RELEASE COMPLETE message to apparatus 220 with a 5GSM cause #96 to indicate invalid mandatory information.
  • FIG. 4 illustrates an example process 400 in accordance with an implementation of the present disclosure.
  • Process 400 may be an example implementation of the proposed schemes described above with respect to handling of invalid mandatory information in mobile communications in accordance with the present disclosure.
  • Process 400 may represent an aspect of implementation of features of apparatus 210 and apparatus 220 .
  • Process 400 may include one or more operations, actions, or functions as illustrated by one or more of blocks 410 and 420 . Although illustrated as discrete blocks, various blocks of process 400 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks of process 400 may executed in the order shown in FIG. 4 or, alternatively, in a different order. Process 400 may also be repeated partially or entirely.
  • Process 400 may be implemented by apparatus 210 , apparatus 220 and/or any suitable wireless communication device, UE, base station or machine type devices. Solely for illustrative purposes and without limitation, process 400 is described below in the context of apparatus 210 in or as a UE and apparatus 220 in or as a network node of a wireless network (e.g., 5G NR mobile network). Process 400 may begin at block 410 .
  • a wireless network e.g., 5G NR mobile network
  • process 400 may involve processor 212 of apparatus 210 determining that there is an error encountered with a mandatory IE in a 5GSM message from apparatus 220 as a network node of a wireless network. Process 400 may proceed from 410 to 420 .
  • process 400 may involve processor 212 handling the error in a way depending on to which PDU session procedure the 5GSM message corresponds.
  • the PDU session procedure to which the 5GSM message corresponds may include a PDU session establishment procedure, a PDU session modification procedure, or a PDU session release procedure.
  • the 5GSM message may include a PDU SESSION ESTABLISHMENT ACCEPT message.
  • process 400 may involve processor 212 initiating a PDU session release procedure.
  • process 400 may involve processor 212 sending, via transceiver 216 , a PDU SESSION RELEASE REQUEST message to apparatus 220 with a 5GSM cause #96 to indicate invalid mandatory information.
  • the 5GSM message may include a PDU SESSION MODIFICATION COMMAND message.
  • process 400 may involve processor 212 sending, via transceiver 216 , a PDU SESSION MODIFICATION COMMAND REJECT message to apparatus 220 with a 5GSM cause #96 to indicate invalid mandatory information.
  • the 5GSM message may include a PDU SESSION RELEASE COMMAND message.
  • process 400 may involve processor 212 sending, via transceiver 216 , a PDU SESSION RELEASE COMPLETE message to apparatus 220 with a 5GSM cause #96 to indicate invalid mandatory information.
  • any two components so associated can also be viewed as being “operably connected”, or “operably coupled”, to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being “operably couplable”, to each other to achieve the desired functionality.
  • operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Computer And Data Communications (AREA)
US16/593,502 2018-10-06 2019-10-04 Handling Of Invalid Mandatory Information In Mobile Communications Abandoned US20200113009A1 (en)

Priority Applications (5)

Application Number Priority Date Filing Date Title
US16/593,502 US20200113009A1 (en) 2018-10-06 2019-10-04 Handling Of Invalid Mandatory Information In Mobile Communications
TW108136184A TWI734209B (zh) 2018-10-06 2019-10-05 無效強制性資訊處理方法及其裝置
CN201980003921.4A CN111295928A (zh) 2018-10-06 2019-10-08 移动通信的无效强制性信息处理技术
PCT/CN2019/109910 WO2020069677A1 (fr) 2018-10-06 2019-10-08 Traitement d'élément d'information obligatoire invalide dans des communications mobiles
IL282397A IL282397A (en) 2018-10-06 2021-04-18 Handling illegal information is necessary in mobile communications

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201862742325P 2018-10-06 2018-10-06
US16/593,502 US20200113009A1 (en) 2018-10-06 2019-10-04 Handling Of Invalid Mandatory Information In Mobile Communications

Publications (1)

Publication Number Publication Date
US20200113009A1 true US20200113009A1 (en) 2020-04-09

Family

ID=70050817

Family Applications (4)

Application Number Title Priority Date Filing Date
US16/593,016 Active US11160123B2 (en) 2018-10-06 2019-10-04 5G session management handling on PSI mismatch
US16/593,030 Active 2039-12-12 US11026275B2 (en) 2018-10-06 2019-10-04 Handling of collision between PDU session establishment and release procedures
US16/593,490 Active 2039-12-25 US11184934B2 (en) 2018-10-06 2019-10-04 AT-command for always-on PDU session
US16/593,502 Abandoned US20200113009A1 (en) 2018-10-06 2019-10-04 Handling Of Invalid Mandatory Information In Mobile Communications

Family Applications Before (3)

Application Number Title Priority Date Filing Date
US16/593,016 Active US11160123B2 (en) 2018-10-06 2019-10-04 5G session management handling on PSI mismatch
US16/593,030 Active 2039-12-12 US11026275B2 (en) 2018-10-06 2019-10-04 Handling of collision between PDU session establishment and release procedures
US16/593,490 Active 2039-12-25 US11184934B2 (en) 2018-10-06 2019-10-04 AT-command for always-on PDU session

Country Status (6)

Country Link
US (4) US11160123B2 (fr)
EP (2) EP3841825B1 (fr)
CN (4) CN111295922B (fr)
IL (1) IL282397A (fr)
TW (4) TWI734209B (fr)
WO (4) WO2020069681A1 (fr)

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11160123B2 (en) * 2018-10-06 2021-10-26 Mediatek Inc. 5G session management handling on PSI mismatch
US11212720B2 (en) * 2018-10-16 2021-12-28 Mediatek Inc. 5GSM handling on invalid PDU session
KR20210020705A (ko) * 2019-08-16 2021-02-24 삼성전자주식회사 무선 통신 시스템에서 pdu 세션을 핸들링하기 위한 장치 및 방법
JP7448279B2 (ja) * 2019-10-31 2024-03-12 日本電気株式会社 無線端末及びその方法
GB2598098B (en) * 2020-08-11 2023-11-22 Samsung Electronics Co Ltd Management of unstructured PDU session types
CN114173335A (zh) * 2020-08-20 2022-03-11 维沃移动通信有限公司 会话处理方法、装置、终端及网络侧设备
WO2022056830A1 (fr) * 2020-09-18 2022-03-24 Qualcomm Incorporated Retransmission rapide d'une demande d'établissement de session pdu après une défaillance de couche inférieure
US20220353937A1 (en) * 2021-04-29 2022-11-03 Mediatek Inc. Multi-access pdu session establishment abnormal handling
US20220353951A1 (en) * 2021-04-29 2022-11-03 Mediatek Inc. Collision of ue-requested pdu session release procedure and network-requested pdu session release procedure
EP4353021A1 (fr) * 2021-06-11 2024-04-17 Samsung Electronics Co., Ltd. Procédé et appareil amf pour fonctionnement nsac sur la base de l'utilisation réelle de l'équipement utilisateur (ue)
CN113596957A (zh) * 2021-07-13 2021-11-02 Oppo广东移动通信有限公司 数据处理方法及装置、设备、存储介质
TWI793697B (zh) * 2021-08-03 2023-02-21 緯創資通股份有限公司 恆在協定資料單元會話之增強信令方法及使用者裝置
KR20230024641A (ko) * 2021-08-12 2023-02-21 삼성전자주식회사 복수의 가입자 식별 모듈을 포함하는 전자 장치
US20230133792A1 (en) * 2021-11-03 2023-05-04 Mediatek Inc. Handling of collision between pdu session establishment and modification procedure
GB202403402D0 (en) * 2022-01-05 2024-04-24 Samsung Electronics Co Ltd Methods for collision and abnormal cases for proximity services,prose

Family Cites Families (46)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1502469B1 (fr) * 2002-05-06 2014-03-12 Nokia Corporation Systeme et procede de traitement de sessions d'urgence dans des reseaux de communications
CN101030964B (zh) 2006-03-03 2011-07-20 华为技术有限公司 会话控制装置和方法
CN101617486A (zh) * 2006-11-06 2009-12-30 维罗森特系统股份有限公司 用来监视移动数据网络中的tcp会话和形成相应性能度量的方法和装置
US7730189B2 (en) * 2006-11-22 2010-06-01 Airvana, Inc. Network-initiated session recovery
AU2013201919A1 (en) * 2007-09-28 2013-04-11 Interdigital Patent Holdings, Inc Method and apparatus for selecting a radio link control protocol data unit size
CN101471869B (zh) 2007-12-27 2011-04-20 华为技术有限公司 会话处理方法、系统和装置
EP2702712B1 (fr) * 2011-04-29 2019-06-05 LG Electronics Inc. Procédé pour le traitement de données associées à la gestion de session et à la gestion de mobilité
US20130182586A1 (en) * 2012-01-18 2013-07-18 Qualcomm Incorporated Obtaining communication session initiation information in a wireless communications system
US20140051415A1 (en) 2012-08-16 2014-02-20 Ozgur Ekici Reducing data transfer latency caused by state transitions in mobile networks
US9554366B2 (en) * 2012-08-31 2017-01-24 Qualcomm Incorporated Optimized always-on wireless service using network assistance and keep-alives
CN103716112A (zh) * 2012-09-28 2014-04-09 中兴通讯股份有限公司 通过控制面信令传输数据的方法、设备及系统
US9094899B2 (en) * 2013-05-28 2015-07-28 Rivada Networks, Llc Cell selection in dynamic spectrum arbitrage system
US20150376383A1 (en) * 2014-06-26 2015-12-31 The Procter & Gamble Company Films having low sound pressure levels
US10142251B2 (en) * 2015-01-26 2018-11-27 Hfi Innovation Inc. Control of maximum transmission unit size discovery using AT commands
US9730062B2 (en) * 2015-04-30 2017-08-08 Intel IP Corporation AT command for secure ESM information
CN112911644A (zh) * 2015-05-18 2021-06-04 苹果公司 用于分组数据网络连接卸荷的注意(at)命令
WO2017139130A1 (fr) * 2016-02-10 2017-08-17 Intel IP Corporation Rattachement sans connectivité de pdn
US10362511B2 (en) 2016-05-17 2019-07-23 Lg Electronics Inc. Method and apparatus for determining PDU session identity in wireless communication system
WO2017200562A1 (fr) 2016-05-19 2017-11-23 Intel Corporation Conception de couche supérieure pour le traitement de paquets de plan de commande dans une communication vestimentaire de cinquième génération (5g)
CN107592331B (zh) * 2016-07-08 2021-11-02 中兴通讯股份有限公司 会话连续的实现方法、装置及系统
CN107690161B (zh) 2016-08-05 2019-08-30 电信科学技术研究院 一种pdu会话的处理方法及设备
CN116347662A (zh) * 2016-08-19 2023-06-27 日本电气株式会社 每个会话用户平面连接激活或停用的方法
EP3547790B1 (fr) * 2016-11-27 2021-04-14 LG Electronics Inc. Procédé de désenregistrement dans un système de communication sans fil, et dispositif correspondant
US10455641B2 (en) * 2017-01-05 2019-10-22 Huawei Technologies Co., Ltd. Protocol data unit management
EP3876661B1 (fr) 2017-01-09 2023-03-08 Telefonaktiebolaget LM Ericsson (publ) Gestion d'une demande de service
CN108289306B (zh) * 2017-01-10 2023-03-10 中兴通讯股份有限公司 一种流程冲突处理方法及装置
US10470199B2 (en) * 2017-01-10 2019-11-05 Htc Corporation Device and method of handling a PDU session in inter-system mobility between a LTE system and a NR/5G system
US10841084B2 (en) * 2017-02-03 2020-11-17 Qualcomm Incorporated Session management authorization token
CN108400997A (zh) * 2017-02-06 2018-08-14 电信科学技术研究院 会话管理方法、终端、管理功能实体及接入网节点
US20180234839A1 (en) 2017-02-13 2018-08-16 Futurewei Technologies, Inc. System and Method for User Equipment Identification and Communications
US10476914B2 (en) * 2017-02-16 2019-11-12 Htc Corporation Device and method for performing an internet protocol multimedia subsystem service
US20200015311A1 (en) * 2017-03-20 2020-01-09 Lg Electronics Inc. Method for processing nas message in wireless communication system and apparatus for same
KR102289879B1 (ko) * 2017-03-20 2021-08-13 삼성전자 주식회사 셀룰러망에서 세션의 다양한 ssc 모드 지원을 위한 upf 변경 방안
WO2018174509A1 (fr) * 2017-03-20 2018-09-27 Samsung Electronics Co., Ltd. Procédé de prise en charge d'activation et de désactivation de session pdu efficaces dans des réseaux cellulaires
US10575220B2 (en) 2017-03-21 2020-02-25 Electronics And Telecommunications Research Institute Session management method based on reallocation of PDU session anchor device, and device performing the session management method
US10757611B2 (en) * 2017-09-22 2020-08-25 Ofinno, Llc SMF and AMF relocation during UE registration
EP3673682B1 (fr) * 2017-09-28 2023-12-27 Ofinno, LLC Relocalisation de smf, d'amf et d'upf pendant l'enregistrement d'un équipement utilisateur (ue)
CN108260162B (zh) * 2018-01-29 2021-02-02 重庆邮电大学 一种5g系统的sdap层功能实现方法
WO2019160376A1 (fr) * 2018-02-18 2019-08-22 엘지전자 주식회사 Procédé d'émission et de réception de signal par smf dans un système de communication sans fil et dispositif associé
EP4210424A1 (fr) * 2018-03-23 2023-07-12 Samsung Electronics Co., Ltd. Procédés, terminal et entité de réseau pour gérer une procédure de demande de service dans un réseau de communication
US10911979B2 (en) * 2018-04-09 2021-02-02 Mediatek Inc. AT commands for 5G session management
CN113993143A (zh) * 2018-05-22 2022-01-28 华为技术有限公司 会话管理方法、装置和系统
US11006478B2 (en) * 2018-06-27 2021-05-11 Mediatek Inc. Enhanced procedure transaction ID handling
CN110831031B (zh) * 2018-08-13 2021-10-01 大唐移动通信设备有限公司 一种持续在线pdu会话的管理方法及装置
US11160123B2 (en) * 2018-10-06 2021-10-26 Mediatek Inc. 5G session management handling on PSI mismatch
US11212720B2 (en) * 2018-10-16 2021-12-28 Mediatek Inc. 5GSM handling on invalid PDU session

Also Published As

Publication number Publication date
CN111295928A (zh) 2020-06-16
WO2020069678A1 (fr) 2020-04-09
US20200113002A1 (en) 2020-04-09
US20200113004A1 (en) 2020-04-09
CN111373836B (zh) 2023-10-13
TWI740226B (zh) 2021-09-21
WO2020069679A1 (fr) 2020-04-09
EP3841826A1 (fr) 2021-06-30
EP3841825A1 (fr) 2021-06-30
US11160123B2 (en) 2021-10-26
CN111418256A (zh) 2020-07-14
TW202021409A (zh) 2020-06-01
WO2020069681A1 (fr) 2020-04-09
TWI786334B (zh) 2022-12-11
US20200113014A1 (en) 2020-04-09
EP3841825A4 (fr) 2021-11-17
IL282397A (en) 2021-06-30
CN111295922A (zh) 2020-06-16
WO2020069677A1 (fr) 2020-04-09
US11184934B2 (en) 2021-11-23
EP3841825B1 (fr) 2023-08-23
TWI734209B (zh) 2021-07-21
TW202017429A (zh) 2020-05-01
CN111418256B (zh) 2023-04-14
TW202021410A (zh) 2020-06-01
TW202015388A (zh) 2020-04-16
CN111295922B (zh) 2023-08-25
CN111373836A (zh) 2020-07-03
TWI747056B (zh) 2021-11-21
EP3841826A4 (fr) 2021-11-17
US11026275B2 (en) 2021-06-01

Similar Documents

Publication Publication Date Title
US20200113009A1 (en) Handling Of Invalid Mandatory Information In Mobile Communications
US10887787B2 (en) Reflective QoS control in wireless communications
US11540312B2 (en) Method and apparatus for handling multiple active configurations of configured grant in mobile communications
US20190132771A1 (en) Buffer Status Report For Split Bearer Preprocessing In Wireless Communications
US20180343689A1 (en) Method And Apparatus For Handling Problem Cell In Mobile Communications
US20200267645A1 (en) Power Saving For New Radio Carrier Aggregation
WO2019091408A1 (fr) Procédé et appareil de gestion de temporisateur de repli dans une solution de contrôle d'encombrement au niveau gestion de session
US11064450B2 (en) Synchronization of QoS flows and rules in mobile communications
US10911300B2 (en) Optimization for device provisioning protocol onboarding in wireless networks
US10616114B2 (en) Congestion control handling between communication apparatus and network
US20210153291A1 (en) Method And Apparatus For Handling Packet Data Convergence Protocol Duplication In Mobile Communications
US11399308B2 (en) Error handling on missing configuration for inter-system change in mobile communications
US11457353B2 (en) Indication of additional security capabilities using NAS signaling in 5G mobile communications
US20230180283A1 (en) Methods For Intra-User Equipment Prioritization In Wireless Communications
CN111183705B (zh) 用于系统间切换的遗失配置错误处理方法及其装置
US20190029064A1 (en) Method And Apparatus For Handling Re-Attempt Indicator In Mobile Communications
US20210266856A1 (en) User Equipment Reachability After Notification In Mobile Communications
WO2022151928A1 (fr) Procédures de planification pusch dans des communications mobiles
US20240008078A1 (en) Methods For Signaling Of UE-Initiated COT In Mobile Communications
US20220225386A1 (en) Methods For Base Station And UE COT Sharing In Mobile Communications
US20200136779A1 (en) Overhead Reduction In Transmission of Small Ethernet Packets Over A Wireless Link

Legal Events

Date Code Title Description
AS Assignment

Owner name: MEDIATEK INC., TAIWAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HUANG-FU, CHIEN-CHUN;TIEN, YU-CHIEH;CHEN, CHI-HSIEN;REEL/FRAME:050628/0967

Effective date: 20191002

STPP Information on status: patent application and granting procedure in general

Free format text: FINAL REJECTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION