Method and apparatus for emergency service handling

Abstract

A method implemented by a first terminal device is provided. The method includes: receiving, from a first network node, information related to network support of an emergency service from a second terminal device; and determining, based on the information received from the first network node, whether the request for the emergency service from the second terminal device complies with the local provisions and operator policies of the service network of the first terminal device. With the method and apparatus of the present disclosure, a mechanism is provided for applying local provisions and operator policies for emergency services of a serving PLMN of a relay UE to a remote UE.

Description

Technical Field

[0001] The present disclosure generally relates to the field of emergency service handling, and more particularly, to a method and apparatus for emergency service handling of a user equipment (UE) to a network relay. Background Art

[0002] This section introduces aspects that may facilitate a better understanding of the present disclosure. Therefore, the statements in this section should be read in this light and not be understood as an admission about what is or is not the prior art.

[0003] In 5GS (fifth generation system) Proximity-based Services (ProSe), a 5G ProSe-capable User Equipment (UE) is defined as a UE that supports 5G ProSe requirements and associated procedures. A 5G ProSe UE-to-network relay is a 5G ProSe-capable UE that provides functionality to support connectivity of (one or more) 5G ProSe remote UEs to the network, which communicate with the DN (data network) via the 5G ProSe UE-to-network relay. 5G ProSe layer 3 UE to network relay reference architecture

[0004] Figure 1 A high-level reference architecture for 5G ProSe layer 3 UE-to-network relay is shown. Figure 1 In , the 5G ProSe layer 3 UE to network relay can be in the HPLMN (home public land mobile network) or the VPLMN (visited public land mobile network).

[0005] Figure 2 The non-roaming reference architecture for 5G ProSe layer 3 UE to network relay when N3IWF (non-3GPP (3rd Generation Partnership Project) interworking function) is supported is shown. Figure 2 In this case, PLMN A and PLMN B can be the same or different. When a 5G ProSe layer 3 remote UE can directly connect to the NG-RAN (next generation radio access network) to access PLMN B, it will play the role of Figure 2 The N3IWF can be connected to the relay UE UPF (User Plane Function) via the data network.

[0006] Figure 3 The roaming reference architecture for 5G ProSe layer 3 UE to network relay when N3IWF is supported is shown. Figure 3 In the example, PLMN A and PLMN B may be the same or different, and / or PLMN A and PLMN C may be the same or different. The N3IWF may be connected to the relay UE UPF via a data network. 5G ProSe layer 2 UE to network relay reference architecture

[0007] For 5G ProSe Layer 2 UE to network relay, when NG-RAN is shared, the serving PLMNs of the remote UE and the relay UE can be different.

[0008] Figure 4 The 5G ProSe Layer 2 UE to Network Relay reference architecture is shown. The 5G ProSe Layer 2 Remote UE and the 5G ProSe Layer 2 UE to Network Relay may be served by the same or different PLMNs. If the serving PLMNs of the 5G ProSe Layer 2 Remote UE and the 5G ProSe Layer 2 UE to Network Relay are different, the NG-RAN is shared by the serving PLMN (see the 5G MOCN architecture in clause 5.18 of TS 23.501).

[0009] It should be noted that the Uu between the 5G ProSe Layer 2 Remote UE and the NG-RAN consists of RRC (Radio Resource Control), SDAP (Service Data Adaptation Protocol) and PDCP (Packet Data Convergence Protocol), and the 5G ProSe Layer 2 Remote UE and the 5G ProSe Layer 2 UE to Network Relay are served by the same NG-RAN. The core network entities (e.g., AMF (Access and Mobility Management Function), SMF (Session Management Function), UPF) serving the 5G ProSe Layer 2 Remote UE and the 5G ProSe Layer 2 UE to Network Relay may be the same or different. UE Registration Process

[0010] The registration procedure for the UE is performed as defined in TS 23.502 clause 4.2.2.2, with the following additions: -The UE includes the 5G ProSe capability as part of the "5GMM (5GS Mobility Management) Capability" in the Registration Request message. The AMF stores the 5G ProSe capability for 5G ProSe operation. -5G ProSe capabilities indicate whether the UE supports one or more of the following ProSe capabilities: -5G ProSe direct discovery; -5G ProSe direct communication; -5G ProSe layer 2 UE to network relay; -5G ProSe layer 3 UE to network relay; -5G ProSe Layer 2 Remote UE; and -5G ProSe layer 3 remote UE. - During the UE registration procedure using the Nudm_SDM service as defined in clause 4.2.2.2.2 of TS 23.502, the AMF obtains the 5G ProSe subscription data from UDM (Unified Data Management) as part of the user subscription data. -AMF determines whether the UE is authorized to use 5G ProSe services based on the UE's 5G ProSe capabilities and the ProSe service authorization included in the subscription data received from the UDM, as specified in clause 5.7. The ProSe NR (New Radio) UE-PC5-AMBR (Aggregate Maximum Bit Rate) is also provided to the AMF as part of the subscription data for the 5G ProSe service. The AMF stores the authorized 5G ProSe capabilities. -AMF sends the authorized 5G ProSe capabilities for 5G ProSe operation to PCF (Policy Control Function). Based on the 5G ProSe capabilities received from AMF, PCF provides PC5 QoS parameters for 5G ProSe to AMF. AMF stores such information as part of the UE context. - If the UE is authorized to use 5G ProSe services, the AMF shall include in the NGAP message sent to the NG-RAN: - "5G ProSe Authorization" information, including one or more of the following: -Whether the UE is authorized to use 5G ProSe direct discovery; -Whether the UE is authorized to use 5G ProSe direct communication; -Whether the UE is authorized to act as a 5G ProSe Layer 2 UE-to-network relay; -Whether the UE is authorized to act as a 5G ProSe Layer 3 UE-to-network relay; -Whether the UE is authorized to act as a 5G ProSe Layer 2 Remote UE. -ProSe NR UE-PC5-AMBR, used by NG-RAN for resource management of PC5 transmission for UEs serving 5G ProSe services in network scheduling mode. - PC5 QoS parameters for 5G ProSe used by NG-RAN for resource management of PC5 delivery for UEs served by ProSe in network scheduled mode. - If the UE is authorized to use 5G ProSe services, the AMF shall not initiate the release of the signaling connection after the completion of the registration procedure. The release of the signaling connection depends on the decision of the NG-RAN as specified in TS 23.502. Summary of the invention

[0011] The present disclosure provides a method and apparatus for emergency service handling in UE-to-network relay.

[0012] According to a first aspect of the present disclosure, a method implemented by a first terminal device is provided. The method includes: receiving information related to network support for emergency services from a second terminal device from a first network node; and determining whether a request for emergency services from the second terminal device complies with local regulations and operator policies of a service network of the first terminal device based on the information received from the first network node.

[0013] In an alternative embodiment of the first aspect, the first terminal device may be in an allowed area or in a not allowed area.

[0014] In another alternative embodiment of the first aspect, the step of determining whether the request complies with local regulations and operator policies of a serving network of the first terminal device may include: Check network support for emergency services from the second end device.

[0015] In yet another alternative embodiment of the first aspect, in a case where the first terminal device and the second terminal device are served by different service networks, the first terminal device may be preferentially processed by the service network of the first terminal device.

[0016] According to a second aspect of the present disclosure, a method implemented by a first network node is provided, the method comprising: providing network support for emergency services from a second terminal device during normal registration of the first terminal device, if the first terminal device is authorized to use a relay service; and transmitting information related to the network support to the first terminal device.

[0017] According to a third aspect of the present disclosure, a method implemented by a second network node is provided. The method includes: receiving a list of service networks of a second terminal device having an agreement with a service network of a first terminal device from a first network node; receiving a radio resource control connection from the second terminal device; determining whether the service network of the second terminal device is in the list; and if the service network of the second terminal device is not in the list, rejecting an emergency service request from the second terminal device.

