CN115669013A - Method, apparatus and computer program product for accelerating emergency service initiation - Google Patents
Method, apparatus and computer program product for accelerating emergency service initiation Download PDFInfo
- Publication number
- CN115669013A CN115669013A CN202180037371.5A CN202180037371A CN115669013A CN 115669013 A CN115669013 A CN 115669013A CN 202180037371 A CN202180037371 A CN 202180037371A CN 115669013 A CN115669013 A CN 115669013A
- Authority
- CN
- China
- Prior art keywords
- request
- registration request
- registration
- response
- emergency 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 123
- 238000004590 computer program Methods 0.000 title claims abstract description 66
- 230000000977 initiatory effect Effects 0.000 title claims description 13
- 230000004044 response Effects 0.000 claims abstract description 116
- 230000006854 communication Effects 0.000 claims description 137
- 238000004891 communication Methods 0.000 claims description 136
- 230000015654 memory Effects 0.000 claims description 34
- 230000001960 triggered effect Effects 0.000 abstract description 2
- 230000006870 function Effects 0.000 description 46
- 230000005540 biological transmission Effects 0.000 description 12
- 238000012545 processing Methods 0.000 description 10
- 230000000737 periodic effect Effects 0.000 description 9
- 238000007726 management method Methods 0.000 description 8
- 238000005516 engineering process Methods 0.000 description 7
- 230000001413 cellular effect Effects 0.000 description 6
- 238000010295 mobile communication Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 6
- 230000004048 modification Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 230000011664 signaling Effects 0.000 description 3
- 230000033228 biological regulation Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 230000002708 enhancing effect Effects 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000000926 separation method Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- RYGMFSIKBFXOCR-UHFFFAOYSA-N Copper Chemical compound [Cu] RYGMFSIKBFXOCR-UHFFFAOYSA-N 0.000 description 1
- XUIMIQQOPSSXEZ-UHFFFAOYSA-N Silicon Chemical compound [Si] XUIMIQQOPSSXEZ-UHFFFAOYSA-N 0.000 description 1
- 238000007792 addition Methods 0.000 description 1
- 230000003321 amplification Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 239000011521 glass Substances 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000014759 maintenance of location Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 238000003199 nucleic acid amplification method Methods 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000010287 polarization Effects 0.000 description 1
- 230000010076 replication Effects 0.000 description 1
- 230000008054 signal transmission Effects 0.000 description 1
- 229910052710 silicon Inorganic materials 0.000 description 1
- 239000010703 silicon Substances 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W60/02—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration by periodical registration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/14—Reselecting a network or an air interface
- H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
- H04W36/1443—Reselecting a network or an air interface over a different radio air interface technology between licensed networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/50—Connection management for emergency connections
-
- 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
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)
- Hardware Redundancy (AREA)
Abstract
A method, apparatus and computer program product provide an enhanced emergency service fallback procedure. A User Equipment (UE) may indicate emergency service fallback to a network entity, such as an access and mobility management function (AMF), within a registration request message. Upon receiving the registration request message, an emergency service fallback procedure is triggered. The UE receives the indication via, for example, an Access Stratum (AS) layer, and the received indication is treated AS a registration response message, such AS by a non-access stratum (NAS) layer in the UE. The UE is configured to respond differently upon receiving a differently configured registration response reject message or upon expiration of a response timer.
Description
Technical Field
Example embodiments are generally directed to supporting and accelerating initiation of an emergency service fallback (fallback) procedure for a user equipment on a communication network, such as a third generation partnership project (3 GPP) fifth generation (5G) communication network.
Background
A communication system may be seen as a facility that enables communication sessions between two or more entities, such as user equipment, base stations/access points, network Functions (NFs) and/or other nodes, by providing connections between the various entities involved in a communication path. A communication system may for example be provided with a communication network and one or more compatible communication devices. With the continued evolution of telecommunication networks, fifth generation mobile networks (5G networks) are now expected to be the next major phase of the mobile telecommunication standard and will bring many improvements in the mobile network user experience. For example, 5G networks should provide new technical solutions to achieve greater throughput, lower latency, higher reliability, higher connectivity, and greater mobility range. In addition to these improvements in performance, 5G networks are also expected to extend the flexibility of network usage and provide users with a wider range of use cases and business models.
The third generation partnership project (3 GPP) is a standards organization that develops mobile telephony protocols and is known for developing and maintaining various standards, including second generation (2G), third generation (3G), fourth generation (4G), long Term Evolution (LTE), and fifth generation (5G) standards. 5G networks have been designed as service-based architectures (SBAs), e.g., a system architecture in which system functions are implemented by a set of NFs that provide services to other authorized NFs to access the services of the set of NFs. The 5G network allows for supporting emergency service fallback registration between User Equipment (UE) and access and mobility management functions (AMF).
The UE initially registers with the AMF and maintains communication through periodic registration updates. If the registration procedure for mobility and periodic registration updates fails due to a lost response from the network or due to current 3GPP rejection criteria, the UE cannot initiate any additional mobility management procedures except for a subsequent attempt to initiate the registration procedure. Due to this limitation, the registration procedure is enhanced so that the UE can include the allowed Protocol Data Unit (PDU) session state Information Element (IE) in the registration request. With this enhancement, if a registration procedure is initiated due to a particular 3GPP standard and there is a PDU session associated with a non-3 GPP access and the UE allows the PDU session to be transferred to the 3GPP access, data Link (DL) data of the PDU session may be transferred directly to the 3GP access via the registration procedure.
However, an enhanced registration procedure has not been provided for emergency service fallback procedures. Thus, the UE needs to perform a registration procedure and then a service request procedure in order for the AMF to trigger an emergency service fallback procedure. In case the registration procedure or the periodic registration update fails, access to the emergency service fallback procedure is delayed accordingly.
Disclosure of Invention
A method, apparatus and computer program product for enhancing an emergency service fallback procedure are disclosed. The emergency service fallback procedure is initiated during the registration update procedure without the UE having to first complete the registration update procedure and then separately initiate and complete the emergency service fallback procedure. As a result, access to emergency service fallback procedures may be advantageously accelerated, such as in the event of a registration update procedure failure.
In an example embodiment, a method is provided that includes causing a registration request to be sent during a registration update procedure, the registration request including at least a registration type value indicating an emergency service fallback request. The method also includes determining a response to the registration request that includes an emergency service fallback request.
In an example embodiment, a method is provided wherein the registration request to be sent further includes a follow-up request bit defining that no follow-up request is pending. In an example embodiment, a method is provided, wherein determining a response to the registration request comprises: in the event that the mode has changed or a connection to the network has been established, it is determined that the emergency service fallback request has been accepted. In an example embodiment, there is provided a method, further comprising: starting a timer when a registration request is caused to be sent; and stopping the timer upon determining that the emergency service fallback request has been accepted. In an example embodiment, a method is provided wherein determining a response to the registration request comprises determining that the emergency service fallback request has not been accepted. In an example embodiment, a method is provided in which a predefined cause value is provided in response to a registration request, the method further comprising selecting a cell connected to an Evolved Packet Core (EPC) or a 5G core network (5 GCN). The method also includes initiating communication via the cell. In an example embodiment, there is provided a method, further comprising: starting a timer when a communication via a cell is transmitted; and stopping the timer upon determining that the communication via the cell has been accepted.
In an example embodiment, a method is provided that includes starting a timer when a registration request is caused to be sent. The method also includes determining that a predefined time limit has expired since the timer was started. The method also includes causing an emergency service fallback attempt failure notification to be sent to the client in response to expiration of the predefined time limit.
In an example embodiment, a method is provided that includes receiving a registration request during a registration update procedure, the registration request including at least a registration type value indicating an emergency service fallback request. The method also includes causing a response to the registration request to be provided.
In an example embodiment, a method is provided in which a response to a registration request defines acceptance of an emergency service fallback request. In an example embodiment, a method is provided in which a response to a registration request defines a rejection of an emergency service fallback request. In an example embodiment, a method is provided wherein the response to the registration request further comprises a predefined cause value for the rejection.
In an example embodiment, an apparatus is provided that includes at least one processor; and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to: cause a registration request to be sent during a registration update procedure, the registration request including at least a registration type value indicating an emergency service fallback request. The apparatus is also caused to determine a response to the registration request that includes an emergency service fallback request.
In an example embodiment, an apparatus is provided that includes at least one processor and at least one memory including computer program code, wherein a registration request to be sent further includes a follow-up request bit defining that no follow-up request is pending. In an example embodiment, an apparatus is provided, wherein determining a response to the registration request comprises: in the event that the mode has changed or a connection to the network has been established, it is determined that the emergency service fallback request has been accepted. In an example embodiment, the apparatus is further caused to start a timer when the registration request is caused to be sent. In an example embodiment, the apparatus is further caused to stop the timer upon determining that the emergency service fallback request has been accepted. In an example embodiment, an apparatus is provided, wherein determining a response to the registration request comprises determining that the emergency service fallback request has not been accepted. In an example embodiment, an apparatus is provided, wherein the apparatus is further caused to select a cell connected to an Evolved Packet Core (EPC) or a 5G core network (5 GCN) in response to a predefined cause value being provided in response to a registration request. The apparatus is also caused to initiate communication via the cell. In an example embodiment, the apparatus is further caused to start a timer when the communication via the cell is transmitted. In an example embodiment, the apparatus is further caused to stop the timer upon determining that the communication via the cell has been accepted.
In an example embodiment, an apparatus is provided that includes at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code further configured to, with the at least one processor, cause the apparatus to start a timer when a registration request is caused to be sent. The apparatus is also caused to determine that a predefined time limit has expired since the timer was started. The apparatus is further caused to cause an emergency service fallback attempt failure notification to be sent to the client in response to expiration of the predefined time limit.
In an example embodiment, an apparatus is provided that includes at least one processor; and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus to receive a registration request during a registration update procedure, the registration request including at least a registration type value indicating an emergency service fallback request. The apparatus is also caused to provide a response to the registration request.
In an example embodiment, an apparatus is provided that includes at least one processor and at least one memory including computer program code, wherein a response to a registration request defines acceptance of an emergency service fallback request. In an example embodiment, an apparatus is provided in which a response to a registration request defines a rejection of an emergency service fallback request. In an example embodiment, an apparatus is provided, wherein the response to the registration request further comprises a predefined cause value for the rejection.
In one example embodiment, a computer program product is provided that includes a non-transitory computer-readable storage medium having program code portions stored thereon, the program code portions configured to, when executed, cause a registration request to be sent during a registration update procedure, the registration request including at least a registration type value indicating an emergency service fallback request. The program code portions are also configured to determine a response to the registration request including an emergency service fallback request.
In one example embodiment, a computer program product is provided that includes a non-transitory computer-readable storage medium having program code portions stored thereon, wherein a registration request to be sent further includes a follow-up request bit that defines that no follow-up request is pending. In an example embodiment, a computer program product is provided, wherein determining a response to a registration request comprises: in the event that the mode has changed or a connection to the network has been established, it is determined that the emergency service fallback request has been accepted. In an example embodiment, the program code portions are further configured to start a timer when the registration request is caused to be sent. In an example embodiment, the program code portions are further configured to stop the timer upon determining that the emergency service fallback request has been accepted. In an example embodiment, a computer program product is provided in which determining a response to a registration request comprises determining that an emergency service fallback request has not been accepted. In an example embodiment, a computer program product is provided in which the program code portions are further configured to select a cell connected to an Evolved Packet Core (EPC) or a 5G core network (5 GCN) in response to a predefined cause value being provided in response to a registration request. The program code portions are also configured to initiate communication via the cell. In an example embodiment, the program code portions are further configured to start a timer when the communication via the cell is transmitted. In an example embodiment, the program code portions are further configured to stop the timer after determining that the communication via the cell has been accepted.
In one example embodiment, a computer program product is provided that includes a non-transitory computer-readable storage medium having program code portions stored thereon, the program code portions configured to, when executed, start a timer when a registration request is caused to be sent. The program code portions are also configured to determine that a predefined time limit has expired since the timer was started. The program code portions are further configured to cause an emergency service fallback attempt failure notification to be sent to the client in response to expiration of the predefined time limit
In one example embodiment, a computer program product is provided that includes a non-transitory computer-readable storage medium having program code portions stored thereon, the program code portions, when executed, being configured to receive a registration request during a registration update procedure, the registration request including at least a registration type value indicating an emergency service fallback request. The program code portions are also configured to cause a response to the registration request to be provided.
In one example embodiment, a computer program product is provided that includes a non-transitory computer-readable storage medium having program code portions stored thereon, wherein a response to a registration request defines acceptance of an emergency service fallback request. In an example embodiment, a computer program product is provided in which a response to a registration request defines a rejection of an emergency service fallback request. In an example embodiment, a computer program product is provided, wherein the response to the registration request further comprises a predefined cause value for the rejection.
In an example embodiment, an apparatus is provided that includes means for causing a registration request to be sent during a registration update procedure, the registration request including at least a registration type value indicating an emergency service fallback request. The apparatus also includes means for determining a response to the registration request that includes an emergency service fallback request.
In an example embodiment, an apparatus is provided that includes means for: the registration request to be sent also includes a follow-up request bit that defines that no follow-up request is pending. In an example embodiment, an apparatus is provided that includes means for: determining the response to the registration request includes determining that the emergency service fallback request has been accepted if the mode has changed or a connection to the network has been established. In an example embodiment, an apparatus is provided that includes means for starting a timer when a registration request is caused to be sent. In an example embodiment, an apparatus is provided that includes means for stopping a timer upon determining that an emergency service fallback request has been accepted. In an example embodiment, an apparatus is provided that includes means for: determining the response to the registration request includes determining that the emergency service fallback request has not been accepted. In an example embodiment, an apparatus is provided, wherein the apparatus is provided in response to a registration request in response to a predefined cause value, the apparatus further comprising means for selecting a cell connected to an Evolved Packet Core (EPC) or a 5G core network (5 GCN). The apparatus also includes means for initiating communication via the cell. In an example embodiment, an apparatus is provided that includes means for starting a timer when a communication via a cell is transmitted. In an example embodiment, an apparatus is provided that includes means for stopping a timer upon determining that communication via a cell has been accepted.
In an example embodiment, an apparatus is provided that includes means for starting a timer when a registration request is caused to be sent. The apparatus also includes means for determining that a predefined time limit has expired since the timer was started. The apparatus also comprises means for causing an emergency service fallback attempt failure notification to be sent to the client in response to expiration of the predefined time limit.
In an example embodiment, an apparatus is provided that includes means for receiving a registration request during a registration update procedure, the registration request including at least a registration type value indicating an emergency service fallback request. The apparatus also includes means for causing a response to the registration request to be provided.
In an example embodiment, an apparatus is provided in which a response to a registration request defines acceptance of an emergency service fallback request. In an example embodiment, an apparatus is provided in which a response to a registration request defines a rejection of an emergency service fallback request. In an example embodiment, an apparatus is provided wherein the response to the registration request further comprises a predefined cause value for the rejection.
Various other aspects are also described in the following detailed description and the appended claims.
Drawings
Having thus described embodiments of the disclosure in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:
fig. 1 illustrates an example architecture of a communication network in accordance with some embodiments;
fig. 2 illustrates an example architecture of a communication network according to some embodiments;
fig. 3 illustrates an example architecture of a communication network according to some embodiments;
FIG. 4 illustrates an example computing device for communicating with other network entities over a communication network in accordance with some embodiments;
FIG. 5 illustrates an example signal flow diagram for a user communication device interfacing with multiple network functions in accordance with some embodiments;
fig. 6 illustrates an example communication process between a UE and an AMF, in accordance with some embodiments;
FIG. 7a illustrates a configuration of a registration type information element, in accordance with some embodiments;
FIG. 7b illustrates a configuration of a register type value table according to some embodiments.
FIG. 8 is a flowchart illustrating operations performed, such as by a communication device or other client device, according to an example embodiment;
FIG. 9 is a flowchart illustrating operations performed, such as by a communication device or other client device, according to an example embodiment; and
fig. 10 is a flowchart illustrating operations performed, such as by a network device, such as an AMF, according to an example embodiment.
Detailed Description
Some embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the invention are shown. Indeed, various embodiments of the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. The term "or" is used herein in both the alternative and combined meanings, unless otherwise specified. The terms "illustrative" and "exemplary" are used for illustration, and do not indicate a level of quality. Like reference numerals refer to like elements throughout. As used herein, the terms "data," "content," "information" and similar terms may be used interchangeably to refer to data capable of being transmitted, received and/or stored in accordance with embodiments of the present invention. Thus, use of any such terms should not be taken to limit the spirit and scope of embodiments of the present invention.
Furthermore, as used herein, the term "circuitry" refers to (a) hardware-only circuit implementations (e.g., implementations in analog circuitry and/or digital circuitry); (b) The combination of circuitry and computer program product(s), including software and/or firmware instructions stored on one or more computer-readable memories, which work together to cause an apparatus to perform one or more functions described herein; and (c) circuitry, such as microprocessor(s) or a portion of microprocessor(s), that requires software or firmware for operation, even if the software or firmware is not physically present. This definition of "circuitry" applies to all uses of this term herein, including in any claims. As another example, as used herein, the term "circuitry" also includes an implementation having one or more processors and/or portion(s) thereof and accompanying software and/or firmware. As another example, the term "circuitry" as used herein also includes, for example, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, other network device, and/or other computing device.
Furthermore, as used herein, the terms "node," "entity," "intermediary," "intermediate entity," "intermediary" and similar terms may be used interchangeably to refer to a computer or program running on a network or networks capable of data creation, modification, deletion, transmission, reception and/or storage in accordance with embodiments of the present invention. Thus, use of any such terms should not be taken to limit the spirit and scope of embodiments of the present invention.
Furthermore, the terms "user equipment", "user device", "apparatus", "mobile device", "personal computer", "notebook computer", "laptop computer", "desktop computer", "mobile phone", "tablet computer", "smartphone", "smart device", "cell phone", "communication device", "user communication device", "terminal" and similar terms may be used interchangeably to refer to a computer configured to access one or more networks at least for the purpose of wired or wireless transmission of communication signals according to example embodiments. Thus, use of any such terms should not be taken to limit the spirit and scope of the disclosed embodiments.
As defined herein, a "computer-readable storage medium" (which refers to a non-transitory physical storage medium (e.g., a volatile or non-volatile memory device)) can be distinguished from a "computer-readable transmission medium" (which refers to an electromagnetic signal). Such a medium may take many forms, including but not limited to non-transitory computer-readable storage media (e.g., non-volatile media, volatile media), and transmission media. Transmission media include, for example, coaxial cables, copper wire, fiber optic cables, and carrier waves that propagate through space without wires or cables, such as acoustic waves and electromagnetic waves, including radio, optical and infrared waves. Signals include man-made transient variations in amplitude, frequency, phase, polarization, or other physical characteristics transmitted through the transmission medium. Examples of a non-transitory computer-readable medium include a magnetic computer-readable medium (e.g., a floppy disk, a hard disk, a magnetic tape, any other magnetic medium), an optical computer-readable medium (e.g., a compact disc read only memory (CD-ROM), a Digital Versatile Disc (DVD), a blu-ray disc, etc.), a Random Access Memory (RAM), a Programmable Read Only Memory (PROM), an Erasable Programmable Read Only Memory (EPROM), a FLASH-EPROM, or any other non-transitory medium from which a computer can read. The term computer-readable storage medium is used herein to refer to any computer-readable medium except transmission media. However, it should be understood that where embodiments are described as using a computer-readable storage medium, in alternative embodiments other types of computer-readable media may be used in place of or in addition to the computer-readable storage medium.
In the following, certain embodiments are explained with reference to communication devices capable of communicating via a wired and/or wireless network and communication systems serving such communication devices. Before explaining example embodiments in detail, certain general principles of a wired and/or wireless communication system, its access system and communication device are briefly explained with reference to fig. 1 to 3. To facilitate an understanding of the underlying technology of the described examples.
According to some embodiments, a communication device or terminal may be provided for wireless access via a cell, base station, access point, or the like (e.g., a wireless transmitter and/or receiver node that provides an access point for a radio access communication system and/or other forms of wired and/or wireless networks). Such wired and/or wireless networks include, but are not limited to, networks configured to conform to 2G, 3G, 4G, LTE, 5G, and any other similar or yet to be developed future communication network standards. The present disclosure contemplates that any method, apparatus, computer program code, and any portion or combination thereof, may also be implemented with communication networks and related standards not yet developed, as will be developed in the future and understood by those skilled in the art in light of the present disclosure.
The access point, and hence the communications conducted thereby, is typically controlled by at least one suitable control means to enable operation thereof and management of the mobile communications device with which it communicates. In some embodiments, the control means of the node may be integrated with, coupled to and/or otherwise provided for controlling the access point. In some embodiments, the control means may be arranged to allow communication between the user equipment and the core network, or a network entity of the core network. To this end, the control device may comprise at least one memory, at least one data processing unit (such as a processor, etc.) and an input/output interface. Via which the control means can be coupled to the relevant other components of the access point. The control means may be configured to execute appropriate software code to provide the control function. It should be understood that similar components may be provided in a control device provided elsewhere in the network system, for example in a core network entity. The control device may be interconnected with other control entities. The control means and functions may be distributed between several control units. In some embodiments, each base station may comprise a control device. In an alternative embodiment, two or more base stations may share a control device.
The access points and associated controllers may communicate with each other via fixed line connections and/or via a radio interface. The logical connections between the base station nodes may be provided by, for example, X2, S1, etc. interfaces. The interface may be used, for example, to coordinate the operation of the station and perform reselection or handover operations. The logical communication connection between the initial communication node and the final communication node on the network may comprise a plurality of intermediate nodes. Further, any node may be added to or removed from the logical communication connection as needed to establish and maintain network functional communication.
The communication device or user device may comprise any suitable device capable of at least receiving communication signals comprising data. The communication signals may be transmitted via a wired connection, a wireless connection, or some combination thereof. For example, the device may be a handheld data processing device provided with a radio receiver, a data processor and a user interface. Non-limiting examples include a Mobile Station (MS), such as a mobile phone or so-called "smart phone", a portable computer, such as a laptop or tablet computer provided with a wireless interface card or other wireless interface facility, a Personal Data Assistant (PDA) provided with wireless communication capabilities, or any combination of these, etc. Further examples include wearable wireless devices, such as devices integrated with a watch or smart watch, glasses, helmets, hats, clothing, headphones with wireless connections, jewelry, and the like, universal Serial Bus (USB) sticks with wireless capability, modem data cards, machine type devices, or any combination of these devices, and the like.
In some embodiments, for example, a communication device configured for communication with a wireless network or core network entity may be exemplified by a handheld or other mobile communication device (or user equipment, UE). The mobile communication device may be provided with wireless communication capabilities and appropriate electronic control means to enable its operation. Thus, the communication device may be provided with at least one data processing entity (e.g. a central processing unit and/or a core processor), at least one memory and possibly other components, such as additional processors and memories, for software and hardware assisted execution of tasks it is designed to perform. The data processing, storage and other related control means may be provided on a suitable circuit board and/or in a chipset. The data processing and storage functions provided by the control means of the communication device are configured to cause control and signalling operations according to some embodiments described later in this specification. The user may control the operation of the communication device through a suitable user interface, such as a touch sensitive display screen or keyboard and/or keypad, one or more actuator buttons, voice commands, combinations of these, and the like. A speaker and a microphone are also typically provided. Further, the mobile communication device may comprise suitable connectors (wired or wireless) to other devices and/or for connecting external accessories (e.g. hands-free devices) to other devices.
In some embodiments, the communication device may communicate wirelessly via appropriate means for receiving and transmitting signals. In some embodiments, the radio unit may be connected to a control of the device. The radio unit may comprise a radio part and an associated antenna arrangement. The antenna arrangement may be arranged inside or outside the communication device.
Fig. 1-3 illustrate various example architectures of a communication network 100 in which various methods, apparatus, and computer program products may be performed and/or used. In some embodiments, the communication network 100 may include any suitable configuration, number, orientation, location, and/or size of components and dedicated devices configured to provide an air interface (e.g., a New Radio (NR)) for communicating or connecting between a user equipment 102 (UE 102) and a data network 116 (DN 116) via a core network 101 (CN 101) of the communication network 100. UE102 may be associated with one or more devices associated with one or more NF service consumers. As shown in fig. 1, a communication network 100 may be provided in which a UE102 is in operable communication with a radio access network 104 (RAN 104), such as through transmission towers, base stations, access points, network nodes, and the like, in the communication network 100. In some embodiments, RAN104 may communicate with CN 101 or a component or entity thereof. In some embodiments, CN 101 may facilitate communications between UE102 and DN 116, such as for sending data, messages, requests, and so forth. In some embodiments, DN 116 or CN 101 may communicate with an Application Server (AS) or Application Function (AF) 112 (AS 112 or AF 112). RAN104, CN 101, DN 116, and/or AS/AF 112 may be associated with a Network Repository Function (NRF), a Network Function (NF) service producer, a secure replication protocol (SCP), a Secure Edge Protection Proxy (SEPP), a Policy Charging Function (PCF), the like, or any combination thereof.
In the context of a 5G network, such as shown in fig. 2 and 3, the communication network 100 may include a series of connected network devices and dedicated hardware distributed across a service area, state, province, city, or country, and one or more network entities that may be stored at and/or hosted by one or more of the connected network devices or dedicated hardware. In some embodiments, UE102 may connect to RAN104, and RAN104 may then relay communications between UE102 and CN 101, CN 101 being connected to DN 116, and DN 116 may communicate with one or more AS/AFs 112. In some embodiments, UE102 may communicate with RAN104, which RAN104 may act as a relay between UE102 and other components or services of CN 101. For example, in some embodiments, the UE102 may communicate with the RAN104, which in turn may communicate with the access and mobility management function 108 (AMF 108). In other cases or embodiments, the UE102 may communicate directly with the AMF 108. In some embodiments, AMF108 may communicate with one or more Network Functions (NFs), such AS an authentication server function 120 (AUSF 120), a network slice selection function 122 (NSSF 122), a network repository function 124 (NRF 124), a policy charging function 114 (PCF 114), a network data analysis function 126 (NWDAF 126), a unified data management function 118 (UDM 118), AS/AF 112, session management function 110 (SMF 110), and so forth.
In some embodiments, SMF 110 may communicate with one or more user plane functions 106 (UPF 106, UPF 106a, UPF 106b, collectively "UPF 106"). For example only, in some embodiments, the UPF 106 may communicate with the RAN104 and the DN 116. In other embodiments, the DN 116 may communicate with the first UPF 106a and the RAN104 may communicate with the second UPF 106b, while the SMF 110 communicates with both the first UPF 106a and the second UPF 106b, and the first UPF 106a and the second UPF 106b communicate with each other.
In some embodiments, UE102 may include single mode or dual mode devices, enabling UE102 to connect to one or more RANs 104. In some embodiments, the RAN104 may be configured to implement one or more Radio Access Technologies (RATs), such as bluetooth, wi-Fi, and global system for mobile communications (GSM), universal Mobile Telecommunications Service (UMTS), LTE, or 5G NR, among others, which may be used to connect the UE102 to the CN 101. In some embodiments, RAN104 may comprise or be implemented using a chip (such as a silicon chip) in UE102 that may be paired with or otherwise identified by a similar chip in CN 101, such that RAN104 is able to establish a connection or communication line between UE102 and CN 102 by identifying and pairing the chip within UE102 with the chip within CN 101. In some embodiments, the RAN104 may implement one or more base stations, towers, etc. to communicate between the UE102 and the AMF108 of the CN 101.
In some embodiments, the communication network 100 or components thereof (e.g., base stations, towers, etc.) may be configured to communicate with a communication device (e.g., UE 102) such as a cellular phone over a plurality of different frequency bands (e.g., FR1 (below 6 GHz), FR2 (millimeter wave (mmWave)), other suitable frequency bands, sub-bands thereof, etc.). In some embodiments, the communication network 100 may include or employ massive multiple-input multiple-output (massive MIMO) antennas. In some embodiments, the communication network 100 may include multi-user MIMO (MU-MIMO) antennas. In some embodiments, the communication network 100 may employ edge computing whereby a computing server is communicatively, physically, computationally, and/or temporally closer to a communication device (e.g., UE 102) to reduce delay and data traffic congestion. In some embodiments, the communication network 100 may employ other technologies, devices, or technologies, such as small cells, low power RANs, beamforming of radio waves, WIFI cellular convergence, non-orthogonal multiple access (NOMA), channel coding, and so forth.
As shown in fig. 3, the UE102 may be configured to communicate with the RAN104 in an N1 interface, e.g., according to a non-access stratum (NAS) protocol. In some embodiments, the RAN104 may be configured to communicate with the CN 101 or components thereof (e.g., the AMF 108) in an N2 interface (e.g., in a control plane between base stations of the RAN104 and the AMF 108). In some embodiments, the RAN104 may be configured to communicate with the UPF 106 in an N3 interface (e.g., in the user plane). In some embodiments, AMF108 and/or SMF 110 may be configured to communicate with other services or network entities within CN 101 in a variety of different interfaces and/or according to a variety of different protocols. For example, in some embodiments, the AMF108 and/or the SMF 110 may be configured to communicate with the AUSF 120 in a Nausf interface or an N12 interface. In some embodiments, AMF108 and/or SMF 110 may be configured to communicate with NSSF122 in an NSSF interface. In some embodiments, AMF108 and/or SMF 110 may be configured to communicate with NRF 124 in an nrrf interface. In some embodiments, AMF108 and/or SMF 110 may be configured to communicate with PCF114 in an Npcf interface or an N7 interface. In some embodiments, AMF108 and/or SMF 110 may be configured to communicate with NWDAF 126 in an NWDAF interface. In some embodiments, the AMF108 and/or SMF 110 may be configured to communicate with the UDM 118 in a Nudm interface, an N8 interface, or an N10 interface. In some embodiments, AMF108 and/or SMF 110 may be configured to communicate with AS/AF 112 in a Naf interface. In some embodiments, the SMF 110 may be configured to communicate with the UPF 106 in an N4 interface, which may act as a bridge between the control plane and the user plane, such as acting as a conduit for a Protocol Data Unit (PDU) session during which information is transferred between, for example, the UE102 and the CN 101 or components/services thereof.
It should be understood that certain example embodiments described herein occur in the context of telecommunications networks, including but not limited to telecommunications networks that conform to and/or otherwise incorporate aspects of the fifth generation (5G) architecture. Although fig. 1-3 illustrate various configurations and/or components of an example architecture of a communication network 100, many other systems, system configurations, networks, network entities, and paths/protocols for communications therein are contemplated and considered within the scope of the present disclosure.
Although the methods, apparatus/devices, and computer program products/code described herein are described in the context of a fifth generation core network (5 GC) and system, such as that shown in fig. 1-3 and described above, the described methods, apparatus, and computer program products may be applied in a broader context within any suitable telecommunications system, network, standard, and/or protocol. It should be understood that the described methods, devices and computer program products may further be applied to future networks and systems not yet developed, as will be apparent to those skilled in the art in light of the present disclosure.
Turning now to fig. 4, an example of an apparatus that may be embodied by a user equipment or network entity (such as a server or other computing device, e.g., an AMF) is depicted in accordance with an example embodiment of the present disclosure. The apparatus 200 of an example embodiment may be configured to perform the functions described herein as described below in connection with the flowcharts, block diagrams, etc. of fig. 5, 6, 7a, 7b, 8, 9, and 10. In any case, the apparatus 200 may be more generally embodied by a computing device, such as a server, personal computer, computer workstation, or other type of computing device, including a computing device that serves as a user device and/or component of a wireless network or wireless local area network (e.g., an AMF). Regardless of the manner in which the apparatus 200 is embodied, the apparatus of the example embodiment may be configured as shown in fig. 4 to include, be associated with, or be in communication with a processor 202 and a memory device 204 and/or (in some embodiments) a communication interface 206. Although not shown, the apparatus of the example embodiments may also optionally include a user interface, such as a touch screen, display, keyboard, and the like.
The processor 202 (and/or a coprocessor or any other circuitry auxiliary to or otherwise associated with the processor) may communicate with the memory device 204 via the bus to transfer information between components of the apparatus 200. The memory device may include, for example, one or more volatile and/or non-volatile memories, such as non-transitory memory devices. In other words, for example, a memory device may be an electronic storage device (e.g., a computer-readable storage medium) that includes a gate configured to store data (e.g., bits) that may be retrievable by a machine (e.g., a computing device, such as a processor). According to example embodiments, the memory device may be configured to store information, data, content, applications, instructions or the like, enabling the apparatus to perform various functions. For example, the memory device may be configured to buffer input data for processing by the processor. Additionally or alternatively, the memory device may be configured to store instructions for execution by the processor.
In some embodiments, the apparatus 200 may be embodied in various computing devices as described above. However, in some embodiments, the apparatus may be embodied as a chip or chip set. In other words, the apparatus may include one or more physical packages (e.g., chips) that include materials, components, and/or wires on a structural component (e.g., a backplane). The structural components may provide physical strength, dimensional retention, and/or electrical interaction constraints for the component circuitry included thereon. Thus, in some cases, the apparatus may be configured to implement an embodiment on a single chip or as a single "system-on-a-chip". Thus, in some cases, a chip or chip set may constitute a means for performing one or more operations to provide the functionality described herein.
The processor 202 may be embodied in a number of different ways. For example, a processor may be embodied as one or more of various hardware processing means such as a coprocessor, a microprocessor, a controller, a Digital Signal Processor (DSP), a processing element with or without an accompanying DSP, or various other circuitry including integrated circuits such as, for example, an ASIC (application specific integrated circuit), an FPGA (field programmable gate array), a microcontroller unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like. As such, in some embodiments, a processor may include one or more processing cores configured to execute independently. The multi-core processor may implement multiprocessing within a single physical package. Additionally or alternatively, the processor may include one or more processors configured in series via a bus to implement independent execution of instructions, pipelining, and/or multithreading.
In an example embodiment, the processor 202 may be configured to execute instructions stored in the memory device 204 or otherwise accessible to the processor. Alternatively or additionally, the processor may be configured to perform hard-coded functions. As such, whether configured by hardware or software methods, or by a combination thereof, a processor may represent an entity (e.g., physically embodied in circuitry) capable of performing operations according to embodiments of the present disclosure while configured accordingly. Thus, for example, when the processor is embodied as an ASIC, FPGA or the like, the processor may be specially configured hardware for performing the operations described herein. Alternatively, as another example, when the processor is embodied as an executor of instructions, the instructions may specifically configure the processor to perform the algorithms and/or operations described herein when the instructions are executed. However, in some cases, the processor may be a processor of a particular device (e.g., an encoder and/or decoder) configured to utilize embodiments of the present disclosure by further configuring the processor with instructions for performing the algorithms and/or operations described herein. The processor may include a clock, an Arithmetic Logic Unit (ALU), and logic gates configured to support processor operations, among others.
In embodiments that include the communication interface 206, the communication interface may be any means, such as a device or circuitry embodied in hardware or a combination of hardware and software, configured to receive and/or transmit data from/to a network and/or any other device or module in communication with the apparatus 200, such as NF, NRF, base station, access point, SCP, UE102, radio access network, core network services, application servers/functions, databases or other storage devices, etc. In this regard, the communication interface may include, for example, an antenna (or multiple antennas) and supporting hardware and/or software for enabling communications with a wireless communication network. Additionally or alternatively, the communication interface may include circuitry for interacting with the antenna(s) to cause transmission of signals via the antenna(s) or to process reception of signals received via the antenna(s). In some environments, the communication interface may alternatively or additionally support wired communication. As such, for example, the communication interface may include a communication modem and/or other hardware/software for supporting communication via cable, digital Subscriber Line (DSL), universal Serial Bus (USB), or other mechanisms. In some embodiments, the session management functions may include 5GC session management functions for any suitable Control and User Plane Separation (CUPS) architecture, such as for a gateway general packet radio service support node (GGSN-C), a trusted radio access gateway (TWAG-C), broadband network gateway control and user plane separation (BNG-CUPS), an N4 interface, a Sxa interface, a Sxb interface, an Sxc interface, an Evolved Packet Core (EPC) secure network gateway control plane function (SWG-C), an EPC packet data network gateway control plane function (PGW-C), an EPC traffic detection function of the control plane (TDF-C), and so forth.
As shown, the apparatus 200 may include a processor 202, the processor 202 being in communication with a memory 204 and configured to provide signals to and receive signals from a communication interface 206. In some embodiments, the communication interface 206 may include a transmitter and a receiver. In some embodiments, the processor 202 may be configured to control, at least in part, the functionality of the apparatus 200. In some embodiments, the processor 202 may be configured to control the functions of the transmitter and receiver by implementing control signaling via electrical leads to the transmitter and receiver. Likewise, the processor 202 may be configured to control other elements of the apparatus 200 by implementing control signals via electrical leads that connect the processor 202 to the other elements (such as a display or memory 204).
The apparatus 200 is capable of operating with one or more air interface standards, communication protocols, modulation types, access types, and/or the like. The signals transmitted and received by processor 202 may include signaling information in accordance with the air interface standard of an applicable cellular system, and/or any number of different wired or wireless network technologies, including but not limited to Wi-Fi, wireless Local Area Network (WLAN) technologies such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, 802.16, 802.3, asymmetric Digital Subscriber Line (ADSL), data Over Cable Service Interface Specification (DOCSIS), and so forth. Further, these signals may include voice data, user generated data, user requested data, and the like.
For example, the apparatus 200 and/or a cellular modem therein may operate in accordance with various first-generation (1G) communication protocols, second-generation (2G or 2.5G) communication protocols, third-generation (3G) communication protocols, fourth-generation (4G) communication protocols, fifth-generation (5G) communication protocols, internet protocol multimedia subsystem (IMS) communication protocols (e.g., session Initiation Protocol (SIP), etc.). For example, device 200 may operate in accordance with 2G wireless communication protocol temporary Standard 136 (IS-136), time Division Multiple Access (TDMA), global System for Mobile communications (GSM), temporary Standard 95 (IS-95), code Division Multiple Access (CDMA), and so forth. Further, for example, the apparatus 200 may operate in accordance with 2.5G wireless communication protocols General Packet Radio Service (GPRS), enhanced Data GSM Environment (EDGE), and/or the like. Further, for example, the apparatus 200 may operate in accordance with 3G wireless communication protocols such as Universal Mobile Telecommunications System (UMTS), code division multiple access 2000 (CDMA 2000), wideband Code Division Multiple Access (WCDMA), time division synchronous code division multiple access (TD-SCDMA), and so on. NA 200 may also operate in accordance with 3.9G wireless communication protocols, such as Long Term Evolution (LTE), evolved universal terrestrial radio access network (E-UTRAN), and so on. Further, for example, the apparatus 200 may operate in accordance with 4G wireless communication protocols (such as LTE advanced, 5G, etc.) and similar wireless communication protocols that may be subsequently developed. In some embodiments, the apparatus 200 may operate in accordance with or within the framework of any suitable CUPS architecture, such as for a gateway GPRS support node (GGSN-C), a trusted radio access gateway (TWAG-C), a Broadband Network Gateway (BNG), an N4 interface, a Sxa interface, a Sxb interface, an Sxc interface, an Evolved Packet Core (EPC) SWG-C, an EPC PGW-C, an EPC TDF-C, and so forth. Indeed, although described herein in connection with the operation of a 5G system, the apparatus and methods may be configured to operate in connection with many other types of systems, including those developed and implemented below.
Some embodiments disclosed herein may be implemented in software, hardware, application logic or a combination of software, hardware and application logic. For example, software, application logic, and/or hardware may reside on the memory 204, the processor 202, or the electronic components. In some example embodiments, the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media. In the context of this document, a "computer-readable medium" may be any non-transitory medium that can contain, store, communicate, propagate, or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer or data processor circuitry, an example of which is illustrated in fig. 4, and may comprise a non-transitory computer-readable storage medium that can contain or store the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.
Fig. 5 illustrates a signal flow diagram between the UE102 and multiple network entities and/or functions (e.g., AMF108, etc.) in order to request emergency service fallback, according to an example embodiment. Emergency services are provided to support emergency sessions and refer to functions (e.g., voice calls, text messages, etc.) provided by a serving network. Emergency services are provided to UEs that are normally registered on the serving network. Further, based on local laws and regulations, emergency services may be provided to unregistered UEs on the serving network in a limited service state. Receiving emergency services in a limited service state does not require a valid subscription, and the network may allow or deny (depending on applicable laws, regulations and operator policies) emergency registration requests for UEs that have been identified as being in a limited service state.
To support various deployment scenarios for acquiring emergency services, the UE and serving network may support an emergency services fallback mechanism. When the current network access configuration of the UE does not support emergency services, an emergency services fallback mechanism directs or redirects the UE to the local network access node(s) that support emergency services. The emergency service fallback procedure may be used when the network does not indicate support for emergency services but indicates support for emergency service fallback.
As shown at 511, the UE102 is configured to select or "camp" in a cell of a cellular system, such as a 5G system (5 GS). This selection of cells to connect to is referred to as "camping on a cell". In this example embodiment, the UE registers its presence in the registration area of the selected cell, such as through a location registration procedure. Once registered, the UE will update its registration for various reasons, such as based on UE mobility resulting in a location change, or periodically. As shown at 512 of fig. 5, the UE has transmitted a registration update request, such as to the AMF. Although not shown, the AMF may accept the registration update request. However, in the event (i) the registration update request is not accepted, such as in the event that the registration update request fails due to lack of response from the network (i.e., AMF), or in other predefined circumstances, such as those described in sub-clauses 5.3.9 and 5.5.1.3.5 of 3gpp TS 24.501, and in the event (ii) the UE determines that an emergency session needs to be established, such as based on input from the user of the UE102 or from upper layers of the UE, as shown at 513, the method and apparatus 200 of the example embodiment still provides a request for, and in at least some cases, initiation of, an emergency service fallback procedure.
In this case, a registration request is sent from the UE102 to the AMF108 through the RAN104, as shown at 514. The registration request includes an indication of the type of emergency service fallback requested and, in some embodiments, a follow-up request bit indicating whether a follow-up request is pending (pending). In an example embodiment, the follow-on request bits include a "0" bit corresponding to the message "no follow-on request pending" and a "1" bit corresponding to the message "follow-on request pending". If accepted by the AMF, the AMF108 will send a request for an emergency service fallback type to the RAN104 to authorize the RAN to support and conduct emergency sessions on behalf of the UE102, as shown at 515. Where the request for the emergency session is accepted, the process 510 of the illustrated embodiment may continue to provide the emergency session with operations defined by blocks 516a, 516b, 517, etc., or some combination thereof. In embodiments where the UE102 determines that a handover procedure is required, such as to support an emergency session, the UE102 may initiate the handover procedure according to an inter-Radio Access Technology (RAT) handover, or Radio Resource Control (RRC) redirection of an E-UTRA handover to a 5GC connection, see block 516a. In this example embodiment, the handover procedure is determined based on measurements (e.g., distance, signal strength, etc.) made by the UE102 with reference to a network access node (e.g., RAN, cell, etc.). For example, in one embodiment in which the UE102 determines that the currently connected network access node is losing signal strength, the UE102 may initiate a handover procedure to handover to another network access node with relatively better or improved signal strength. Additionally or alternatively, in some embodiments, the UE102 may initiate a handover procedure for inter-system handover, or RRC redirection to EPS, see block 516b. In some embodiments, the signal flow 510 may proceed directly from issuing an emergency service fallback request to the RAN104 at block 515 to an IMS procedure for establishing an IMS emergency session (e.g., voice, text message, file transfer, real-time video, etc.) as shown at block 517 without any handover procedure (such as shown at blocks 516a and 516 b). In other embodiments, the signal flow 510 requires a handoff procedure as shown in blocks 516a and 516b, and then the emergency session continues to be established in block 517. Further, any of the described handoff procedures may occur multiple times in various combinations and should not be limited to only the examples shown with respect to blocks 516b and 516a.
However, in the event that the request for the emergency session included within the registration request is denied, such as via a registration reject message from the AMF108, the UE102 of the example embodiments may attempt to reconnect via another cell in the current or another tracking area, and further initiate at least, for example, a 5GMM, EMM, or other mobility management procedure. Alternatively, in case the registration request sent due to the request from its upper layer to perform emergency service fallback is not performed and no response is received at least within a predefined time period, the UE102 may consider that the registration response has failed and may inform its upper layer and/or the user, e.g. send an indication to the upper layer that the emergency service fallback attempt failed.
Fig. 6 shows another illustration of three alternative signal flows 610 between the UE102 and a network entity, such as the AMF108, according to an example embodiment. In some embodiments, communications between UE102 and AMF108 are established directly between UE102 and AMF108 using an N1 interface. In other embodiments, communications between UE102 and AMF108 are established indirectly between UE102 and AMF108 via RAN104 or another intermediate network entity using an N2 interface.
Prior to the signal flow shown in fig. 6, UE102 has registered with AMF108 and is updating its registration, such as a mobility registration update or a periodic registration update. In the case shown in fig. 6, the registration update request is not accepted by the AMF, such as in the case where the registration update request fails due to lack of response from the network or due to predefined conditions (such as those described in sub-clauses 5.3.9 and 5.5.1.3.5 of 3gpp TS 24.501), but the UE determines that an emergency session needs to be established based on input, such as from the user of UE102 or from upper layers of the UE.
In this case, the UE102 of the example embodiment begins running a first timer, such as a T3510 timer, as shown in block 611a, after sending a registration request for emergency service fallback to the AMF108, as shown in 612 a. Upon receiving the registration request for emergency service fallback, the AMF108 of this example embodiment will determine whether a temporary identity is allocated, and if the temporary identity is allocated, the AMF108 starts running a second timer, such as a T3550 timer, after sending a registration accept response to the UE102 (as shown by 614 a), as shown in block 613 a. Upon receiving the registration acceptance response, the UE102 of this example embodiment stops running the first timer, as shown at 615a, and optionally determines at block 616a whether a temporary identity is allocated and sends a registration complete notification to the AMF108, as shown at 617a, if a temporary identity is allocated. Upon receiving the registration completion notification, the AMF108 stops running the second timer, as shown at 618 a. However, in case the UE102 does not send a registration complete notification to the AMF108, then a running second timer (such as a T3550 timer) will expire after a predefined time. Upon the first expiration of the second timer, AMF108 may retransmit the registration acceptance response to UE102, as shown at 614a, and the second timer should be reset and restarted. In the subsequent case of expiration of the second timer, the AMF108 may follow the procedure described in subclause 5.5.1.2.8.c of 3gpp TS 24.501, including a number of additional transmissions of registration accept responses to the UE 102. In the event that the specified number of additional transmissions (e.g., 4 to 5 additional transmissions) of the registration accept response to the UE102 are exhausted, then the AMF108 may enter the 5GMM deregister state.
In another example signal flow sequence 610, the UE102 begins running a first timer, such as a T3510 timer, as shown at block 611b, after sending a registration request for emergency service fallback to the AMF108, as shown at 612 b. Upon receiving the registration request for emergency service fallback, the AMF108 of this example embodiment determines that the registration is accepted at block 613b, and sends an Access Stratum (AS) indication response to the UE102, AS shown at 614 b. According to this example embodiment, upon receiving the Access Stratum (AS) indication response, the UE102 will stop running the first timer, AS shown at 615 b.
In another example signal flow sequence 610, the UE102 begins running a first timer, such as a T3510 timer, as shown at block 611c, after sending a registration request for emergency service fallback to the AMF108, as shown at 612 c. Upon receiving the registration request for emergency service fallback, the AMF108 of this example embodiment determines that registration is denied and sends a registration denial response to the UE102, as shown in blocks 613c and 614c, respectively. Upon receiving the registration rejection response, the UE102 will stop running the first timer, as shown in block 615 c.
Fig. 7a illustrates a configuration of an example registration type Information Element (IE) 700a, according to some embodiments. In this embodiment, bits 1 through 8 are depicted in the top row 701 and correspond to the octet information labeled in the bottom row 702. The 5GS registration type information representing the "emergency service fallback" IE type value corresponds to bits 1 to 3 of IE 700 a. In this embodiment, the follow request bit (FOR) corresponds to bit 4 of IE 700 a.
Fig. 7b illustrates a configuration of an example registration type value table 700b depicting "emergency services fallback" IE type values that may be used in conjunction with the registration type IE of fig. 7a, in accordance with some embodiments. In this example embodiment, the emergency service fallback IE type value included in the registration request as a request for emergency service fallback is defined by the bit sequence 1-0-1 (which corresponds to bits 1 to 3 of the registration type IE 700 a) to distinguish the registration request for emergency service fallback from other types of registrations, such as initial registration, mobility registration update, periodic registration update, or emergency registration. In this embodiment, the follow-on request bit (FOR) corresponding to bit 4 of registration type IE 700a is set to 0 FOR no follow-on request pending to distinguish the registration request from a registration request with follow-on request pending as shown by FOR bit value 1. In some embodiments, unified access control is required and the UE102 assigns an access class of 2 (= emergency) to an access attempt caused by a registration request for emergency service fallback sent from the UE102 to the AMF 108. In some embodiments, the UE102 NAS layer does not provide any single network slice selection assistance information (S-NSSAI) to the UE AS layer if the registration request message is sent for emergency service fallback.
Fig. 8 illustrates a flowchart of the operations of an example method 810 performed by the example apparatus 200, and in one embodiment, the example apparatus 200 may be embodied by a computer program product comprising computer program code executed by the processor 202 of the UE 102. As indicated at block 811, the apparatus 200 of this example embodiment includes components, such as the processor 202, memory 204, communication interface 206, etc., for causing a registration request, including an emergency service fallback request, to be sent to a network entity, such as the AMF referenced by way of example and not limitation throughout the discussion of fig. 8. In this example embodiment, a registration request including an emergency service fallback request is transmitted during a registration update procedure. In this regard, prior to the operations illustrated in fig. 8, the UE102 has registered with the network (such as the AMF 108) and is updating its registration, such as a mobility registration update or a periodic registration update. However, the registration update request has not been accepted by the AMF, such as in the case where the registration update request fails due to lack of response from the network or due to predefined conditions (such as those described in sub-clauses 5.3.9 and 5.5.1.3.5 of 3gpp TS 24.501). In this case, the UE determines that an emergency session needs to be established, such as based on input from a user of the UE102 or from upper layers of the UE, and a registration request including an emergency service fallback request is generated and transmitted, such as by the processor 202 and/or the communication interface 206. The registration request of this example embodiment may include an emergency services fallback request in the form of a registration type value, such as a 5G system (5 GS) registration type value, and a follow-up request bit, as described above. The apparatus 200 of the example embodiment includes means, such as the processor 202, for starting a first timer, such as a T3150 timer, concurrently with transmission of a registration request including an emergency service fallback request. See block 812.
As shown at block 813, the apparatus 200 further includes means, such as the processor 202, for determining a response (such as from the AMF 108) to the registration request that includes the emergency service fallback request. Although it may be determined in various ways that the response to the emergency service fallback request is an acceptance of the emergency service fallback request, as shown in block 814, apparatus 200 of an example embodiment includes means, such as processor 202, for determining that a network entity, such as AMF, has accepted the emergency service fallback request and triggered an emergency service fallback procedure, such as specified in sub-4.13.4.2 of 3gpp TS 23.502, in an instance in which an indication is provided, such as via an underlay, that a mode of the UE has changed (such as to S1 mode) and/or that a network connection has been established, such as in an instance in which E-UTRA has connected to a 5 GCN. In determining the response to the registration request, the AMF may skip checking for restrictions (e.g., area subscription restrictions, access restrictions, closed access group restrictions) if the registration request includes a registration type value indicating emergency service fallback or emergency registration. If a UE operating in single registration mode has changed to S1 mode, the UE (such as a processor) may disable the N1 mode capability of the 3GPP access. In the event that the apparatus 200, such as the processor 202, determines that the emergency service fallback request has been accepted, the apparatus comprises means, such as a processor or the like, for stopping the first timer. See block 815.
In the event that a registration request including an emergency service fallback request is not accepted, the apparatus 200 (such as the processor 202) may make this determination in various ways. In one case, as shown at block 816, the apparatus 200 further includes means, such as the processor 202, the communication interface 206, or the like, for receiving a rejection response (such as a registration rejection message) from a network (such as the AMF 108). In some embodiments, a response to a registration request (such as a registration reject message) including an emergency service fallback request may identify the reason for the rejection, such as by a provided reason value. In the event the cause value has a predefined value, the apparatus 200 of one example embodiment further comprises means, such as the processor 202, the communication interface 206, or the like, for selecting a cell connected to an Evolved Packet Core (EPC) or 5G core network (5 GCN) and initiating communication via the cell, thereby potentially providing emergency services, albeit in a different manner than originally requested. See block 817. In the event that the apparatus 200 (such as the processor 202, the communication interface 206, etc.) receives a reject response to a registration request that includes an emergency service fallback request, the apparatus includes means (e.g., a processor, etc.) for stopping the first timer. See block 818.
For example, in response to a predefined cause value (e.g., # 9) indicating that the identity of the UE102 cannot be derived by the network, an apparatus 200 embodied by the UE (such as the processor 202, the communication interface 206, etc.) may be configured to attempt to select an E-UTRA cell connected to the EPC or 5GCN according to the domain priority and selection rules specified in 3gpp TS 23.167. If the UE finds a suitable E-UTRA cell, the UE proceeds with the appropriate EMM or 5GMM procedure. As another example, in response to a predefined cause value (e.g., # 15) indicating that there are no suitable cells in the tracking area, an apparatus embodied by the UE (such as a processor, a communication interface, etc.) may attempt to select an E-UTRA cell connected to the EPC or 5GC according to an emergency services support indicator (see 3gpp TS 36.331). If the UE finds a suitable E-UTRA cell, the UE then proceeds with the appropriate EMM or 5GMM procedure. Otherwise, the UE may search for a suitable cell in another tracking area according to 3gpp TS 38.304.
In another case where the registration request, including the emergency service fallback request, is not accepted, the apparatus 200 includes means, such as the processor 202, for determining that the first timer has expired without a response from the network (such as the AMF 108). See block 819. In such a case, the apparatus 200 of the example embodiment comprises means, such as the processor 202, for causing a notification of a timer expiration if the emergency service to be provided is not established, such as by causing an emergency service fallback attempt failure notification to be sent to a client (e.g., upper layer, user, etc.). See block 820.
Fig. 9 illustrates another flowchart of the operations of the example method 910 performed by the example apparatus 200, and in one embodiment, the example apparatus 200 may be embodied by a computer program product comprising computer program code executed by the processor 202 of the UE 102. As indicated at block 911, the apparatus 200 of this example embodiment comprises means, such as the processor 202, the memory 204, the communication interface 206, and the like, for causing a registration request to be sent during a registration update procedure that includes an emergency service fallback request defined by a registration type value, such as indicating the emergency service fallback request, and in some embodiments a successor request bit that defines whether a successor request is pending. As described above, prior to the operation shown in fig. 9, UE102 has registered with the network (such as AMF 108) and is updating its registration, such as a mobility registration update or a periodic registration update. However, the registration update request has not been accepted by the AMF, such as in the case where the registration update request fails due to lack of response from the network or due to predefined conditions (such as those described in sub-clauses 5.3.9 and 5.5.1.3.5 of 3gpp TS 24.501). In this case, the UE determines that an emergency session needs to be established, such as based on input from a user of the UE102 or from upper layers of the UE, and a registration request including an emergency service fallback request is generated and transmitted, such as by the processor 202 and/or the communication interface 206. As shown at block 911, the apparatus 200 of this example embodiment comprises means, such as the processor 202, the memory 204, the communication interface 206, or the like, for determining a response to a registration request that comprises an emergency service fallback request. The response includes an acceptance or rejection of the emergency service fallback request, such as described in the example provided above.
Fig. 10 illustrates a flowchart of the operations of an example method 1010 performed by the example apparatus 200, which example apparatus 200 may be embodied in one embodiment by a computer program product comprising computer program code executed by a processor 202 of a network entity, such as the AMF 108. As indicated at block 1011, the apparatus 200 of this example embodiment comprises means, such as the processor 202, the memory 204, the communication interface 206, and/or the like, for receiving a registration request including an emergency service fallback request during a registration update procedure, the emergency service fallback request being defined by a registration type value, such as indicating the emergency service fallback request, and in some embodiments by a successor request bit that defines whether a successor request is pending. In this regard, prior to the operations shown in fig. 10, the UE102 has registered with the network (such as the AMF 108) and is updating its registration, such as a mobility registration update or a periodic registration update. However, the network entity (such as the AMF) has not accepted the registration update request, such as in the case where the network entity (such as the AMF) has not provided a response, or due to other predefined conditions (such as the conditions described in sub-clauses 5.3.9 and 5.5.1.3.5 of 3gpp TS 24.501). In this case, the UE has determined that an emergency session needs to be established, such as based on input from a user of the UE102 or from upper layers of the UE, and a registration request including an emergency service fallback request has been generated and transmitted and then received by a network entity (such as an AMF). As indicated at block 1012, the apparatus 200 of this example embodiment comprises means, such as the processor 202, the memory 204, the communication interface 206, or the like, for causing a response to a registration request, including an emergency service fallback request, to be provided. The response may constitute an acceptance or rejection of the emergency service fallback request.
In one case, the response indicating acceptance of the emergency service fallback request is not explicitly provided to the UE102, but may be determined by the UE based on other changes caused by the AMF108, in this case as an accepted form of response. For example, the apparatus 200 (such as the AMF 108) may indicate that the emergency service fallback request has been accepted and trigger an emergency service fallback procedure, such as specified in sub-clause 4.13.4.2 of 3gpp TS 23.502, by causing a mode change of the UE (such as to S1 mode) and/or causing a network connection to be established with the UE, such as in the case where the E-UTRA has connected to a 5 GCN. Alternatively, in the event that the registration request including the emergency service fallback request is not accepted, the apparatus 200 (such as the processor 202) may cause a rejection response (such as a registration rejection message) to be transmitted to the UE 102. In some embodiments, a response to a registration request (such as a registration reject message) including an emergency service fallback request may identify the reason for the rejection, such as by a cause value. In the event that the cause value has a predefined value, the UE may be caused to select a cell, such as a cell connected to an Evolved Packet Core (EPC) or 5G core network (5 GCN), and initiate communication via that cell, thereby potentially providing emergency services, albeit in a different manner than originally requested.
For example, the apparatus 200 (such as the processor 202) embodied by the network entity (e.g., the AMF 108) may be configured to cause the registration reject message to include a predefined cause value (e.g., # 9) indicating that the identity of the UE cannot be derived by the network. As another example, an apparatus 200 (such as the processor 202) embodied by a network entity (e.g., the AMF 108) may be configured to cause a registration reject message to include a predefined cause value (e.g., # 15) indicating that there are no suitable cells in the tracking area.
In another case where the registration request including the emergency service fallback request is not accepted, the apparatus 200 (such as the processor 202) may not provide a response, at least for a predefined time period measured by the first timer, resulting in expiration of the first timer and providing an indication that the emergency service fallback request is not accepted.
As described above, a method, apparatus 200 and computer program product for enhancing an emergency service fallback procedure are disclosed. The emergency service fallback procedure is initiated during the registration update procedure without the UE having to first complete the registration update procedure before separately initiating and completing the emergency service fallback procedure. As a result, access to emergency service fallback procedures may be advantageously accelerated, such as in the event of a failure of a registration update procedure (e.g., a periodic registration update).
As mentioned above, reference is made to a flow chart of a method that can be performed by an apparatus according to a related computer program product comprising computer program code. It will be understood that each block of the flowchart, and combinations of blocks in the flowchart, can be implemented by various means, such as hardware, firmware, processor, circuitry, and/or other devices associated with execution of software including one or more computer program instructions. For example, one or more of the procedures described above may be embodied by computer program instructions. In this regard, the computer program instructions which embody the procedures described above may be stored by a memory device (e.g., 204) of an apparatus (e.g., 200) employing an embodiment of the present invention and executed by a processor (e.g., 202) of the apparatus. As will be appreciated, any such computer program instructions may be loaded onto a computer or other programmable apparatus (e.g., hardware) to produce a machine, such that the resulting computer or other programmable apparatus implement the functions specified in the flowchart block or blocks. These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture the execution of which implements the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart block or blocks.
Thus, a computer program product is defined in which computer program instructions (such as computer-readable program code portions) are stored by at least one non-transitory computer-readable storage medium, wherein the computer program instructions (such as computer-readable program code portions) are configured to, when executed, perform the functions described above. In other embodiments, the computer program instructions (such as computer-readable program code portions) need not be stored or otherwise embodied by a non-transitory computer-readable storage medium, but may be embodied by a transitory medium, with the computer program instructions (such as computer-readable program code portions) still configured to perform the functions described above when executed.
Accordingly, blocks of the flowchart support combinations of means for performing the specified functions and combinations of operations for performing the specified functions. It will also be understood that one or more blocks of the flowchart, and combinations of blocks in the flowchart, can be implemented by special purpose hardware-based computer systems which perform the specified functions, or combinations of special purpose hardware and computer instructions.
In some embodiments, some of the operations, methods, steps, processes, etc. described above may be modified or further amplified. Moreover, in some embodiments, additional optional operations, methods, steps, processes, etc. may be included. Modifications, additions, subtractions, inverse transforms, correlations, proportionality, non-proportionality, attenuations, and/or amplifications to the above operations may be performed in any order and in any combination. It will also be understood that where specific operations, methods, steps, processes, etc., require specific hardware, such hardware should be considered part of the apparatus 200 for any such embodiments. For example, where GPS is used to determine the location of the device 200, as described above, such appropriate GPS modules and hardware should be considered as part of the device 200.
Many modifications and other embodiments of the inventions set forth herein will come to mind to one skilled in the art to which these inventions pertain having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the inventions are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Moreover, although the foregoing descriptions and the associated drawings describe example embodiments in the context of certain example combinations of elements and/or functions, it should be appreciated that different combinations of elements and/or functions may be provided by alternative embodiments without departing from the scope of the appended claims. In this regard, for example, different combinations of elements and/or functions than those explicitly described above are also contemplated as may be set forth in some of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.
Claims (40)
1. A method, comprising:
causing a registration request to be sent during a registration update procedure, the registration request including at least a registration type value indicating an emergency service fallback request; and
determining a response to the registration request including the emergency service fallback request.
2. The method of claim 1, wherein the registration request to be sent further comprises a follow-up request bit defining that no follow-up request is pending.
3. The method of any of claims 1 or 2, wherein determining the response to the registration request comprises: determining that the emergency service fallback request has been accepted in case a mode has changed or a connection to a network has been established.
4. The method of claim 3, further comprising:
starting a timer when the registration request is caused to be sent; and
stopping the timer upon determining that the emergency service fallback request has been accepted.
5. The method of any of claims 1 or 2, wherein determining the response to the registration request comprises: determining that the emergency service fallback request has not been accepted, and wherein the registration request is provided in response to a predefined cause value, the method further comprising:
selecting a cell connected to an Evolved Packet Core (EPC) or 5G core network (5 GCN); and
initiating communication via the cell.
6. The method of claim 5, further comprising:
starting a timer when the communication via the cell is transmitted; and
stopping the timer upon determining that the communication via the cell has been accepted.
7. The method of any of claims 1 or 2, further comprising:
starting a timer when the registration request is caused to be sent;
determining that a predefined time limit has expired since starting the timer; and
causing an emergency service fallback attempt failure notification to be sent to the client in response to the expiration of the predefined time limit.
8. A method, comprising:
receiving a registration request during a registration update procedure, the registration request including at least a registration type value indicating an emergency service fallback request; and
causing a response to the registration request to be provided.
9. The method of claim 8, wherein the response to the registration request defines acceptance of the emergency service fallback request.
10. The method of claim 8, wherein the response to the registration request defines a rejection of the emergency service fallback request; and the response to the registration request further comprises a predefined cause value for the rejection.
11. An apparatus, comprising:
at least one processor; and
at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform:
causing a registration request to be sent during a registration update procedure, the registration request including at least a registration type value indicating an emergency service fallback request; and
determining a response to the registration request including the emergency service fallback request.
12. The apparatus of claim 11, wherein the registration request to be sent further comprises a follow-up request bit defining that no follow-up request is pending.
13. The apparatus of any of claims 11 or 12, wherein determining the response to the registration request comprises: determining that the emergency service fallback request has been accepted in case a mode has changed or a connection to a network has been established.
14. The apparatus of claim 13, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to perform:
starting a timer when the registration request is caused to be sent; and
stopping the timer upon determining that the emergency service fallback request has been accepted.
15. The apparatus of any of claims 11 or 12, wherein determining the response to the registration request comprises: determining that the emergency service fallback request has not been accepted, and wherein in response to a predefined cause value being provided in response to the registration request, the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to perform:
selecting a cell connected to an Evolved Packet Core (EPC) or 5G core network (5 GCN); and
initiating communication via the cell.
16. The apparatus of claim 15, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to perform:
starting a timer when the communication via the cell is transmitted; and
stopping the timer upon determining that the communication via the cell has been accepted.
17. The apparatus according to any of claims 11 or 12, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to perform:
starting a timer when the registration request is caused to be sent;
determining that a predefined time limit has expired since starting the timer; and
causing an emergency service fallback attempt failure notification to be sent to the client in response to the expiration of the predefined time limit.
18. An apparatus, comprising:
at least one processor; and
at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform:
receiving a registration request during a registration update procedure, the registration request including at least a registration type value indicating an emergency service fallback request; and
causing a response to the registration request to be provided.
19. The apparatus of claim 18, wherein the response to the registration request defines acceptance of the emergency service fallback request.
20. The apparatus of claim 18, wherein the response to the registration request defines a rejection of the emergency service fallback request; and the response to the registration request further comprises a predefined cause value for the rejection.
21. A computer program product comprising a non-transitory computer-readable storage medium having program code portions stored thereon, the program code portions configured to, when executed, perform:
causing a registration request to be sent during a registration update procedure, the registration request including at least a registration type value indicating an emergency service fallback request; and
determining a response to the registration request including the emergency service fallback request.
22. The computer program product of claim 21, wherein the registration request to be sent further comprises a follow-up request bit defining that no follow-up request is pending.
23. The computer program product of any of claims 21 or 22, wherein determining the response to the registration request comprises: determining that the emergency service fallback request has been accepted in case a mode has changed or a connection to a network has been established.
24. The computer program product of claim 23, wherein the program code portions are further configured to perform:
starting a timer when the registration request is caused to be sent; and
stopping the timer upon determining that the emergency service fallback request has been accepted.
25. The computer program product of any of claims 21 or 22, wherein determining the response to the registration request comprises: determining that the emergency service fallback request has not been accepted, and wherein in response to a predefined cause value being provided in response to the registration request, the program code portions are further configured to perform:
selecting a cell connected to an Evolved Packet Core (EPC) or 5G core network (5 GCN); and
initiating communication via the cell.
26. The computer program product of claim 25, wherein the program code portions are further configured to perform:
starting a timer when the communication via the cell is transmitted; and
stopping the timer upon determining that the communication via the cell has been accepted.
27. The computer program product according to any of claims 21 or 22, wherein the program code portions are further configured to perform:
starting a timer when the registration request is caused to be sent;
determining that a predefined time limit has expired since starting the timer; and
causing an emergency service fallback attempt failure notification to be sent to the client in response to the expiration of the predefined time limit.
28. A computer program product comprising a non-transitory computer-readable storage medium having program code portions stored thereon, the program code portions configured to, when executed, perform:
receiving a registration request during a registration update procedure, the registration request including at least a registration type value indicating an emergency service fallback request; and
causing a response to the registration request to be provided.
29. The computer program product of claim 28, wherein the response to the registration request defines acceptance of the emergency service fallback request.
30. The computer program product of claim 28, wherein the response to the registration request defines a rejection of the emergency service fallback request; and the response to the registration request further comprises a predefined cause value for the rejection.
31. An apparatus, comprising:
means for causing a registration request to be sent during a registration update procedure, the registration request including at least a registration type value indicating an emergency service fallback request; and
means for determining a response to the registration request including the emergency service fallback request.
32. The apparatus of claim 31, wherein the registration request to be sent further comprises a follow-up request bit defining that no follow-up request is pending.
33. The apparatus of any of claims 31 or 32, wherein determining the response to the registration request comprises: determining that the emergency service fallback request has been accepted in case a mode has changed or a connection to a network has been established.
34. The apparatus of claim 33, further comprising:
means for starting a timer when the registration request is caused to be sent; and
means for stopping the timer upon determining that the emergency service fallback request has been accepted.
35. The apparatus of any of claims 31 or 32, wherein determining the response to the registration request comprises: determining that the emergency service fallback request has not been accepted, and wherein provided in response to the registration request in response to a predefined cause value, the apparatus further comprises:
means for selecting a cell connected to an Evolved Packet Core (EPC) or a 5G core network (5 GCN); and
means for initiating communication via the cell.
36. The apparatus of claim 35, further comprising:
means for starting a timer when the communication via the cell is transmitted; and
means for stopping the timer upon determining that the communication via the cell has been accepted.
37. The apparatus of any one of claims 31 or 32, further comprising:
means for starting a timer when the registration request is caused to be sent;
means for determining that a predefined time limit has expired since the timer was started; and
means for causing an emergency service fallback attempt failure notification to be sent to the client in response to expiration of the predefined time limit.
38. An apparatus, comprising:
means for receiving a registration request during a registration update procedure, the registration request including at least a registration type value indicating an emergency service fallback request; and
means for causing a response to the registration request to be provided.
39. The apparatus of claim 38, wherein the response to the registration request defines acceptance of the emergency service fallback request.
40. The apparatus of claim 38, wherein the response to the registration request defines a rejection of the emergency service fallback request; and the response to the registration request further comprises a predefined cause value for the rejection.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US202063007097P | 2020-04-08 | 2020-04-08 | |
| US63/007,097 | 2020-04-08 | ||
| PCT/EP2021/051049 WO2021204432A1 (en) | 2020-04-08 | 2021-01-19 | Method, apparatus, and computer program product for expediting an emergency services initiation |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115669013A true CN115669013A (en) | 2023-01-31 |
Family
ID=74191596
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202180037371.5A Pending CN115669013A (en) | 2020-04-08 | 2021-01-19 | Method, apparatus and computer program product for accelerating emergency service initiation |
Country Status (6)
| Country | Link |
|---|---|
| US (2) | US11924798B2 (en) |
| EP (1) | EP3893534B1 (en) |
| JP (1) | JP2023521702A (en) |
| CN (1) | CN115669013A (en) |
| TW (1) | TWI813966B (en) |
| WO (1) | WO2021204432A1 (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023093795A1 (en) * | 2021-11-25 | 2023-06-01 | Telefonaktiebolaget Lm Ericsson (Publ) | Network node, user equipment, and methods therein for communication in edgeapp |
| CN116437405A (en) * | 2022-01-04 | 2023-07-14 | 北京三星通信技术研究有限公司 | Node in wireless communication system and method for performing the same |
| WO2024035522A1 (en) * | 2022-08-08 | 2024-02-15 | Qualcomm Incorporated | Mobility robustness optimization enhancement using fallback indications for inter-system handover reports |
Family Cites Families (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10684350B2 (en) * | 2000-06-02 | 2020-06-16 | Tracbeam Llc | Services and applications for a communications network |
| US8382865B2 (en) * | 2006-08-30 | 2013-02-26 | Kyocera Corporation | Reaction apparatus, fuel cell system and electronic device |
| US20100297979A1 (en) * | 2009-04-14 | 2010-11-25 | Interdigital Patent Holdings, Inc. | Method and apparatus for processing emergency calls |
| US20110026687A1 (en) * | 2009-07-31 | 2011-02-03 | Vladimir Smelyansky | Emergency 911 services with just-in-time provisioning for voip customers |
| US20130290459A1 (en) * | 2012-03-26 | 2013-10-31 | Michael Cuff | Configurable Escalation Queue |
| WO2018231813A1 (en) * | 2017-06-13 | 2018-12-20 | Intel IP Corporation | Systems, methods and devices for legacy system fallback in a cellular communications system |
| RU2763395C2 (en) | 2017-06-23 | 2021-12-28 | ЭлДжи ЭЛЕКТРОНИКС ИНК. | Method and device for checking access ban |
| WO2019097302A1 (en) * | 2017-11-20 | 2019-05-23 | Lenovo (Singapore) Pte. Ltd. | Fallback assistance information |
| EP3744115A1 (en) * | 2018-01-23 | 2020-12-02 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods, core network node and ran node for enabling emergency services |
| CN110166984B (en) * | 2018-02-13 | 2021-09-24 | 维沃移动通信有限公司 | Service processing method, information sending method and related equipment |
| US10757612B2 (en) * | 2018-03-06 | 2020-08-25 | T-Mobile Usa, Inc. | Controlling fallback procedures for different user groups or device groups |
| JP2019186719A (en) * | 2018-04-09 | 2019-10-24 | シャープ株式会社 | UE and core network device |
| JP6847892B2 (en) * | 2018-06-21 | 2021-03-24 | シャープ株式会社 | UE and communication control method |
| JP2020025212A (en) * | 2018-08-08 | 2020-02-13 | シャープ株式会社 | UE and core network device |
| EP3861797A4 (en) * | 2018-10-04 | 2021-12-29 | NEC Corporation | Procedure to update the parameters related to unified access control |
| WO2020074093A1 (en) * | 2018-10-12 | 2020-04-16 | Telefonaktiebolaget Lm Ericsson (Publ) | Indication of evolved packet system fallback capability |
| CA3118784C (en) * | 2018-11-14 | 2023-10-03 | Nokia Technologies Oy | Apparatus, method and computer program for connection management |
| US20220124869A1 (en) * | 2019-01-18 | 2022-04-21 | Telefonaktiebolaget Lm Ericsson (Publ) | Emergency calls with service request triggered fallback |
| WO2020171529A1 (en) * | 2019-02-22 | 2020-08-27 | Lg Electronics Inc. | Method for performing communication related to packet switch data off |
| US11490291B2 (en) * | 2019-03-28 | 2022-11-01 | Ofinno, Llc | Handover for closed access group |
| WO2020202078A1 (en) * | 2019-04-02 | 2020-10-08 | Telefonaktiebolaget Lm Ericsson (Publ) | Handling of emergency services for non-public networks |
| US10887749B1 (en) * | 2019-08-15 | 2021-01-05 | Blackberry Limited | Emergency services handling |
| WO2021056384A1 (en) * | 2019-09-27 | 2021-04-01 | Qualcomm Incorporated | Back-off mechanisms for transmission of data over control plane |
-
2021
- 2021-01-19 CN CN202180037371.5A patent/CN115669013A/en active Pending
- 2021-01-19 JP JP2022560970A patent/JP2023521702A/en active Pending
- 2021-01-19 WO PCT/EP2021/051049 patent/WO2021204432A1/en active Application Filing
- 2021-01-19 EP EP21152319.6A patent/EP3893534B1/en active Active
- 2021-03-12 US US17/249,782 patent/US11924798B2/en active Active
- 2021-03-18 TW TW110109776A patent/TWI813966B/en active
-
2024
- 2024-03-04 US US18/594,710 patent/US20240334365A1/en active Pending
Also Published As
| Publication number | Publication date |
|---|---|
| JP2023521702A (en) | 2023-05-25 |
| US11924798B2 (en) | 2024-03-05 |
| US20210321356A1 (en) | 2021-10-14 |
| TW202142009A (en) | 2021-11-01 |
| TWI813966B (en) | 2023-09-01 |
| EP3893534B1 (en) | 2024-09-18 |
| US20240334365A1 (en) | 2024-10-03 |
| WO2021204432A1 (en) | 2021-10-14 |
| EP3893534A1 (en) | 2021-10-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7485772B2 (en) | Method, apparatus, and computer program product for handling emergency services in a private network | |
| KR20210126584A (en) | Systems and Methods Supporting Device Triggered Reauthentication of Slice-Specific Secondary Authentication and Authorization | |
| TWI813966B (en) | Method, apparatus, and computer program product for expediting an emergency services initiation | |
| US20240188024A1 (en) | Methods, apparatuses, and computer program products for providing selection of cells serving network slices for an area | |
| WO2021165049A1 (en) | Methods, apparatuses, and computer program products for managing a devices network capabilities in private networks | |
| US20220264283A1 (en) | Method, apparatus, and computer program product to facilitate control of terminal timing information within a network | |
| WO2020160783A1 (en) | Apparatus, method and computer program | |
| US20230388769A1 (en) | Method, apparatus, and computer program product for service-continuity indication in sidelink user equipment to network relay during path switch | |
| US20230143638A1 (en) | Method, apparatus, and computer program product for network slice aware public land mobile network selection | |
| WO2022068903A1 (en) | Network selection method and apparatus, information transmission method and apparatus, and information acquisition method and apparatus | |
| WO2022069481A2 (en) | Method, apparatus, and computer program product for network slice and frequency band selection configuration | |
| CN115175256A (en) | Method and communication device for transmitting context | |
| US20210120628A1 (en) | Apparatus, method and computer program for emergency call | |
| US20230319697A1 (en) | Methods, apparatuses, and computer program products for supporting onboarding and authentication of user equipment for networks and network slices | |
| US20230319906A1 (en) | Methods, apparatuses, and computer program products for supporting simultaneous access to mutally isolated network slices | |
| US20230388386A1 (en) | Method, apparatus, and computer program product for enlarging usage of user category within a core network | |
| WO2022214064A1 (en) | Method for accessing network, network side device, and terminal | |
| WO2024078753A1 (en) | Access path switching | |
| CN117835214A (en) | Communication method, device and readable storage medium | |
| CN117528665A (en) | Access information transmission method and device and network side equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |