Relay selection in cellular slicing networks
Through network relay entities assist in selecting relay devices and slices, the complexity and security issues of relay device selection in 5G cellular communication systems are solved, and efficient and secure relay connections are achieved.
Patent Information
- Application Number
- CN202080049030.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-01-10
- Filing Date
- 2020-05-13
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2040-05-13
AI Technical Summary
In 5G cellular wireless communication systems, UE-based relay technology faces the challenge of selecting suitable relay devices and network slicing, especially in the issues of device mobility, resource constraints, security and trust. The prior art is difficult to effectively solve these problems. question.
Introducing a network relay entity (NRF) to assist in selecting relay devices, sending request messages to cellular communication systems, receiving response messages to determine the capabilities of available slicing and relay devices, optimizing relay selection process, and through security background and identification Ensure trustworthy connections.
Improve the efficiency and accuracy of relay device selection, ensure that mobile devices can obtain the best slicing support in 5G networks, reduce resource waste and security risks, and enhance trust evaluation and authorization management of relay devices.
Smart Images

Figure CN114128396B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the well-known field of cellular wireless communication systems (CCS), such as LTE, 4G or 5G networks. A cellular wireless communication system comprises a core network (CN) and a radio access network (RAN) comprising a plurality of cellular base stations (BS). A cellular communication system may provide a cellular network supporting network slicing and indirect connection, and a mobile device may be connected to the core network via a base station. The access network is managed by a so-called provider or mobile network operator (MNO). Network slicing uses a shared physical infrastructure of a cellular communication system to provide a logical network. An indirect connection provides data transmission between a mobile device and a cellular communication system via at least one relay device. Background Art
[0002] Mobile devices that communicate using cellular wireless communication standards (e.g., according to the 3GPP 5G specifications) are being developed. The wireless devices can be different types of devices, such as mobile phones, vehicles for vehicle-to-vehicle (V2V) or more generally vehicle-to-everything communication (V2X), Internet of Things (IoT) devices, medical (emergency) diagnostic and treatment devices, virtual reality (VR) headsets, etc. Because the characteristics of mobile devices such as the above devices vary greatly (e.g., in terms of low power operation, maximum latency tolerated, required bandwidth, and mobility), the 5G system and radio access network specifications define the concept of network slicing (see [23.501], [38.300], [Elayoubi]).
[0003] Network slicing can be viewed as an isolated "virtual 5G network" that runs on a common shared hardware / software platform, where platform components can be shared between multiple slices, but each slice still runs independently. Each slice can provide performance, service levels, policies and features that are optimally tailored for a specific use case or application area. Slices can also be run as a service by different network operators (rather than by the network operator that owns the hardware / software platform). Slicing can be done in the core network (CN), in the radio access network (RAN), or in both.
[0004] A mobile device, often referred to as User Equipment (UE), can be part of multiple slices at the same time. The UE can establish multiple Protocol Data Unit (PDU) sessions to the CN, each session running in a specific slice. Further explanation of network slicing can be found in [PavelShulgin]. The UE also covers the case where the UE is a fixed device. A user equipment can be any device that is directly used by the end user. This includes non-fixed devices and fixed devices. Another characteristic of the UE is that it usually communicates with the base station using the 3GPP Uu interface, and it usually has its own mobile subscription, its own SIM card and can be identified by the IMSI.
[0005] An example of requesting a session to run in a slice is discussed in [EventHelix]. Figure 1 shows an excerpt from a diagram showing a user equipment (UE) requesting a slice. The UE sends Requested Network Slice Selection Assistance Information (NSSAI) in the 21:RRCSetupComplete message, and the base station (gNB) forwards this information in the 24:NGAP Initial UE Message it sends. The term 5GC is used to refer to the 5G core network.
[0006] In the 3GPP specifications for 4G, Proximity Services (ProSe) functionality is defined (see [23.303] and [24.334]) to enable cellular user equipment (UE) that is temporarily out of the coverage of a cellular network base station (eNB) to connect. This particular functionality is called ProSe UE-to-network relay, or simply relay UE. A relay UE is a UE that helps another out-of-coverage (OoC) UE communicate with an eNB by relaying application and network traffic in both directions between the OoC UE and the eNB. Local communication between a relay UE and an OoC UE is called device-to-device (D2D) communication or sidelink (also known as PC5) communication (see [23.303] and [24.334]). Once the relay relationship is established, the OoC UE returns to the coverage via the relay UE and acts in the role of a "remote UE". This situation means that the remote UE has an indirect connection to the 4G core network, rather than a direct network connection, which is the normal situation.
[0007] Ongoing work in 3GPP (see [22.866]) extends the concept of single-hop relaying to support communications over multiple wireless hops and the use of relays for commercial / IoT application areas. Figure 2 shows an illustration of communication via a single hop (left) and multiple hops (right) using a UE-based relay device. Currently, ProSe (as shown in the left figure) only allows single-hop relaying to be provided to the network / gNB to enable remote UEs to have indirect connections to the eNB and 4G core network. The goal is to enable multi-hop relaying (as shown in the right figure), where UEs with relay capabilities can be connected to other UEs with relay capabilities.
[0008] Other work in 3GPP (see [23.733] and [36.746]) involves research on architectural enhancements. This research enables IoT devices (in the role of remote UEs) to operate at very low power by using relay UEs to connect to a wider network. Because the relay UEs are physically very close, this can be achieved using very low power transmissions. This work also includes improvements to the security, speed, and stability of ProSe. These improvements have not yet been implemented in 4G-based ProSe, but may be adopted in 5G-based ProSe.
[0009] In this document, the terms "eNB" (4G terminology) and "gNB" (5G terminology) mean a cellular base station. eNB / gNB is part of the radio access network RAN, which interfaces to functions in the core network CN. "OoC" means out of coverage. "Indirect connection" is the same as "indirect network connection" defined in [22.261]. The slice-specific 5G terms NSSAI, S-NSSAI, NSSF, etc. are as defined in [23.501]. "D2D" is device-to-device communication, and "PC5" is an interface for sidelink communication, as defined by ProSe [23.303], eProSe [36.746] or V2X [23.287].
[0010] Various conventional solutions involving relaying are known in the art and are related to 3GPP work (each number below is a separate topic):
[0011] US20180092017A1, US9826460, US10212651B2, US20160212721A1 describe selecting a relay from multiple candidate relays based on signal strength or advertising group ID;
[0012] US10177834B2 describes that an eNB broadcasts bandwidth requirements for relaying into its cells and that relay-capable devices automatically use this method to determine if they meet the requirements to become a relay;
[0013] US20160227518A1 describes that the eNB determines that the UE is OoC and needs to send some information to the UE (via a relay) to help it connect again;
[0014] US20160227518A1 describes a UE with relay capability, which becomes a relay only when it has sufficient connectivity or battery power or appropriate service type / context;
[0015] US9445352B2 describes an OoC UE that needs a relay, so it sends a D2D message to its neighbors to request a device to become a relay, at which point one or more UEs become relays;
[0016] WO2018083381A1 describes an OoC UE that asks a peer UE for certain configuration information via a sidelink / D2D, which needs to be connected back to the network via a relay;
[0017] US20180035448A1 describes an eNB that sends sidelink scheduling grant information with a specific schedule for OoC UEs; the information is received by UEs in coverage and retransmitted by these UEs to the OoC UEs;
[0018] US9565573B2 describes that a UE in coverage sends a D2D signal, to which the OoC UE can respond with an indication that it needs coverage. The UE in coverage then sends this received indication to the network. Optionally, the network can use this indication to instruct the UE in coverage to become a relay.
[0019] WO 2018129543 discloses a relay device which has been pre-configured to initiate a discovery procedure to serve as a relay for a remote WRTD. Summary of the invention
[0020] There is a need to include ProSe relay technology or similar technology for UE-based relaying to next-generation cellular communication networks (e.g., 5G). However, if UE-based relaying needs to be considered, the use of network slicing as introduced by 5G introduces new requirements and new challenges, such as the following case.
[0021] The UE needs to be able to connect to one or more of its required and / or preferred 5G network slice instances via a relay UE, so the UE needs to know which nearby relay UEs are able or unable to achieve this;
[0022] There may be multiple candidate relay UEs within the radio range of the UE, where the relay UE may move around and go out of range, and new relay UEs may appear in range;
[0023] The network slice instance required and / or preferred by the UE may be different from the slice(s) to which the best relay UE candidate is currently connected;
[0024] UE may be OoC when selection is required;
[0025] The relay UE may be a resource-constrained device and therefore may not be able to provide QoS as expected / required by a certain network slice;
[0026] The relay UE may have one or more PDU connections of its own (i.e., since it is typically a UE owned by someone else who wishes to access e.g. the Internet) and may have very limited resources to support indirect network communications for another UE;
[0027] The frequency band used by the network slice requested or preferred by the UE may be different from the frequency band currently used by the relay UE candidate;
[0028] A UE may participate in two or more network slices, each of which has its own unique requirements in terms of forming an optimal relay and corresponding network path for indirect connections, so two (or even more) relay UEs may need to be selected as the optimal solution for performing relaying;
[0029] Candidate relay UEs are often a priori unknown and untrusted to the UE - posing a mutual security risk as there is no initial trust between the parties and using an insecure process to connect to the relay UE also poses a security risk. For example, the UE with which the relay / remote relationship is to be initiated may have never been encountered before. This may often occur if, for example, 1) a mobile cellular IoT device is moving around or 2) a mobile or fixed cellular IoT device is being deployed and activated for the first time in a new environment.
[0030] The candidate relay UE may not be authorized and may not have the necessary credentials to connect to the network slice and / or send data to / receive data from the network slice and / or participate in a relay connection towards the network slice, in particular a private network slice that is only allowed to be used by UEs belonging to a predefined group.
[0031] Some of these considerations also apply to access to non-public networks (NPNs), see [23.501]. This concept has some similarities with network slicing, which has been introduced in 5G. An NPN is a dedicated network for a limited set of users and can operate as a separate mobile core network or on top of a public land mobile network (PLMN) of a mobile network operator, where the NPN is typically deployed as a slice and / or closed access group within the PLMN. In addition to the fact that the NPN is implemented on top of an existing hardware / software infrastructure using network slicing, the NPN may also have one or more slices of its own, especially in the case where the NPN is operated as a separate independent network. In a manner similar to slicing, the relaying of traffic destined for certain NPNs is also limited to remote UEs and relay UEs that are authorized to access the NPN. Moreover, the NPN may also have some requirements for minimum QoS and service area restrictions and other aspects similar to network slicing, and other dynamic aspects need to be considered to evaluate whether the relay UE is suitable to be used as a relay for data connections between remote UEs and the NPN. In the rest of this document, the term network slicing is also used to refer to non-public networks.
[0032] The object of the present invention is to provide an appropriate selection of a relay device in a cellular communication system using network slicing, which relay device is able to provide an indirect connection to the cellular communication system to a mobile device.
[0033] For this purpose, a device and a method as claimed in the accompanying claims are provided. According to one aspect of the present invention, a cellular communication system as claimed in claim 1 is provided. A mobile device as claimed in claim 12 is provided. According to a further aspect of the present invention, a relay device as claimed in claim 13 and a network relay entity as claimed in claim 14 are provided. According to a further aspect of the present invention, methods as claimed in claims 15, 16 and 17 are provided. According to a further aspect of the present invention, a computer program product is provided, which can be downloaded from a network and / or stored on a computer-readable medium and / or a microprocessor-executable medium, the product comprising program code instructions for implementing the above method when the program code instructions are executed on a computer.
[0034] The cellular communication system (CCS) includes a radio access network (RAN) and a core network (CN), the radio access network including a plurality of cellular base stations (BS). The cellular communication system provides a cellular network supporting network slicing and indirect connections, each network slice using a shared physical infrastructure of the cellular communication system to provide a logical network, each indirect connection providing data transmission between a mobile device and the cellular communication system via at least one relay device, the at least one relay device being a mobile device arranged to communicate with the radio access network and capable of supporting the indirect connection. The cellular communication system includes at least one network relay entity, the at least one network relay entity being arranged to provide a network relay function (NRF) for managing the indirect connection.
[0035] The mobile device comprises: a transceiver arranged for wireless communication in the cellular network; and a connection processor arranged for managing a connection with the cellular network, the connection processor providing a relay function (116) for managing at least one indirect connection. The relay function may be arranged to perform the following operations:
[0036] Initiating an indirect connection procedure by sending a request message (M) to at least one relay device (UEx), the request message comprising a request identifier (ID1), the request identifier indicating the network slice to which the mobile device is requesting access;
[0037] receiving at least one response message (N) from at least one relay device, the response message optionally including an indication of at least one available slice for relaying via at least one relay device to provide an indirect connection (e.g., slice relay information), the indication being either explicit (e.g., as part of an additional "slice relay information" field in the response message N) or implicit (e.g., the message N is a confirmation that the requested slice can be relayed via the corresponding relay device);
[0038] selecting a relay device (UEy) from the at least one relay device according to the response message; and
[0039] The indirect connection is joined to the requested slice via the selected relay device.
[0040] The relay device comprises: a communication unit arranged for communication in the cellular network; and a relay processor arranged for managing the communication in the cellular network and for managing an indirect connection between the mobile device and the cellular network. The relay processor may be arranged to perform the following operations:
[0041] receiving the request message (M) from the mobile device;
[0042] sending a transmission request message (M') to the cellular communication system according to the request message, the transmission request message indicating a request from the mobile device to communicate with the requested slice via an indirect connection, and the transmission request message including an identifier (ID1) of the request;
[0043] receiving a transmission response message (N') from said cellular communication system;
[0044] The response message (N) is sent to the mobile device according to the transmission response message.
[0045] The network relay function may be arranged to perform the following operations:
[0046] Receiving at least one transmission request message (M') via at least one cellular base station, including sending, by the relay device, the transmission request message (M') in response to the request message (M);
[0047] obtaining relay capability data about a relay device capable of data transmission to and from the mobile device for at least one available slice, the available slice being determined based on an identifier (ID1) of the request; and
[0048] At least one transmission response message (N') is sent via at least one cellular base station, the transmission response message including network relay information indicating at least one relay device capable of transmitting data of the network slice to which the mobile device is requesting access.
[0049] Receiving a transmission request message via a base station may mean that the base station may be the initiator of sending a new message to a network relay function that encapsulates information contained in a message M' sent by the relay device. Similarly, sending a transmission response message (N') via at least one cellular base station may mean that the base station may terminate a message from the network relay function and encapsulate the message in a new message (N), which is then sent to the relay device.
[0050] Advantageously, cellular networks are able to assist mobile devices (e.g., 5G UEs) that require relays — in order to send messages to / receive messages from the network (e.g., devices that are out of coverage, have a poor signal to a nearby base station, or are very low on battery) — by allowing these devices to initiate communications via a selected relay device that optimally supports the network slice or set of network slices that the UE needs to use.
[0051] Additionally, the requested identifier may include a connection context identifier (CCI).
[0052] The enhanced relay selection also performs RAN attach faster and more efficiently than a trial and error approach where the UE simply tries to set up a connection to the requested slice through each of the candidate relay UEs, then performs a CN attach / authentication, and then only learns if the selected relay is actually good enough or is not allowed to connect to its desired slice(s). If not, it can try a second relay candidate, however, in this way the selection of the best relay remains unknown until all candidates have been tried. This process can be long and wasteful of RF / energy resources.
[0053] In addition, the enhanced relay device selection done with the assistance of NRF will be better than the relay device selected locally by the UE because the NRF is able to use more information for selection. This information can be, for example, knowledge of the connection quality of potential relay devices (towards the gNB or towards other relay devices), historical QoS performance of potential relay devices, and knowledge about the characteristics of each slice being requested, etc. It may also have information related to roaming, such as the mobile device may be an inbound roaming device, and the relay device may not have knowledge about such a roaming device. So in summary, the new cellular communication network is able to apply complex and / or dynamic and / or slice-dependent and / or non-public network-dependent strategies to the relay device selection process.
[0054] Additionally, enhanced relay device selection performed with the assistance of NRF also allows for the use of the latest information required to make a good assessment of whether the relay device can meet the requirements of the slice (including the use of dynamic aspects, such as how much resources are left on the relay device and the network to handle the additional traffic from the mobile device, the signal strength between the mobile device and the relay device, and the signal strength between the relay device and the network, the current location and / or tracking / service area of the relay device and the mobile device, and the number of hops between the mobile device and the network in the case of multiple hops). Because it is able to use the latest information, the enhanced relay device selection performed with NRF also benefits mobile devices (and relay devices) that may have been out of coverage (OoC) or dormant for a period of time, particularly when the mobile device is outside the direct coverage of the base station when it wishes to discover and connect to the relay device. While some solutions based on ProSe discovery first require the mobile device and relay device to request permission from the network and retrieve the required information before they can start discovering or connecting to the relay device, and if the mobile device has been out of coverage for a period of time, the mobile device and relay device may therefore use outdated information, by using enhanced relay device selection with the assistance of NRF, the mobile device can (for example, using the normal discovery and connection request mechanism described in further detail below) always initiate a request for a specific network slice, at which time even if the relay device has no information about the requested network slice, it can request the NRF to evaluate whether the relay device is authorized (or can be authorized) and whether it can (or (for example, by reconfiguring the PDU session or starting an additional PDU session) enable) perform relaying of data to / from the requested network slice or a non-public network.
[0055] Additionally, information about slices and non-public networks may be considered privacy sensitive information. It may cause unwanted tracking of mobile devices as well as expose the operator's deployment information (e.g., which slices and NPNs are supported by the core network). Therefore, by using NRF, non-essential information does not need to be stored in the relay UE, which is usually an untrusted end-user device.
[0056] Existing techniques (including 3GPP specifications) do not address these issues because network slice information is not conveyed in the system information blocks (e.g., MIB and SIB in [38.331]) that the base station is broadcasting to UEs in coverage (and which reaches the OoC UE via the ProSe-based relay UE). Furthermore, in 5G, to prevent privacy leakage of slice information, slice information may only be sent to the UE later in the CN attach / authentication process, after some initial security context is in place, so that slice information is not sent earlier in the process (or only encrypted or temporary slice information is sent). Furthermore, the relay UE may not be able to access, is not authorized to access, or may not be able to support the characteristics of the slice that the remote UE wants to use (e.g., the required QoS or frequency band).
[0057] Moreover, selecting a relay device based solely on whether the relay device is part of the same slice does not work effectively, for example because if the 5G network supports a certain slice for a given relay device R, this does not imply that a remote UE or other relay device connected to relay device R can also use this slice. This may not be the case, for example because a specific slice is dedicated to ultra-reliable low latency communication (URLLC), and the extra "hop" via the relay device conflicts with the low latency properties of the URLLC slice. Therefore, it may be the case that the relay device should not provide such a slice at all. In addition, the decision whether a certain relay device can relay data traffic for a specific slice must be based on the latest information, and the above situation may still work effectively if the mobile device (and the relay device) is out of coverage or has been dormant for a period of time.
[0058] The method according to the present invention can be implemented on a computer as a computer-implemented method, or implemented in dedicated hardware, or implemented in a combination of the two. The executable code of the method according to the present invention can be stored on a computer program product. Examples of computer program products include memory (e.g., memory stick), optical storage device (e.g., CD), integrated circuit, server, online software, etc.
[0059] A computer program product in non-transient form may include a non-transient program code unit stored on a computer-readable medium, and when the program product is run on a computer, the non-transient program code unit is used to perform the method according to the present invention. In an embodiment, the computer program includes a computer program code unit, and when the computer program is run on a computer, the computer program code unit is suitable for performing all steps or stages of the method according to the present invention. Preferably, the computer program is embodied on a computer-readable medium. A computer program product in transient form is also provided, the computer program product can be downloaded from a network and / or stored in a volatile computer-readable memory and / or a microprocessor executable medium, the product including program code instructions, and the program code instructions are used to implement the method as described above when run on a computer.
[0060] Another aspect of the invention provides a method of making a computer program available for download in transient form. The content of this aspect is used when the computer program is uploaded to Apple's App Store, Google's Play Store or Microsoft's Windows Store and when the computer program is available for download from such stores.
[0061] Further preferred embodiments of the device and the method according to the invention are given in the dependent claims, the disclosure content of which is incorporated herein by reference.
[0062] In one aspect, the request message (M) comprises a plurality of requested identifiers (IDx), and wherein, if the requested identifiers are configured in a relay device, the relay device excludes any of the requested identifiers from the transmission request message (M').
[0063] In one aspect, the identifier (ID1) of the request indicates a general network slice to which the mobile device (110) is requesting access, and the request message (M) further includes an identifier (ID2) of a second request, the identifier of the second request indicating a specific network slice to which the mobile device (110) is requesting access, and wherein the relay device performs one of the following operations:
[0064] sending, as part of the transmission request message (M'), an identifier (ID2) of the second request for the specific network slice instead of sending the general slice identifier (ID1);
[0065] Both the identifier of the second request for the specific network slice and the common slice identifier are sent as part of the transmission request message (M'), and wherein the response message (N) only includes the identifier (ID2) of the second request for the specific network slice, and does not include the identifier (ID1) of the request for the common network slice.
[0066] In one aspect, the request message (M) includes a security context identifier (ID3) indicating a security context or a security key, and the relay processor is arranged to: send the transmission request message (M') to the cellular communication system according to the request message only when the security context or security key indicated by the security context identifier (ID3) corresponds to the security context or security key configured in the relay device; and if there is no match, not send the transmission request message (M').
[0067] In one aspect, the indirect connection to the requested slice is set up on the same logical data connection as the logical data connection via which the request message (M) and the response message (N) are sent, and the logical data connection is at least one of a PC5 connection, a side link connection or a D2D connection.
[0068] In one aspect, the NRF uses the requested identifier (ID1) to retrieve a set of PDU session parameters including a network slice identifier, and the NFR configures the PDU session of the relay device and / or the mobile device based on at least one parameter in the retrieved set of PDU session parameters.
[0069] In one aspect, the NRF uses the identifier (ID1) of the request to retrieve a set of PDU session parameters including an identifier referring to a non-public network, the NRF configures the PDU session of the relay device to connect to a cellular base station (BS), the cellular base station is configured to broadcast the identifier referring to the non-public network as part of its system information, and / or the cellular base station is configured to report the identifier referring to the non-public network to the core network (CN) when the relay device is directly connected to the cellular base station or the mobile device is indirectly connected to the cellular base station via the relay device.
[0070] In one aspect, the NRF uses the requested identifier (ID1) to contact a different Public Mobile Land Network (PLMN) to retrieve a set of PDU session parameters including a network slice identifier.
[0071] In one aspect, the transmission response message (N') includes network relay information indicating a set (T) of relay devices; and / or the response message (N) includes the set (T) of relay devices.
[0072] In one aspect, the network relay entity is arranged to: determine that there is no relay device capable of transmitting data to and from the mobile device that is capable of transmitting slices that accommodate the requested identifier; and when it is determined that this is the case, send a slice denial message to the relay device and / or the mobile device, wherein the slice denial message indicates that there is no relay device capable of transmitting data for slices that accommodate the requested identifier.
[0073] In one aspect, the network relay entity is arranged to: determine that the indirect connection engaged from the mobile device via the selected relay device is addressed to the requested slice; and if the indirect connection is addressed to a different slice, perform one or more of the following actions:
[0074] sending a PDU session reject message to the remote UE via the indirect network connection;
[0075] Sending a slice denial message to the relay device and / or the mobile device;
[0076] Reconfigure the relay UE;
[0077] Terminates the relay connection.
[0078] In one aspect, the connection processor in the mobile device is arranged to:
[0079] Starts the relay discovery process and engages the initial indirect connection, and then
[0080] sending the request message via the initial indirect connection; and
[0081] Therein, the network relay entity (140) or the relay function is arranged to reconfigure the initial indirect connection so that the indirect connection goes to the selected slice via the selected relay device.
[0082] In one aspect, the relay processor in the relay device is arranged to perform the following operations:
[0083] A preliminary response message (N**) is sent to the mobile device according to the request message (M); the preliminary response message indicates that the relay device exists, but according to the transmission response message (N'), the response message (N) will be sent later based on the network relay information.
[0084] In one aspect, the identifier of the request includes a set of requested network slices, and wherein the network relay entity (140) is arranged to determine at least one subset of the available slices that accommodates the requested network slices and at least one relay device capable of transmitting data of the subset of available slices, and / or the response message (N) contains the determined subset of available slices, at which time the mobile device selects one of the available slices to be indirectly connected to the selected slice via the relay device from which the mobile device receives the response message (N).
[0085] In one aspect, the network relay entity (140) is arranged to determine additional relay capability data about at least one relay device, the additional relay capability data indicating a preference or suitability to act as a relay;
[0086] The transmission response message (N') includes the additional relay capability data in the network relay information; and / or
[0087] Said response message (N) comprises at least part of said additional relay capability data.
[0088] In one aspect, the network relay entity (140) is arranged to perform the following operations:
[0089] determining multi-hop relay capability data for at least one multi-hop indirect connection implemented via a plurality of hops using a plurality of relay devices, the multi-hop relay capability data indicating available slices via the multi-hop indirect connection;
[0090] The transmission response message (N') includes the multi-hop relay capability data in the network relay information; and / or
[0091] The response message (N) comprises at least part of the multi-hop relay capability data; or wherein the network relay entity (140) is arranged to perform the following operations:
[0092] determining the available relay devices for the requested slice based on an achievable QoS; or
[0093] Determine which relay devices to use first based on the attributes or requirements of the corresponding slices.
[0094] In one aspect, the request message includes one or more of the following:
[0095] security information about security credentials or a security context in which the mobile device operates or is required to operate for the indirect connection, or about an identifier associated with the request;
[0096] Status information indicating the reason for requesting relay;
[0097] Received signal strength of messages received from nearby devices;
[0098] The device includes power information about a power source of the mobile device.
[0099] In one aspect, the network relay entity (140) is arranged to obtain metadata from the cellular communication system, such as received signal strength, signal quality or distance estimation results; or, wherein the transmission request message includes metadata identifying the current connection status, such as the mode of network connection, quality of service (QoS) and number of hops, connection stability information and / or the frequency band in use or the supported frequency band of the relay device, and wherein the network relay entity (140) is arranged to determine the transmission response message based on the metadata.
[0100] A method for use in the cellular communication system is provided, the method comprising steps of performing the relay function in the mobile device, the steps comprising:
[0101] managing at least one indirect connection;
[0102] Sending a request message (M) to at least one relay device (UEx) to initiate an indirect connection procedure, the request message comprising a request identifier (ID1), the request identifier indicating a network slice that the mobile device (110) is requesting to access;
[0103] receiving at least one response message (N) from at least one relay device, the response message indicating at least one available slice for relaying via at least one relay device to provide an indirect connection;
[0104] selecting a relay device (UEy) from the at least one relay device according to the response message; and
[0105] The indirect connection is joined to the requested slice via the selected relay device.
[0106] In one aspect, the method comprises the steps of performing the relay function in the relay device, the steps comprising:
[0107] managing said communications in said cellular network;
[0108] managing an indirect connection between the mobile device and the cellular network;
[0109] receiving the request message (M) from the mobile device;
[0110] sending a transmission request message (M') to the cellular communication system according to the request message, the transmission request message indicating a request from the mobile device to communicate with the requested slice via an indirect connection, and the transmission request message including an identifier (ID1) of the request;
[0111] receiving a transmission response message (N') from said cellular communication system;
[0112] The response message (N) is sent to the mobile device according to the transmission response message.
[0113] In one aspect, the method comprises the steps of performing the network relay function in the network, the steps comprising:
[0114] receiving, via at least one cellular base station, at least one transmission request message (M'), the transmission request message comprising an identifier (ID1) indicating a request for a network slice to which a mobile device (110) is requesting access, wherein the relay device has sent the transmission request message (M') in response to receiving the request message (M) at the relay device, the mobile device sending the request message to initiate an indirect connection procedure;
[0115] obtaining relay capability data about a relay device capable of data transmission to and from the mobile device for at least one available slice, the available slice being determined based on an identifier (ID1) of the request; and
[0116] At least one transmission response message (N') is sent via at least one cellular base station, wherein the transmission response message including network relay information indicates at least one available slice and at least one relay device, and the at least one relay device is capable of transmitting data of the available slice.
[0117] A computer program product is also provided, which can be downloaded from a network and / or stored on a computer-readable medium and / or a microprocessor-executable medium, the product comprising program code instructions for implementing the method as disclosed herein when the program code instructions are executed on a computing device. BRIEF DESCRIPTION OF THE DRAWINGS
[0118] These and other aspects of the invention will be apparent from and elucidated with reference to the embodiments described hereinafter by way of example and with reference to the accompanying drawings, in which:
[0119] FIG1 shows an extract from a diagram showing a user equipment (UE) requesting a slice,
[0120] FIG. 2 shows a diagram of communication using a UE-based relay device via a single hop (left) and multiple hops (right),
[0121] Figure 3 A mobile device and a relay device and a network relay entity and a cellular communication network are shown,
[0122] Figure 4 shows an example of an NRF-assisted relay selection sequence chart,
[0123] Figure 5 shows an example multi-hop relay topology for a mobile UE,
[0124] Figure 6a A computer readable medium is shown, and
[0125] Figure 6b A schematic representation of a processor system is shown.
[0126] The accompanying drawings are purely diagrammatic and not drawn to scale.In the accompanying drawings, elements corresponding to elements already described may have the same reference numerals.
[0127] Figure 7 An example of an NRF-assisted relay selection sequence according to an embodiment is shown. DETAILED DESCRIPTION
[0128] Figure 3 A mobile device and a relay device and a network relay entity and a cellular communication network are shown. In the cellular communication system 100, the mobile device 110 is arranged for wireless communication in the cellular communication network 130. The mobile device can be, for example, a mobile phone, a wearable medical device, or a data communication unit embedded in a car. A cellular communication system (CCS) may include a radio access network (RAN) and a core network (CN), wherein the radio access network includes multiple cellular base stations (BS). The cellular communication system provides a cellular network that supports network slicing and indirect connections.
[0129] Each network slice uses the shared physical infrastructure of the cellular communication system to provide a logical network. This is also generally the case for non-public networks (NPNs), especially for NPNs that run on public networks. In the case of independent NPNs, the logical network can also be deployed as a separate mobile core network, and a private small cell infrastructure can be run. Sharing means that the physical infrastructure can be shared in full or in part. For example, some network functions of the first slice or NPN may be software running on other computers different from the network functions of the second slice or NPN, and the RAN components can be fully shared between the two slices or between the two NPNs. Moreover, the first slice or NPN may be assigned to a frequency band different from the second slice or NPN, and the RAN components may be fully shared. Each indirect connection provides data transmission between a mobile device and a cellular communication system via at least one relay device. Another typical feature of network slicing is that network traffic associated with the slice is isolated from other network traffic. Independent NPNs also have the above situation.
[0130] As explained in the introduction, the cellular communication network may be an enhanced 5G network. Figure 1 schematically shows a network 130 for providing communication between a mobile device MOB-DEV 110 and a relay device REL-DEV 120. The core network may be managed by at least one telecommunication provider (e.g. for managing subscription databases and invoicing).
[0131] The network may also be coupled to a network relay entity 140, which provides a network relay function (NRF) for managing indirect connections. The network relay entity may be implemented on a processor system, for example provided at the core network, in a radio access network or on a separate server on the Internet. The entity may be coupled to the network in a wireless and / or wired manner or via a dedicated link.
[0132] A relay device may be a mobile device for communicating with a radio access network and capable of supporting indirect connections for data transfer to and from the mobile device. Note that the NRF manages the difference in the multiple indirect connections mentioned above. The NRF may manage the indirect connections of 1000 UEs, while the relay device only manages the indirect connection(s) of the mobile devices in its vicinity.
[0133] The mobile device 110 may be arranged to communicate wirelessly with a network and has a transceiver 111 arranged for wireless communication, and a connection processor 112 is arranged to control the mobile device and provide an interface to a user. The connection processor may be arranged to manage a connection with a cellular network and provide a relay function 116 for managing at least one indirect connection explained below. The mobile device may be provided with a user interface 113, which may include, for example, a display and one or more user input elements 115. For example, the user input element may include one or more of a touch screen, various buttons, a mouse or a touch pad, etc. The button may be a traditional physical button, a touch sensor, or a virtual button (e.g., a virtual button on a touch screen or an icon to be activated via a mouse). The user interface may also be a remote user interface.
[0134] The relay device 120 has a relay processor 122 arranged for managing communications in a cellular network and for managing indirect connections with mobile devices as explained below, and a communication unit 121 arranged for wireless communications with the network.
[0135] In a mobile device, a relay function may be arranged to perform the following operations. First, a request message (M) is sent to at least one relay device (UEx). The request message may include an identifier (ID1) indicating a request for a network slice that the mobile device is requesting access to. Next, at least one response message (N) is received from at least one relay device. The response message may include an indication of at least one available slice for relaying via at least one relay device to provide an indirect connection. The indication may be defined explicitly (e.g., as part of an additional "slice relay information" field in the response message N), or implicitly (e.g., message N is a confirmation that the requested slice can be relayed via the corresponding relay device). Then, based on the response message, a relay device (UEy) is selected from at least one relay device that supports the requested slice. The response message may also include information about additional slices that can be supported that the remote UE can select from. If the remote UE is limited to only a single (e.g., private) slice or if only one available slice is suitable for the UE, the selection is to effectively take the single slice. If the selected slice is the same as the requested slice, the remote UE may select the corresponding relay UE from which the response was received, and the same device-to-device (D2D) connection (e.g., PC5) between the remote UE and the relay UE may be reused for setting up an indirect connection to the network via the relay UE. If there is only a single available relay UE suitable for the remote UE, the selection is effectively to take such a single relay UE. The indirect connection is then joined to the selected slice via the selected relay UE, and the selected relay UE may reuse the same D2D connection between the remote UE and the relay UE for sending the request message (M) and / or receiving the response message (N).
[0136] In the relay device, the relay processor can be arranged to perform the following operations. First, a request message (M) is received from a mobile device. Then, a transmission request message (M') is sent to the cellular communication system according to the request message. The transmission request message indicates a request for data transmission to and from the mobile device via an indirect connection. The transmission request message includes an identifier (ID1) of the request. The transmission request message can be the same as the message M, or it can be a message newly constructed by the relay device based on the information received in the message M, or it can be a message that encapsulates the content of the message M (for example, as part of an IPSec tunnel, or by adding / changing some routing headers) or a variant thereof. The identifier sent as part of the transmission request message (M') can be a copy of the identifier (ID1) of the request, or it can be an encrypted, encoded, hashed and / or snatched ID1, or it can be a one-to-one mapped replacement identifier.
[0137] Then, a transmission response message (N') is received from the cellular communication system, which message is explained below. Then, a response message (N) is sent to the mobile device based on the transmission response message.
[0138] In the network relay entity, a network relay function (NRF) is arranged to perform the following operations. First, at least one transmission request message (M') is received via at least one cellular base station. Then, relay capability data about the relay device for at least one available slice capable of data transmission to and from the mobile device is obtained. (One or more) available slices are determined according to the identifier (ID1) of the request. Next, at least one transmission response message (N') is sent via at least one cellular base station. The transmission response message includes network relay information, which indicates at least one available slice and at least one relay device capable of transmitting data of the available slice.
[0139] Optionally, in the network relay information, the transmission response message (N') includes a set of relay devices (T). Also, or alternatively, (e.g., in the slice relay information field,) the response message (N) includes a set of relay devices (T). For example, the set of relay devices may be an ordered list of available relay devices, e.g., an ordered list by preference level or suitability.
[0140] Optionally, the corresponding transmission response message may be directed only to one specific relay device, and the response message may indicate the relay device itself as a relay device. Such a message may only implicitly indicate the relay device. Therefore, the message may not explicitly indicate the relay device with some "relay ID" or similar message element. Alternatively, the message may, for example, only include the network address of a specific relay as the destination address in the message header. The relay device may be implicitly indicated by the destination address of the relay (for example, in the case of the transmission response message (N')), or by the source address of the relay (for example, in the case of the response message (N)). For example, a use case may have 3 relay devices a, b, c, each of which responds to the broadcast of the mobile device with information about their own (one or more) slices that they can support to the mobile device. Then the message N does not need to list any relay (capable) devices, because each relay (a / b / c) answers on its own behalf. In this case, in the message format, the identity of relay (a / b / c) can only be found in the standard "source" field (e.g., MAC source address) in the message header. The identity of relay (a / b / c) may not be present in higher-level messages, or the identity of relay (a / b / c) may indicate itself. The mobile device selects a relay device from the relay devices that received the corresponding response message, and engages the indirect connection via the selected relay device.
[0141] Optionally, the corresponding transport response message includes instructions for various actions. There may be instructions to reconfigure an existing PDU session between the relay device and the network to accommodate relay network traffic for a specific slice (e.g., change DNN, connect to a different user plane function), update UE configuration (possibly including information such as different S-NSSAI information, different policy information, different credentials), which will trigger the device to reconnect to the network by breaking the existing PDU session and setting up a new PDU session, which will cause a different access and mobility management function (AMF) to be selected to serve the network slice. The transport response message may include instructions for initiating an additional PDU session with the network in case the relay UE is already serving other remote UEs, and the transport response message may also include instructions for connecting to a different PLMN / NPN. The transport response message may also include instructions to reside on a specific cell associated with a closed access group (CAG) ID to access the slice, particularly in the case of an NPN operating on a public network.
[0142] Optionally, the corresponding transmission response message includes instructions / information about resource scheduling requirements of base stations based on available slices in the network relay information (e.g., related to characteristics, QoS flows, minimum / maximum / preferred bit rates, priorities, frequency bands, bandwidths, resource partitioning between different slices), which the base station is using to schedule sidelink resources for mobile devices and available relay devices or selected relay devices for communication with available or selected slices. Alternatively, instructions / information about base station resource scheduling requirements of base stations based on available slices can be sent as a separate message from the NRF to the base station (or nearby base station) via the AMF in a direct manner or in a routed / tunneled manner.
[0143] Optionally, the corresponding transmission response message may include some configuration update information or authorization update information or policy update information for the remote UE that has been out of coverage for a period of time. The relay UE may forward the information to the remote UE using a response message N. The information may be encrypted using security credentials known only to the remote UE to prevent the information from being exposed to the relay UE.
[0144] In a detailed embodiment, a cellular communication system involves a mobile device UE0 operating as a cellular communication user equipment, a set of relay devices S{UE1,...,UEn} (n>=1) operating as a cellular communication user equipment and also capable of relaying network traffic from UE0 to a cellular communication system CC capable of supporting relay operations and network slicing / network traffic from a cellular communication system CC capable of supporting relay operations and network slicing to UE0.
[0145] The device UE0 may operate as follows.
[0146] The device UE0 sends a message M to a relay device UEx of the set S. The message includes an identifier, which may be a network slice identifier ID1 to which the device UE0 is requesting access. ID1 may be an S-NSSAI (as defined in 3GPP [24.501]), optionally part of a set of slice identifiers. Alternatively, the message may include a temporary slice identifier (complete or as a hash value) (as defined in 3GPP [33.813]) or an encrypted slice identifier (as defined in 3GPP [33.813]). Note that in this case it would be convenient for the core network to keep a list of previous temporary identifiers to see if there is a match, as the remote UE may have been out of coverage for some time and the temporary identifier may no longer be up to date. Alternatively, the message may include a combination of a PLMN and a network identifier (NID) or a CAG ID to refer to the slice, particularly in the case of an NPN. The message may include any other type of identifier (for example, an identifier pre-configured in the UE, or an identifier that is updated periodically at registration or after registration, or an identifier that can be derived from a derivation function or mapping table that can be uniquely pre-configured for each UE), based on which the NRF (for example, AMF / NSSF / ProSe function or other network function) or relay device Ux is able to derive (for example, using a hash table or other type of mapping function) which slice the device UE0 requests.
[0147] The message M may be, for example, a D2D / PC5 discovery message (as defined in 3GPP [23.303]) having an additional information element to indicate the requested network slice identifier, or the message M may be, for example, a PC5 direct communication request (as defined in 3GPP [23.287]) having an additional information element to indicate the requested network slice identifier, or the message M may be a PDU session establishment request (as defined in 3GPP [24.501]) having an additional information element to indicate the requested network slice identifier, or the message M may be, for example, a registration request (as defined in 3GPP [24.501]) using the existing “Requested NSSAI” attribute, or the message M may be, for example, a UL NAS request (as defined in 3GPP [24.501]) using the existing “S-NSSAI” attribute. TRANSPORT, or message M may be, for example, another type of PC5 / NAS / RRC message having an additional information element to indicate the requested network slice identifier.
[0148] Device UE0 receives a message N from device UEx. In one embodiment, the message includes a network slice identifier ID2, for example as part of an additional slice relay information field. ID2 may be the same as ID1 or an instance identifier or an allowed slice identifier or a default slice identifier. In another embodiment, message N may include a subset S' of a set S that UE0 is allowed or not allowed or prefers to use to set up an indirect connection session with a network slice of a cellular communication system CCS identified by ID2. In another embodiment, message N includes a Boolean value or a set of Boolean values indicating support for a set of requested and / or supported slices. In yet another embodiment, message N is a confirmation that a match has been found between the requested slice and a list of slice IDs to which the mobile device can connect via an eRelay UE. In a further embodiment, message N may only be sent if the relay device UEx is able to act as a relay for an indirect communication session for device UE0 within the requested network slice. Message N may be formatted, for example, as a D2D / PC5 discovery response message (as defined in 3GPP [23.303]), or a PC5 direct communication accept message (as defined in 3GPP [23.287]), or a PDU session establishment accept message (as defined in 3GPP [24.501]), or a registration accept message (as defined in 3GPP [24.501]), or a DL NAS TRANSPORT using the existing "S-NSSAI" attribute (as defined in 3GPP [24.501]), or other types of PC5 / NAS / RRC messages.
[0149] The device UE0 selects a relay device UEy from the set S for communicating with the cellular communication system CCS. UEy may be different from UEx if it is not allowed or preferred to use the device UEx to set up an indirect connection to the requested network slice.
[0150] Note that, optionally, the relay UE may reply via message N on its own, e.g. based on pre-configured information from the NRF that it is able to serve a certain slice, e.g. because it is part of the same slice, has the same security context, and has sufficient resources to act as a relay for the remote UE. This option may also work for a default slice, e.g. operating in the same PLMN, and for relays operating in private slices, e.g. operated and configured by the same third party to be part of the same group, or belonging to a special group of devices (e.g. public security UEs). Optionally, the NRF may pre-configure the relay UE for a set of slices (e.g. default slices and / or specific private slices in which the relay UE is able to operate), and optionally for relevant policy rules, e.g. when the relay UE is authorized, enabled or obtains resources to reply to the relay discovery message. This may be done, for example, by pre-sending a message containing the pre-configured slice relay information to the relay UE.
[0151] The relay device UEx (1<=x<=n) may operate as follows.
[0152] Device UEx receives a message M from device UE0, which includes the network slice identifier ID1 that device UE0 is requesting to access.
[0153] The device UEx sends a message M' based at least in part on the message M to the cellular communication system CCS in a direct manner or via one or more other relay devices UEy (1<=y<=n).
[0154] The device UEx receives a message N' from a cellular communication system CCS, which includes: a network slice identifier ID2 and a subset S' of the set S that UE0 is allowed or not allowed or prefers to use to set up a relay connection session with the network slice of the cellular communication system CCS identified by ID2.
[0155] The device UEx sends the message N to the device UE0 based at least in part on the message N′.
[0156] The message M' may be, for example, a ProSe matching report (as defined in 3GPP [24.334]), or the message M' may be, for example, another message on a PC3 interface with (some or some) additional field to indicate information about the slices requested by UE0, or the message M' may be, for example, a NAS message (as defined in 3GPP [24.501]) with (some or some) additional field to indicate information about the slices requested by UE0. In the case of layer 2 relay, the message M' may be a received PDCP frame containing a NAS message received from device UE0, which is transparently forwarded by the relay device UEx to the base station / core network via its Uu interface (or to subsequent relay devices via other PC5 interfaces). It may also be a new dedicated NAS or RRC message (e.g., a relay request message) containing the required information about the slices requested by UE0.
[0157] In a cellular communication system CCS, a relay device UEx can be communicatively coupled via base stations BS of multiple cellular base stations of the RAN. In the CCS, a network relay function (NRF) is provided. The base station can be communicatively coupled to an access and mobility management function (AMF) in the CN. The core network can host multiple access and mobility management functions assigned to different slices. The base station can select an appropriate AMF based on the requested slice identifier ID1 received in the message M'.
[0158] The base station BS is capable of receiving a message M' from (one or more) relay devices UEx, and can forward the message to the NRF or AMF, generate a new message to the NRF or AMF based on the received message, or interpret the message M' via the NRF (e.g., through a built-in NRF). The forwarded message may be a NAS message. The new message may be, for example, an initial registration message, a UE context information message, or other NG application protocol (NGAP) messages on the N2 interface, which is similar to the S1 application protocol S1AP on the S1 interface in 4G.
[0159] The CCS may also host different network relay functions, or different NRF instances may be assigned to different slices. The base station may select an appropriate NRF based on the requested slice identifier ID1 received in the message M' and forward the message to the selected NRF. In the case where the NRF is not directly coupled to the base station but is directly coupled to the AMF, the AMF may select an appropriate NRF based on the received requested slice identifier ID1 in the message received from the base station.
[0160] In CCS, the Network Relay Function (NRF) may operate as follows.
[0161] A message M' or a message M'' based at least in part on the message M' is received from an access and mobility management function (AMF), or a message M' or a message M'' based at least in part on the message M' is received directly from a base station BS, the message including a network slice identifier ID1 that UE0 is requesting to access.
[0162] Information I about a set T of UEs capable of relaying network traffic from UE0 to RAN / from RAN to UE0 and the capabilities of these UEs is obtained.
[0163] The relay device is determined based in part on the received message M" and the obtained information I. The relay devices may constitute a subset T' of T that UE0 is allowed or not allowed or prefers to use as relay devices for setting up a relay communication session with a network slice of the cellular communication system CCS identified by ID1.
[0164] The message N" may be sent back to the AMF or base station BS. The message N" may include information about the subset T' and the network slice identifier ID2.
[0165] Finally, the AMF or the base station BS sends a message N' to the relay device UEx based at least in part on the message N'. Note that the message may also or alternatively be addressed directly to a subset of the remote UE or relay UEs (e.g. via the AMF), or may be addressed to an intermediate node, e.g. a base station connected to the relay UE, which then forwards the information in the new message to the relay UE.
[0166] In an embodiment, NRF-assisted relay selection is described via a requesting UE during discovery, wherein the UE makes a selection based on an NRF pre-selection. In this embodiment, the UE may be configured to connect to one or more network slices, and may be further configured to discover nearby relay-capable UEs in certain circumstances based on configured policies, for example, relay-capable UEs outside the coverage of a base station. In order to discover nearby relay-capable UEs, the UE sends a D2D / PC5 discovery message that includes a new attribute indicating one or more IDs of the slice to which it wants to connect. Relay-capable UEs within radio range will receive the message and may each report information from the message to a network relay function (NRF) in the core network (CN). The message specifically includes information of the ID(s) of the slice(s) that the UE is requesting.
[0167] Based on the received information, the NRF determines which (potential or already activated) candidate relay UEs are able and / or are allowed and / or will optimally utilize (one or more) requested slices to serve the requesting UE or to serve a subset of the requesting UE if the complete set is not available. To this end, the NRF may need to request / receive information from other network functions (e.g., access and mobility management function (AMF) or radio access network (RAN)), or directly from the relay UE, further specifying capabilities, context information, connection attributes and other information, such as mobility / location / speed information of each relay-capable UE in the discovery range of the UE, or it is able to or involves (e.g., in the case of multi-hop relay) setting up an indirect connection from the UE to the radio access network. The NRF may use this information together with other information that may be requested / received from other network functions (e.g., Policy Control Function (PCF), Unified Data Management (UDM), Network Slice Selection Function (NSSF), ...) to evaluate whether each of these candidate relay UEs is allowed, able, and has sufficient resources available and is able to obtain the required QoS to act as a relay UE for the requested network slice. In addition, the NRF may request information about the "reputation as a relay UE" (e.g., from the Network Data Analysis Function (NWDAF)), because a relay UE can have a "bad reputation" (or record) when it starts acting as a relay, for example, it may drop connections, perform service denial by ignoring all remote UE's traffic, limit the bandwidth of remote UEs, etc.
[0168] Additionally, the NRF may consider other criteria, such as RAN congestion or whether the base station or AMF / MME to which the candidate relay UE is connected is approaching or has reached a certain maximum number of UE / PDN connections per slice, and may provide different candidate relay UEs for the requesting UE to connect to.
[0169] Furthermore, the NRF may use the preliminary UE subscription information to check whether the UE is allowed to operate in the slice(s) it requested. Note: Because the UE has indeed not yet authenticated with the core network at this point, and the UE only sends information about its identity via the Relay Discovery Request, which may be unauthenticated data (i.e., can be easily forged / altered), the NRF does not use this information to authenticate the UE. But only as a guide in the selection process.
[0170] When the network relay function (NRF) receives the identifier (ID1) of the request in the transmission request message (M'), the NRF may use ID1 to obtain relay capability data about relay devices that are capable of performing data transmission to / from a specific network slice based on the characteristics of the network slice indicated by ID1. However, in the case of a roaming remote UE, the NRF may know neither the identifier ID1 nor the characteristics of the slice indicated by the identifier ID1. Alternatively, the NRF does know the identifier ID1, but the identifier ID1 has different slice characteristics because the operator of the relay UE and the operator of the remote UE use the identifier ID1 for different purposes. In other words, if the operators do not use mutual agreement on the value of identifiers such as ID1, there may be overlap between identifiers. To address these potential issues, after receiving M', the NRF may contact the NRF of the remote UE's home PLMN (HPLMN) (if known), or may contact the AMF (or database) of one or more other PLMNs (using, for example, a request message M" to the HPLMN NRF) to obtain the characteristics of the slice indicated by ID1, and may also verify if the remote UE is authorized to connect to the slice indicated by ID1. Once the characteristics of the slice are retrieved (for example, via a response message N" from the HPLMN NRF), the NRF may configure the relay UE with parameters to support relaying for the slice indicated by ID1, such as sending security keys or parameters from which security keys can be derived to the relay UE. The NRF may include such configuration information in whole or in part in the transmission response message N', or the NRF may include the configuration information in other separate messages. The NRF may also configure the PDU sessions of the relay UE and / or the remote UE based on the retrieved characteristics of the slice indicated by ID1, for example, to optimally meet the QoS service requirements of a particular slice. Moreover, the NRF may configure parameters on the gNB that is serving the relay UE to, for example, optimally meet the QoS service requirements of a specific slice, which may include communication latency requirements or data throughput requirements.
[0171] Another solution is to coordinate the allocation of identifiers such as ID1 between operators, for example one operator reaches an agreement with all operators to enable roaming UEs from other operators on its own cellular network(s).
[0172] The NRF may then send a message to one or more selected candidate relay UEs, wherein the message for each relay UE includes a set of slices that can be provided to the requesting UE via that particular relay UE. In other words, for each candidate relay UE, a set of "acceptable slice IDs" is included. The NRF may also include a set of "rejected slice IDs" in case the complete set of requested slices cannot be reached, or in the case where the relay UE is not allowed to serve as a relay UE for network communications for the requested slice. The received slice information can also be an instance identifier or an allowed slice identifier or a default slice. Optionally, the message may contain information about a list of other possible candidate relay UEs that can be used to set up an indirect connection with the core network to access the requested slice. The list can be sorted according to preference or suitability to act as a relay UE for the requested slice.
[0173] Each relay UE that receives such a message will use the information from the message to send a discovery response back to the requesting UE, optionally containing slice information (or other information from which the requesting UE can derive whether the relay UE can support relay communications for the requested slice), and optionally also containing information about other candidate relay UEs. Because the (potential) relay UE communicates with the NRF before sending a discovery response to the requesting UE, a discovery response that may potentially be sent by the relay UE may be later than expected by the requesting UE. In this case, the relay UE is able to send a preliminary discovery response indicating that there is further information including slice information, but that further information will still be sent later, pending approval by the NRF / CN.
[0174] Based on the received discovery responses received from the candidate relay UEs, the UE is now able to select the best candidate relay UE to connect to, and then connect to it (e.g., through a process similar to ProSe), and via the core network process, the UE is connected to the requested slice(s) or an available subset thereof. Alternatively, the NRF selects only a single relay UE and instructs the relay UE to connect to the UE requesting the relay to connect to the requested slice.
[0175] Figure 4 An example of an NRF-assisted relay selection sequence diagram is shown. The diagram schematically provides an example flow and message sequence. In the diagram:
[0176] NF is the Network Relay Function NRF as described above;
[0177] NF2 is an optional extension of NRF (or ProSe functionality) that handles the issue of accepting admission of new remote UEs for relay UEs;
[0178] R1, R2, R3 are relay UEs or potential relay UEs; it is assumed here that R3 is connected to a different gNB, i.e., gNB2. In this example message sequence, detailed information about each relay UE (e.g., capabilities, signal quality, etc.) is sent directly to the NF to reduce the time required for the NF to collect all this information;
[0179] The "opt" box refers to optional communications, which are used to request further information from the RAN about slices, QoS, but also possibly information about other potential relay UEs in the vicinity, measurement information, location / mobility information of different UEs, etc. Currently, it is shown as information requested from the RAN, but it may also be necessary to request information from the AMF, PCF, UDM, NSSF or other network functions. It is shown as optional because the NRF may have received this information in advance;
[0180] NSSAI is a set of up to 8 slice IDs, as further described in 3GPP specification [23.501].
[0181] In another embodiment of the cellular communication system, a connection processor in a mobile device may be arranged to initiate a relay discovery process and engage an initial indirect connection. Subsequently, the connection processor sends a request message via the initial indirect connection. The network relay entity (140) or relay function may be arranged to reconfigure the initial indirect connection so that the indirect connection goes to the selected slice via the selected relay device. Thus, an activated relay UE may be reconfigured to use another relay, wherein the UE initially selects the initial relay and the NRF or UE reconfigures the selection. In this embodiment, a UE that needs to select a relay UE sends a D2D / PC5 message to initiate relay discovery. Relay UEs and potential relay-capable UEs within radio range will receive the message and will respond to the discovery response using a prior art process (possibly a ProSe process). The UE then selects a suitable relay UE candidate, even if it is not yet known whether the relay UE will fully support all of its required slices, and the UE connects to these slices. Connecting through the relay UE, the UE uses a prior art process to perform 5G network registration and / or PDU session establishment, which includes a request for one or more slices.
[0182] The NRF may involve the following process. Once the base station or access and mobility management function (AMF) receives the NSSAI requested by the UE, the NRF may be informed of this information, after which the NRF may determine which (potential) relay UE or set of relay UEs can and / or is allowed and / or will optimally utilize the requested set of slices to serve the requesting UE in the same manner as described for the first embodiment. Then, if the NRF determines that the most suitable relay UE for the UE requesting access to one or more slices is another relay UE instead of the current relay UE, the NRF sends a reconfiguration message to the UE (e.g., a configuration update command as defined in 3GPP [24.501]). The message may be sent directly or addressed via an intermediary such as a gNB or a relay UE, and may indicate in a new attribute in the message the ID or address of the relay UE to be used preferentially and the set of slices that can be obtained using the relay UE. The set may be larger than the currently supported slices for the UE. In addition, the NRF may also send a list of relay UEs together with the preference level and / or slice set of each relay UE. Alternatively, information about which relay UEs can or should be used for specific slices can be provided as a new extension to the UE Routing Selection Policy (URSP) as defined in 3GPP [29.507][23.503]], which can be sent to the UE using the UE Policy Delivery Protocol defined in Annex D of 3GPP [24.501].
[0183] When the UE receives the reconfiguration message or updated URSP, and based on the received information, the UE may continue to use the relay UE it was already using, or the UE may need to perform relay UE discovery again, optionally by specifically searching for a new preferred relay UE during this discovery and connecting to it.
[0184] In a further embodiment, an enhanced ProSe (eProSe) scenario in 5G is described, which embodies the reconfiguration of another eRelay UE (enhanced relay UE) that better supports the requested slice. The example scenario illustrates how this embodiment is applied to the 5G system architecture. The scenario assumes that the devices with relay capabilities have activated their relay functions and are therefore used as relay devices with 5G network licenses. On-demand activation of the relay function in the devices with relay capabilities is also possible, but this is not described further.
[0185] An example eProSe scheme involves the following. A mobile device UE that has lost connection to the 5G core network and cannot reestablish such a connection uses eRelay open discovery to start the process of eProSe eRelay discovery model B. The mobile device performs the role of an eRemote UE in this process. If the right to perform this process is granted by the ProSe function for out-of-coverage situations, the mobile device first checks in its UE configuration. If this is the case, the mobile device checks in its UE configuration whether the ProSe function authorizes it to act as an eRemote UE when out of coverage. If this is also the case, the mobile device sends a PC5_DISCOVERY message of the eRelay discovery solicitation type to request nearby eRelay UEs (which may also be referred to as eProSe UEs to network relay UEs). The message is sent via sidelink (SL) spectrum resources. In this example, open discovery is used, which means that the broadcast request is not protected by encryption: any eRelay UE can parse the request without requiring a specific security context or key. In an alternative embodiment, not further described here, a secure discovery process called eRelay restricted discovery can be used to prevent potential information leakage.
[0186] Each eRelay UE then reports the information and / or request parameters received from the mobile device to the ProSe function using a message such as ProSe MATCH_REPORT via the PC3 interface or its 5G eProSe equivalent. The ProSe function collects all MATCH_REPORTs sent by the eRelay UEs. It determines what the response to each message should be and sends each response message back to the corresponding eRelay UE (using, for example, a MATCH_REPORT_ACK message via the PC3 interface or its 5G eProSe equivalent). Each eRelay UE that receives such a message (i.e., a message implemented as MATCH_REPORT_ACK via PC3, for example) will send a response message to the mobile device based on its content. The response message is implemented, for example, as a PC5_DISCOVERY message of the eRelay discovery response type via interface PC5-D. The mobile device receives such a message from one or more eRelay UEs, which allows the mobile device to select an eRelay UE that seems suitable to be connected to using, for example, a decision process that has been standardized for 4G ProSe or its 5G eProSe equivalent.
[0187] Subsequently, by using the selected eRelay UE, the mobile device proceeds with the 5G core network attachment process, wherein the communication is relayed by the selected eRelay UE at the MAC layer (i.e., L2). The process may, for example, include the mobile device, whose role is eRemote UE, sending an INDIRECT_COMMUNICATION_REQUEST message to the eRelay UE via PC5, based on which the eRelay sends a message to the relevant network function, which may be implemented as sending a UE-triggered service request message to the access and mobility management function (AMF) or the ProSe function in the 5G core network, etc., so that the 5G core network can decide what response the eRelay UE is to send to the mobile device. The 5G network function (e.g., AMF or ProSe function) sends a response from the core network to the eRelay UE, based on which the eRelay UE sends a message such as a TCP / IP protocol to the mobile device via the PC5 interface.
[0188] INDIRECT_COMMUNICATION_REQUEST and other response messages. After a positive response that can be successfully processed, the mobile device will run a process similar to the existing 5G core network registration process - the main difference is that the message sent by the mobile device is not sent directly to the base station, but is relayed to the base station via the eRelay UE and finally reaches the core network. The registration process starts with the 5G-NR RRC connection setup process, which ends with the mobile device sending the RRCSetupComplete message to the base station including the NAS registration request. The NAS registration request includes the NSSAI requested by the elements of each standard 5G process in turn. Based on this process, the base station (gNB) initiates UE registration with the 5G core network, which starts by forwarding the NAS registration request of the mobile device to the AMF. The NAS registration request containing the requested NSSAI acts as a transmission request message of the current embodiment. In this case, the AMF largely implements the NRF as described herein. The AMF (which may be assisted by other network functions (e.g. ProSe functions) - this would constitute a distributed NRF) determines the optimal eRelay UE to which the mobile device should connect in order to best satisfy its requested NSSAI, and also determines the allowed NSSAIs (i.e. the set of slice IDs (S-NSSAIs) that the optimal eRelay UE is able to serve). In response to the NAS Registration Request, the AMF constructs a response message NAS Registration Accept, which includes a new information element per embodiment indicating the "Allowed NSSAIs served by the "optimal eRelay UE" and the identity / address information of the optimal eRelay UE. Note that the AMF may alternatively include multiple eRelay UEs, each of which includes a set of allowed NSSAIs, thus enabling the mobile device to select an eRelay UE from a set of multiple "optimal" eRelay UEs. The NAS Registration Accept will be transmitted back to the base station.
[0189] Subsequently, based on the above received message, the base station sends a message, for example, RRC reconfiguration, which includes information about "allowed NSSAI served by the best eRelay UE" as a new element in the message and an indication of the best eRelay, or alternatively includes a set of multiple eRelays with their allowed NSSAIs. This triggers the mobile device to evaluate the new information to detect another eRelay UE that can better provide service using the indicated slice in the allowed NSSAI, and restart the relay process by connecting via the indicated best eRelay UE. This process can optionally involve updated discovery of eRelay UEs.
[0190] Additionally, the "Allowed NSSAI served by the best eRelay UE" information may be supplemented by an optional field for each eRelay UE, which indicates the security context ID or application ID that the mobile device should use to correctly discover the eRelay UE.
[0191] In another embodiment, a second eProSe scenario in 5G is described, in which the slice information is present in the eProSe discovery, and the Model B message enables the UE to directly select the optimal relay device. Moreover, this example scenario also assumes that the devices with relay capabilities have activated their relay functions.
[0192] The second eProSe scenario involves the following. A mobile device UE that has lost connection to the 5G core network and cannot reestablish such a connection uses eRelay open discovery to start the process of eProSe eRelay discovery model B. The mobile device performs the role of eRemote UE in this process. If the right to perform this process is granted by the ProSe function for out-of-coverage situations, the mobile device first checks in its UE configuration. If this is the case, the mobile device checks in its UE configuration whether the ProSe function is authorized to act as an eRemote UE when out of coverage. If this is also the case, the mobile device sends a PC5_DISCOVERY message on the sidelink (SL) spectrum of the eRelay discovery solicitation type to request nearby eRelay UEs (which may also be referred to as eProSe UEs to network relay UEs) to respond with relay information. In this example, open discovery is used, which means that the broadcast request sent is not protected by encryption, so that any eRelay UE can parse the request without requiring a specific security context or key. Alternatively, a secure discovery process eRelay restricted discovery can be used to prevent information leakage, but this is not discussed further. The eRelay Discovery Solicitation message may include an additional element "Requested NSSAI", which is a list of one or more slice IDs (i.e., a list of S-NSSAIs) to which the mobile device wishes to connect via the eRelay UE.
[0193] Each eRelay UE then reports the information and / or request including the requested NSSAI received from the mobile device to the ProSe function using a message such as ProSe MATCH_REPORT over the PC3 interface or its 5G eProSe equivalent. The ProSe function implements the network relay function and collects all transmission request messages. It determines for each eRelayUE which slice of the slices in the requested NSSAI the eRelay UE can provide to the mobile device via an indirect connection. This determination may involve communication with other network functions (RAN, base station, AMF, server containing MNO subscription information, etc.) to obtain the optimal slice decision that can be supported.
[0194] The ProSe function then sends a transport response message back to each of the corresponding eRelay UEs using, for example, a MATCH_REPORT_ACK message over the PC3 interface or its 5G eProSe equivalent. This message to a given eRelayUE optionally contains an additional information element per embodiment, "Allowed NSSAI" is a list of one or more slice IDs to which the mobile device can connect via the eRelay UE (i.e., a list of S-NSSAIs); and it optionally contains an additional information element per embodiment, "Rejected NSSAI" is a list of one or more slice IDs that the ProSe function determines cannot be accessed via the eRelay UE.
[0195] Subsequently, each eRelay UE that receives this message (i.e., a message implemented, for example, as a MATCH_REPORT_ACK over PC3) will send a response message to the mobile device, which response message is implemented, for example, as a PC5_DISCOVERY message of eRelay discovery response type sent to the mobile device over interface PC5-D. The message now includes, as a new element per embodiment, the slice ID included in the MATCH_REPORT_ACK, which is an optional allowed NSSAI in the case where a given eRelay UE is able to serve as an eRelay UE for a mobile device for (some or some) slices, and is an optional rejected NSSAI in the case where the eRelay UE is rejected by the ProSe function to serve as an eRelay UE for a mobile device for (some or some) slices. Alternatively, the response message includes, as a new element, a supported Boolean value or a set of Boolean values for a set of requested and / or supported slices. Alternatively, the response message is a message of a different format that confirms that a match has been found between the requested slice and a list of slice IDs to which the mobile device can connect via the eRelay UE. In another embodiment, a response message is only sent if the given eRelay UE is capable of acting as a relay for the mobile device for the requested network slice.
[0196] Subsequently, the mobile device receives the message from one or more eRelay UEs, which allows it to select, for example, one eRelay UE that initially provides services for all or the most network slices indicated in its requested NSSAI. Alternatively, the mobile device may select an eRelay UE that does not provide the most network slices, but the eRelay UE does provide the most important (highest priority) network slices that the mobile device wishes to connect to. Using the selected eRelay UE, the mobile device proceeds with the 5G core network attachment process, in which the communication is relayed by the selected eRelay UE at L2. The process may, for example, include the mobile device (whose role is eRemote UE) first sending an INDIRECT_COMMUNICATION_REQUEST message to the eRelay UE via PC5, based on which the eRelay UE sends a message to the relevant network function, which may be implemented as sending a UE-triggered service request message to the access and mobility management function (AMF) or the ProSe function in the 5G core network, etc., so that the core network can decide the content of the response that the eRelay UE is to send to the mobile device. The network function sends the response from the core network to the eRelay UE, based on which the eRelay UE sends an INDIRECT_COMMUNICATION_REQUEST to the mobile device via the PC5 interface. After a positive response that can be successfully parsed, the mobile device will initiate a process similar to the normal 5G core network registration process - the key difference is that the relevant traffic is relayed via the eRelay UE. The process starts with the 5G-NR RRC connection setup process, which again ends with the mobile device sending an RRCSetupComplete message to the base station including the requested NSSAI for each standard 5G process. Based on this process, the base station (gNB) initiates a UE registration with the 5G core network, which includes a connection to one or more network slices.
[0197] In the third eProSe scenario in 5G, the discovery process is skipped and instead the requested slice identifier is sent to the eRelay UE via PC5 as part of the INDIRECT_COMMUNICATION_REQUEST message. At this time, after performing a message exchange with the AMF or ProSe function (or other network function) to confirm whether the eRelay UE is able and allowed to serve as a relay for the eRemote UE to communicate with the requested network slice, the eRelay UE sends an INDIRECT_COMMUNICATION_REQUEST including information (e.g., a set of allowed slice IDs, a Boolean value indicating support for the requested slice) to confirm that the eRemote UE is able to connect to the requested slice via the eRelay UE.
[0198] In another alternative, relaying may be done at layer 3 or via an application level relay, in which case the DIRECT_COMMUNICATION_REQUEST message (as defined in 3GPP [23.287]) and the DIRECT_COMMUNICATION_ACCEPT message (as defined in 3GPP [23.287]) may be used instead of
[0199] INDIRECT_COMMUNICATION_REQUEST message and INDIRECT_COMMUNICATION__RESPONSE message.
[0200] In another example scenario, a vehicle mobile device may communicate with a destination in the network (V2X). The car UE may use V2X 5G communication on two specific slices, "V2X" and "Entertainment" which may lose its gNB coverage at some time. The car UE initiates a relay UE discovery and finds 10 candidates belonging to different PLMNs. Two of the candidates indicate specific support for V2X slices and entertainment slices in their discovery response messages. The car UE selects the one with the highest signal quality from the two candidates and initiates a connection to the relay UE as a remote UE. During the core network registration process, both slices are indicated as "Allowed NSSF" for the car UE.
[0201] Figure 5An example multi-hop relay topology for a mobile UE is shown. The mobile UE may have been out of coverage while it was previously connected to the gNB / eNB. The UE in out of coverage (OoC) may initiate a relay discovery procedure indicating that it requires slices X and Y. In the figure, both UE (1) and UE (3) receive the discovery message and report the information of the OoC UE along with the requested slices X / Y to the NRF in the CN via the gNB. The NRF may determine that slice X is related to Ultra Reliable Low Latency Communication (URLLC) and is best served with the lowest number of hops for lowest latency, while for slice Y, high data rate is important.
[0202] The NRF determines that UE(1) has the fastest connectivity with the gNB and sufficient bandwidth to add additional relay traffic and also satisfies slice Y. The NRF then reports back to UE(1) with slice IDs of X and Y and a preference value of "high". Furthermore, the NRF may authorize UE(1) to become a relay UE for serving OoC UEs. The authorization may be done based on a separate message / protocol or in combination with the previous step. The CN may also (at the same time) provide credentials to allow the relay UE to access the requested slice(s).
[0203] The NRF may report to UE(2) with slice IDs of X and Y and preference value "low". Upon receiving the NRF response, UE(1) may send a discovery response to the OoC UE with slices X / Y and preference "high".
[0204] UE (3) may receive the NRF response and will send a discovery response to the OoC UE with slice X / Y and preference “low”.
[0205] The OoC UE may receive two discovery responses and may select UE(1) as a relay UE; and perform an attachment procedure to the relay UE. Thus, by running the above flow, UE(1) becomes a relay UE during the process. It may optionally perform this operation when it determines a high probability of being selected as a relay UE by the OoC UE due to a "high" preference value.
[0206] Note that the above concepts can be mapped to the 5G cellular communication system (5GS). The network relay function (NRF) can be mapped to the network slice selection function (NSSF) defined in 5G [23.501] or a combination of NSSF and AMF [23.501], but the NRF can also be a new separate network function. The requested slice / slice instance can be mapped to the requested NSSAI [23.501] or a temporary / encrypted slice identifier [33.813] or some other newly defined identifier. The allowed / supported slices determined by the NRF can be mapped to the allowed NSSAI [23.501]. The slice ID can be mapped to the S-NSSAI [23.501] and the set of slice IDs can be mapped to the NSSAI [23.501].
[0207] Moreover, the "discovery message" can be a discovery type message or an announcement type message. It can be sent on a sidelink (SL) scheduled resource; or it can be a RACH (random access channel) type message sent through a sidelink or uplink (UL) non-scheduled resource. It can also be sent through non-3GPP defined spectrum (e.g., Bluetooth, Wi-Fi).
[0208] In addition, the discovery message sent by the requesting UE may optionally include the following. Initially, the UE may send a discovery message to find a relay or potential relay. The content of the message shall include the requested slice in the "NRF assisted relay selection" embodiment, and may include the requested slice in the "NF reconfiguration relay" embodiment. Moreover, the discovery message may include any one of the following:
[0209] o a message header or message type that indicates that the requesting device is requesting that the other device act as a relay for traffic originating from the requester; or
[0210] oA message header or message type that indicates that the requester intends to discover available relay devices.
[0211] Moreover, the discovery message may include some information about the security context in which the UE is running or the UE wishes to run, such as a slice-specific security context, encryption credentials provided by the eNB, encrypted PLMN session keys, security context identifier, ProSe group ID or service ID and relevant group / service credential information.
[0212] Furthermore, the discovery message may include a reason indicating why relaying is requested, e.g., low battery, out of range of base station, poor signal to base station, recommendation of relay by NRF. It may include the received signal strength of any message received from nearby devices, which signal strength data may assist the NRF in making relay selection. Furthermore, it may include power status information of the device, e.g., power supply, battery powered, mains powered, or solar; or battery current level information. Furthermore, it may include standard fields, e.g., the transmitted signal strength of the message, UE identity information. The UE identity information may optionally be a temporary ID derived or for privacy reasons, which the NRF / CN is able to calculate back to the real UE ID if necessary.
[0213] Moreover, the discovery message may include distance measurement data or other types of location information, for example, the speed of the mobile device (which may be an absolute speed or a relative speed) and / or header / direction information. The mobile device 110 and / or the relay device may be arranged to perform distance measurement between the mobile device and the relay device. The connection processor 112 may be arranged to enable distance measurement and transmit the measured distance to the network for determining the location data of the mobile device and / or the relay device. By receiving one or more distance measurement results between the mobile device and the relay device, the NRF is enabled to enhance the selection of the relay device. In fact, the location data obtained based on the transmission received from the mobile device is not very accurate, for example, with a tolerance of 100 meters. On the contrary, the local distance measurement result is much more accurate, for example, with a tolerance of 1 meter. Combining the multiple positions of multiple mobile devices with the distance between the devices positioned in this way can improve the accuracy of the location data.
[0214] In an embodiment of the system, in order to detect the distance between the mobile device and the relay device, a special mode can be requested on the device to measure the distance, for example, by using Wi-Fi fine time measurement specified in IEEE802.11-2016 or the MNO authorizing ProSe functionality (as specified in [23.303] and [24.334]) on both devices so that they can discover each other using the sidelink D2D communication channel and perform distance measurement or proximity detection (for example, via PC5 or Wi-Fi Aware Ranging).
[0215] In an embodiment of the system, possible contents of the request message (M) with the requested network slice identifier may be the following. When the requesting UE initiates a request message that is further sent to the NRF as part of the registration process, the message may include the source address or identifier of the mobile device, i.e., the UE itself. The request message may also include a set of QoS requirements or requested QoS, for example, a preferred set and an alternative fallback set. It may also contain information about the relay UEs in the area obtained during the original relay UE discovery process (e.g., signal strength). Alternatively, the information may be included in the transmission request message (M') by the relay device or the selected relay device for indirect connection, and / or, when the information is forwarded from the UE to the core network, the information may be included in the transmission request message (M') by the base station. Alternatively, the NRF may request the information and additional related information from the RAN, AMF or other network functions as described above.
[0216] When a relay device initiates a message based on information received from a requesting UE (e.g., during a discovery process or indirect connection setup), the relay UE may send the message to the NRF to indicate that the requesting UE is looking for the relay UE and includes its own source address or identifier in the message.
[0217] In an embodiment of the cellular communication system, the network relay entity may be arranged to obtain metadata from the cellular communication system, such as received signal strength, signal quality or distance estimation results. Alternatively or additionally, the transmission request message includes metadata identifying the current connection state, such as the mode of network connection, quality of service (QoS) and number of hops, connection stability information and / or the frequency band being used or the supported frequency band of the relay device. The network relay entity (140) may be arranged to determine the network relay information based on the metadata.
[0218] The metadata may also be obtained from other sources in the cellular communication system, e.g. sources within the RAN or the core network. For example, the number of hops may be obtained from the base station and the distance estimation result may come from location services in the core network. Furthermore, subscription information from the UDM is important, e.g. for assessing whether the relay UE is operated by the same MNO as the remote UE, or for assessing whether the relay UE is authorized to access a specific slice, or to act as a relay within a specific slice. The UE capability information may come directly from the UE, but may also be (partially) provided by the UDM or the SCEF. Since the resources of the relay UE and the remote UE are typically scheduled by the base station, the base station is the device that has the knowledge of whether the relay UE and the remote UE can be given sufficient sidelink resources to accommodate a certain QoS request from the AMF / NRF to accommodate the QoS requirements of a certain network slice.
[0219] In an embodiment, the NRF may decide whether the QoS requirements for a certain network slice can be met. QoS represents an important criterion for deciding which relay devices can act as relays for a specific slice.
[0220] In an embodiment, the NRF may use the attributes / requirements of a particular slice to determine which relay(s) to prioritize. For example, for an IoT slice, a fixed relay device or a relay device that is not an IoT device itself may be prioritized.
[0221] The relay device may optionally include metadata about the message of the requesting UE (e.g., RSSI or signal quality or distance estimate) or the signal quality or distance estimate result for another relay device. It may also include information identifying its current connection state, such as one or more of the following:
[0222] Direct / indirect connection method;
[0223] QoS information and / or number of hops towards the gNB;
[0224] (Past) connection stability information;
[0225] Cache size
[0226] Current number of connections;
[0227] Information about data flow or duty cycle / sleep cycle;
[0228] ·The frequency band currently being used by the relay UE, or the supported frequency band. The NRF may also obtain such information by interfacing with the RAN / gNB or other core network functions. The RAN / gNB may provide additional information, such as information about the available resources for each of the relay UEs for sidelink communication with the remote UE. Upon receiving such information, the NRF may use the information to perform a decision process. For example, the NRF may use the number of hops and / or signal quality information together with QoS information to determine whether a given relay UE can satisfy the slice required by the UE. For example, if it is a slice that provides low-latency communication, a relay UE with a large number of hops is not preferred. If the required latency cannot be achieved due to the number of hops, the NRF may even prohibit the use of the slice and may indicate this to the originating UE.
[0229] Furthermore, the message to the NRF may optionally include the UE capabilities of the relay UE. The UE capability information may include:
[0230] Information about relay capabilities, which may include, for example, specific constraint information if the UE is capable of relaying;
[0231] Radio Rx / Tx speed category, or 3GPP UE category / class;
[0232] Radio frequency bands used or supported;
[0233] Processor performance class and / or current load;
[0234] Mobility information: either fixed (e.g., a roadside V2X node), or potentially mobile (e.g., a mobile phone or wearable sensor). May also include location / header information (e.g., in the V2X case);
[0235] Power source, battery level, or expected device operation duration information (which can be used to make optimal relay decisions);
[0236] Identification of the security context associated with the specific relay that the device already supports;
[0237] Preferences for relaying certain application types, application IDs, or groups of IDs;
[0238] Support for IP traffic and certain packet sizes;
[0239] Support for certain services (e.g., location support);
[0240] The type of relay that the relay device is capable of supporting, e.g., Layer 2 (at PDCP level) relay or Layer 3 (at IP level) relay. The NRF may use the above capability information to determine the best choice for relaying the UE given the attributes / requirements of the requested specific slice or slices. For example:
[0241] For IoT slicing: non-mobile mains-powered nodes with ample resources and high-speed connectivity are preferred as relay UEs over battery-powered mobile, low-resource IoT sensors;
[0242] For IoT slicing: using a relay UE that is not an IoT device itself may be preferred over a direct network connection for IoT devices in order to save battery;
[0243] For V2X slicing: using a relay UE that is itself in the V2X slice may be preferred;
[0244] For V2X slices: a relay UE moving in the same direction as the requesting UE may be preferred. This is true even if the relay UE is not in the same V2X slice;
[0245] The NRF may use the currently used frequency band information of the relay UE in the selection process. When the NF obtains information about the currently used frequency band(s) of the relay UE (e.g., from a message received from the relay UE or from the gNB or otherwise), the NRF may use this information in the selection to determine which relay UE cannot serve a particular slice. This occurs, for example, in the following case: the slice is associated with the use of specific dedicated frequency band(s), for example, a "V2X" slice that uses a V2X reserved frequency band. Some candidate relay UEs may not currently operate in that frequency band, and therefore these candidate relay UEs may not be suitable to perform any relay role for that slice. The NRF may exclude these candidate relay UEs from the selection process, or may still include these candidate relay UEs, but as candidates with low preference. As a fallback solution, such a relay UE may serve the "V2X" slice via a different frequency band. The same situation applies to NB-IoT / LTE-M devices, which may operate in a guard band that is not supported by, for example, a mobile phone that may be a candidate relay UE.
[0246] In a further embodiment, the requesting UE may indicate a security context or key for subsequent attachment to the relay UE. The security context for relaying may be linked to the security context for the slice. In ProSe, the remote UE and the relay UE need to have a shared security context (i.e., key material) in order to be able to establish a D2D connection for relay purposes. In existing specifications, the security context is pre-configured at the application level, which limits the usefulness of the relay functionality to devices with the same application context only. In an enhancement, arbitrary and unknown UEs may be supported as relays. In this embodiment, the following may apply.
[0247] The requesting UE may indicate in its discovery message the security contexts or keys C that it supports. This may be a slice-specific security context, or more generally a security context valid for multiple slices, or for example a security context for a (third party) defined group of devices (e.g. all medical devices within a hospital or a group of ProSe applications). The context information may also include a random ID or partial key that can be used later by the NRF / CN to derive the full key to be used.
[0248] • The relay UE may send information about the security context C to the NRF, so that the NRF can retrieve information related to the security context from the CN.
[0249] • The NRF may include information based on the above (eg, key material or credentials) in the response message sent back to the relay UE.
[0250] • The relaying UE may then use the security information to accept the secure relay request from the requesting UE, performing the secure relay request in a secure manner, e.g. to prevent eavesdropping, replay, packet injection, etc. during the relay establishment protocol.
[0251] Note that by using the random ID or partial key mentioned above, the potential impact of malicious relay UEs storing and sharing security material is reduced, as the security material will only be valid for a temporary period.
[0252] In an embodiment, the CN may detect a UE that has been to OoC. Subsequently, the CN may request one or more UEs that the CN calculates may be near the OoC UE to start broadcasting a "relay available" message, thereby assisting the OoC UE to quickly discover a suitable relay UE. In this case, the CN may involve the NRF to determine which relay UEs are most suitable to become available in this way based on the previous slice information of the OoC UE.
[0253] Additionally, the NRF may authorize and instruct the selected relay UE candidate(s) to activate their relay functionality in case they are not already used as relays. This ensures a quick connection with the chosen relay UE later on, as it has already been activated and has network permission / authorization to act as a relay UE. Moreover, after the NRF has determined the optimal relay device for the requesting UE, it may inform the gNB of the decision and the expected slice requirements from the requesting UE. This allows the gNB to start scheduling appropriate resources to support the requesting UE. This has the benefit that appropriate resources have already been prepared and scheduled at the gNB for the operation of the requesting UE in its desired slice(s), even before the UE is fully attached to the relay UE and the CN. This shortens any temporary QoS / bandwidth issues during relay handover or during transition from a direct network connection to a relay connection.
[0254] Additionally, if one of the requested slices is an "emergency" type slice, that slice may be prioritized in the selection process, or may receive special treatment from potential candidate relay UEs, such as automatically enabling them to be used as relay UEs, and allowing emergency connections to be set up to any discovered candidate relay UEs. Alternatively, emergency slices may be automatically included in the discovery response generated by the candidate relay UEs. This may also be done for relay UEs participating in slices with known restricted use (e.g., public safety). These are unlikely to be used as relay UEs for any other device, and therefore public safety slices may be automatically included in their responses, and the NF may not even be contacted in the process.
[0255] Additionally, the discovery message or "request relay" message may include an identifier indicating a class of devices or a class of applications to which the UE is associated. For example, medical devices may be a separate class as well as emergency service devices. The application class may be "IoT applications for local governments". This identifier may help the UE make a decision as to whether it will act as a relay UE for devices indicating this particular identifier. This allows potential relay devices to configure the purposes they wish to assist in the relay role, for example, medical applications may be considered more important to the user than purely commercial applications. Furthermore, not all relay devices may be used in an acceptable manner to relay medical or safety-related data (e.g. in order to comply with regulatory rules for the processing and transportation of medical data). To prevent fraud (spoofing of identifiers), cryptographic certificates, signatures or proof elements may be added to the communication, enabling the UE to prove that it is part of the claimed application or class of device.
[0256] In an embodiment, the following situation may occur: the UE is out of range, but is still able to (e.g., weakly) receive synchronization information and / or other broadcast messages from the eNB, but is unable to send the information back due to too long a distance, signal blocking, or lack of battery power or transmitter output power, i.e., the eNB will not hear the device. In such a case, the eNB may assume that the UE may still listen and the eNB actively transmits certain instructions to the UE. For example, the network may instruct such a UE to start requesting relaying with instructions, which may include channel information and timing information. Or it may transmit to the UE what time is the optimal time to transmit a "relay request", for example as part of a discovery message.
[0257] If the UE has just lost contact with the eNB, the UE can use (previous) synchronization with the base station as the basis for its local clock, or alternatively detect a synchronization signal from a device operating in discovery mode. If contact has just been lost, the eNB can provide synchronization information to various candidate relay UEs in the vicinity, which synchronization information includes information about when the UE was last seen, and / or also includes possible estimates of clock drift and / or timing margin to adjust its listening time window to ensure the maximum probability of hearing the expected transmission from the UE. Alternatively, the candidate relay device can receive information from the eNB about previously scheduled resources for the UE on the sidelink or uplink channel. The relay device can use this information to listen to the "relay request" message at the correct time / frequency.
[0258] If the UE is already connected to a slice via a relay connection and detects that insufficient bandwidth / QoS is available for communication as required / expected for the slice currently in use, the UE may initiate a request to one of the other candidate relay UEs that it has previously discovered based on the preference information indicated by the NRF. Alternatively, it may initiate a new discovery procedure or send a request directly to the NRF (or AMF / RAN) to provide (up-to-date) information about which other relay UE to select to achieve the QoS attributes of the slice, in which case the NRF / RAN / AMF may be involved in initiating a discovery procedure between the relay UE and the gNB in a specific geographical area near the UE.
[0259] Similar to the above, the eNB / network may detect that the available bandwidth or QoS is insufficient and proactively initiate a process to find a suitable relay. The UE is then instructed first to send a "Request Relay" message and secondly to connect to a specific relay or select a relay from a set of relays.
[0260] Note that to enable this, the user or operator of a UE that provides relay functionality to others may be rewarded or compensated. Compensation may be in various forms such as payment, usage credit added to their cellular subscription bundle, or special service benefits (e.g., being able to utilize other relay devices). Some charging functionality may need to be extended for this. This may include special charging functionality for a UE that acts as a relay UE for a slice that may or may not have a subscription to operate in, for example, a private slice.
[0261] In an additional embodiment, the mobile network defines a set of connection context identifiers (CCIs), where each CCI is mapped to a combination of PDU session parameters [23.501] (e.g., PLMN ID (+NID / CAG ID), S-NSSAI, DNN, PDU session type, etc.) and some possible additional parameters (e.g., the group ID that the remote UE may wish to use to connect to the core network via the relay UE, QoS requirements, frequency, security context, etc.). Some of these parameters may impose restrictions on whether the relay UE is authorized and can act as a relay for the remote UE.
[0262] Since much of the above information is privacy sensitive and may result in the remote UE being tracked and the operator's deployment information (e.g., which slices / NPNs are supported by the core network) being exposed, it may be preferable to store this information in the core network and use it as much as possible in the core network, and not provide this information to the relay UE, which can be considered an untrusted end-user device. Storing, using and processing this information inside the core network can also enable handling of the dynamic aspects of using slices, such as to achieve QoS requirements defined by the service level agreement for the network slice. Even if the remote UE is also an untrusted end-user device, some of this information may need to be provided to the remote UE, as the remote UE may be out of coverage when they need to discover and utilize the relay UE to reach the network. However, it is not a problem for the remote UE to expose some of this information, as the remote UE can be provided with only the PDU session parameters enabled by the remote UE's subscription. This is different for the relay UE, as it may potentially be used as a relay for a diverse set of remote UEs (which may even include inbound roaming remote UEs). The CCI that the remote UE can use may only be known to the operator of the remote UE, so the relay UE may not know the CCI at the time of discovery, but the network operator of the relay UE (ie, the visited network) can retrieve the CCI from the home operator of the remote UE.
[0263] Furthermore, given the potential number of slices and NPNs that a 5GC can support, the number of possible combinations of the above parameters may be very high and may require a significant number of CCIs.
[0264] In order to provide as little CCI as possible to the relay UE, and also to ensure that the remote UE that can use potentially unknown or outdated CCI can still discover the relay UE and request to access the network via the relay UE, one solution is to use one or more common CCIs. While CCI is bound to a specific set of PDU session parameters, and the relay UE may not know the CCI, the common CCI is an identifier that can be used as a "wildcard" to request access to any set of PDU session parameters for one or more PLMNs (e.g., a predefined value that may have a longer service life and may be shared by different PLMNs). The common CCI value can be mapped to or indicate some wildcard values (e.g., asterisks, regular expressions). The common CCI value can be associated with an initial security context, through which the remote UE and the relay UE can prove that they are authorized to issue a discovery or connection setup request, through which the remote UE can request access to a specific slice / NPN and / or use a specific set of PDU session parameters via the relay UE. The common CCI can also be associated with a default network slice for one or more PLMNs. Alternatively, the normal CCI may be associated with an application context or (V2X) application ID [23.287]. Advantageously, at least one normal CCI is provided in both the remote UE and the relay UE. Using normal CCI may also make it easier to support Model A discovery (i.e. broadcasting "I am here"), as these messages can be kept small and typically do not contain an extended list of CCIs (which may need to change regularly). It also makes it easier to discover all available options available to the remote UE by using a single identifier in the request message (rather than having to include a potentially large list of identifiers). Normal CCI may also be used as a trigger in the remote UE and relay UE to include specific CCI as part of a discovery message or connection request. Alternatively, a separate message may be defined to send normal CCI, but the benefit of using normal CCI is that the same discovery and PC5 connection setup messages can be reused.
[0265] The following describes and Figure 7 The detailed process is illustrated.
[0266] Step 0: Before discovery of the relay UE can be performed, the following information shall be provisioned in advance in the remote UE and the relay UE (e.g. by using the UE configuration update procedure [23.501] (e.g. initiated from the AMF or PCF)):
[0267] For remote UE:
[0268] One or more CCIs that the remote UE is authorized to use, in case it is a normal CCI or a specific CCI, it includes a flag indicating for each CCI.
[0269] Mapping between each CCI that the remote UE is authorized to use, and the default destination Layer-2 ID for initial signalling to establish a PC5 unicast connection [23.287].
[0270] The mapping between each CCI and a set of PDU session parameter values may include one or more of the following:
[0271] PLMN ID
[0272] NID / CAG ID
[0273] S-NSSAI
[0274] DNN
[0275] PDU Session Type
[0276] For normal CCI, the set may be empty or a small subset of the parameters, may indicate some wildcard values (eg, asterisk, regular expression), or may contain special predefined values, eg to refer to the default slice.
[0277] (Optionally) a mapping between each CCI and a security context (eg, a set of credentials).
[0278] A policy that restricts the remote UE's PDU Session to the PDU Session parameter values corresponding to the requested CCI.
[0279] For relay UE:
[0280] The relay UE is authorized to expose and re-act one or more CCIs during discovery, including a flag indicating for each CCI in case it is a common CCI or a specific CCI. This should be a small subset of all CCIs that the relay UE can process and configure for after consulting the relay UE's AMF in order to reduce exposure of potential privacy sensitive information.
[0281] Relays a mapping between each of the CCIs that the UE is authorized to expose and re-act during discovery and the default destination Layer-2 ID used for initial signaling to establish a PC5 unicast connection [23.287].
[0282] (Optionally) a mapping between each CCI and a security context (eg, a set of credentials).
[0283] (Optional) Default destination Layer 2 ID for broadcast communications over PC5 [23.287].
[0284] In addition, the following information shall be provided to the AMF of the relaying UE (provided in advance, or when the AMF receives the transmission request message (M), the AMF can consult each network function (e.g., PCF, NSSF, UDM)):
[0285] An extended list of CCIs for which the relay UE can process and obtain authorization, including a flag indicating for each CCI if it is a normal CCI or a specific CCI. Since the list of CCIs for the AMF may not always be updated at the same time as the remote UEs (and relay UEs) (which may be out of coverage for some time), the AMF should also keep a history of old CCI values.
[0286] The mapping between each CCI and a set of PDU session parameter values may include one or more of the following:
[0287] PLMN ID
[0288] NID / CAG ID
[0289] S-NSSAI
[0290] DNN
[0291] PDU Session Type
[0292] For normal CCI, the set may be empty or a small subset of the parameters, may indicate some wildcard values (eg, asterisk, regular expression), or may contain special predefined values, eg to refer to the default slice.
[0293] The PCF in the HPLMN of the UE that needs to be provided as a remote UE or a relay UE may interact with the PCF of other PLMNs (eg, a possible visited PLMN of a roaming partner) to perform CCI allocation and management.
[0294] Step 1: The relay UE may periodically broadcast one or more CCIs, which are configured by the relay UE using a (V2X) broadcast message via PC 5. In order to keep the broadcast message small, the CCI set is preferably kept very small and preferably includes a common CCI.
[0295] Step 2:The remote UE can initiate discovery to find a relay UE by sending a direct communication request via PC5 as specified in TS23.287 or a similar message with the requested CCI used as the (V2X) service / application identifier. If the requested CCI is a normal CCI, the direct communication request may include additional CCI indicating the set of PDU parameters that the remote UE wishes to use. The direct communication request uses the default destination Layer 2 ID configured for the requested CCI (or the Layer 2 ID of the target relay UE if known), and in the case of V2X is typically sent over a sidelink shared broadcast / multicast channel and can be received by multiple relay UEs. The direct communication request message corresponds to the request message (M) referenced elsewhere in this document.
[0296] Step 3: One or more relay UEs may receive a direct communication request via PC5. If the CCI in the direct communication request matches the CCI known to the relay UE, the relay UE sends a registration request [23.501] or a service request [23.501] or a dedicated request message to the serving AMF of the relay UE (which is not only in the CM_IDEL state but also in the CM_CONNECTED state). The registration / service / dedicated request message includes the requested CCI, and if the relay UE has received additional CCI in the direct communication request in step 2, the additional CCI will be included in the registration / service / dedicated request message. Preferably, the additional CCI is included and used instead of the normal CCI. The relay UE may (re)use an existing PDU session, which has been pre-established to connect to the AMF of the relay UE, to send a registration / service / dedicated request message. The registration / service / dedicated request message corresponds to the transmission request message (M') used in other parts of this document.
[0297] Step 4:The serving AMF of the relay UE shall receive the transmission request message (M') and verify whether the relay UE is authorized to act as a relay UE for the given CCI (and in particular the associated network slice (indicated by S-NSSAI) and / or NPN (indicated by PLMN ID+NID / CAG ID) in the mapping table between CCI and PDU session parameters), and also verify whether the relay UE can meet the requirements associated with the PDU parameters of the CCI (in particular if it can and is authorized to act as a relay UE for the associated network slice (indicated by S-NSSAI) and / or NPN (indicated by PLMN ID+NID / CAG ID) and whether it can meet the QoS requirements for the specific slice / NPN. To perform this verification, the AMF may request information from other network functions such as the NSSF (about allowed network slices), the RAN (about capabilities and loads of the relay UE, congestion and signal quality), the SMF (about ongoing PDU sessions and their QoS), the UDM (for subscription related information), the PCF (for policy information, PDU session configuration and QoS related information), the NWDAF (for combined measurement information, analytical data and historical data), the ProSe function, the application function, etc. If the relay UE sends normal CCI to the AMF and no additional value is provided in the Transfer Request message (M'), the AMF shall decide, for each set of combinations of PDU session parameters, whether the relay UE is able to provide service for these sets. If the CCI value is not part of the mapping of PDU session parameters to the AMF, the AMF may search its history of previous CCI values or may contact the AMF (or database) of the 5G network of the other network operator.
[0298] Step 5: If it is decided that the relay UE can act as a relay for a given CCI and its associated (one or more) network slices and / or (one or more) NPNs and other PDU session parameters, the AMF will send an RRC connection reconfiguration message to the relay UE and / or may send a UE configuration update and / or a dedicated message to the relay UE. The connection reconfiguration / UE configuration update / dedicated message may include information for the following operations:
[0299] Reconfigure the existing PDU session between the relay device and the network to accommodate the relay network traffic for a specific slice (e.g., change DNN, connect to a different user plane function);
[0300] The UE configuration is updated (possibly including different S-NSSAI information, different policy information, different credentials) and a reconnect is issued (which may, for example, result in the selection of a different Access and Mobility Management Function (AMF) to serve the network slice).
[0301] The connection reconfiguration / UE configuration update / dedicated message may include instructions for initiating an additional PDU session with the network if the relay UE is already serving other remote UEs. The connection reconfiguration / UE configuration update / dedicated message may also include instructions for connecting to a different PLMN / NPN, and may include instructions for the radio access network, for example, instructions for sending an updated list of allowed NSSAI values for the relay UE and / or remote UEs, or for example instructions for camping on a specific cell of the access NPN (identified by the CAG ID in the case of a public network operating NPN, or by the NID (together with the PLMN ID information) in the case of a standalone NPN).
[0302] In particular, the AMF may configure the PDU session of the relay device to connect to a cellular base station that is configured (within the radio access network, e.g. based on NGAP messages [38.413] from the AMF to the radio access network) with a CAG ID / NID that is part of the allowed CAG / NID list in the mobility restriction information and / or is configured as a CAG unit, which may broadcast the CAG ID / NID within the system information block and / or the radio access network is configured to report it to the core network (e.g. within NGAP messages [38.413] to the AMF). In the case where the relay device is directly connected to the cellular base station or the mobile device is indirectly connected to the cellular base station via the relay device (the cellular base station is configured as a CAG unit and / or the CAG ID / NID is part of the allowed CAG / NID list in the mobility restriction information), the CAG ID / NID refers to a non-public network.
[0303] If it is decided that the relay UE cannot act as a relay for a given CCI and its associated (one or more) network slices and / or (one or more) NPNs and other PDU session parameters, the AMF shall include a "Relay Reject" error code for the requested CCI as part of the connection reconfiguration / UE configuration update / dedicated message. The connection reconfiguration / UE configuration update / dedicated message may also include information about other CCIs (e.g. a list of CCIs for possible combinations of PDU session parameters for which the relay UE can only relay if a normal CCI is sent to the AMF) and information about other nearby relay UEs. The connection reconfiguration / UE configuration update / dedicated message corresponds to the transport response message (N') used in other parts of this document.
[0304] Step 6:If the serving AMF of the relay UE does not reject relaying for the given CCI in step 4 / 5, the relay UE performs the PC5 unicast link security procedure [23.287] and sends a direct communication acceptance message [23.287] to the remote UE, which includes the given CCI as a (V2X) service / application identifier. The direct communication acceptance message may include some QoS information, IP configuration information (e.g. for Layer 3 relays), and some additional information about the relay. The message may also include information about other CCIs and information about other nearby relay UEs. If the serving AMF of the relay UE rejects relaying for the given CCI in step 4 / 5, the relay UE may not send any response to the remote UE, or may send a direct communication rejection message [24.587]. This can be used to send other CCIs and information about other nearby relay UEs to the remote UE. The direct communication acceptance / rejection message corresponds to the response message (N) used in other parts of this document.
[0305] Step 7: After successfully completing step 2-6, the remote UE can initiate indirect communication with the core network by using the PC5 connection established between the remote UE and the relay UE using the direct communication request / accept process, wherein the relay UE relays the traffic received from the remote UE to the network. In the case of layer 2 relay (i.e., forwarding PDCP messages), the remote UE can initiate / resume a PDU session by sending a registration / service request to the network, wherein the PDU parameters it uses (e.g., in the initial registration) need to be restricted to the configured PDU parameters associated with the CCI received in the direct communication accept message. In the case of layer 3 relay (i.e., forwarding IP packets), the remote UE will receive IP address information from the relay UE, which the remote UE can use to transmit IP traffic to the relay UE, and then forward the IP traffic to the correct destination based on the configured PDU parameters associated with the CCI. If the remote UE wants / needs to establish a PDU session using different PDU parameters (e.g., different S-NSSAI or different CAG ID / NID), the remote UE should repeat steps 2-7. In case of Layer 2 relay, each time the remote UE sets up a new PDU Session, the AMF shall verify that the PDU parameters used correspond to the CCI received in step 4. If this is not the case, the AMF may reject the PDU Session or send an RRC Reconfiguration or UE Configuration Update message to the remote UE via an indirect connection.
[0306] Various methods are provided for use in a cellular communication system as described above. A first method includes the step of performing a relay function in a mobile device. A second method includes the step of performing a relay processor function in a relay device. A third method includes the step of performing a network relay function in a cellular network.
[0307] These methods can be implemented in many different ways, as will be apparent to one skilled in the art. For example, the order of the stages or steps can be changed, or some stages can be performed in parallel. In addition, other method steps can be inserted between steps. Inserted steps can represent a refinement of the method, for example, described herein, or can be unrelated to the method.
[0308] A computer program product is provided, which can be downloaded from a network and / or stored on a computer-readable medium and / or a microprocessor-executable medium, and which includes program code instructions, which are used to implement the above-mentioned method, connection sequence, security process and other operations when executed on a computer device. Therefore, the method according to the present invention can be run using software, which includes instructions for causing a processor system to execute the corresponding method.
[0309] Typically, the mobile device, relay device and NRF each include a processor coupled to a memory containing appropriate software code stored at the device; for example, the software may have been downloaded and / or stored in a corresponding memory, such as a volatile memory such as RAM or a non-volatile memory such as a flash memory (not shown). The device may, for example, be equipped with a microprocessor and a memory (not shown). Alternatively, the device may be implemented in whole or in part with a programmable logic unit, such as a field programmable gate array (FPGA). The device and server may be implemented in whole or in part as a so-called application specific integrated circuit (ASIC), i.e., an integrated circuit (IC) customized for their specific use. For example, the circuit may be implemented in CMOS (e.g., using a hardware description language (e.g., Verilog, VHDL, etc.)).
[0310] The software may include only those steps adopted by a specific sub-entity of the system. The software may be stored in a suitable storage medium (e.g., a hard disk, a floppy disk, a memory, etc.). The software may be sent as a signal along a wired or wireless or using a data network (e.g., the Internet). The software may be downloaded and / or used remotely on a server. A bitstream arranged to configure a programmable logic unit (e.g., a field programmable gate array (FPGA)) may be used to run the method according to the present invention to perform the method. It will be appreciated that the software may be in the form of source code, object code, code intermediate source, and object code in a partially compiled form, or any other form suitable for use in an embodiment of the method according to the present invention. An embodiment relating to a computer program product includes computer executable instructions corresponding to each processing step in the processing steps of at least one of the methods described. These instructions may be subdivided into subroutines and / or stored in one or more files that may be statically or dynamically linked. Another embodiment relating to a computer program product includes computer executable instructions corresponding to each module in the modules of at least one of the systems and / or products described.
[0311] Figure 6a A computer readable medium 1000 is shown having a writable portion 1010 including a computer program 1020, the computer program 1020 including instructions for causing a processor system to perform one or more of the above methods and processes in the system described with reference to Figures 1-4. The computer program 1020 may be embodied on the computer readable medium 1000 as a physical mark or by means of magnetization of the computer readable medium 1000. However, any other suitable embodiments are also conceivable. In addition, it will be appreciated that although the computer readable medium 1000 is shown here as an optical disk, the computer readable medium 1000 may also be any suitable computer readable medium, such as a hard disk, a solid state memory, a flash memory, etc., and may be non-recordable or recordable. The computer program 1020 includes instructions for causing a processor system to perform the method.
[0312] Figure 6bA schematic representation of a processor system 1100 according to an embodiment of the device or method as described with reference to Figures 1-4 is shown. The processor system may include a circuit 1110, for example, one or more integrated circuits. The architecture of the circuit 1110 is schematically shown in the figure. The circuit 1110 includes a processing unit 1120, for example, a CPU, which is used to run a computer program component to run a method according to an embodiment and / or implement its modules or units. The circuit 1110 includes a memory 1122 for storing programming code, data, etc. Parts of the memory 1122 may be read-only. The circuit 1110 may include a communication element 1126, for example, an antenna, a transceiver, a connector, or both. The circuit 1110 may include a dedicated integrated circuit 1124, which is used to perform some or all of the processing defined in the method. The processor 1120, the memory 1122, the dedicated IC 1124, and the communication element 1126 may be connected to each other via an interconnect 1130 (e.g., a bus). The processor system 1110 may be arranged to implement wired communications and / or wireless communications using connectors and / or antennas, respectively.
[0313] It will be appreciated that, for the sake of clarity, the above description describes embodiments of the present invention with reference to different functional units and processors. However, it should be appreciated that any suitable functional distribution between different functional units or processors can be used without departing from the present invention. For example, the function performed by a separate unit, processor or controller may be performed by the same processor or controller. Therefore, reference to a specific functional unit is only considered as a reference to a suitable unit for providing the described function, rather than indicating a strict logical or physical structure or organization. The present invention can be implemented in any suitable form including any combination of hardware, software, firmware or these items.
[0314] It should be noted that in this document, the verb "comprise" does not exclude the presence of elements or steps other than those listed, and the word "one" or "an" in front of an element does not exclude the presence of multiple such elements. When a statement such as "at least one of" appears after a list of elements, such a statement means selecting all elements or any subset of the elements from the list. For example, the statement "at least one of A, B, and C" should be understood to include only A, only B, only C, both A and B, both A and C, both B and C, or all A, B, and C. Any figure mark does not limit the scope of the claim. The present invention can be implemented by means of both hardware and software. Several "modules" or "units" can be represented by the same item of hardware or software, and the processor can implement the functions of one or more units, possibly in collaboration with hardware elements to implement the functions of one or more units. In addition, the present invention is not limited to these embodiments, and the present invention lies in each novel feature or feature combination described above or recorded in different dependent claims.
[0315] In summary, the cellular communication system supports network slicing and has a network relay function for managing indirect connections. A mobile device can send a request message to a relay device, the request message including an identifier indicating the requested slice to be accessed. The response message optionally includes information indicating (one or more) available slices and / or (one or more) relay devices. The device selects a relay device based on the response message. The relay device receives the request message and sends a transmission request message to the cellular communication system, the transmission request message indicating a request to transmit data via an indirect connection and including the requested identifier, and the relay device sends a response message. The network relay function receives the transmission request message, obtains relay capability data about (one or more) relay devices that can transmit data for (one or more) available slices according to the requested slice, and sends a transmission response message including information indicating (one or more) available slices and (one or more) relay devices.
[0316] References:
[0317] [22.261] 3GPP TS 22.261 v16.7.0, Service requirements for the 5G system; Stage 1, March 2019.
[0318] [22.866] 3GPP TR 22.866 v0.2.0, enhanced Relays for Energy Efficiency and Extensive Coverage; Stage 1, February 2019.
[0319] [23.287] 3GPP TS23.287v1.0.0, Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services (version 16), May 2019.
[0320] [23.303] 3GPP TS 23.303 v15.0.0, Proximity-based services (ProSe); Stage 2, June 2017.
[0321] [23.501] 3GPP TS 23.501, System Architecture for the 5G System; Stage 2, v16.0.2, April 2019. - [23.503] 3GPP 23.503, TS Policy and charging control framework for the 5G System (5GS); Stage 2 (version 15.6.0, June 2019)
[0322] [23.733] 3GPP TR 23.733 v15.1.0, Study on Architecture Enhancements to ProSe UE-to-Network Relay (Release 15), December 2017.
[0323] [24.334] 3GPP TS 24.334 v15.1.0, Proximity-services (ProSe) User Equipment (UE) to ProSe function protocol aspects; Stage 3, December 2017.
[0324] [24.501] 3GPP TS 24.501, Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (version 15.4.0, June 2019)
[0325] [29.507] 3GPP TS 29.507, 5G System; Access and Mobility Policy Control Service; Stage 3, (Version 15.4.0, June 2019)
[0326] [33.813] 3GPP TR 33.813v0.5.0, Study on Security Aspects of Enhanced Network Slicing, June 2019. [36.300] 3GPP TS 36.300v15.2.0, Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 15), June 2018.
[0327] [36.746] 3GPP TR 36.764 v15.1.0, Study on further enhancements to LTE device to Device (D2D), User Equipment (UE) to network relays for Internet of Things (IoT) and wearables; (Release 15), December 2017. [38.300] 3GPP TS 38.300 v15.5.0, NR; NR and NG-RAN Overall Description; Stage 2, March 2019. [38.331] 3GPP TS 38.331 v15.5.1, NR; Radio Resource Control (RRC) protocol specification, April 2019.
[0328] [38.473] 3GPP TS 38.473, v15.4.1, NG-RAN; F1 application protocol (F1AP), January 2019.
[0329] [38.874] 3GPP TR 38.874v16.0.0, NR; Study on Integrated Access and Backhaul, December 2018.
[0330] [S2-1907204] 3GPP TS23.501CR1522 Introduction of the IAB support in5GS, June 2019.
[0331] [elayoubi] elayoubi et al., 5G RAN Slicing for Verticals: Enablers and Challenges (IEEE Communications Magazine, Vol. 57, No. 1, 2019).
[0332] [EventHelix] EventHelix website, https: / / www.eventhelix.com / 5g / stestalone-access-registration / , with links to pdf files with overview and detailed information.
[0333] [Pavelshulgin]5G StandAlone Access-Registration Procedure-Part2 (AMFselection procedures, slices), https: / / www.linkedin.com / pulse / 5g-standalone-access-registration-procedure-part2amf-pavel-shulgin /
Claims
1. A cellular communication system (CCS) comprising a radio access network (RAN) and a core network (CN), the radio access network comprising a plurality of cellular base stations (BSs), the cellular communication system providing a cellular network supporting network slicing and indirect connection, Each network slice provides a logical network using the shared physical infrastructure of the cellular communication system, Each indirect connection provides data transmission between a mobile device and the cellular communication system via at least one relay device, the at least one relay device being a mobile device arranged for communication with the radio access network and capable of supporting the indirect connection, The cellular communication system comprises at least one network relay entity (140), the at least one network relay entity being arranged to provide a network relay function (NRF) for managing the indirect connection, The mobile device (110) comprises: a transceiver (111) arranged for wireless communication in said cellular network (130); as well as a connection processor (112) arranged to manage a connection with the cellular network, the connection processor providing a relay function (116) for managing at least one indirect connection, The relay function is arranged to at least perform the following operations: Initiating an indirect connection procedure by sending a request message (M) to at least one relay device (UEx), the request message comprising a request identifier (ID1), the request identifier being a connection context identifier (CCI) mapped to a PDU session parameter or containing a common value, the request identifier indicating a network slice to which the mobile device (110) is requesting access; receiving at least one response message (N) from a relay device, the response message indicating at least one available slice for relaying via at least one relay device to provide an indirect connection; selecting a relay device (UEy) from the at least one relay device according to the response message; and bonding the indirect connection to the requested slice via the selected relay device; The relay device (120) comprises: a communication unit (121) arranged for communication in said cellular network (130); and a relay processor (122) arranged to manage the communications in the cellular network and arranged to manage an indirect connection between the mobile device and the cellular network, The relay processor is arranged to perform the following operations: receiving the request message (M) from the mobile device; sending a transmission request message (M') to the cellular communication system according to the request message, the transmission request message indicating a request from the mobile device to communicate with the requested slice via an indirect connection, and the transmission request message including an identifier (ID1) of the request; receiving a transmission response message (N') from said cellular communication system; sending the response message to the mobile device according to the transmission response message (N); The network relay function is arranged to perform the following operations: receiving, via at least one cellular base station, at least one transmission request message (M') including said transmission request message; obtaining relay capability data about a relay device capable of data transmission to and from the mobile device for at least one available slice, the available slice being determined based on an identifier (ID1) of the request; and At least one transmission response message (N') including the transmission response message is sent via at least one cellular base station, and the transmission response message indicates at least one relay device capable of transmitting data of the network slice to which the mobile device is requesting access.
2. The cellular communication system according to claim 1, wherein: The network relay function is arranged to determine the at least one relay device based on the received transmission request message (M') and the obtained relay capability data.
3. The cellular communication system according to claim 1, wherein: The request message (M) contains a plurality of requested identifiers (IDx), and wherein, if the requested identifiers are configured in a relay device, the relay device excludes any of the requested identifiers from the transmission request message (M').
4. The cellular communication system according to claim 1, wherein: The identifier (ID1) of the request indicates a common network slice to which the mobile device (110) is requesting access, and the request message (M) further includes an identifier (ID2) of a second request, the identifier of the second request indicating a specific network slice to which the mobile device (110) is requesting access, and wherein the relay device performs one of the following operations: sending, as part of the transmission request message (M'), an identifier (ID2) of the second request for the specific network slice instead of sending the general slice identifier (ID1); Both the identifier of the second request for the specific network slice and the common slice identifier are sent as part of the transmission request message (M'), and wherein the response message (N) only includes the identifier (ID2) of the second request for the specific network slice, and does not include the identifier (ID1) of the request for the common network slice.
5. The cellular communication system according to claim 1, wherein: The identifier (ID1) of the request includes a connection context identifier (CCI).
6. The cellular communication system according to claim 1, wherein: The request message (M) includes a security context identifier indicating a security context or a security key, and the relay processor is arranged to: send the transmission request message (M') to the cellular communication system according to the request message only when the security context or security key indicated by the security context identifier corresponds to the security context or security key configured in the relay device; and if there is no match, not send the transmission request message (M').
7. A cellular communication system as claimed in claim 1, wherein: The indirect connection to the requested slice is set on the same logical data connection as the logical data connection via which the request message (M) and the response message (N) are sent, and the logical data connection is at least one of a PC5 connection, a side link connection or a D2D connection.
8. The cellular communication system according to claim 1, wherein: The network relay function (NRF) uses the requested identifier (ID1) to retrieve a set of protocol data unit (PDU) session parameters including a network slice identifier, and the NFR configures the PDU session of the relay device and / or the mobile device based on at least one parameter in the retrieved set of PDU session parameters.
9. The cellular communication system according to claim 1, wherein: The NRF uses the identifier (ID1) of the request to retrieve a set of PDU session parameters including an identifier referring to a non-public network, and the NRF configures the PDU session of the relay device to connect to a cellular base station (BS), the cellular base station being configured to broadcast the identifier referring to the non-public network as part of its system information, and / or the cellular base station being configured to report the identifier referring to the non-public network to the core network (CN) when the relay device is directly connected to the cellular base station or the mobile device is indirectly connected to the cellular base station via the relay device.
10. The cellular communication system according to claim 1, wherein: The NRF uses the requested identifier (ID1) to contact a different Public Mobile Land Network (PLMN) to retrieve a set of PDU session parameters including a network slice identifier.
11. The cellular communication system of claim 1, wherein The transmission response message (N') includes network relay information indicating a set (T) of relay devices; and / or The response message (N) includes a set (T) of relay devices.
12. The cellular communication system of claim 1, wherein: The network relay entity (140) is arranged to: determine that there is no relay device capable of transmitting data to and from the mobile device (116) that is capable of transmitting slices that accommodate the requested identifier; and when it is determined that this is the case, send a slice denial message to the relay device and / or the mobile device, the slice denial message indicating that there is no relay device capable of transmitting data for slices that accommodate the requested identifier.
13. The cellular communication system of claim 1, wherein: The network relay entity (140) is arranged to: determine that the indirect connection engaged from the mobile device via the selected relay device is addressed to the requested slice; and if the indirect connection is addressed to a different slice, perform one or more of the following actions: sending a PDU session reject message to the mobile device via the indirect network connection; Sending a slice denial message to the relay device and / or the mobile device; reconfigure relay mobile equipment; Terminates the relay connection.
14. The cellular communication system of claim 1, wherein: The connection processor in the mobile device is arranged to: Starts the relay discovery process and engages the initial indirect connection, and then sending the request message via the initial indirect connection; and Therein, the network relay entity (140) or the relay function is arranged to reconfigure the initial indirect connection so that the indirect connection goes to the selected slice via the selected relay device.
15. The cellular communication system of claim 1, wherein: The relay processor in the relay device is arranged to perform the following operations: A preliminary response message (N**) is sent to the mobile device according to the request message (M); the preliminary response message indicates that the relay device exists, but according to the transmission response message (N'), the response message (N) will be sent to the mobile device later.
16. The cellular communication system of claim 1, wherein: The identifier of the request includes a set of requested network slices, and wherein the network relay entity (140) is arranged to determine at least a subset of the set of available slices that accommodates the requested network slices, and at least one relay device capable of transmitting data of the subset of available slices and / or the response message (N) contains the determined subset of available slices, at which time the mobile device selects one of the available slices to be indirectly connected to the selected slice via the relay device from which the mobile device receives the response message (N).
17. The cellular communication system of claim 1, wherein: The network relay entity (140) is arranged to determine additional relay capability data about at least one relay device, the additional relay capability data indicating a preference or suitability to act as a relay; The transmission response message (N') includes the additional relay capability data; and / or Said response message (N) comprises at least part of said additional relay capability data.
18. The cellular communication system of claim 1, wherein: The network relay entity (140) is arranged to perform the following operations: determining multi-hop relay capability data for at least one multi-hop indirect connection implemented via a plurality of hops using a plurality of relay devices, the multi-hop relay capability data indicating available slices via the multi-hop indirect connection; The transmission response message (N') includes the multi-hop relay capability data; and / or The response message (N) comprises at least part of the multi-hop relay capability data; or wherein the network relay entity (140) is arranged to perform the following operations: determining the available relay devices for the requested slice based on an achievable QoS; or Determine which relay devices to use first based on the attributes or requirements of the corresponding slices.
19. The cellular communication system of claim 1, wherein: The request message includes one or more of the following: security information about security credentials or a security context in which the mobile device operates or is required to operate for the indirect connection, or about an identifier associated with the request; Status information indicating the reason for requesting relay; Received signal strength of messages received from nearby devices; The device includes power information about a power source of the mobile device.
20. The cellular communication system of claim 1, wherein: The network relay entity (140) is arranged to obtain metadata, such as received signal strength, signal quality or distance estimation results, from the cellular communication system; or, The transmission request message includes metadata identifying a current connection state, the current connection state including: a network connection mode, quality of service (QoS) and number of hops, connection stability information and / or a frequency band in use or a supported frequency band of the relay device, and, Therein, the network relay entity (140) is arranged to determine the transmission response message according to the metadata.
21. A relay device (120) for use in a cellular communication system according to any one of claims 1 to 20, the relay device (120) comprising: a communication unit (121) arranged for communication in said cellular network (130); as well as a relay processor (122) arranged to manage the communications in the cellular network and arranged to manage an indirect connection between the mobile device and the cellular network, the relay processor being arranged to: receiving the request message (M) from the mobile device, the request message comprising an identifier (ID1) indicating a request for a network slice to which the mobile device (110) is requesting access, wherein the relay device has sent the transmission request message (M') in response to receiving the request message (M) at the relay device, the mobile device sending the request message to initiate an indirect connection procedure; sending a transmission request message (M') to the cellular communication system according to the request message, the transmission request message indicating a request from the mobile device to communicate with the requested slice via an indirect connection, and the transmission request message including an identifier (ID1) of the request; receiving a transmission response message (N') from said cellular communication system; sending the response message to the mobile device according to the transmission response message (N), Wherein, the requested identifier (ID1) includes a connection context identifier (CCI), and the relay processor is arranged to reconfigure a protocol data unit (PDU) session between the relay device and the network to accommodate relay network traffic for a specific slice associated with the CCI.
22. The relay device (120) according to claim 21, wherein: The requested identifier (ID1) includes a connection context identifier (CCI), and the relay processor is arranged to initiate an additional protocol data unit (PDU) session between the relay device and the network to accommodate relay network traffic for a specific slice associated with the CCI.
23. A network relay entity (140) providing a network relay function (NRF) for use in a cellular communication system as claimed in any one of claims 1 to 20, the network relay entity being arranged to: receiving at least one transmission request message (M') via at least one cellular base station, including a transmission request message (M') sent by a relay device in response to the request message (M), wherein, the relay device having sent the transmission request message (M') in response to receiving a request message (M) at the relay device, the mobile device sending the request message to initiate an indirect connection procedure; obtaining relay capability data about a relay device capable of data transmission to and from the mobile device for at least one available slice, the available slice being determined based on an identifier (ID1) of the request, the identifier of the request indicating a network slice to which the mobile device (110) is requesting access; and At least one transmission response message (N') is sent via at least one cellular base station, and the transmission response message including network relay information indicates at least one relay device capable of transmitting data of the requested slice.
24. A method for use in a cellular communication system as claimed in any one of claims 1 to 20, the method comprising the step of performing the relay function in the mobile device, the step comprising: managing at least one indirect connection; Sending a request message (M) to at least one relay device (UEx) to initiate an indirect connection procedure, the request message comprising a request identifier (ID1), the request identifier being a connection context identifier (CCI) mapped to a PDU session parameter or containing a common value, the request identifier indicating a network slice to which the mobile device (110) is requesting access; receiving at least one response message (N) from at least one relay device, the response message indicating at least one available slice for relaying via at least one relay device to provide an indirect connection; Selecting a relay device (UEy) from the at least one relay device according to the response message; and The indirect connection is joined to the requested slice via the selected relay device.
25. A method for use in a cellular communication system according to any one of claims 1 to 20, the method comprising a step of performing the relay function in the relay device, the step comprising: managing said communications in said cellular network; managing an indirect connection between the mobile device and the cellular network; receiving the request message (M) from the mobile device, the request message comprising an identifier (ID1) indicating a request for a network slice to which the mobile device (110) is requesting access; sending a transmission request message (M') to the cellular communication system according to the request message, the transmission request message indicating a request from the mobile device to communicate with the requested slice via an indirect connection, and the transmission request message including an identifier (ID1) of the request; receiving a transmission response message (N') from said cellular communication system; sending the response message to the mobile device according to the transmission response message (N), wherein the identifier of the request is a connection context identifier (CCI), and the transmission response message (N') includes instructions for reconfiguring an existing protocol data unit (PDU) session between the relay device and the network to accommodate traffic for a specific slice associated with the CCI, and the method includes reconfiguring the PDU session.
26. The method of claim 25, wherein: The transport response message (N') includes instructions for initiating an additional protocol data unit (PDU) session between the relay device and the network to accommodate traffic for a specific slice associated with the CCI, and the method includes starting the additional PDU session.
27. A method for use in a cellular communication system as claimed in any one of claims 1 to 20, the method comprising steps of performing the network relay function in the network, the steps comprising: Receiving at least one transmission request message (M') from a relay device via at least one cellular base station, the transmission request message comprising an identifier (ID1) indicating a request for a network slice to which a mobile device (110) is requesting access, the identifier of the request being a connection context identifier (CCI) mapped to a PDU session parameter or containing a common value, wherein the relay device has sent the transmission request message (M') in response to receiving the request message (M) at the relay device, the mobile device sending the request message to initiate an indirect connection procedure; obtaining relay capability data about a relay device capable of data transmission to and from the mobile device for at least one available slice, the available slice being determined based on an identifier (ID1) of the request; and At least one transmission response message (N') is sent via at least one cellular base station, wherein the transmission response message including network relay information indicates at least one available slice and at least one relay device, and the at least one relay device is capable of transmitting data of the available slice.
28. The method of claim 27, wherein the transmission request message includes an identifier (ID1) of the request, the NRF is using the identifier (ID1) of the request to retrieve a set of PDU session parameters, the set of PDU session parameters including a network slice identifier, and the transmission response message includes instructions for reconfiguring an existing PDU session between the relay device and the network to accommodate relay network traffic for the available slice, or the method starts an additional PDU session.
29. The method of claim 27, wherein the transmission request message includes an identifier (ID1) of the request, the NRF is using the identifier (ID1) of the request to retrieve a set of PDU session parameters, the set of PDU session parameters including a network slice identifier, and the transmission response message includes instructions for starting an additional PDU session between the relay device and the network to accommodate relay network traffic for the available slice.
30. A computer program product that can be downloaded from a network and / or stored on a computer-readable medium and / or a microprocessor-executable medium, the product comprising program code instructions for implementing the method of any one of claims 24 to 29 when the program code instructions are executed on a computing device.