[0018] According to a fourth aspect of the present disclosure, a first terminal device is provided. The first terminal device includes a processor and a memory communicatively coupled to the processor. The memory is suitable for storing instructions, and when the instructions are executed by the processor, the first terminal device performs the operation according to the method of the first aspect above.

[0019] According to a fifth aspect of the present disclosure, a first terminal device is provided. The first terminal device is suitable for executing the method of the first aspect.

[0020] According to a sixth aspect of the present disclosure, a first network node is provided. The first network node comprises a processor and a memory communicatively coupled to the processor. The memory is adapted to store instructions, which, when executed by the processor, cause the first network node to perform operations according to the method of the second aspect above.

[0021] According to a seventh aspect of the present disclosure, a first network node is provided. The first network node is adapted to execute the method of the second aspect.

[0022] According to an eighth aspect of the present disclosure, a second network node is provided. The second network node includes a processor and a memory communicatively coupled to the processor. The memory is suitable for storing instructions, and when the instructions are executed by the processor, the second network node performs the operation according to the method of the third aspect above.

[0023] According to a ninth aspect of the present disclosure, a second network node is provided. The second network node is adapted to execute the method of the third aspect.

[0024] According to a tenth aspect of the present disclosure, a wireless communication system is provided. The wireless communication system comprises: a first terminal device of the fourth or fifth aspect; a first network node of the sixth or seventh aspect, the first network node at least communicating with the first terminal device; and a second network node of the eighth or ninth aspect, the second network node at least communicating with the first network node.

[0025] According to an eleventh aspect of the present disclosure, a non-transitory computer readable medium having a computer program stored thereon is provided. When the computer program is executed by a set of one or more processors of a first terminal device, the computer program causes the first terminal device to perform the operation of the method according to the first aspect above.

[0026] According to a twelfth aspect of the present disclosure, a non-transitory computer readable medium having a computer program stored thereon is provided. When the computer program is executed by a set of one or more processors of a first network node, the computer program causes the first network node to perform the operation of the method according to the second aspect above.

[0027] According to a thirteenth aspect of the present disclosure, a non-transitory computer readable medium having a computer program stored thereon is provided. When the computer program is executed by a set of one or more processors of a second network node, the computer program causes the second network node to perform the operation of the method according to the third aspect above.

[0028] By using the method and apparatus of the present disclosure, a mechanism is provided for applying the local regulations and operator policies on emergency services of the serving PLMN of the relay UE to the remote UE. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] The present disclosure may be best understood by way of example with reference to the following description and accompanying drawings which illustrate embodiments of the present disclosure. In the drawings: Figure 1 is a schematic diagram illustrating a reference architecture of 5G ProSe layer 3 UE to network relay; Figure 2 is a schematic diagram illustrating a non-roaming architecture model of 5G ProSe layer 3 UE to network relay with N3IWF support; Figure 3 is a schematic diagram illustrating a 5G ProSe layer 3 UE to network relay roaming architecture model with N3IWF support; Figure 4 is a schematic diagram illustrating a 5G ProSe layer 2 UE to network relay reference architecture; Figure 5 is a sequence diagram illustrating the layer 2 link establishment process; Figure 6 is a flowchart illustrating a method implemented on a first terminal device according to some embodiments of the present disclosure; Figure 7 is a flow chart illustrating a method implemented on a first network node according to some embodiments of the present disclosure; Figure 8 is a flow chart illustrating a method implemented on a second network node according to some embodiments of the present disclosure; Fig. 9 is a block diagram illustrating a first terminal device according to some embodiments of the present disclosure; Fig.10 is another block diagram illustrating a first terminal device according to some embodiments of the present disclosure; Fig.11 is a block diagram illustrating a first network node according to some embodiments of the present disclosure; Fig.12 is another block diagram illustrating a first network node according to some embodiments of the present disclosure; Fig.13 is a block diagram illustrating a second network node according to some embodiments of the present disclosure; Fig.14 is another block diagram illustrating a second network node according to some embodiments of the present disclosure; Fig.15 is a block diagram illustrating a wireless communication system according to some embodiments of the present disclosure; Fig.16 is a block diagram schematically illustrating a telecommunications network connected to a host computer via an intermediate network; Fig.17is a general block diagram of a host computer communicating with a user device via a base station over a partially wireless connection; and Figures 18 to 21 is a flow chart illustrating a method implemented in a communication system including a host computer, a base station, and a user equipment. DETAILED DESCRIPTION

[0030] The following detailed description describes methods and apparatus for emergency service handling in UE to network relay. In the following detailed description, many specific details such as logic implementation, types and interrelationships of system components are set forth to provide a more thorough understanding of the present disclosure. However, it should be appreciated by those skilled in the art that the present disclosure can be implemented without such specific details. In other instances, control structures, circuits, and instruction sequences have not been shown in detail in order not to obscure the present disclosure. With the included description, one of ordinary skill in the art will be able to implement appropriate functionality without undue experimentation.

[0031] References in the specification to "one embodiment," "an embodiment," "an example embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it is considered to be within the knowledge of those skilled in the art to affect such feature, structure, or characteristic in conjunction with other embodiments, whether or not explicitly described.

[0032] Text within brackets and boxes with dashed borders (e.g., large dashed lines, small dashed lines, dot-dash lines, and dots) may be used herein to illustrate optional operations that add additional features to embodiments of the present disclosure. However, such symbols should not be understood to mean that these are the only options or optional operations, and / or that in certain embodiments of the present disclosure, boxes with solid borders are not optional.

[0033] In the following detailed description and claims, the terms "coupled" and "connected," as well as their derivatives, may be used. It should be understood that these terms are not intended as synonyms for each other. "Coupled" is used to indicate that two or more elements cooperate or interact with each other, which may or may not be in direct physical or electrical contact with each other. "Connected" is used to indicate that communication is established between two or more elements that are coupled to each other.

[0034] Electronic devices use machine-readable media (also called computer-readable media) to store and transmit (internally and / or over a network with other electronic devices) code (which consists of software instructions and which is sometimes referred to as computer program code or computer program) and / or data, such as machine-readable storage media (e.g., magnetic disks, optical disks, read-only memory (ROM), flash memory devices, phase change memory) and machine-readable transmission media (also called carriers) (e.g., electrical, optical, radio, acoustic or other forms of propagated signals, such as carrier waves, infrared signals). Thus, an electronic device (e.g., a computer) includes hardware and software, such as a set of one or more processors coupled to one or more machine-readable storage media to store code for execution on the set of processors and / or to store data. For example, an electronic device may include non-volatile memory containing code, because non-volatile memory can save code / data even when the electronic device is turned off (when power is removed), and when the electronic device is turned on, the portion of the code to be executed by the processor(s) of the electronic device is typically copied from the slower non-volatile memory to the volatile memory of the electronic device (e.g., dynamic random access memory (DRAM), static random access memory (SRAM)). A typical electronic device also includes a collection of one or more physical network interfaces to establish a network connection with other electronic devices (using propagation signals to transmit and / or receive code and / or data). One or more parts of the embodiments of the present disclosure may be implemented using different combinations of software, firmware and / or hardware. Establishing a layer 2 link over the PC5 reference point

[0035] In order to perform the unicast mode of ProSe direct communication over the PC5 reference point, the UE is configured with relevant information as described in clause 5.1.3 of TS 23.304 v17.3.0.

[0036] Figure 5 The Layer 2 link establishment procedure for unicast mode of ProSe direct communication over PC5 reference point is shown.

[0037] At step 1, the UE(s) determine the destination layer 2 ID for signaling reception for PC5 unicast link establishment, as specified in clause 5.8.2.4 of TS 23.304 v17.3.0.

[0038] In step 2, the ProSe application layer in UE-1 provides application information for PC5 unicast communication. The application information includes ProSe service information and the application layer ID of the UE. The application layer ID of the target UE may be included in the application information.

