GB2587660A - Improvements in and relating to proximity services - Google Patents

Abstract

A method and system to configure a group of user equipments (UE) for proximity services in a telecommunication system. The group of UEs are selected according to a combination of proximity to each other and also according to a directional relationship between them. The system may be used for device to device (D2D) communication in a 5G New Radio system. The advantages of the invention are said to be that it addresses shortcomings in discovery procedures related to the formation and management of Network-Controlled Interactive Services (NCIS) such as interactive gaming or data sharing. Examples of implementation of the invention are an interactive case whereby a user can share experiences via Augmented Reality/Virtual Reality (AR/VR) applications or public safety scenarios such as communication between an emergency vehicle and a crowd where discovery latency may be minimised and reliability of transmission ensured. The invention may utilise New Radio PC5 parameters such as range and directions of interest.

Description

Improvements in and relating to Proximity Services The present invention relates to improvements in Proximity Services (Prose) in the context of commercial or Public Safety applications.

Proximity Services have been developed in Evolved Packet System (EPS) from LTE Rel-12 to support both commercial and public safety services. In 3GPP Rel-14, the Proximity Services (specifically direct communication) has been enhanced to support V2X services over LIE. For the Fifth Generation System (5GS), proximity services are expected to be an important system-wide enabler to support various applications and services.

Another class of commercial services has recently emerged known as "Network-controlled Interactive services" (NCIS) that share some commonality of requirements with public safety services and applications. NCIS Service refers to a kind of service which needs at least more than one UE to join and share data, e.g. interactive gaming or data sharing. Those UEs in the same NCIS session are grouped together as one NCIS group, and the group is determined by application layer (i.e. NCIS application server).

Embodiments of the present invention address shortcomings in a discovery procedure related to the formation and management of such NCIS groups, whether such shortcomings are disclosed herein or not.

According to the present invention there is provided an apparatus and method as set forth in the appended claims. Other features of the invention will be apparent from the dependent

claims, and the description which follows.

According to an aspect of the present invention, there is provided a method of configuring a group of User Equipments, UEs, for proximity services, wherein the UEs to form the group are selected according to a combination of proximity to each other and also according to a directional relationship between them.

In an embodiment, a configuration update for the group of UEs is triggered due to a topology change observed within a Network Function of a telecommunication system within which the group of UEs is operating.

In an embodiment, a configuration update for the group of UEs is triggered due to a change observed in group charging policy within a Network Function of a telecommunication system within which the group of UEs is operating.

Although a few preferred embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes and modifications might be made without departing from the scope of the invention, as defined in the appended claims.

For a better understanding of the invention, and to show how embodiments of the same may be carried into effect, reference will now be made, by way of example only, to the accompanying diagrammatic drawings in which: Figure 1 shows sample environments in which embodiments of the invention find utility; Figure 2 shows service flow steps in accordance with an embodiment of the present invention; Figure 3 shows service flow steps in accordance with an embodiment of the present invention; and Figure 4 shows service flow steps in accordance with an embodiment of the present invention. 20 The new generation of services referred to above are not only reliant on proximity but also directions of interest. The directions of interest come from user intent and environmental context. This simplifies and/or accelerates the discovery procedure by limiting the search space to one or more specific directions. It also helps to improve power consumption during the discovery procedure. It may additionally enable more customised location-dependent charging mechanisms.

As an example, in an interactive case like a stadium, a concert or an opera house, where users can share their experience via Augmented RealityNirtual Reality (AR/VR) applications, a user is more interested in certain directions, i.e. seat views with very different angles from his/her own. In a similar manner, when it comes to public safety cases addressing emergency situations within such public venues, directionality of proximity services can become equally important to minimise any discovery latency, to ensure reliability of transmission and, more importantly, to achieve accurate situational awareness (e.g. by identifying critical areas for evacuation, or suitable non designated areas for assembly points via AR/VR assisted drones).

Figures la and lb shows two example cases of directional applications for both commercial and public safety usage.

