Apparatus, methods, and computer programs

Abstract

A method comprises receiving information at a first network entity indicating a first data network identity associated with a request from a communications device; and selecting at the first network entity a second data network identity which is usable with respect to the communications device when said first data network identity is not usable with respect to said communications device, said selecting being in dependence on information associated with said communications device.

Claims

1. An apparatus comprising: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: cause a request to be sent to a first network entity that said first network entity notify said apparatus when said first network entity determines that a request originating from a communications device comprises a data network identity which is configured to identify a data network for a data session with the communications device and which is not usable with respect to said communications device, wherein said request to notify said apparatus is to cause a first data network identity associated with a request from said communications device and not supported by said network to be replaced by a second data network identity supported by said network.

2. The apparatus as claimed in claim 1, wherein the data network identity which is not usable with respect to said communications device is one or more of: not supported by said network; not permitted in relation to said communications device; not permitted by a policy associated with the communications device; or not permitted by a subscription associated with the communications device.

3. The apparatus as claimed in claim 1, wherein said first network entity comprises an access and mobility management function.

4. The apparatus as claimed in claim 1, further comprising a policy control function.

5. An apparatus comprising at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: determine information about a misconfiguration of communications device by a request originating from the communications device and comprising a data network identity which is configured to identify a data network for a data session with the communications device and which is one or more of: not supported by a network, not permitted in relation to said communications device, not permitted by a policy associated with said communications device, or not permitted by a subscription associated with said communications device; and cause information to be provided to a third network entity about said determined misconfiguration of said communications device, wherein providing said information to said third network entity is to cause a first data network identity associated with a request from said communications device and not supported by said network to be replaced by a second data network identity supported by said network.

6. The apparatus as claimed in claim 5, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform: receive a request from the third network entity requesting that said apparatus notify said third network entity when said apparatus determines a misconfiguration of a communications device.

7. The apparatus as claimed in claim 5, wherein determining said misconfiguration comprises determining one or more of: a request associated with the communications device comprises a data network identity which is not usable with respect to said communications device; a request associated with the communications device indicates a session type which is not usable with respect to said communications device; a request associated with the communications device indicates single network slice selection assistance information which is not usable with respect to said communications device; or a request associated with the communications device indicates a session and service continuity mode which is not usable with respect to said communications device.

8. The apparatus as claimed in claim 5, wherein said third network entity comprises a policy control function.

9. The apparatus as claimed in claim 5, further comprising an access and mobility management function.

10. An apparatus comprising at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: receive a request from a first network entity comprising a first data network identity associated with a request from a communications device and a second data network identity selected by said network to replace said first data network identity, wherein each of the first data network identity and the second data network identity is configured to identify a data network for a data session with the communications device, and wherein said first data network identity is one or more of: a data network identity not supported by said network, a data network identity not permitted in relations to said communications device, a data network identity not permitted by a policy associated with said communications device, or a data network identity not permitted by a subscription associated with said communications device; and provide a response to said request, said response to be directed to said communications device and comprising at least one of said second data network identity and said first data network identity.

11. The apparatus as claimed in claim 10, wherein said second data network identity is a data network identity supported by said network, selected to replace a first data network identity not supported by said network.

12. The apparatus as claimed in claim 10, wherein said first network entity comprises an access and mobility management function.

13. The apparatus as claimed in claim 10, further comprising a session management function.

Description

BRIEF DESCRIPTION OF THE FIGURES

(1) Embodiments will now be described, by way of example only, with reference to the accompanying Figures in which:

(2) FIG. 1 shows a schematic representation of a communication system;

(3) FIG. 2 shows a schematic representation of a communications device;

(4) FIG. 3 shows a schematic representation of an apparatus;

(5) FIG. 4 shows a schematic representation of a non-volatile memory medium storing instructions which when executed by a processor allow a processor to perform one or more of the steps of the method of some embodiments;

(6) FIG. 5 shows a signalling flow of some embodiments;

(7) FIG. 6 shows a method of some embodiments performed in a first network entity;

(8) FIG. 7 shows a method of some embodiments performed in a second network entity;

(9) FIG. 8 shows a method of some embodiments performed in a third network entity;

(10) FIG. 9 shows a method of some embodiments performed in a communications device; and

(11) FIG. 10 shows another method of some embodiments.

DETAILED DESCRIPTION OF THE FIGURES

(12) In the following certain embodiments are explained with reference to communications devices capable of communication via a wireless cellular system and communication systems serving such communications devices. Before explaining in detail the exemplifying embodiments, certain general principles of a wireless communication system, access systems thereof, and communications devices are briefly explained with reference to FIGS. 1 to 4 to assist in understanding the technology underlying the described examples.

(13) An example of wireless communication systems are architectures standardized by the 3rd Generation Partnership Project (3GPP). A latest 3GPP based development is often referred to as 5G. Other examples of radio access system comprise those provided by base stations of systems that are based on technologies such as wireless local area network (WLAN) and/or WiMAX (Worldwide Interoperability for Microwave Access). It should be appreciated that although some embodiments are described in the context of a 5G system, other embodiments may be provided in any other suitable system including but not limited to subsequent systems or similar protocols defined outside the 3GPP forum.

(14) Reference is made to FIG. 1 which shows an example system in which some embodiments may be provided. The system may be a wireless communications. It should be appreciated that the system of FIG. 1 is a 5G system but other embodiments may be used in association with any other suitable standard or system.

(15) A communications device 102 is provided. This will be referred to as a UE but it should be appreciated that the device may be any suitable communications device and the term UE is intended to cover any such device. Some examples of communications devices are discussed below and as used in this document the term UE is intended to cover any one or more of those devices and/or any other suitable device.

(16) The communications device has a wireless connection to an access node AN 104. This access node may be a gNB or a ng-eNB. It should be appreciated that the information exchange between the UE and the AMF may alternatively take place over a non 3GPP access to the 5GC (5G core network.). For example this may be over a non 3GPP interworking function for non-3gpp access N3IWF, a trusted non 3GPP access function TNGF, an access gateway for wireline access W-AGF, or any other similar function.

(17) The AN 104 is configured to communicate with an access and mobility management function (AMF) 110. The AMF may provide functions which relate to UE-based authentication, authorisation, registration, mobility and/or connection management.

(18) The AMF 110 is configured to communicate with a session management function (SMF) 112. The SMF may provide session management functions, such allocating Internet Protocol (IP) addresses to UEs.

(19) The AMF 110 and the SMF 112 are configured to communicate with a policy control function (PCF) 114. The PCF may determine policies about mobility and session management for a given UE for the UE, AMF or SMF to enforce.

(20) The access node AN 104 is configured to communicate with a user plane function (UPF) 106. The UPF 106 is configured to communicate with a data network DN 108.

(21) FIG. 2 illustrates an example of a communications device 300, such as the wireless communications device 102, 104 or 105 shown on FIG. 1. The wireless communications device 300 may be provided by any device capable of sending and receiving radio signals. Non-limiting examples comprise a mobile station (MS) or mobile device such as a mobile phone or what is known as a ‘smart phone’, a computer provided with a wireless interface card or other wireless interface facility (e.g., USB dongle), personal data assistant (PDA) or a tablet provided with wireless communication capabilities, machine-type communications (MTC) devices, IoT type communications devices or any combinations of these or the like.

(22) The device 300 may receive signals over an air or radio interface 307 via appropriate apparatus for receiving and may transmit signals via appropriate apparatus for transmitting radio signals. In FIG. 2 transceiver apparatus is designated schematically by block 306. The transceiver apparatus 306 may be provided for example by means of a radio part and associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device.

(23) The wireless communications device 300 may be provided with at least one processor 301a and at least one memory. The at least one memory may comprise at least one ROM 302a and/or at least one RAM 302b. The communications device may comprise other possible components 303 for use in software and hardware aided execution of tasks it is designed to perform, including control of access to and communications with access systems and other communications devices. The at least one processor 301 is coupled to the at least one memory. The at least one processor 301 may be configured to execute an appropriate software code 308 to implement one or more of the following aspects. The software code 308 may be stored in the at least one memory, for example in the at least one ROM 211b.

(24) The processor, storage and other relevant control apparatus can be provided on an appropriate circuit board and/or in chipsets. This feature is denoted by reference 304.

(25) The device may optionally have a user interface such as key pad 305, touch sensitive screen or pad, combinations thereof or the like.

(26) Optionally one or more of a display, a speaker and a microphone may be provided depending on the type of the device.

(27) Communication protocols and/or parameters which shall be used for the connection are also typically defined. The communications devices may access the communication system based on various access techniques.