[0039] The ProSe application layer in UE-1 may provide the ProSe application requirements for this unicast communication. UE-1 determines the PC5 QoS (Quality of Service) parameters and PFI (PC5 QoS Flow Identifier) ​​as specified in clause 5.6.1 of TS23.304v17.3.0.

[0040] If UE-1 decides to reuse the existing PC5 unicast link as specified in clause 5.3.4 of TS 23.304 v17.3.0, the UE triggers the Layer 2 Link Modification procedure as specified in clause 6.4.3.4 of TS 23.304 v17.3.0.

[0041] In step 3, UE-1 sends a direct communication request message to initiate a unicast layer 2 link establishment process. The direct communication request message includes: - Source user information: the application layer ID of the initiating UE (i.e., the application layer ID of UE-1). If the ProSe application layer provides the application layer ID of the target UE in step 2, the following information is included: - Target user information: the application layer ID of the target UE (ie, the application layer ID of UE-2). - ProSe service information: Information about the ProSe identifier(s) requesting Layer 2 link establishment. - Security information: information to establish security.

[0042] The source layer 2ID and destination layer 2ID used to send the direct communication request message are determined as specified in clauses 5.8.2.1 and 5.8.2.4 of TS23.304v17.3.0, and the destination layer 2ID can be a broadcast or unicast layer 2ID. When using a unicast layer 2ID, target user information shall be included in the direct communication request message.

[0043] UE-1 sends a direct communication request message via PC5 by broadcast or unicast using the source layer 2ID and the destination layer 2ID.

[0044] The default PC5 DRX (discontinuous receive) configuration can be used to transmit and receive this message.

[0045] 4. Security with UE-1 is established as follows: 4a. If the target user information is included in the direct communication request message, the target UE (ie, UE-2) responds by establishing security with UE-1. 4b. If the target user information is not included in the direct communication request message, then the user is interested in using the announced (one or more) on the PC5 unicast link with UE-1. The ProSe served UE responds by establishing security with UE-1.

[0046] When security protection is enabled, UE-1 sends the following information to the target UE: - If using IP communication: -IP address configuration: For IP communication, IP address configuration is required for this link road and indicates one of the following values: - "DHCPv4 (Dynamic Host Configuration Protocol version 4) server", if the initiating UE only supports IPv4 (Internet Protocol version 4) address allocation mechanism, i.e. acts as a DHCPv4 server; or - "IPv6 router", if the initiating UE supports only IPv6 address allocation mechanisms, i.e. acts as an IPv6 router; or - "DHCPv4 server and IPv6 router", if the initiating UE supports both IPv4 address allocation mechanism and IPv6 address allocation mechanism; or - "Not support address allocation", if the initiating UE supports neither the IPv4 address allocation mechanism nor the IPv6 address allocation mechanism. - Link-local IPv6 address: A link-local IPv6 address formed locally based on RFC 4862 if UE-1 does not support the IPv6 IP address allocation mechanism, i.e., the IP address configuration indicates "address allocation not supported". -QoS Information: Information about (one or more) PC5 QoS flows. For each PC5 QoS flow, PFI and corresponding PC5 QoS parameters (i.e. PQI (PC5 QoS Identifier) ​​and other parameters in conditional cases, such as MFBR (Maximum Flow Bit Rate) / GFBR (Guaranteed Flow Bit Rate) etc.) and optionally associated (one or more) ProSe identifiers. -Optional (one or more) PC5 QoS rules.

[0047] The source layer 2 ID for the security establishment procedure is determined as specified in clauses 5.8.2.1 and 5.8.2.4 of TS 23.304 v17.3.0. The destination layer 2 ID is set to the source layer 2 ID of the received direct communication request message.

[0048] Upon receiving the Security Setup Procedure message, UE-1 obtains the Layer 2 ID of the peer UE for future communications, for signaling and data traffic of this unicast link.

[0049] In step 5, the target UE(s) that have successfully established security with UE-1 sends a direct communication accept message to UE-1: 5a. (Layer 2 Link Establishment Towards UE) If the target user information is included in the Direct Communication Request message, if the application layer ID of UE-2 matches, the target UE (ie, UE-2) responds with a Direct Communication Accept message. 5b. (Layer 2 Link Establishment for ProSe Services) If the target user information is not included in the direct communication request message, the UE interested in using the announced ProSe service(s) acknowledges the user by sending a direct communication accept message ( Figure 5 UE-2 and UE-4) in response to the request.

[0050] Direct communication acceptance messages include: -Source user information: the application layer ID of the UE that sends the direct communication acceptance message. -QoS Information: Information about (one or more) PC5 QoS flows. For each PC5 QoS flow, the PFI requested by UE-1 and the corresponding PC5 QoS parameters (i.e., PQI and other parameters where conditional, such as MFBR / GFBR, etc.) and optionally the associated (one or more) ProSe identifiers. -Optional (one or more) PC5 QoS rules. - If using IP communication: -IP address configuration: For IP communication, IP address configuration is required for this link road and indicates one of the following values: - "DHCPv4 Server", if the target UE only supports IPv4 address allocation mechanism, i.e. acts as a DHCPv4 server; or - "IPv6 router", if the target UE only supports IPv6 address allocation mechanisms, i.e. acts as an IPv6 router; or - "DHCPv4 server and IPv6 router", if the target UE supports both IPv4 address allocation mechanism and IPv6 address allocation mechanism; or - "Not support address allocation", if the target UE supports neither IPv4 address allocation mechanism nor IPv6 address allocation mechanism. - Link-local IPv6 address: A link-local IPv6 address formed locally based on RFC 4862. If the target UE does not support the IPv6 IP address allocation mechanism, i.e., the IP address configuration indicates "address allocation is not supported", and UE-1 includes a link-local IPv6 address in the direct communication request message, the target UE shall include a non-conflicting link-local IPv6 address.

[0051] If both UEs (ie, the initiating UE and the target UE) choose to use link-local IPv6 addresses, they should disable duplicate address detection as defined in RFC 4862.

[0052] It should be noted that when the initiating UE or the target UE indicates support for IPv6 routing, the corresponding address configuration process will be performed after the layer 2 link is established, and the link-local IPv6 address is ignored.

[0053] The ProSe layer of the UE that establishes the PC5 unicast link passes the PC5 link identifier and PC5 unicast link related information assigned to the unicast link downward to the AS (Access Stratum) layer. The PC5 unicast link related information includes layer 2 ID information (i.e., source layer 2 ID and destination layer 2 ID). This enables the AS layer to maintain the PC5 link identifier and PC5 unicast link related information.

[0054] Two UEs may negotiate the PC5 DRX configuration in the AS layer and may configure PC5 DRX parameter values ​​in the AS layer for each pair of source and destination Layer 2 IDs.

[0055] In step 6, ProSe data is transmitted via the established unicast link as follows: The PC5 link identifier and PFI are provided to the AS layer together with the ProSe data.

[0056] Optionally, in addition, layer 2 ID information (ie, source layer 2 ID and destination layer 2 ID) is provided to the AS layer.

[0057] It should be noted that it is up to the UE implementation to provide the Layer 2 ID information to the AS layer.

[0058] UE-1 sends ProSe data using a source Layer 2 ID (ie, the Layer 2 ID of UE-1 for this unicast link) and a destination Layer 2 ID (ie, the Layer 2 ID of the peer UE for this unicast link).

[0059] It should be noted that the PC5 unicast link is bidirectional, so UE- 1 's peer UE can send ProSe data to UE- 1 on the unicast link with UE- 1 . Emergency services support in 5GS and EPS (Evolved Packet System)

[0060] According to TS23.401 and TS23.501, depending on local regulations and operator policies, the MME (Mobility Management Entity) can support emergency services for the UE as follows: a. Only valid UE. b. Only authenticated UEs are allowed. c. IMSI (International Mobile Subscriber Identity) is required, authentication is optional. d. Allow all UEs. Emergency Services

[0061] Emergency services are provided to support IMS emergency sessions. "Emergency services" refers to the functionality provided by a serving network when the serving network is configured to support emergency services. Emergency services are provided to normally registered UEs and to emergency registered UEs, which may be normally registered or in a restricted service state. Depending on local regulations, a valid subscription is not required to receive emergency services in a restricted service state. Depending on local regulations and the operator's policies, the network may allow or reject an emergency services registration request (i.e., emergency registration) from a UE that has been identified as being in a restricted service state. Four different behaviors for emergency services as defined in clause 4.3.12.1 of TS 23.401 are supported. IMS emergency session support

[0062] IMS Emergency Sessions provides an overview of emergency bearer service functionality. Unless otherwise specified, this overview applies to eCall over IMS. Specific functionality is described in the affected procedures and functions of this specification.

[0063] Emergency bearer services are provided to support IMS emergency sessions. Emergency bearer services are functionality provided by the serving network when the network is configured to support emergency services. Emergency bearer services are provided to normally attached or emergency attached UEs and, depending on local provisions, to UEs in limited service state. No subscription is required to receive emergency services in limited service state. Depending on local provisions and the operator's policy, the MME may allow or reject an emergency attach request for a UE in limited service state. Four different behaviors for emergency bearer support have been identified as follows: a. Only valid UEs. Limited service state UEs are not supported in the network. Only UEs with valid subscription, authenticated and authorized for PS services in attached location are allowed. When the UE detects an IMS emergency session, the UE should attach to the network and then perform a PDN (Packet Data Network) connection request. b. Only authenticated UEs are allowed. These UEs must have a valid IMSI. These UEs are authenticated and may be in a restricted service state due to being in a location where they are restricted. UEs that cannot be authenticated will be rejected. c.IMSI is required, authentication is optional. These UEs must have an IMSI. If authentication fails, the UE is granted access and the unauthenticated IMSI is retained in the network for logging purposes. IMEI (International Mobile Equipment Identity) is used as a UE identifier in the network. UEs with only IMEI will be rejected (e.g. UEs without UICC). d. All UEs are allowed. In addition to authenticated UEs, this also includes UEs with IMSIs that cannot be authenticated and UEs with only IMEIs. If an unauthenticated IMSI is provided by the UE, the unauthenticated IMSI is retained in the network for logging purposes. The IMEI is used in the network to identify the UE. Emergency support from UE to network relay

[0064] According to TS22.101, emergency services are defined as a service for citizens to the authorities, and it is up to the national authorities to decide whether the network accepts emergency calls, for example only for valid UEs, or for UEs without SIM / USIM / ISIM (Subscriber Identity Module / Universal Subscriber Identity Module / International Mobile Subscriber Identity).

[0065] In 5G ProSe UE to network relay, if there is an emergency request from the remote UE, this implies that the relay UE needs to be responsible for the emergency service of the remote UE.

[0066] Assuming that a UE relaying emergency services for another UE complies with local regulations, the following aspects of 5G ProSe UE-to-network relay need to be addressed whether and how: - Whether and how the UE-to-network relay identifies emergency services from a remote UE and vice versa; - the conditions under which it is ensured that the emergency call is routed to a PSAP in the same country as the remote UE; - What are the operating principles and UE and network behaviors of the remote UE and 5G ProSe UE to network relay to be enhanced for emergency services, the following are some (but not limited to) aspects: - Override mobility restrictions (as defined in TS 23.501) where applicable. - Support emergency services in limited service state (as defined in clause 5.16.4 of TS 23.501). - Support congestion control (as defined in clause 5.19 of TS23.501). Emergency services from UE to network relay

[0067] The solution disclosed herein addresses the support of emergency services for UE to network relay.

[0068] Assuming that the UE responsible for emergency services of another UE complies with local regulations, and the relay UE and the remote UE belong to the same PLMN, the solution disclosed in this article includes the following aspects: -Emergency service support -5G ProSe UE to Network Relay advertises its support for emergency services only if the UE receives an Emergency Support Indication in the Registration Accept. -5G ProSe Remote UE becomes aware during discovery whether the 5G ProSe UE to Network Relay can support emergency services. - The 5G ProSe Remote UE indicates an emergency access request to the 5G ProSe UE to Network Relay during PC5 link establishment, and the 5G ProSe UE to Network Relay informs its network (both the radio network and the core network) of the emergency services. - If a 5G ProSe remote UE completes an emergency call, it can wait for a configurable period of time before initiating the release of the PC5 link for emergency services. This is to prepare for any possible call back. - When the PC5 link for emergency services is released, for Layer 2 UE to network relay, if the 5G ProSe UE to network relay is not involved in emergency services from any remote UE, the relay UE notifies the AMF to remove the emergency indication. process -5G ProSe UE to network relay strategy / parameter configuration -5G ProSe UE to network relay mobility restrictions reflecting support for emergency services -ProSe UE to network relay discovery - ProSe communication via 5G ProSe layer 3 UE to network relay without N3IWF - ProSe communication via 5G ProSe layer 3 UE to network relay with N3IWF support - 5G ProSe communication via 5G ProSe Layer 2 UE to network relay, where: -If the state of the 5G ProSe UE to the network relay UE is in RRC_IDLE, the relay UE sets the RRC establishment cause to "Emergency". -If the state of the 5G ProSe UE to network relay UE is in RRC_CONNECTED, the 5G ProSe UE to network relay needs to notify its CN through NAS that the UE is involved in emergency services for the 5G ProSe UE to network remote UE, so that the 5G ProSe UE to network relay UE can be exempted from, for example, overload control.

[0069] For emergency services from a 5G ProSe remote UE, the local regulations and operator policies of the relaying UE's serving PLMN may not be applied to the remote UE. The following are some examples of how the local rules of the relaying UE's serving network may be applied to the remote UE: - If the serving PLMN of the 5G ProSe UE to the network relay UE supports emergency services from UEs with IMSI, emergency services from the 5G ProSe remote UE without IMSI present shall be rejected; - If the serving PLMN of the relay UE supports emergency services from UEs with IMSI but authentication optional, the relay can skip the security procedures for 5G ProSe communication from UE to network relay via 5G ProSe Layer 3.

[0070] Furthermore, for Layer 2 UE to network relay, when the serving PLMNs of the L2 remote UE and relay UE are different, there is no mechanism for the serving PLMN of the relay UE to have some control whether emergency services from the remote UE (served by another PLMN) should be allowed.

[0071] In this regard, the UE registration procedure may be enhanced as follows: In the case of a 5G ProSe capable UE, if the UE is authorized to act as a relay, the AMF may provide the remote UE with information related to network support for emergency services as follows: IMSI is required, authentication is optional; ●IMSI is required, authentication is required; or ● Allow all UEs (with or without IMSI)

[0072] As for whether the UE has an IMSI, this is detected by whether the remote UE provides a PRUK ID (ProSe Remote User Key Identifier) ​​or a SUCI (Subscription Concealment Identifier) ​​to the relay UE.

[0073] Information provided in relation to network support for emergency services may also include: • Only remote UEs served by the same PLMN are required.

[0074] For layer 2 5G ProSe UE to network relay: ●The AMF may send to the NG-RAN in an NGAP (NG Application Protocol) message (e.g., Initial Context Setup Request) a list of serving PLMN(s) of the remote UE that have an agreement with the PLMN of the relay UE. ● When a Layer 2 remote UE establishes its RRC connection to the NG-RAN, the NG-RAN may determine whether the remote UE’s serving PLMN is in a list that has an agreement with the relay UE’s PLMN. If the remote UE’s serving PLMN is inconsistent with the relay UE’s PLMN, the NG-RAN may reject the emergency service request.