Figure la shows a concert or sports stadium. Located at a relatively central location is a first user 10. An NCIS group may be formed with directionally diverse users 20 and 30 who are located at positions that offer them different viewpoints to each other. If these users wish to share images or video to create an AR/VR experience, then directional communication between them, as shown by the shaded beams 40 may be advantageous.

Figure lb shows a drone 100 operable in a public safety NCIS scenario. In this case the drone 100 wishes to communicate with a crowd 110 and an emergency vehicle 120. By use of directional beams 130 as shown, embodiments of the invention can offer advantages as will be 10 described.

Embodiments of the present invention provide enhanced support for a 5G System so that it can offer directional proximity-based services with one common architecture that can be used for both public safety and commercial related applications.

Embodiments of the invention provide novel methods, procedures, service flows and triggers related to how proximity-based services may be enhanced to support and leverage inherent directionally within some services.

Embodiments of the invention provide means whereby a 5G Core (5GC) can configure a UE or group of UEs for proximity services, based on the number of directions of interest and corresponding beam management support. The directions of interest are set relative to a given UE with respect to surrounding points of interest.

Figure 2 illustrates a first embodiment, relating to an application-driven User Configuration Update.

Figure 2, and the following figures, show various network functions/entities: whose functions and definitions are known in the art in at least: 3GPP TS 23.501, 3GPP IS 23.502 and 3GPP TS 23.503. The various known functions of these network functions/entities is varied/enhanced as set out in the following paragraphs.

For completeness, the various functions/entities shown are: User Equipment: UE, (Radio) Access Network: (R)AN, Access and Mobility Management Function: AMF, Session Management Function: SMF, User Plane Function: UPF, Policy Control Function: PCF, User Data Management: UDM, Unified Data Repository: UDR, Network Exposure Function: NEF, Application Function: AF.

Charging Function: CHF The inputs from directional proximity-based application (at AF-level) is provisioned to corresponding UEs as part of NR PC5 Policy parameters. In particular, directional proximity parameters may be optionally used as part of P05 QoS mapping configuration to set a tuple of (range, directions of interest) per UE (or set of UEs). This is in addition to standardized P05 5Q1s (POI) defined for ProSe communication over NR based P05.

S1 UE indicates Prose Support, with Beam Management (BM) capability during registration request to AMF.

S2-S6. If UE is authorised to use directional NCIS services, AMF selects the PCF (via NRF) which supports directional services and establishes a UE policy association with the PCF for Policy/Parameter delivery. PCF may store information like the Permanent Equipment Identifier (PEI) or the OS Id within UDR as part of "UE context policy control data". The PCF also subscribes to notification of the data modification in the UDR.

57. At AF level, NCIS (directional) group is created (or updated) with inputs of specific NCIS group identifier(s) and tuple of (range, directions of interest).

S8. The AF invokes a ServiceParameter_Create (or Update) operation through NEF providing the above parameters along any other NCIS group parameters.

S9-S10. The NEF stores the AF provided information in the UDR and responds to the AF request 511. The PCF receives the notification of data change from UDR (as already subscribed to).

S12. PCF creates a new UE policy container for UE access selection and PDU Session selection including authorised tuple of (discovery range, directions of interest). Then, it initiates policy provisioning via invoking N1N2MessageTransfer service provided by AMF. The AMF transfers transparently the UE Policy container to the corresponding UEs via Ni (DL NAS TRANSPORT message).

In the service flow of Figure 2, PCF role can be replaced with a newly defined ProSe Function within service-based 5GC that takes over the relevant service authorisation and policy updates roles. The ProSe Function may receive AF-level group creation (update) notifications either through UDR as outlined above or alternatively it may directly get updates from AF (via NEF).

Figure 3 illustrates a second embodiment, relating to an AMF-driven directional group policy update.