(28) An example apparatus is shown in FIG. 3. FIG. 3 shows an example of an apparatus 200 for a network function such as an AMF or PCF or SMF any other suitable function. The apparatus comprises at least one memory. The at least one memory may be at least one random access memory (RAM) 211a and/or at least one read only memory (ROM) 211b, at least one processor 212, 213 and an input/output interface 214. The at least one processor 212, 213 is coupled to the RAM 211a and the ROM 211b. The at least one processor 212, 213 may be configured to execute an appropriate software code 215 to implement one or more of the following aspects. The software code 215 may be stored in the ROM 211b.

(29) FIG. 4 shows a schematic representation of non-volatile memory media 1600a (e.g. computer disc (CD) or digital versatile disc (DVD)) and 1200b (e.g. universal serial bus (USB) memory stick) storing instructions and/or parameters 1602 which when executed by a processor allow the processor to perform one or more of the steps of any of the methods of any of the embodiments.

(30) One or more of the following aspects relate to a 5G system (5GS). (5G is sometimes referred to as new radio (NR)). However, it will be understood that some of these aspects may be transposed to other radio access technology systems such as UTRAN (3G radio), the long-term evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) and/or any other suitable system.

(31) In some embodiments, a first network entity such as an AMF may receive from N1 signalling from the UE information indicating a first (requested) data network identity or data network name (DNN).

(32) The first network entity may detect that this first (requested) data network identity is either not supported by the network and/or not allowed by the subscription and/ policy related with the UE.

(33) The first network entity may take into account further information in the UE subscription and/or UE request, and select a second (accepted) data network identity (DNN) which is supported in the network and by the user related subscription and/or policy.

(34) If the first network entity chooses to replace the UE requested DNN by a second (accepted) DNN, then the first network entity uses the second DNN for the remainder of the procedure, including passing the second (accepted) DNN to a second network entity to be used for PDU session related operations. The second network entity may be the SMF.

(35) The first network entity may also pass to the second network entity an indication on whether the second network entity is expected to include the UE requested or the second (accepted) DNN in the SMF response to the UE. This response may be a PDU session establishment accept response. This indication may be implicit (by including both the UE requested DNN and second DNN) or explicit, by including a specific indicator on which DNN to send to the UE.

(36) The data used by the first entity to determine whether it needs to consider another DNN (second data network identity) other than the UE requested DNN may comprise one or more of: data identifying an expected service set; service related data; and capabilities of the communications device.

(37) In some embodiments, the data identifying an expected service set may be S-NSSAI (single network slice selection assistance information) data or the like. A network slice is a logical end to end network. Each slice may serve a particular service type. A communications device may access a plurality of slices over the same (R)AN (or 5G AN entity connecting the UE to the 5GC), for example. The S-NSSAI is used to identify a network slice that supports a specific set of services. In some embodiments, a S-NSSAI may comprise a SST (slice/service type) and/or a SD (slice differentiator). The AMF may only take into account the SST or may take into account the full S-NSSAI when performing the selection of the second (accepted) data network identity (DNN).

(38) The SST refers to the network slice behaviour in terms of features and services. In some embodiments, the SST may identify one of eMBB (enhanced mobile broadband), URLLC (ultra reliable low latency communications), or MIoT (massive internet of things). It should be appreciated that alternatively or additionally the SST may identify any other suitable service type.

(39) The SD differentiates different slices of the same slice/service type. The S-NSSAI may be associated with one or more of a network ID such as a PLMN ID, network specific values, standard values.

(40) The S-NSSAI may be provided by the UE or may be a subscribed S-NSSAI identifying an expected service set.

(41) The capabilities of the communications device related data may comprise, for example CIoT (cellular IoT) capabilities in some embodiments. This may be provided by the communications device. This information may be provided as part of a communications device's preferred network behaviour. Alternatively or additionally, different device capability data may be provided.

(42) The service related data may be provided by the communications device and/or contained in subscription data.

(43) In some embodiments, the AMF may, based on one or more of the above criteria, replace the communications device requested explicit (that is non empty) DNN value by another DNN value. The AMF may inform the PCF that a DNN configuration issue in UE has been detected. The PCF updates the UE (communications device) policy of the communications device. This policy is updated as the previous policy was out-of-date, in that a non-supported DNN was requested by the communications device. The AMF notification to the PCF may be controlled by an explicit request from the PCF in order for the AMF to request a policy update from the PCF (indicating that a DNN configuration issue in UE has been detected) when the AMF has detected such UE configuration issue.