[0075] Furthermore, during Layer 2 link establishment over the PC5 reference point for 5G ProSe UE to Network Relay: - The remote UE may need to inform the relay UE whether it has an IMSI (which may currently be possible if the remote UE sends a PRUK ID or SUCI to the relay UE in the direct communication request); - The relay UE shall check its serving network's support of the remote UE's emergency services as follows: - If the network relaying the UE requires an IMSI, emergency services from a remote UE without a SIM may not be allowed. -If the network of the relaying UE does not require authentication of the remote UE, the relaying UE can skip the security procedures for 5G ProSe communications via the 5G ProSe UE to the network relay. -For Layer 2 UE to network relay, if the remote UE has a different serving PLMN, but the serving network of the relaying UE does not allow emergency services from the remote UE with a different serving PLMN, the emergency services from the remote UE will be rejected with an appropriate reason so that the remote UE will select the same serving PLMN as the relaying UE.

[0076] The above disclosure of the solution may be enhanced in at least the following aspects: When a 5G ProSe-capable UE acts as a relay, based on the SA1 response, the relay UE can have a normal registration in the network. The UE can be in an allowed area or in a disallowed area.

[0077] For a remote UE where no SIM / USIM / ISIM exists, the local regulations and operator policies of the relaying UE's serving PLMN may also be applied to the remote UE.

[0078] In order to allow the 5G ProSe UE to Network Relay to determine as early as possible whether the emergency request of the remote UE complies with the local regulations and operator policies of the serving PLMN of the relaying UE, assuming that the local regulations and operator policies of the serving PLMN of the relaying UE will also apply to the remote UE: - During registration from a 5G ProSe capable UE, if the UE is authorized to act as a relay, the AMF may provide network support for emergency services to the remote UE as follows: IMSI is required, authentication is required; IMSI is required and authentication is optional; or All UEs are allowed.

[0079] When a UE with relay capability (also referred to as a "relay-enabled UE") performs a normal registration, the AMF may check whether the relay service is authorized (e.g., by means of the AMF checking the subscription data from the UDM, locally configured). If it is authorized, the AMF may provide information about network support for emergency services from the remote UE. - When the remote UE establishes a PC5 link for emergency services towards the relay UE, the relay UE may need to check the network support for the emergency services of the remote UE. -Depending on the network support for emergency services of the remote UE, the relay UE may reject the layer 2 link establishment request or may skip the security procedures for 5G ProSe communications via 5G ProSe UE to the network relay. During PC5 layer 2 link establishment, when determining whether to reject the link establishment, or continue with the link establishment but skip the security procedures for 5G ProSe communications via 5G ProSe layer 3 UE to the network relay, the relay UE will also check the network support for emergency services of the remote UE provided by the AMF.

[0080] For Layer 2 5G ProSe UE to network relay, if the remote UE and relay UE are served by different PLMNs (i.e., the RAN is shared by multiple PLMNs), in order to avoid the drop of emergency services from the L2 remote UE, there may be an implication that the Layer 2 relay UE needs to be preferentially handled by its serving network which is different from the serving network of the remote UE.

[0081] Figure 6 6 is a flowchart illustrating a method 600 implemented on a first terminal device according to some embodiments of the present disclosure. As an example, the operations of this flowchart may be performed by a UE capable of relaying in the entire context, but they are not limited thereto. The operations in this flowchart and other flowcharts will be described with reference to exemplary embodiments of other figures. However, it should be appreciated that the operations of the flowchart may be performed by embodiments of the present disclosure other than those discussed with reference to the other figures, and that the embodiments of the present disclosure discussed with reference to these other figures may perform operations different from those discussed with reference to the flowchart.

[0082] In one embodiment, a first terminal device may receive information about network support for emergency services from a second terminal device from a first network node (block 601). The first terminal device may then determine whether a request for emergency services from the second terminal device complies with local regulations and operator policies of a serving network of the first terminal device based on the information received from the first network node (block 602). As an example, the second terminal device may be a remote UE and the first network node may be an AMF.

[0083] As an example, the first terminal device may be in an allowed area or in a disallowed area.

[0084] As an example, the step of determining whether the request complies with local regulations and operator policies of the serving network of the first terminal device may include: Check network support for emergency services from the second end device.

[0085] As another example, the information related to network support may include at least: The IMSI of the second terminal device is required, and authentication of the second terminal device is required; The IMSI of the second terminal device is required and authentication of the second terminal device is optional; or All second terminal devices among the second terminal devices are allowed.

[0086] As still another example, the information related to network support may also include at least: Only second terminal devices served by the same service network as the first terminal device are allowed.

[0087] As further examples, network supported checks may include: In response to the IMSI being requested, denying emergency services from a second terminal device that does not have the IMSI; In response to authentication being optional, continuing with the emergency service and skipping security procedures for communications via the first terminal device; or Emergency services are denied from a second terminal device having a different service network than the first terminal device.

[0088] As an example, in a case where the first terminal device and the second terminal device are served by different service networks, the first terminal device may be preferentially processed by the service network of the first terminal device.

[0089] In addition, the present disclosure provides a first terminal device suitable for executing method 600 .

[0090] Figure 77 is a flowchart illustrating a method 700 implemented on a first network node according to some embodiments of the present disclosure. As an example, the operations of this flowchart may be performed by an AMF.

[0091] In one embodiment, during normal registration of a first terminal device, a first network node may provide network support for emergency services from a second terminal device if the first terminal device is authorized to use a relay service (block 701). The first network node may then transmit information related to the network support to the first terminal device (block 702). As an example, the first terminal device may be a relay-enabled UE, and the second terminal device may be a remote UE.

[0092] As an example, the information related to network support may include at least: The IMSI of the second terminal device is required, and authentication of the second terminal device is required; The IMSI of the second terminal device is required and authentication of the second terminal device is optional; or All second terminal devices among the second terminal devices are allowed.

[0093] As another example, the information related to network support may also include at least: Only second terminal devices served by the same service network as the first terminal device are allowed.

[0094] As an example, the method 700 may further include: A list of service networks of the second terminal device having an agreement with the service network of the first terminal device is transmitted to the second network node.

[0095] Furthermore, the present disclosure provides a first network node suitable for performing the method 700 .

[0096] Figure 8 8 is a flowchart illustrating a method 800 implemented on a second network node according to some embodiments of the present disclosure. As an example, the operations of this flowchart may be performed by a NG-RAN.

[0097] In one embodiment, the second network node may receive from the first network node a list of service networks of a second terminal device that have an agreement with the service network of the first terminal device (box 801). The second network node may receive an RRC connection from the second terminal device (box 802). The second network node may determine whether the service network of the second terminal device is in the list (box 803). Then, if the service network of the second terminal device is not in the list, the second network node may reject the emergency service request from the second terminal device (box 804). As an example, the first network node may be an AMF, the first terminal device may be a UE capable of relaying, and the second terminal device may be a remote UE.

[0098] Furthermore, the present disclosure provides a second network node suitable for performing the method 800 .

[0099] Fig. 9 1 is a block diagram illustrating a first terminal device 900 according to some embodiments of the present disclosure. As an example, the first terminal device 900 may act as a UE capable of implementing relay, but is not limited thereto. It should be appreciated that the first terminal device 900 may use a UE other than Fig. 9 It may be implemented by components other than those described in .

[0100] refer to Fig. 9 , the first terminal device 900 may include at least a processor 901, a memory 902, a network interface 903, and a communication medium 904. The processor 901, the memory 902, and the network interface 903 may be communicatively coupled to each other via the communication medium 904.

[0101] The processor 901 may include one or more processing units. A processing unit may be a physical device or article including one or more integrated circuits, which read data and instructions from a computer-readable medium such as memory 902 and selectively execute instructions. In various embodiments, the processor 901 may be implemented in various ways. As an example, the processor 901 may be implemented as one or more processing cores. As another example, the processor 901 may include one or more separate microprocessors. In yet another example, the processor 901 may include an application-specific integrated circuit (ASIC) that provides specific functionality. In yet another example, the processor 901 may provide specific functionality by using an ASIC and / or by executing computer-executable instructions.

[0102] The memory 902 may include one or more computer usable or computer readable storage media capable of storing data and / or computer executable instructions. It should be appreciated that the storage media are preferably non-transitory storage media.

