GB2616728A - Improvements in and relating to a user equipment, UE - Google Patents

Improvements in and relating to a user equipment, UE Download PDF

Info

Publication number
GB2616728A
GB2616728A GB2301770.0A GB202301770A GB2616728A GB 2616728 A GB2616728 A GB 2616728A GB 202301770 A GB202301770 A GB 202301770A GB 2616728 A GB2616728 A GB 2616728A
Authority
GB
United Kingdom
Prior art keywords
control plane
mode
request message
service request
plane service
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
GB2301770.0A
Inventor
Watfa Mahmoud
Kumar Lalith
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.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co Ltd
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 Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Priority to PCT/KR2023/001934 priority Critical patent/WO2023153841A1/en
Publication of GB2616728A publication Critical patent/GB2616728A/en
Pending legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/30Connection release
    • H04W76/38Connection release triggered by timers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/90Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02Power saving arrangements
    • H04W52/0209Power saving arrangements in terminal devices
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02Power saving arrangements
    • H04W52/0209Power saving arrangements in terminal devices
    • H04W52/0225Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0235Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a power saving command
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02Power saving arrangements
    • H04W52/0209Power saving arrangements in terminal devices
    • H04W52/0261Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
    • H04W52/0274Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof
    • H04W52/028Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof switching on or off only a part of the equipment circuit blocks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/12Setup of transport tunnels
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/20Manipulation of established connections
    • H04W76/27Transitions between radio resource control [RRC] states

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • Emergency Management (AREA)
  • Environmental & Geological Engineering (AREA)
  • Public Health (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

A method of operating a User Equipment UE in a first mode (EPS/S1) or a second mode (5GS/N1), wherein in the first mode if: the UE receives a SERVICE ACCEPT message; the UE has set a Control plane service type of a CONTROL PLANE SERVICE REQUEST message to "mobile terminating request" and an "active" flag in the Control plane service type Information Element to 0; User Plane radio bearers have not been set up; and the CONTROL PLANE SERVICE REQUEST message was sent from EMM-IDLE mode, then the UE starts a T3440 timer to guard a time during which the UE remains in connected mode; and in the second mode if: the UE sends a CONTROL PLANE SERVICE REQUEST message; the UE did not set a Control plane service type IE to "emergency services fallback"; the UE has not included an Uplink data status IE in the CONTROL PLANE SERVICE REQUEST message, or the UE has included the Uplink data status IE in the CONTROL PLANE SERVICE REQUEST message but a received SERVICE ACCEPT message indicates that no user-plane resources of any PDU sessions are to be re-established, then the UE starts a T3540 timer to guard a time during which the UE remains in connected mode.

Description

Improvements in and relating to a User Equipment, UE The present invention relate to control of one or more certain timers in a User Equipment, UE, operable to communication with a telecommunication network. The timer or timers are provided to control certain operations in the UE. In certain circumstances in the prior art, it is possible that proper control of the timers cannot be provided which can have adverse effects, including, but not limited to, exhausting battery power due to prolonged periods in an incorrect operational state.
The UE starts timer T3440 when some conditions are met as specified in TS 24.301 V17.5.0.
The timer T3440 guards the time during which the UE keeps the NAS connection and leaves the decision to the network to release the NAS signalling connection. Upon the expiry of T3440, the UE then releases the NAS signalling connection. The need to release the connection is because, for example, the UE detects that no data or signalling has arrived from the network for a specific time (e.g. 10s) which then means that remaining in connected mode would drain power and so it is better to preserve power and enter idle mode. The different conditions that lead to the start of T3440 can be seen in section 5.3.1.2.1 of 3GPP TS 24.301 V17.5.0.
Note that a similar timer is used in 5GS, where the timer is referred to as T3540. Details of when this timer should be started is defined in section 5.3.1.3 of 3GPP TS 24.501 V17.5.0.
There is a problem with the prior art in that there is a missing case for which T3440 should be started: namely when responding to paging.
There is a particular case in which the UE should start T3440 but this case is missing in the prior art. The case is when the UE is responding to paging with the Control Plane, CP, Service Request message wherein the UE receives a Service Accept message without any User-Plane, UP, resources being established. In this case, if the UE does not start T3440, then the UE may end up remaining in connected mode for a long time and hence power will be wasted.
There are other possible cases for starting T3540 or T3440, as explained below.
The current specification, TS 24.501, does not consider the Control Plane Service Request for starting T3540. It only considers the Service Request message. However, this may be regarded as incorrect since the UE may send the Control Plane Service Request message and meet all the conditions that are defined in TS 24.501 in order to start T3540 with the Service Request message. This means that if the UE indeed sends the Control Plane Service Request message, then the UE will stay in connected mode for a longer time and waste battery resources Further, there is another case which is missing for which T3440 or T3540 is not started. This is when the UE sends a Control Plane Service Request message and indicates to the network that it has no more uplink data to send, nor any downlink data that is expected. If this occurs, then the UE will remain in connected mode for potentially a long time and drain battery resources.
It is an aim of embodiments of the present invention to define certain conditions to avoid wasting battery resources, in particular. Other problems, not set out above may be addressed or overcome, at least in part.
According to the present invention there is provided an apparatus and method as set forth in the appended claims. Other features of the invention will be apparent from the dependent claims, and the description which follows.
According to a first aspect of the present invention, there is provided a method of operating a User Equipment, the UE being operable in a first mode or a second mode, and being further operable to communicate with a telecommunication network, wherein in the first mode (EPS/S1) if: the UE receives a SERVICE ACCEPT message; the UE has set a Control plane service type of a CONTROL PLANE SERVICE REQUEST message to "mobile terminating request" and an "active" flag in the Control plane service type Information Element, IE, to 0; User Plane, UP, radio bearers have not been set up; and the CONTROL PLANE SERVICE REQUEST message was sent from EMM-IDLE mode, then the UE starts a timer to guard a time during which the UE remains in connected mode; and in the second mode (5GS/N1) if: the UE sends a CONTROL PLANE SERVICE REQUEST message; the UE did not set a Control plane service type IE to "emergency services fallback"; the UE has not included an Uplink data status IE in the CONTROL PLANE SERVICE REQUEST message, or the UE has included the Uplink data status IE in the CONTROL 30 PLANE SERVICE REQUEST message but a received SERVICE ACCEPT message indicates that no user-plane resources of any PDU sessions are to be re-established, then the UE starts a timer to guard a time during which the UE remains in connected mode.
In an embodiment, additionally in the second mode, the timer is started if: the UE has not included an Allowed PDU session status IE or has included the Allowed PDU session status IE indicating there is no PDU session for which the UE allowed a user-plane resource to be re-established over 3GPP access in the SERVICE REQUEST message or the CONTROL PLANE SERVICE REQUEST message; or the UE has included the Allowed PDU session status IE in the SERVICE REQUEST message or the CONTROL PLANE SERVICE REQUEST message but the SERVICE ACCEPT message does not indicate that any user-plane resources of any PDU sessions are to be re-established.
In an embodiment, the first mode is EPS or S1, and the second mode is 5GS or Ni.
In an embodiment, the timer in the first mode is T3440, and the timer in the second mode is T3540.
According to a second aspect of the present invention, there is provide a UE operable to perform the method of the first aspect.
Although a few preferred embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes and modifications might be made without departing from the scope of the invention, as defined in the appended claims.
For a better understanding of the invention, and to show how embodiments of the same may be carried into effect, reference will now be made, by way of example only, to the accompanying diagrammatic drawings in which: Figure 1 shows a flowchart illustrating the operation of an embodiment of the invention.
An embodiment of the present invention defines a set of new conditions for starting timer T3440. In this embodiment, the UE should start timer T3440 when any combination of the following conditions are met, where the conditions may be verified in any order: a) the UE receives a SERVICE ACCEPT message b) the UE sent a CONTROL PLANE SERVICE REQUEST message optionally from EMM-IDLE mode (or from EMM-IDLE mode with suspend indication) c) the Control plane service type indicated "mobile terminating request" (or the Control plane service type did not indicate "mobile originating request") d) the "Active" flag bit in the Control plane service type IE is set to "No radio bearer establishment requested" i.e. it is set to the value 0 (or the "Active" flag bit in the Control plane service type IE is not set to "Radio bearer establishment requested" i.e. the "Active" flag bit in the Control plane service type IE is not set to the value 1) Alternatively, the "Active" flag bit in the Control plane service type IE is set to "Radio bearer establishment requested" i.e. the "Active" flag bit in the Control plane service type IE is set to the value 1.
H. Alternatively, the value of the "Active" flag bit in the Control plane service type IE is not relevant i.e. its value or the entire bit itself may be ignored e) the user plane radio bearers have not been set up 0 the UE is using control plane CloT EPS optimization g) Optionally, the Control Plane Service Request message did not include the ESM message container IE (or the NAS message container 1E) h) Optionally, the Control Plane Service Request message did include the ESM message container IE but the DDX field in the Release assistance indication IE is set to a value that indicates "No further uplink and no further downlink data transmission subsequent to the uplink data transmission is expected" Further, if some or all of the conditions above are met, the UE can/should start T3440. Note that this means that the UE may also check for other conditions in addition to those listed above and then the UE starts the timer T3440 when the conditions are met. As such, the conditions listed above may not be exhaustive for all the cases which may arise in the future. Note that some of the conditions above may also be different, where for example, the value of an IE may be any value and not just limited to one value. For example, any combination of the conditions may be considered in addition to Control plane service type field taking any value.
Note that the UE may start T3440 when a subset (or any combination, where it may be at least one condition) of the conditions above is met i.e. not all of the conditions above need to be met but a subset (in any combination) of them may be sufficient to start T3440.
The UE may stop (and optionally restart) the timer T3440 when any combination of the following occurs: a) the UE receives any NAS message, such as, but not limited to, ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST, MODIFY EPS BEARER CONTEXT REQUEST, DEACTIVATE EPS BEARER CONTEXT REQUEST, DOWNLINK NAS TRANSPORT or DOWNLINK GENERIC NAS TRANSPORT message b) the UE receives the ESM DATA TRANSPORT message c) the user plane radio bearers are set up The UE may then use the existing NAS signalling connection to send uplink signalling via the existing NAS signalling connection.
Note that the details set out above can also be applicable to N1 mode, where the same or substantially similar conditions can be checked and the timer T3540 can be started when the relevant conditions are met.
In a further embodiment, the prior art conditions defined in TS 24.501 are also applicable to the Control Plane Service Request message. Here, the UE should also start T3540 when any of the following conditions are met, in any order or combination: a) the UE receives a SERVICE ACCEPT message; b) the UE set the Control plane service type IE to "mobile terminating request" (or did not set the Control plane service type IE to "mobile originating request", or did not set it to "emergency services", or did not set it to "emergency services fallback"), the UE has not included the Uplink data status IE in the CONTROL PLANE SERVICE REQUEST message, or the UE has included the Uplink data status IE in the CONTROL PLANE SERVICE REQUEST message but the SERVICE ACCEPT message indicates that no user-plane resources of any PDU sessions are to be re-established; c) the UE has not included the Allowed PDU session status IE in the CONTROL PLANE SERVICE REQUEST message, or has included the Allowed PDU session status IE indicating there is no PDU session(s) for which the UE allowed the user-plane resource to be re-established over 3GPP access in the CONTROL PLANE SERVICE REQUEST message, or the UE has included the Allowed PDU session status IE in the CONTROL SERVICE REQUEST message but the SERVICE ACCEPT message does not indicate that any user-plane resources of any PDU sessions are to be re-established; d) the service request procedure has been initiated in SGMM-IDLE mode; e) the user-plane resources for PDU sessions have not been set up; f) the UE need not request resources for V2X communication over PC5 reference point (see 3GPP TS 23.287 [6C]); and g) the UE need not request resources for ProSe direct discovery over PC5 or ProSe direct communication over PC5 (see 3GPP TS 23.304); Note that the lower layers indicate when the user-plane resources for PDU sessions are successfully established or released.
Note, also, that the above conditions are meant as an example, and a subset of the above may be verified. It should also be noted that the order of verifying the conditions may vary i.e. the order in which the various conditions are verified is not significant to the operation of any particular embodiment. It should also be noted that at least any combination of the above can be verified, in addition to other conditions that can be introduced later. Once these conditions are met, the UE should start T3540.
In this case, the UE may stop (and optionally restart) the timer T3540 when any combination of the following occurs: a) the UE receives any NAS message b) the user plane radio bearers are set up or the user resources are set up The UE may then use the existing NAS signalling connection to send uplink signalling via the existing NAS signalling connection.
In a still further embodiment, there are certain other conditions which may be evaluated or used to start T3440 or T3540, as appropriate.
The UE should start timer T3440 (in S1 mode) or T3540 (in N1 mode) when any of the following conditions are met, in any order or combination: a) the UE receives a SERVICE ACCEPT message b) the UE sent a CONTROL PLANE SERVICE REQUEST message from EMM-IDLE mode (or EMM-IDLE mode with suspend indication) for the case of S1 mode, or from 5GMM-IDLE mode (or 5GMM-IDLE mode with suspend indication) for the case of N1 mode c) the Control plane service type indicated "mobile originating request" (or it did not indicate "mobile terminating request") d) the "Active" flag bit in the Control plane service type IE is set to "No radio bearer establishment requested" i.e. it is set to the value 0 (or the "Active" flag bit in the Control plane service type IE is not set to "Radio bearer establishment requested" i.e. the "Active" flag bit in the Control plane service type IE is not set to the value 1). Note that this is applicable to S1 mode only e) The UE did not include the Uplink data status IE in the Control Plane Service Request message. Note that this is applicable to N1 mode only f) the user plane radio bearers, or user plane resources, have not been set up g) the UE is using control plane CloT EPS optimization in S1 mode, or the UE is using control plane CloT 5GS optimization in N1 mode h) The DDX field in the Release assistance indication IE is set to a value that indicates "No further uplink and no further downlink data transmission subsequent to the uplink data transmission is expected" i.e. it is set to the value '01' i. Note that in S1 mode, this field is in the ESM DATA TRANSPORT message ii. Note that in N1 mode, this field is in the CloT small data container IE, or in the Release assistance indication IE that is part of the Control Plane Service Request message Further, when one or more of the conditions above are met, the UE can start T3440 or T3540. This means that the UE may also check for other conditions in addition to those listed above and then the UE starts the timer T3440 or T3540 when the conditions are met. As such, the conditions listed above are not intended to be exhaustive for all the cases which may arise in the future. Note that some of the conditions above may also be different, where for example, the value of an IE may be any value and not just limited to one value. For example, any combination of the conditions may be considered in addition to Control plane service type field taking any value.
In this case, the UE may stop (and optionally restart) the timer T3440 or T3540 when any combination of the following occurs: a) the UE receives any NAS message b) the user plane radio bearers are set up or the user resources are set up The UE may then use the existing NAS signalling connection to send uplink signalling via the existing NAS signalling connection.
Note that for all of the procedures set out herein, the UE should enter EMM-IDLE mode when timer T3440 expires in S1 mode, or the UE should enter 5GMM-IDLE mode when T3540 expires in N1 mode.
Figure 1 shows a representation of the operation of an embodiment of the present invention.
At step S101, the UE is operable in one of a first mode (EPS) and second mode (5GS). At step S102, one or more conditions are checked, as set out in the foregoing and if true, the appropriate timer (T3440 or T3540, as appropriate) is started to guard a time during which the UE remains in connected mode.
At least some of the example embodiments described herein may be constructed, partially or wholly, using dedicated special-purpose hardware. Terms such as 'component', 'module' or unit' used herein may include, but are not limited to, a hardware device, such as circuitry in the form of discrete or integrated components, a Field Programmable Gate Array (FPGA) or Application Specific Integrated Circuit (ASIC), which performs certain tasks or provides the associated functionality. In some embodiments, the described elements may be configured to reside on a tangible, persistent, addressable storage medium and may be configured to execute on one or more processors. These functional elements may in some embodiments include, by way of example, components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. Although the example embodiments have been described with reference to the components, modules and units discussed herein, such functional elements may be combined into fewer elements or separated into additional elements. Various combinations of optional features have been described herein, and it will be appreciated that described features may be combined in any suitable combination. In particular, the features of any one example embodiment may be combined with features of any other embodiment, as appropriate, except where such combinations are mutually exclusive. Throughout this specification, the term "comprising" or "comprises" means including the component(s) specified but not to the exclusion of the presence of others.
Attention is directed to all papers and documents which are filed concurrently with or previous to this specification in connection with this application and which are open to public inspection with this specification, and the contents of all such papers and documents are incorporated herein by reference.
All of the features disclosed in this specification (including any accompanying claims, abstract 35 and drawings), and/or all of the steps of any method or process so disclosed, may be combined in any combination, except combinations where at least some of such features and/or steps are mutually exclusive.
Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise. Thus, unless expressly stated otherwise, each feature disclosed is one example only of a generic series of equivalent or similar features.
The invention is not restricted to the details of the foregoing embodiment(s). The invention extends to any novel one, or any novel combination, of the features disclosed in this specification (including any accompanying claims, abstract and drawings), or to any novel one, or any novel combination, of the steps of any method or process so disclosed.