(44) This update of the policy provides a mechanism whereby those communications devices UE(s) whose configuration is outdated are determined and a repair of the configuration policy is triggered.

(45) The AMF indication that a DNN configuration issue in UE has been detected may trigger the PCF to perform a UE policy configuration (URSP-UE route selection policy) update.

(46) Some embodiments provide a method whereby an AMF is able to decide which one of the supported DNNs to use instead of the non-supported DNN that was requested by the communications device.

(47) One example of the interaction between the communications device, the AMF and the PCF will now be described with reference to FIG. 5.

(48) In step S1, the PCF, as part of policy information sent to the AMF about an UE, sends to the AMF a request to be notified when a configuration issue in the UE has been detected. This may be a misconfiguration issue in the UE. In some embodiments, this configuration issue may be a DNN issue. However in other embodiments, this misconfiguration issue may be any other suitable misconfiguration issue.

(49) This request may be for specific communications devices or any of the UEs for which the PCF stores policy information. The notification from the AMF may be any suitable update. In some embodiments, the notification may be a Npcf_AMPolicyControl_Update message.

(50) In step S2, the UE sends a PDU (protocol data unit) session establishment request to the 5GC (5G core network) that is handled by the AMF. The UE may provide a requested DNN that the AMF needs to consider as the AMF needs the DNN for SMF selection.

(51) In step S3, the AMF determines that there is an issue with the DNN that was requested by the UE.

(52) This issue may be that the DNN in the request is not supported by the network or by the subscription of the UE. In such a case, the AMF may select a supported DNN. This may be as previously described. This selection may take into account one or more of the S-NSSAI information, UE capability information (e.g. CIoT support and preferred network behaviour) and the subscription information related to the S-NSSAI and/or CIoT.

(53) After replacing the UE requested DNN with a supported DNN, the AMF uses that replaced DNN that is supported in the network for to select the SMF. In step S4, the AMF sends a PDU session request to the SMF. The request may comprise the updated DNN and optionally the UE requested DNN. The AMF may optionally pass to SMF an indication on whether the SMF is expected to include the UE requested or the second (accepted) DNN in the SMF response to the UE. This indication may be implicit (by including both UE requested DNN and second DNN) or explicit, by including a specific indicator on which DNN to send to the UE.

(54) The SMF includes a DNN in PDU session related procedures. The DNN or DNNs which are included may be dependent on the information received from the AMF. For example, in step S5, the SMF sends a PDU session accept message to the AMF with the updated DNN.

(55) The PDU session accept message provided by the SMF to AMF may be directed by the AMF to the UE in step S6.

(56) The AMF may indicate to the SMF (in step S4) whether the replaced DNN can be shown to the UE or if the DNN replacement needs to be done inside the network only and hidden from the UE. The UE may include the requested DNN in its request (see step S2) message and the SMF includes a DNN in a SMF reply message such as a PDU session establishment accept message (This may be the message of step S5). The message from the SMF may be transported by the AMF in a downlink container. The AMF may not be expected to open up the SMF container or to change its contents. The AMF therefore needs to tell the SMF what value to send where the DNN requested by the UE has been changed. For example, the AMF informs the SMF whether to use the replaced DNN or the UE requested DNN in the message directed towards the UE (in step S6).

(57) It should be appreciated that the SMF may use the UE requested DNN in the response message. This may be the case where for example the DNN value is updated by the PCF as will be described later. However in some embodiments, the SMF may use the updated DNN value even if the DNN value is updated by the PCF as described later.

(58) It should be appreciated that in some embodiments, where the SMF uses the UE requested DNN value in its messages, the core network components may be using the updated DNN value.

(59) As mentioned, the AMF may be configured (by the PCF in step S1) to determine that a PCRT (policy control request trigger) condition has occurred when a DNN configuration issue in the communications device is detected.

(60) In some embodiments, this condition may be set up by the PCF at the initialization of an AMF-PCF association related to the policies for an UE.

(61) In some embodiments, this condition may be torn down or removed as a trigger condition by the PCF.