[0103] The network interface 903 may be a device or product that enables the first terminal device 900 to send data to other devices or receive data from other devices. In different embodiments, the network interface 903 may be implemented in different ways. As an example, the network interface 903 may be implemented as an Ethernet interface, a token ring network interface, a fiber network interface, a network interface (e.g., Wi-Fi, WiMax, etc.), or other types of network interfaces.

[0104] The communication medium 904 can facilitate communication between the processor 901, the memory 902, and the network interface 903. The communication medium 904 can be implemented in various ways. For example, the communication medium 904 can include a peripheral component interconnect (PCI) bus, a PCI Express bus, an accelerated graphics port (AGP) bus, a serial advanced technology attachment (ATA) interconnect, a parallel ATA interconnect, a fiber channel interconnect, a USB bus, a small computing system interface (SCSI) interface, or another type of communication medium.

[0105] exist Fig. 9 In the example of Figure 6 Those instructions that describe the method.

[0106] Fig.10 1 is another block diagram illustrating a first terminal device 1000 according to some embodiments of the present disclosure. As an example, the first terminal device 1000 may act as a UE capable of implementing relay, but is not limited thereto. It should be appreciated that the first terminal device 1000 may use Fig.10 It may be implemented by components other than those described in .

[0107] refer to Fig.10 , the first terminal device 1000 may include at least a receiving unit 1001 and a determining unit 1002. The receiving unit 1001 may be adapted to at least perform Figure 6 The determining unit 1002 may be adapted to perform at least Figure 6 The operations described in block 602 of .

[0108] Fig.11 1 is a block diagram illustrating a first network node 1100 according to some embodiments of the present disclosure. As an example, the first network node 1100 may act as an AMF. It should be appreciated that the first network node 1100 may use Fig.11 It may be implemented by components other than those described in .

[0109] refer to Fig.11, the first network node 1100 may include at least a processor 1101, a memory 1102, a network interface 1103, and a communication medium 1104. The processor 1101, the memory 1102, and the network interface 1103 are communicatively coupled to each other via the communication medium 1104.

[0110] Processor 1101 , memory 1102 , network interface 1103 , and communication medium 1104 are similar in structure to processor 901 , memory 902 , network interface 903 , and communication medium 904 , respectively, and will not be described in detail herein.

[0111] exist Fig.11 In an example, the instructions stored in the memory 1102 may include, when executed by the processor 1101, causing the first network node 1100 to implement the Figure 7 Those instructions that describe the method.

[0112] Fig.12 1 is another block diagram illustrating a first network node 1200 according to some embodiments of the present disclosure. As an example, the first network node 1200 may act as an AMF, but is not limited thereto. It should be appreciated that the first network node 1200 may use other than Fig.12 It may be implemented by components other than those described in .

[0113] refer to Fig.12 , the first network node 1200 may include at least a providing unit 1201 and a transmitting unit 1202. The providing unit 1201 may be adapted to perform at least Figure 7 The transmission unit 1202 may be adapted to perform at least Figure 7 The operations described in block 702 of .

[0114] Fig.13 1 is a block diagram illustrating a second network node 1300 according to some embodiments of the present disclosure. As an example, the second network node 1300 may serve as an NG-RAN, but is not limited thereto. It should be appreciated that the second network node 1300 may use other than Fig.13 It may be implemented by components other than those described in .

[0115] refer to Fig.13 The second network node 1300 may include at least a processor 1301, a memory 1302, a network interface 1303, and a communication medium 1304. The processor 1301, the memory 1302, and the network interface 1303 are communicatively coupled to each other via the communication medium 1304.

[0116] Processor 1301 , memory 1302 , network interface 1303 , and communication medium 1304 are structurally similar to processor 901 or 1101 , memory 902 or 1102 , network interface 903 or 1103 , and communication medium 904 or 1104 , respectively, and will not be described in detail herein.

[0117] exist Fig.13 In the example of, the instructions stored in the memory 1302 may include, when executed by the processor 1301, causing the second network node 1300 to implement the Figure 8 Those instructions that describe the method.

[0118] Fig.14 1 is another block diagram illustrating a second network node 1400 according to some embodiments of the present disclosure. As an example, the second network node 1400 may provide a function as a NG-RAN, but is not limited thereto. It should be appreciated that the second network node 1400 may use other than Fig.14 It may be implemented by components other than those described in .

[0119] refer to Fig.14 , the second network node 1400 may include at least a receiving unit 1401, a determining unit 1402 and a rejecting unit 1403. The receiving unit 1401 may be adapted to at least perform Figure 8 The determining unit 1402 may be adapted to perform at least Figure 8 The rejecting unit 1403 may be adapted to perform at least Figure 8 The operations described in block 804 of .

[0120] Fig.10 , 12 The units shown in 14 may constitute machine executable instructions contained in a machine (e.g., a readable medium), which, when executed by the machine, will cause the machine to perform the described operations. In addition, any of these units may be implemented as hardware, such as an application specific integrated circuit (ASIC), a digital signal processor (DSP), a field programmable gate array (FPGA), etc.

[0121] Furthermore, it should be appreciated that the arrangements described herein are set forth only as examples. Other arrangements (e.g., more controllers or more detectors, etc.) may be used to supplement or replace those shown, and some units may be omitted entirely. Figure 6-8 The functionality and cooperation of these units are described in more detail accordingly.

[0122] Fig.151 is a block diagram illustrating a wireless communication system 1500 according to some embodiments of the present disclosure. The wireless communication system 1500 includes at least a first terminal device 1501, a first network node 1502, and a second network node 1503. In one embodiment, the first terminal device 1501 may function as Fig. 9 In the first terminal device 900 or 1000 depicted in FIG. 10 , the first network node 1502 may act as Fig.11 The first network node 1100 or 1200 depicted in or 12, and the second network node 1503 may act as Fig.13 Or the second network node 1300 or 1400 depicted in FIG. 14. In one embodiment, the first terminal device 1501 and the second network node 1503 may communicate with the first network node 1502.

[0123] Fig.16 is a block diagram schematically illustrating a telecommunications network connected to a host computer via an intermediary network.

[0124] refer to Fig.16 According to an embodiment, a communication system includes a telecommunication network 1610 such as a cellular network of the 3GPP type, the telecommunication network 1610 including an access network 1611 such as a radio access network and a core network 1614. The access network 1611 includes a plurality of base stations 1612a, 1612b, 1612c such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 1613a, 1613b, 1613c. Each base station 1612a, 1612b, 1612c is connectable to the core network 1614 via a wired or wireless connection 1615. A first user equipment (UE) 1691 located in the coverage area 1613c is configured to be wirelessly connected to the corresponding base station 1612c or to be paged by the corresponding base station 1612c. A second UE 1692 in the coverage area 1613a is wirelessly connectable to the corresponding base station 1612a. Although multiple UEs 1691 , 1692 are illustrated in this example, the disclosed embodiments are equally applicable to situations where a single UE is in the coverage area or where a single UE is connecting to the corresponding base station 1612 .

[0125] The telecommunications network 1610 itself is connected to a host computer 1630, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 1630 may be under the ownership or control of a service provider, or may be operated by or on behalf of a service provider. The connections 1621 and 1622 between the telecommunications network 1610 and the host computer 1630 may extend directly from the core network 1614 to the host computer 1630, or may be via an optional intermediate network 1620. The intermediate network 1620 may be one of a public, private, or managed network, or a combination of more than one of a public, private, or managed network; the intermediate network 1620 (if any) may be a backbone network or the Internet; in particular, the intermediate network 1620 may include two or more sub-networks (not shown).