Claims (5)

  1. CLAIMS1. A method of operating a User Equipment, the UE being operable in a first mode or a second mode, and being further operable to communicate with a telecommunication network, wherein in the first mode if: the UE receives a SERVICE ACCEPT message; the UE has set a Control plane service type of a CONTROL PLANE SERVICE REQUEST message to "mobile terminating request" and an "active" flag in the Control plane service type Information Element, IE, to 0; User Plane, UP, radio bearers have not been set up; and the CONTROL PLANE SERVICE REQUEST message was sent from EMM-IDLE mode, then the UE starts a timer to guard a time during which the UE remains in connected mode; and in the second mode if: the UE sends a CONTROL PLANE SERVICE REQUEST message; the UE did not set a Control plane service type IE to "emergency services fallback"; the UE has not included an Uplink data status IE in the CONTROL PLANE SERVICE REQUEST message, or the UE has included the Uplink data status IE in the CONTROL PLANE SERVICE REQUEST message but a received SERVICE ACCEPT message indicates that no user-plane resources of any PDU sessions are to be re-established, then the UE starts a timer to guard a time during which the UE remains in connected mode.
  2. 2. The method of claim 1 wherein additionally in the second mode, the timer is started if: the UE has not included an Allowed PDU session status IE or has included the Allowed PDU session status IE indicating there is no PDU session for which the UE allowed a user-plane resource to be re-established over 3GPP access in the SERVICE REQUEST message or the CONTROL PLANE SERVICE REQUEST message; or the UE has included the Allowed PDU session status IE in the SERVICE REQUEST message or the CONTROL PLANE SERVICE REQUEST message but the SERVICE ACCEPT message does not indicate that any user-plane resources of any PDU sessions are to be re-established.
  3. 3. The method of claim 1 or claim 2 wherein the first mode is EPS or S1, and the second mode is 5GS or N1.
  4. 4. The method of any preceding claim wherein the timer in the first mode is T3440, and the timer in the second mode is T3540.
  5. 5. A UE operable to perform the method of any preceding claim.