521. UE is already configured as part of a Directional Service Group (e.g. based on AF-driven procedure in Figure 2.

S22. AMF decides that a group policy update is needed based on a significant group topology change. AMF may rely on location reporting information through NG-RAN as covered in 3GPP 3A2, TS23.502 or other Location services (LCS) procedures through Gateway Mobile Location Centre (GMLC).

523. AMF invokes "UEPolicyControl_Update" service from PCF including any changes in tuple of (discovery range, directions of interest) based on group location updates.

524. The PCF generates a new UE policy container including modified tuple of (discovery range, directions of interest) and responds to AMF request.

525. The PCF may also update "UE context policy control data" within UDR.

S26. The PCF initiates another policy provisioning via invoking N1N2MessageTransfer service provided by AMF. The AMF transfers transparently the UE Policy container to the corresponding UEs via Ni (DL NAS TRANSPORT message).

In service flow of Figure 3, PCF role can be replaced with a newly defined ProSe Function within service-based 5GC that takes over the relevant service authorisation and policy updates roles. The ProSe Function may still update UDR as outlined above or alternatively it may only communicate with the AF (via NEF).

Figure 4 illustrates a third embodiment, relating to CHF-driven directional group policy update.

A given user can be linked to other users in directional proximity whist they reach their spending limit (implying that the network cannot support that target direction anymore). Unless the given user finds an alternative user(s) to link to within the direction(s) of interest, it may face a new group topology arrangement (as such direction(s) cannot be supported anymore).

Therefore, sending messages towards such direction(s) may become temporarily or permanently restricted.

531. UE is already configured as part of a Directional Service Group (e.g. based on AF-driven procedure Figure 2 532. PCF subscribes to CHF for spending limit reporting (i.e. to notifications of policy counter status changes).

S33. CHF decides that some UEs within NCIS Group have reached their spending limits.

S34. CHF notifies PCF on the UEs reaching the limit based on PCF subscription.

535. PCF decides on a group configuration update (e.g. to remove directions of interest with UEs already reaching the limits). PCF also generates a modified UE policy container including a limited tuple of (discovery range, directions of interest).

536. The PCF may also update "UE context policy control data" within UDR.

537. The PCF initiates another policy provisioning via invoking N1N2MessageTransfer service provided by AMF. The AMF transfers transparently the UE Policy container to the corresponding UEs via Ni (DL NAS TRANSPORT message).

In service flow of Figure 4, PCF role can be replaced with a newly defined ProSe Function within service-based 5GC that takes over the relevant service authorisation and policy updates roles. The ProSe Function may still update UDR as outlined above or alternatively it may only communicate with the AF (via NEF) At least some of the example embodiments described herein may be constructed, partially or wholly, using dedicated special-purpose hardware. Terms such as 'component', 'module' or unit used herein may include, but are not limited to, a hardware device, such as circuitry in the form of discrete or integrated components, a Field Programmable Gate Array (FPGA) or Application Specific Integrated Circuit (ASIC), which performs certain tasks or provides the associated functionality. In some embodiments, the described elements may be configured to reside on a tangible, persistent, addressable storage medium and may be configured to execute on one or more processors. These functional elements may in some embodiments include, by way of example, components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. Although the example embodiments have been described with reference to the components, modules and units discussed herein, such functional elements may be combined into fewer elements or separated into additional elements. Various combinations of optional features have been described herein, and it will be appreciated that described features may be combined in any suitable combination. In particular, the features of any one example embodiment may be combined with features of any other embodiment, as appropriate, except where such combinations are mutually exclusive. Throughout this specification, the term "comprising" or "comprises" means including the component(s) specified but not to the exclusion of the presence of others.

Attention is directed to all papers and documents which are filed concurrently with or previous to this specification in connection with this application and which are open to public inspection with this specification, and the contents of all such papers and documents are incorporated herein by reference.

All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and/or all of the steps of any method or process so disclosed, may be combined in any combination, except combinations where at least some of such features and/or steps are mutually exclusive.

Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise. Thus, unless expressly stated otherwise, each feature disclosed is one example only of a generic series of equivalent or similar features.

The invention is not restricted to the details of the foregoing embodiment(s). The invention extends to any novel one, or any novel combination, of the features disclosed in this specification (including any accompanying claims, abstract and drawings), or to any novel one, or any novel combination, of the steps of any method or process so disclosed.

Claims (9)

1. CLAIMS1. A method of configuring a group of User Equipments, UEs, for proximity services, wherein the UEs to form the group are selected according to a combination of proximity to each other and also according to a directional relationship between them.
2. 2. The method of claim 1 wherein a configuration update for the group of UEs is triggered due to a topology change observed within a Network Function of a telecommunication system within which the group of UEs is operating.
3. 3. The method of claim 1 wherein a configuration update for the group of UEs is triggered due to a change observed in group charging policy within a Network Function of a telecommunication system within which the group of UEs is operating.
4. 4. The method of claim 2 or 3 wherein the telecommunication system is a Fifth Generation system.
5. 5. The method of any preceding claim wherein the method further comprises the steps: Sl. A first UE indicates Prose Support, with Beam Management (BM) capability during registration request to AMF; S2-S6. If the first UE is authorised to use directional NCIS services, AMF selects the PCF (via NRF) which supports directional services and establishes a UE policy association with the PCF for Policy/Parameter delivery.S7. At AF level, NCIS (directional) group is created (or updated) with inputs of specific NCIS group identifier(s) and tuple of (range, directions of interest); 88. The AF invokes a ServiceParameter Create (or Update) operation through NEF providing the aforementioned parameters along with any other NCIS group parameters; S9-S10. The NEF stores the AF provided information in the UDR and responds to the AF request; S11. The PCF receives the notification of data change from UDR;. and S12. The PCF creates a new UE policy container for UE access selection and PDU Session selection including authorised tuple of (discovery range, directions of interest), and initiates policy provisioning via invoking N1N2MessageTransfer service provided by AMF and the AMF transfers transparently the UE Policy container to the corresponding UEs via Ni (DL NAS TRANSPORT message).
6. 6. The method of claim 5 wherein at steps S2-S6, the PCF stores information such as the Permanent Equipment Identifier (PEI) or the OS Id within UDR as part of "UE context policy control data"; and The PCF also subscribes to notification of the data modification in the UDR.
7. 7. The method of any of claims Ito 4 wherein the method further comprises the steps: 521. One of the group of UEs is already configured as part of a Directional Service Group, S22. AMF decides that a group policy update is needed based on a significant group topology change; S23. AMF invokes "UEPolicyControl_Update" service from PCF including any changes in tuple of (discovery range, directions of interest) based on group location updates; 524. The PCF generates a new UE policy container including modified tuple of (discovery range, directions of interest) and responds to AMF request; S25. The PCF updates "UE context policy control data" within UDR; and S26. The PCF initiates a policy provisioning via invoking N1N2MessageTransfer service provided by AMF and the AMF transfers transparently the UE Policy container to the corresponding UEs via Ni (DL NAS TRANSPORT message).
8. 8. The method of any of claims 1 to 4 wherein the method further comprises the steps of: S31. One of the group of UES is already configured as part of a Directional Service Group, S32. PCF subscribes to CHF for spending limit reporting; S33. CHF decides that some UEs within the Group have reached their spending limits; S34. CHF notifies PCF on the UEs reaching the limit based on PCF subscription; 535. PCF decides on a group configuration update and PCF also generates a modified UE policy container including a limited tuple of (discovery range, directions of interest); 536. The PCF updates "UE context policy control data" within UDR; and 537. The PCF initiates policy provisioning via invoking N1N2MessageTransfer service provided by AMF and the AMF transfers transparently the UE Policy container to the corresponding UEs via Ni (DL NAS TRANSPORT message).
9. 9. A telecommunication system comprising a network and at least two UEs operable to perform the method of any preceding step.