[0126] Fig.16 The communication system as a whole enables connectivity between one of the connected UEs 1691, 1692 and the host computer 1630. The connectivity may be described as an over-the-top (OTT) connection 1650. The host computer 1630 and the connected UEs 1691, 1692 are configured to communicate data and / or signaling via the OTT connection 1650 using the access network 1611, the core network 1614, any intermediate networks 1620, and possible additional infrastructure (not shown) as intermediaries. The OTT connection 1650 may be transparent in the sense that the participating communication devices through which the OTT connection 1650 passes are unaware of the routing of uplink and downlink communications. For example, the base station 1612 may not be informed or need not be informed of the past routing of incoming downlink communications, where data originating from the host computer 1630 is to be forwarded (e.g., handed over) to the connected UE 1691. Similarly, base station 1612 need not be aware of future routing of outbound uplink communications originating from UE 1691 toward host computer 1630 .

[0127] Now refer to Fig.171700, a host computer 1710 includes hardware 1715, which includes a communication interface 1716 configured to establish and maintain a wired or wireless connection with different communication devices of the communication system 1700. The host computer 1710 further includes a processing circuit 1718 that may have storage and / or processing capabilities. In particular, the processing circuit 1718 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The host computer 1710 further includes software 1711, which is stored in the host computer 1710 or can be accessed by the host computer 1710 and can be executed by the processing circuit 1718. Software 1711 includes a host application 1712. The host application 1712 may be operable to provide services to a remote user, such as a UE 1730 connected via an OTT connection 1750 terminating at the UE 1730 and the host computer 1710. In providing services to the remote user, the host application 1712 may provide user data transmitted using the OTT connection 1750.

[0128] The communication system 1700 further includes a base station 1720 provided in the telecommunication system and including hardware 1725 enabling it to communicate with the host computer 1710 and with the UE 1730. The hardware 1725 may include a communication interface 1726 for establishing and maintaining wired or wireless connections with different communication devices of the communication system 1700 and for establishing and maintaining at least connections with devices located in the coverage area served by the base station 1720 (not in the Fig.17 The communication interface 1726 may be configured to facilitate a connection 1760 to the host computer 1710. The connection 1760 may be direct or it may be through a core network of the telecommunications system (not shown in FIG. Fig.17 ) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 1725 of the base station 1720 further includes processing circuitry 1728, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) adapted to execute instructions. The base station 1720 further has software 1721 stored internally or accessible via an external connection.

[0129] The communication system 1700 further includes the UE 1730 already mentioned. Its hardware 1735 may include a radio interface 1737, which is configured to establish and maintain a wireless connection 1770 with a base station serving the coverage area where the UE 1730 is currently located. The hardware 1735 of the UE 1730 further includes a processing circuit 1738, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The UE 1730 further includes software 1731, which is stored in the UE 1730 or can be accessed by the UE 1730 and can be executed by the processing circuit 1738. The software 1731 includes a client application 1732. With the support of the host computer 1710, the client application 1732 can be operable to provide services to human or non-human users via the UE 1730. In the host computer 1710, the executing host application 1712 can communicate with the executing client application 1732 via the OTT connection 1750 terminated at the UE 1730 and the host computer 1710. When providing services to users, the client application 1732 can receive request data from the host application 1712 and provide user data in response to the request data. The OTT connection 1750 can transmit both the request data and the user data. The client application 1732 can interact with the user to generate the user data it provides.

[0130] Notice that Fig.17 The host computer 1710, base station 1720 and UE 1730 described in Fig.16 The host computer 1630, one of the base stations 1612a, 1612b, 1612c, and one of the UEs 1691, 1692 may be the same. That is, the internal workings of these entities may be the same as Fig.17 As shown in , and independently, the surrounding network topology can be Fig.16 The surrounding network topology.

[0131] exist Fig.17 , an OTT connection 1750 has been abstractly drawn to illustrate communications between a host computer 1710 and a user device 1730 via a base station 1720, without explicit reference to any intermediate devices and the precise routing of messages via these devices. The network infrastructure may determine the routing, which may be configured to be hidden from the UE 1730 or hidden from the service provider operating the host computer 1710, or hidden from both. While the OTT connection 1750 is active, the network infrastructure may further make decisions by which it dynamically changes the routing (e.g., based on network reconfiguration or load balancing considerations).

[0132] The wireless connection 1770 between the UE 1730 and the base station 1720 is in accordance with the teachings of the embodiments described throughout the present disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE 1730 using the OTT connection 1750, where the wireless connection 1770 forms the last segment. More specifically, the teachings of these embodiments can improve radio resource utilization and thereby provide benefits such as reduced user waiting time.

[0133] The measurement process may be provided for the purpose of monitoring data rate, latency, and other factors improved by one or more embodiments. In response to changes in the measurement results, there may be further optional network functionality for reconfiguring the OTT connection 1750 between the host computer 1710 and the UE 1730. The measurement process and / or the network functionality for reconfiguring the OTT connection 1750 may be implemented with the software 1711 of the host computer 1710 or with the software 1731 of the UE 1730 or with both. In an embodiment, a sensor (not shown) may be deployed in a communication device through which the OTT connection 1750 passes or may be associated with a communication device through which the OTT connection 1750 passes; the sensor may participate in the measurement process by providing the values ​​of the monitoring quantities exemplified above or providing the values ​​of other physical quantities by which the software 1711, 1731 can calculate or estimate the monitoring quantities. The reconfiguration of the OTT connection 1750 may include message formats, retransmission settings, preferred routing selection, etc.; the reconfiguration does not need to affect the base station 1720, and it may be unknown or imperceptible to the base station 1720. Such processes and functionality may be known and implemented in the art. In certain embodiments, the measurements may involve proprietary UE signaling that facilitates measurements of the host computer 1710 of throughput, propagation time, latency, etc. The measurements may be achieved because the software 1711 and 1731 uses the OTT connection 1750 to cause messages to be transmitted, particularly empty messages or "fake" messages to be transmitted, while the software 1711 and 1731 monitors propagation time, errors, etc.

[0134] Fig.18 is a flow chart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a Fig.16 and Fig.17 For the sake of simplicity of this disclosure, only the host computers, base stations and UEs described in this section will be included. Fig.18In a first step 1810 of the method, a host computer provides user data. In an optional sub-step 1811 of the first step 1810, the host computer provides the user data by executing a host application. In a second step 1820, the host computer initiates a transmission to the UE carrying the user data. In an optional third step 1830, in accordance with the teachings of the embodiments described throughout the present disclosure, the base station transmits the user data carried in the transmission initiated by the host computer to the UE. In an optional fourth step 1840, the UE executes a client application associated with the host application executed by the host computer.

[0135] Fig.19 is a flow chart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a Fig.16 and Fig.17 For the sake of simplicity of this disclosure, only the host computers, base stations and UEs described in this section will be included. Fig.19 In a first step 1910 of the method, a host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In a second step 1920, the host computer initiates a transmission to the UE carrying the user data. According to the teachings of the embodiments described throughout the present disclosure, the transmission may pass through a base station. In an optional third step 1930, the UE receives the user data carried in the transmission.

[0136] Fig. 20 is a flow chart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a Fig.16 and Fig.17 For the sake of simplicity of this disclosure, only the host computers, base stations and UEs described in this section will be included. Fig. 20 . In an optional first step 2010 of the method, the UE receives input data provided by a host computer. Additionally or alternatively, in an optional second step 2020, the UE provides user data. In an optional sub-step 2021 of the second step 2020, the UE provides the user data by executing a client application. In another optional sub-step 2011 of the first step 2010, the UE executes a client application, which provides user data as a reaction to the received input data provided by the host computer. When providing the user data, the executed client application may further consider the user input received from the user. Regardless of the specific manner in which the user data is provided, the UE initiates the transmission of the user data to the host computer in an optional third sub-step 2030. In a fourth step 2040 of the method, in accordance with the teachings of the embodiments described throughout the present disclosure, the host computer receives the user data transmitted from the UE.

[0137] Fig.21 is a flow chart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a Fig.16 and Fig.17 For the sake of simplicity of this disclosure, only the host computers, base stations and UEs described in this section will be included. Fig.21 In an optional first step 2110 of the method, the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout the present disclosure. In an optional second step 2120, the base station initiates a transmission of the received user data to the host computer. In a third step 2130, the host computer receives the user data carried in the transmission initiated by the base station.