(62) In step S7, when the AMF detects a DNN configuration issue in a communications device condition, the AMF issues an update to the PCF. This may be a Npcf_UEPolicyControl_Update message or any other message to the PCF. This update message may comprise one or more of: the S-NSSAI received from the UE, the corresponding S-NNSAI used by the HPLMN (home public land mobile network) if different and the DNN received from the UE.

(63) In step S8, this update message may trigger the PCF to update information associated with the communications device. This may ensure that the UE has the updated DNN. The UE may store the updated DNN. For example, the PCF may update the URSP associated with the communications device. The update from the PCF to UE may comprise an update to URSP rules. The URSP rules indicate which DNN the UE shall use to carry the traffic of an application. When this application is started on the UE, the UE is to ensure that a PDU session towards the DNN configured in the URSP is established. In some embodiments, the UE will store the new or updated URSP rules that have the updated DNN.

(64) In some embodiments, steps S7 and S8 may run in parallel with steps S4 to S6 or even take place before those steps.

(65) Steps S1, S7 and S8 may be omitted in some embodiments.

(66) In some embodiments step S6 may be omitted.

(67) In another embodiment, the AMF may determine that there is an issue with the DNN. When an issue is determined, the AMF may cause the SMF return a response to the UE with the updated DNN. The UE will then update it stored DNN to the updated DNN and use that updated DNN in the future. In some embodiments, the response from the network corresponds to a PDU session accept response of step S6 which originates from the SMF. This message may thus be used by the UE to detect that the network has replaced the UE requested DNN by another DNN that the serving network wants to use instead of the UE requested DNN. The UE could in such case store the updated DNN that was replaced by the network in order to use it instead of the DNN that was requested by the UE, or as an alias of the DNN that was requested by the UE. In this way, the network indicates to the UE dynamically that the DNN requested by the UE is not valid, and the UE should start using another (“updated”) DNN instead of the one that it requested. In such an embodiment, steps S1, S7 and S8 may be omitted.

(68) It should be appreciated the 5GC (5G core network) supports a PDU connectivity service i.e. a service that provides exchange of PDUs between a communications network and a data network identified by a DNN. The PDU connectivity service may be supported via PDU Sessions that are established upon request from the communications device.

(69) The subscription information for each S-NSSAI may contain a subscribed DNN list and one default DNN. When the communications device does not provide a DNN in a NAS (non access stratum message) containing a PDU session establishment request for a given S-NSSAI, the serving AMF determines the DNN for the requested PDU session by selecting the default DNN for this S-NSSAI if a default DNN is present in the subscription Information. Otherwise the serving AMF selects a DNN that corresponds with this S-NSSAI. This may be as previously described.

(70) If the DNN provided by the communications device is not supported by the network and the AMF cannot select an SMF by querying NRF (as e.g. the NRF does not provide SMF supporting the requested DNN either in HPLMN or in the local PLMN), the AMF replaces the unsupported DNN by a supported DNN. This may be as outlined previously. When determining which DNN value to use, the AMF may consider the S-NSSAI and the UE preferred network behaviour indicated by the UE or subscription data or both.

(71) Reference is made to FIG. 6 which shows a method of some embodiments. This method may be performed in a first network entity or by an apparatus in the first network entity. The apparatus may comprise at least one processor and at least one memory including computer code for one or more programs, the at least one memory and the computer code configured, with the at least one processor, to cause the apparatus at least to perform the method of FIG. 6.

(72) In step A1, the first network receives information indicating a first data network identity associated with a request from a communications device.

(73) In step A2, the first network entity selects a second data network identity which is usable with respect to the communications device when said first data network identity is not usable with respect to said communications device, said selecting being in dependence on information associated with said communications device.

(74) The first network entity may be an AMF or any other suitable network entity.

(75) Reference is made to FIG. 7 which shows a method of some embodiments. This method may be performed in a second network entity or by an apparatus in the second network entity. The apparatus may comprise at least one processor and at least one memory including computer code for one or more programs, the at least one memory and the computer code configured, with the at least one processor, to cause the apparatus at least to perform the method of FIG. 7.

(76) In step B2, the second network entity receives a request from a first network entity comprising a first data network identity associated with a request from a communications device and which is not usable with respect to said communications device and a second data network identity which is usable with respect to the communications device.

(77) In step B2, the second network entity provides a response to said request, said response to be directed to said communications device and comprising at least one of said second data network identity and said first data network identity.

(78) The second network entity may be an SMF or any other suitable network function.