GB2301770.0A 2022-02-09 2023-02-08 Improvements in and relating to a user equipment, UE Pending GB2616728A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/KR2023/001934 WO2023153841A1 (en) 2022-02-09 2023-02-09 Improvements in and relating to a user equipment, ue

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
IN202231006896 2022-02-09

Publications (1)

Publication Number Publication Date
GB2616728A true GB2616728A (en) 2023-09-20

Family

ID=87760150

Family Applications (2)

Application Number Title Priority Date Filing Date
GB2301770.0A Pending GB2616728A (en) 2022-02-09 2023-02-08 Improvements in and relating to a user equipment, UE
GBGB2402559.5A Pending GB202402559D0 (en) 2022-02-09 2023-02-08 Improvements in and relating to a user equipment,ue

Family Applications After (1)

Application Number Title Priority Date Filing Date
GBGB2402559.5A Pending GB202402559D0 (en) 2022-02-09 2023-02-08 Improvements in and relating to a user equipment,ue

Country Status (1)

Country Link
GB (2) GB2616728A (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2606436A (en) * 2021-02-16 2022-11-09 Samsung Electronics Co Ltd Improvements in and relating to the operation of a User Equipment and a telecommunication network

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2606436A (en) * 2021-02-16 2022-11-09 Samsung Electronics Co Ltd Improvements in and relating to the operation of a User Equipment and a telecommunication network

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
Mediatek Inc."Correction of T3440 start scenarios for TAU procedure" *

Also Published As

Publication number Publication date
GB202402559D0 (en) 2024-04-10

Similar Documents

Publication Publication Date Title
CN112333825B (en) Method and device for updating UE (user Equipment) strategy and computer storage medium
EP2687060B1 (en) Methods, apparatuses and system for preserving session context during inter-radio access technology service retry
EP3860189B1 (en) Ue migration method, apparatus, system, and storage medium
US11206537B2 (en) Session activation method, apparatus, and system
TWI657707B (en) Device and method of handling a state mismatch in a wireless communication system
CN112690021B (en) Method and apparatus for determining whether to transmit network slice selection assistance information
JP2021508217A (en) NG-RAN node, UE, NG-RAN node method, and UE method
JP2008533894A (en) Call re-establishment via an alternative access network
TW201511586A (en) System and method for peer-to-peer authorization via non-access stratum procedures
WO2012041197A1 (en) Method and network side device for handling mobility management process
WO2011088728A1 (en) Informing method and equipment for index parameter of access type/frequency of selection priority
GB2606436A (en) Improvements in and relating to the operation of a User Equipment and a telecommunication network
JP2014515573A (en) Service response method, apparatus and system
EP1327364B1 (en) Connection release in a two-layer communication network
GB2594533A (en) Emergency services for user equipment
GB2616728A (en) Improvements in and relating to a user equipment, UE
GB2614410A (en) Improvements in and relating to improving disaster roaming service
CN111277990B (en) VoLTE-based emergency call method, system, terminal, device and storage medium
CN112715038B (en) Parameter configuration method and device and network equipment
GB2611413A (en) Improvements in and relating to control plane data transmission
GB2616115A (en) Methods for collision and abnormal cases for proximity services, ProSe
GB2608262A (en) Improvements in and relating to proximity services in a telecommunication network
GB2619827A (en) Improvements in and relating to proximity services in a telecommunication network
US20230189202A1 (en) Network transferring method, terminal, and network-side device
WO2019063086A1 (en) Context transfer via last visited ran node