[0138] Some parts of the foregoing detailed description have been presented in terms of algorithms and symbolic representations of transactions on data bits within a computer memory. These algorithmic descriptions and representations are used by those skilled in the art of data processing to most effectively communicate the essence of their work to other skilled in the art. Algorithms are considered here and generally to be self-consistent sequences of transactions that lead to desired results. Transactions are those transactions that require physical manipulation of physical quantities. Typically, although not necessarily, these quantities take the form of electrical or magnetic signals that can be stored, transmitted, combined, compared, and otherwise manipulated. Mainly for general reasons, it has sometimes proven convenient to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, etc.

[0139] It should be appreciated, however, that all of these and similar terms are associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise, as is apparent from the above discussion, it is appreciated that throughout the description, discussions utilizing terms such as "processing" or "computing" or "calculating" or "determining" or "displaying" etc. refer to the actions and processes of a computer system or similar electronic computing device that manipulates and transforms data represented as physical (electronic) quantities in the computer system's registers and memories into other data similarly represented as physical quantities in the computer system's memories or registers or other such information storage, transmission or display devices.

[0140] The algorithms and displays presented herein are not inherently related to any particular computer or other device. According to the teachings herein, various general purpose systems can be used together with the program, or it may prove convenient to construct more specialized equipment to perform the required method affairs. The structures required for various these systems will emerge from the above description. In addition, embodiments of the present disclosure are not described with reference to any particular programming language. It should be appreciated that various programming languages ​​can be used to implement the teachings of the embodiments of the present disclosure as described herein.

[0141] An embodiment of the present disclosure may be an article of manufacture in which a non-transitory machine-readable medium (such as a microelectronic memory) has stored thereon instructions (e.g., computer code) that program one or more data processing components (collectively referred to herein as "processors") to perform the operations described above. In other embodiments, some of these operations may be performed by specific hardware components that include hardwired logic (e.g., dedicated digital filter blocks and state machines). Alternatively, those operations may be performed by any combination of programmed data processing components and fixed hardwired circuit components.

[0142] In the foregoing detailed description, embodiments of the present disclosure have been described with reference to specific exemplary embodiments of the present disclosure. It will be apparent that various modifications may be made thereto without departing from the spirit and scope of the present disclosure as set forth in the appended claims. Therefore, the specification and drawings are to be regarded in an illustrative sense rather than a restrictive sense.

[0143] Throughout the description, some embodiments of the present disclosure have been presented through flow charts. It should be appreciated that the transactions and the order of transactions described in these flow charts are intended only for illustrative purposes and are not intended as limitations of the present disclosure. Those of ordinary skill in the art will recognize that the flow charts may be changed without departing from the spirit and scope of the present disclosure as set forth in the appended claims.

Claims

1. A method (600) implemented by a first terminal device, the method comprising: receiving (601) from a first network node information related to network support of an emergency service from a second terminal device; as well as Based on the information received from the first network node, it is determined (602) whether the request for the emergency service from the second terminal device complies with local regulations and operator policies of a serving network of the first terminal device.

2. The method of claim 1, wherein: The first terminal device is in an allowed area or in a not allowed area.

3. The method according to claim 1 or 2, wherein: The step of determining whether the request complies with the local regulations of the service network of the first terminal device and the operator policy comprises: The network support of the emergency service from the second terminal device is checked.

4. The method of claim 3, wherein: The information related to the network support includes at least: an International Mobile Subscriber Identity IMSI of the second terminal device is required, and authentication of the second terminal device is required; The IMSI of the second terminal device is required and authentication of the second terminal device is optional; or All second terminal devices among the second terminal devices are allowed.

5. The method of claim 4, wherein: The information related to the network support includes at least: Only second terminal devices served by the same service network as the first terminal device are allowed.

6. The method according to claim 4 or 5, wherein: The checks supported by the network include: in response to the IMSI being requested, denying the emergency service from a second terminal device that does not have the IMSI; In response to the authentication being optional, continuing the emergency service and skipping security procedures for communications via the first terminal device; or The emergency service is denied from a second terminal device having a different service network than the first terminal device.

7. The method according to any one of claims 1 to 6, wherein: In the case where the first terminal device and the second terminal device are served by different service networks, the first terminal device is preferentially processed by the service network of the first terminal device.

8. The method according to any one of claims 1 to 7, wherein: The first terminal device is a relay-enabled terminal device, the second terminal device is a remote terminal device, and the first network node is an access and mobility management function.

9. A method (700) implemented by a first network node, the method comprising: providing (701) network support for emergency services from a second terminal device during normal registration of the first terminal device, provided that the first terminal device is authorized to use relay services; as well as Information related to the network support is transmitted (702) to the first terminal device.

10. The method of claim 9, wherein: The information related to the network support includes at least: an International Mobile Subscriber Identity IMSI of the second terminal device is required, and authentication of the second terminal device is required; The IMSI of the second terminal device is required and authentication of the second terminal device is optional; or All second terminal devices among the second terminal devices are allowed.

11. The method of claim 10, wherein: The information related to the network support includes at least: Only second terminal devices served by the same service network as the first terminal device are allowed.

12. The method according to any one of claims 9 to 11, further comprising: A list of serving networks of the second terminal device having an agreement with the serving network of the first terminal device is transmitted to the second network node.

13. The method according to any one of claims 9 to 11, wherein: The first network node is an Access and Mobility Management Function, the first terminal device is a relay-enabled terminal device, and the second terminal device is a remote terminal device.

14. A method (800) implemented by a second network node, the method comprising: Receiving (801) from a first network node a list of service networks of a second terminal device having an agreement with a service network of a first terminal device; as well as receiving (802) a radio resource control connection from a second terminal device; Determine (803) whether the serving network of the second terminal device is in the list; as well as If the serving network of the second terminal device is not in the list, rejecting (804) the emergency service request from the second terminal device.

15. The method of claim 14, wherein: The second network node is a next generation radio access network, the first network node is an access and mobility management function, the first terminal device is a relay enabled terminal device, and the second terminal device is a remote terminal device.

16. A first terminal device (900), comprising: Processor (901); as well as A memory (902) communicatively coupled to the processor and adapted to store instructions which, when executed by the processor, cause the first terminal device to perform the operations of the method of any one of claims 1-8.

17. A first terminal device, adapted to execute the method according to any one of claims 1 to 8.

18. A first network node (1100), comprising: Processor(1101); as well as A memory (1102) communicatively coupled to the processor and adapted to store instructions which, when executed by the processor, cause the first network node to perform the operations of the method of any one of claims 9-13.

19. A first network node, adapted to execute the method according to any one of claims 9 to 13.

20. A second network node (1300), comprising: Processor(1301); as well as A memory (1302) communicatively coupled to the processor and adapted to store instructions which, when executed by the processor, cause the second network node to perform the operations of the method of any of claims 14-15.

21. A second network node, adapted to execute the method according to any one of claims 14-15.

22. A wireless communication system (1500), comprising: The first terminal device (1501) of claim 16 or 17; The first network node (1502) of claim 18 or 19, the first network node (1502) communicating with at least the first terminal device; as well as The second network node (1503) of claim 20 or 21, said second network node (1503) being in communication with at least said first network node.

23. A non-transitory computer readable medium having stored thereon a computer program, the computer program, when executed by a set of one or more processors of a first terminal device, causes the first terminal device to perform the operations of any one of the methods of claims 1-8.

24. A non-transitory computer readable medium having stored thereon a computer program, which, when executed by a set of one or more processors of a first network node, causes the first network node to perform the operations of the method of any one of claims 9-13.

25. A non-transitory computer readable medium having stored thereon a computer program, which, when executed by a set of one or more processors of a second network node, causes the second network node to perform the operations of the method of any one of claims 14-15.

Images