(79) Reference is made to FIG. 8 which shows a method of some embodiments. This method may be performed in a third network entity or by an apparatus in the third network entity. The apparatus may comprise at least one processor and at least one memory including computer code for one or more programs, the at least one memory and the computer code configured, with the at least one processor, to cause the apparatus at least to perform the method of FIG. 8.

(80) In step C1, the third network entity causes a request to be sent to a first network entity that said first entity notify said third network entity when said first network entity selects a second data network identity which is usable with respect to a communications device when a first data network identity is not usable with respect to said communications device, said first data network identity being associated with a request from the communications device.

(81) In step C2, the third network entity receives a notification from said first network entity when said first network entity selects the second data network identity, said notification comprising said second data network identity and optionally said first data network identity.

(82) The third network entity may be a PCF or any other suitable network function.

(83) Reference is made to FIG. 9 which shows a method of some embodiments. This method may be performed in a communications device or by an apparatus in the communications device. The apparatus may comprise at least one processor and at least one memory including computer code for one or more programs, the at least one memory and the computer code configured, with the at least one processor, to cause the apparatus at least to perform the method of FIG. 9.

(84) In step D1, the communications device causes a request to be sent with a first data network identity.

(85) In step D2, the communications device receives information indicating that said first data network identity is updated to a second data network identity.

(86) Reference is made to FIG. 10 which shows another embodiment.

(87) In step T1, a network function receives from a PCF 114 a request that the network function notify the PCF when there is a misconfiguration of a communications device. That network function may be an AMF, a SMF or any other suitable network function. This step may be optional in some embodiments.

(88) In step T2, the network function determines that there is a misconfiguration of the communications device.

(89) In step T3, the network functions causes a notification of the misconfiguration to be provided to the PCF.

(90) By way of example, the AMF detects in step T2 a UE request for PDU Session establishment targeting an unknown DNN or a DNN that is not subscribed by the user (as previously described). In this case it is the AMF that notifies the PCF in step T3.

(91) In another example, the AMF of the HPLMN detects in step T2 a UE request for registration targeting an unknown S-NSSAI or a S-NSSAI that is not subscribed by the user. In this case it is the AMF that notifies the PCF in step T3.

(92) In another example, the SMF detects in step T2 a UE request for PDU Session establishment targeting an unknown PDU session type or a PDU session type that is not subscribed by the user or that is incompatible with the DNN. In this case it is the SMF that notifies the PCF in step T3.

(93) In another example, the SMF detects in step T2 a UE request for PDU session establishment targeting an unknown SSC (session and service continuity) mode or a SSC mode that is not subscribed by the user or that is incompatible with the DNN. In this case it is the SMF that notifies the PCF in step T3.

(94) It is noted that while the above describes example embodiments, there are several variations and modifications which may be made to the disclosed solution without departing from the scope of the present invention. For example, the above aspects are not limited to 5GS. These aspects may be transposed to other radio access technology systems.

(95) The embodiments may thus vary within the scope of the attached claims. In general, some embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although embodiments are not limited thereto. While various embodiments may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

(96) The embodiments may be implemented by computer software stored in a memory and executable by at least one data processor of the involved entities or by hardware, or by a combination of software and hardware. Further in this regard it should be noted that any procedures, e.g., in FIGS. 5 to 10 may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software may be stored on such physical media as memory chips, or memory blocks implemented within the processor, magnetic media such as hard disk or floppy disks, and optical media such as for example DVD and the data variants thereof, CD.

(97) The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The data processors may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASIC), gate level circuits and processors based on multi-core processor architecture, as non-limiting examples.

(98) Alternatively or additionally some embodiments may be implemented using circuitry. The circuitry may be configured to perform one or more of the functions and/or method steps previously described. That circuitry may be provided in the base station and/or in the communications device.

(99) As used in this application, the term “circuitry” may refer to one or more or all of the following:

(100) (a) hardware-only circuit implementations (such as implementations in only analogue and/or digital circuitry);

(101) (b) combinations of hardware circuits and software, such as: (i) a combination of analogue and/or digital hardware circuit(s) with software/firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as the communications device or base station to perform the various functions previously described; and

(102) (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

(103) This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example integrated device.

(104) The foregoing description has provided by way of exemplary and non-limiting examples a full and informative description of some embodiments However, various modifications and adaptations may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the teachings will still fall within the scope as defined in the appended claims.