WO2021028050A1 - Apparatus, methods, and computer programs - Google Patents
Apparatus, methods, and computer programs Download PDFInfo
- Publication number
- WO2021028050A1 WO2021028050A1 PCT/EP2019/071871 EP2019071871W WO2021028050A1 WO 2021028050 A1 WO2021028050 A1 WO 2021028050A1 EP 2019071871 W EP2019071871 W EP 2019071871W WO 2021028050 A1 WO2021028050 A1 WO 2021028050A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- message
- request
- response
- access node
- communications mode
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/24—Negotiation of communication capabilities
Definitions
- the present disclosure relates to an apparatus, methods, and computer programs and in particular but not exclusively for apparatus, methods and computer programs to be used in a communications system.
- a communication system can be seen as a facility that enables communication sessions between two or more entities such as user terminals, base stations/access points and/or other nodes by providing carriers between the various entities involved in the communications path.
- a communication system can be provided for example by means of a communication network and one or more compatible communications devices.
- Access to the communication system may be by means of an appropriate communications device or terminal.
- a communications device is provided with an appropriate signal receiving and transmitting apparatus for enabling communications, for example enabling access to a communication network or communications directly with other communications device.
- the communications device may access a carrier provided by a station or access point, and transmit and/or receive communications on the carrier.
- the communication system and associated devices typically operate in accordance with a given standard or specification which sets out what the various entities associated with the system are permitted to do and how that should be achieved.
- an apparatus comprising 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: cause a request to be provided from a core network entity to a radio access node for information indicating if a communications device is using or supporting a communications mode associated with one or more given communication categories; and receive a response comprising an indication from the radio access node which indicates that the communication device is using or supporting the communications mode when said communications device is using or supporting said communications mode.
- the at least one memory and the computer code may be configured, with the at least one processor, to cause the apparatus to determine if the information is already available to said apparatus and only providing said request if said information is not already available to said apparatus.
- the communications mode may comprise one or more of a machine communications mode or an IoT communications mode.
- the communications mode may comprise a LTE-M.
- the one or more communication categories may comprise one or more of category Ml and category M2.
- the at least one memory and the computer code may be configured, with the at least one processor, to cause the apparatus to provide to the radio access node radio capabilities of said communications device from which said radio access node is able to determine the indication.
- the at least one memory and the computer code may be configured, with the at least one processor, to cause the apparatus causing the request and said radio capabilities to be provided in a same message.
- At least one of said request and said response may be provided in a respective dedicated message.
- At least one of said request and said response may be provided in a message with at least one other information element.
- the message may be an N2 message.
- the message may be an S 1 message.
- At least one of said request and said response may be provided by a context setup request and response, respectively.
- the response may comprise information from the radio access node indicating that said radio access node does not support the communication mode when the radio access node does not support the communications mode.
- the core network entity may be a mobility management entity and the radio access node may be a base station
- the core network entity may be an access and mobility management function and the radio access node is a base station.
- the apparatus may be provided in the core network entity.
- the apparatus may comprise the core network entity.
- an apparatus comprising means for: causing a request to be provided from a core network entity to a radio access node for information indicating if a communications device is using or supporting a communications mode associated with one or more given communication categories; and receiving a response comprising an indication from the radio access node which indicates that the communication device is using or supporting the communications mode when said communications device is using or supporting said communications mode.
- the means may be for determining if the information is already available to said apparatus and only providing said request if said information is not already available to said apparatus.
- the communications mode may comprise one or more of a machine communications mode or an IoT communications mode.
- the communications mode may comprise a LTE-M.
- the one or more communication categories may comprise one or more of category Ml and category M2.
- the means may be for causing the apparatus to provide to the radio access node radio capabilities of said communications device from which said radio access node is able to determine the indication.
- the means may be for causing the request and said radio capabilities to be provided in a same message.
- At least one of said request and said response may be provided in a respective dedicated message.
- At least one of said request and said response may be provided in a message with at least one other information element.
- the message may be an N2 message.
- the message may be an S 1 message.
- At least one of said request and said response may be provided by a context setup request and response, respectively.
- the response may comprise information from the radio access node indicating that said radio access node does not support the communication mode when the radio access node does not support the communications mode.
- the core network entity may be a mobility management entity and the radio access node may be a base station
- the core network entity may be an access and mobility management function and the radio access node is a base station.
- the apparatus may be provided in the core network entity.
- the apparatus may comprise the core network entity.
- a method performed by an apparatus comprising: causing a request to be provided from a core network entity to a radio access node for information indicating if a communications device is using or supporting a communications mode associated with one or more given communication categories; and receiving a response comprising an indication from the radio access node which indicates that the communication device is using or supporting the communications mode when said communications device is using or supporting said communications mode.
- the method may comprise determining if the information is already available to said apparatus and only providing said request if said information is not already available to said apparatus.
- the communications mode may comprise one or more of a machine communications mode or an IoT communications mode.
- the communications mode may comprise a LTE-M.
- the one or more communication categories may comprise one or more of category Ml and category M2.
- the method may comprise causing the radio access node radio capabilities of said communications device to be provided to the radio access node from which said radio access node is able to determine the indication.
- the method may comprise causing the request and said radio capabilities to be provided in a same message.
- At least one of said request and said response may be provided in a respective dedicated message.
- At least one of said request and said response may be provided in a message with at least one other information element.
- the message may be an N2 message.
- the message may be an S 1 message.
- At least one of said request and said response may be provided by a context setup request and response, respectively.
- the response may comprise information from the radio access node indicating that said radio access node does not support the communication mode when the radio access node does not support the communications mode.
- the core network entity may be a mobility management entity and the radio access node may be a base station
- the core network entity may be an access and mobility management function and the radio access node is a base station.
- the method may be performed by apparatus provided in the core network entity.
- the apparatus may comprise the core network entity.
- an apparatus comprising 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: receive a request from a core network entity to a radio access node for information indicating if a communications device is using or supporting a communications mode associated with one or more given communication categories; and cause a response comprising an indication to be provided from the radio access node to the core network entity which indicates that the communication device is using or supporting the communications mode when said communications device is using s or supporting aid communications mode.
- the communications mode may comprise one or more of a machine communications mode or an IoT communications mode.
- the communications mode may comprises a LTE-M.
- the one or more communication categories may comprise one or more of category Ml and category M2.
- the at least one memory and the computer code may be configured, with the at least one processor, to cause the apparatus to receive radio capabilities of said communications device and to determine the indication from the radio capabilities of said communications device.
- the at least one memory and the computer code may be configured, with the at least one processor, to cause the apparatus to receive the request and said radio capabilities in a same message.
- At least one of said request and said response is provided in a respective dedicated message.
- At least one of said request and said response may be provided in a message with at least one other information element.
- the message may be an N2 message.
- the message may be an SI message.
- At least one of said request and said response may be provided by a context setup request and response, respectively.
- the core network entity may be a mobility management entity and the radio access node may be a base station
- the core network entity may be an access and mobility management function and the radio access node may be a base station.
- the apparatus may be provided in a radio access node.
- the apparatus may be a radio access node.
- an apparatus comprising means for: receiving a request from a core network entity to a radio access node for information indicating if a communications device is using or supporting a communications mode associated with one or more given communication categories; and causing a response comprising an indication to be provided from the radio access node to the core network entity which indicates that the communication device is using or supporting the communications mode when said communications device is using or supporting said communications mode.
- the communications mode may comprise one or more of a machine communications mode or an IoT communications mode.
- the communications mode may comprises a LTE-M.
- the one or more communication categories may comprise one or more of category Ml and category M2.
- the means may be for causing the apparatus to receive radio capabilities of said communications device and to determine the indication from the radio capabilities of said communications device.
- the means may be for causing the apparatus to receive the request and said radio capabilities in a same message.
- At least one of said request and said response is provided in a respective dedicated message.
- At least one of said request and said response may be provided in a message with at least one other information element.
- the message may be an N2 message.
- the message may be an SI message.
- At least one of said request and said response may be provided by a context setup request and response, respectively.
- the core network entity may be a mobility management entity and the radio access node may be a base station
- the core network entity may be an access and mobility management function and the radio access node may be a base station.
- the apparatus may be provided in a radio access node.
- the apparatus may be a radio access node.
- a method performed by an apparatus comprising: receiving a request from a core network entity to a radio access node for information indicating if a communications device is using or supporting a communications mode associated with one or more given communication categories; and causing a response comprising an indication to be provided from the radio access node to the core network entity which indicates that the communication device is using or supporting the communications mode when said communications device is using or supporting said communications mode.
- the communications mode may comprise one or more of a machine communications mode or an IoT communications mode.
- the communications mode may comprises a LTE-M.
- the one or more communication categories may comprise one or more of category Ml and category M2.
- the method may comprise receiving radio capabilities of said communications device and determining the indication from the radio capabilities of said communications device.
- the method may comprise receiving the request and said radio capabilities in a same message.
- At least one of said request and said response is provided in a respective dedicated message.
- At least one of said request and said response may be provided in a message with at least one other information element.
- the message may be an N2 message.
- the message may be an S 1 message.
- At least one of said request and said response may be provided by a context setup request and response, respectively.
- the core network entity may be a mobility management entity and the radio access node may be a base station
- the core network entity may be an access and mobility management function and the radio access node may be a base station.
- the method may be performed by apparatus in a radio access node.
- the method may be performed by an apparatus which is a radio access node.
- a computer program comprising computer executable code which when run on at least one processor is configured to cause any of the previously described methods to be performed.
- a computer program comprising computer executable code which when run on at least one processor of an apparatus is configured to cause any of the previously described methods to be performed.
- a computer readable medium comprising program instructions stored thereon for performing at least one of the above methods.
- a non-transitory computer readable medium comprising program instructions stored thereon for performing at least one of the above methods.
- non-volatile tangible memory medium comprising program instructions stored thereon for performing at least one of the above methods.
- Figure 1 shows a schematic representation of a communication system
- Figure 2 shows a schematic representation of a communications device
- Figure 3 shows a schematic representation of an apparatus
- Figure 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;
- Figure 5 shows a first signal flow
- Figure 6 shows a second signal flow
- Figure 7 shows a third signal flow
- Figure 8 shows a method of some embodiments.
- Figure 9 shows another method of some embodiments. Detailed description
- wireless systems can be divided into cells, and are therefore often referred to as cellular systems.
- a base station provides at least one cell.
- the cellular system can support communications between user equipment (UE).
- UE user equipment
- the present disclosure relates to cellular radio implementation, including 2G, 3G, 4G, and 5G radio access networks (RANs); cellular internet of things (IoT) RAN; and cellular radio hardware.
- RANs 2G, 3G, 4G, and 5G radio access networks (RANs); cellular internet of things (IoT) RAN; and cellular radio hardware.
- IoT internet of things
- wireless communication systems are architectures standardized by the 3rd Generation Partnership Project (3GPP).
- 3GPP 3rd Generation Partnership Project
- 5G 3rd Generation Partnership Project
- 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).
- WLAN wireless local area network
- WiMAX Worldwide Interoperability for Microwave Access
- FIG. 1 shows an example system 100 in which some embodiments may be provided.
- the system may be a wireless communications.
- a communications device such as a UE (user equipment) 104 is configured to communicate via a radio connection with a RAN (radio access network) 106.
- the RAN may comprise a wireless access point such as a base station.
- a base station is sometimes referred to as an eNodeB and 5G, a base station is sometimes referred as a gNodeB.
- the RAN 106 is configured to communicate with a core network 102 which comprises one or more core network functions.
- FIG 2 illustrates an example of a communications device 300, such as the wireless communications device 104 shown on Figure 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.
- MS mobile station
- PDA personal data assistant
- MTC machine-type communications
- IoT type communications devices IoT type communications devices or any combinations of these or the like.
- 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.
- 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.
- 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 302a.
- 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.
- the device may optionally have a user interface such as key pad 305, touch sensitive screen or pad, combinations thereof or the like.
- one or more of a display, a speaker and a microphone may be provided depending on the type of the device.
- 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.
- FIG. 3 shows an example of an apparatus 200 for a radio access node or a core network entity such as described later.
- 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 21 lb.
- Figure 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.
- non-volatile memory media 1600a e.g. computer disc (CD) or digital versatile disc (DVD)
- 1200b e.g. universal serial bus (USB) memory stick
- E-UTRA evolved universal mobile telecommunications system
- NR new radio
- UTRAN UMTS terrestrial radio access network
- MTC machine type communication
- NB narrowband
- MTC capable communication equipment refers to a category of communication devices that perform or are capable of providing IoT (internet of things) or machine-to-machine (M2M) communication.
- IoT internet of things
- M2M machine-to-machine
- LTE-Machine Type Communication is a 3 GPP low power wide area network (LPWAN) radio technology standard developed to enable machine-to-machine and Intemet- of-Things (IoT) applications.
- LTE-M may be LTE CatMl or LTE Cat M2. This may be as defined in TS 36.306 or TS 36.331.
- LTE-M may be used as a 3 GPP RAT (radio access technology) type identifier used in the core network. This may be a sub-type E-UTRAN RAT type, and in EPS, it is defined to identify in the core network the E-UTRAN when used by a UE indicating Category M in its UE radio capability.
- the LTE-M indication may indicate that the UE is a LTE-M UE and the UE radio access capability includes LTE Cat- Ml or LTE Cat-Mi and LTE Cat-M2.
- 3 GPP release 15 as introduced in 4G provides means to notify the EPC (evolved packet core) at registration that a UE is a category M1/M2 device. This allows for specific charging.
- traffic associated with UE accessing via LTE-M or NB-IoT may be associated with a different charging policy than “normal” traffic over other access technology, such as speech or video traffic or the like.
- a UE is not permitted to indicate both a Cat.M and a “normal” LTE UE category at the same time,
- a Cat.M UE needs to detach and re-attach if it changes to another UE category.
- a Cat.M 1/M2 UE may can only successfully attach to a LTE-M network.
- the eNB may extract the cat- M1/M2 information.
- an eNB receives an initial UE context setup request message, which does not contain the UE radio capabilities, the eNB fetches the UE radio capabilities from the UE and extracts the Cat M1/M2 (LTE-M) information from the UE radio capabilities.
- the eNB sends both the UE Radio Capabilities and the LTE-M indication within the S 1AP UE capability info indication message to a MME (mobility management entity) in separate information elements (IE).
- MME mobility management entity
- the MME stores this Cat M1/M2 (LTE-M) information until the UE detaches.
- the MME provides this Cat M1/M2 (LTE-M) information to S/P-GW (serving/packet gateway) as a new RAT (radio access technology) type.
- S/P-GW serving/packet gateway
- the source MME provides the LTE-M indication to a target MME.
- CIoT in a 5GS may also benefit from a requirement to identify a UE’s LTE-M access for possible policy and charging decisions in the network.
- the CN node derives the LTE-M access indication from the UE radio capabilities when they are received from the RAN.
- the LTE-M indication may be sent to the MME together with the UE radio Capabilities in a UE capability info indication message. This means that when the eNB does not send this message there may be no means for an MME to get the LTE- M indication if the LTE-M indication is not available at the MME.
- the MME typically includes the UE radio capabilities in every initial context setup request message towards the eNB.
- the eNB infers that the MME already has the UE radio capabilities.
- the eNB thus does not query the UE to retrieve the UE radio capabilities and deliver the UE radio capabilities back to MME. Therefore, the eNB does not send the UE capability info indication message to the MME in this scenario and has no means to deliver the LTE-M indication.
- the MME may not be able to retrieve the LTE-M and charging will not be accurate.
- a scenario may exist, for example, when the UE attaches first via a legacy eNB (e.g. pre-release 15) which does not support sending the LTE-M indication, or the UE attaches to an MME which does not support the LTE-M indication. At subsequent handover this MME would thus transfer to a target MME the UE radio capabilities only and the target MME has no means to retrieve the LTE-M indicator even if target MME supports this LTE-M indication feature.
- a legacy eNB e.g. pre-release 15
- the MME itself to determine from the UE radio capabilities whether the UE is Cat M1/M2.
- the MME would need to support RRC PDU (radio resource control packet data unit) encoding in order to decode the UE Radio Capabilities that are only stored in the MME as a container, but not for the MME internal use.
- RRC PDU radio resource control packet data unit
- the eNB always include the LTE-M indicator in every initial UE Message from eNB to MME whenever the UE connects to EPC or, for 5G, from NG-RAN (next generation RAN) node to AMF.
- the UE may include the LTE-M indication within the RRC setup Complete message (also called Message 5).
- This may entail a security risk because it relies on the UE itself to provide the information relating to the use of LTE-M resources and the UE may be biased to influence the charging.
- Another option may be for the eNB to infer the planned use of LTE-M resources by the UE using dedicated RACH resources.
- the information of which RACH resources to be used would be assumed to be broadcasted beforehand over SIB 1. Having dedicated RACH resources may be costly. Also, because the same RACH resources are used by normal UEs in CE mode and LTE-M UEs, clear differentiation may be problematic.
- Some embodiments may provide a specific MME “request” in an initial context setup request message. In the case of a 4G system, this may enable the MME to request the eNB to decode the UE radio capabilities. If the CatMl/M2 capabilities are indicated as supported, the eNB may respond to the MME request by including the LTE-M indicator into the initial context setup response so that the MME is aware of LTE-M access.
- This specific request or “trigger” in the request message avoids the eNB, at every initial context setup request received, determining from the UE Radio Capabilities the CatMl/M2 capabilities before replying with the LTE-M indicator into the initial context setup response. This may be redundant processing given that the MME may already have the LTE-M Indication stored when it sends the UE radio capabilities.
- FIG. 5 shows a signalling flow for an example implementation in a 4G system.
- a LTE-M Request indicator IE is included in a Sl-AP initial context setup request message.
- an apparatus of the MME causes a paging message to be sent to the eNB.
- step S2 an apparatus of the eNB causes a paging message to be sent to the UE.
- step S3 the random access procedure is performed between the UE and eNB.
- step S4 an apparatus of the UE is configured to cause a service request to be sent from the UE to the MME relayed by the eNB.
- This service request may be a NAS (non access stratum service request).
- step S5 the apparatus of the eNB is configured to cause a message to be sent from the eNB to the MME.
- This message may be a Sl-AP initial UE message containing the previous NAS message.
- step S6 the apparatus of the MME is configured to cause a message to be sent from the MME to the eNB.
- This may be an Sl-AP initial context setup request.
- An LTE-M request indicator IE is included in the initial context setup request message from the MME to the eNB. This will only be included in the message if the MME requires this information.
- the initial context setup request may additionally comprise one or more of the following:
- step S7 the apparatus of the eNB causes a message to be sent from the eNB to the UE.
- This may be a radio bearer setup message.
- This may be a RRC message.
- the message may contain a NAS message.
- step S8 the apparatus of the UE causes a message to be sent from the UE to the eNB.
- This may be a radio bearer setup complete message.
- This may be a RRC message.
- the apparatus of the eNB causes a message to be sent from the eNB to the MME.
- This may be an initial context setup response.
- This may be an Sl-AP initial context setup response.
- the initial context setup response sent from the eNB to the MME includes the LTE-M indicator.
- the indicator may be optional.
- the eNB gets this information from the UE radio capabilities which are included in the Initial Context Setup Request from the MME.
- the MME may not be radio aware and as such may not be able to decode the UE radio capabilities.
- the MME may not be permitted to examine the content of an RRC information element.
- the apparatus of the eNB is able to decode the UE radio capabilities to provide the LTE-M indicator to the eNB.
- the indication may in some embodiments comprise two values: “LTE-M UE” or “not LTE-M UE”. Therefore, the MME will be able to differentiate the case where the eNB does not support the provision of the LTE-M indicator (LTE-M indicator EE will not be included in the initial context setup response) from the case where the UE is not an LTE-M UE (the LTE- M Indicator IE will be included in the initial context setup response but set to the value “not LTE-M”).
- the indication may indicate the category, for example Cat Ml or Cat M2.
- the initial context setup response may comprise the eNB UE signalling connection ID.
- Figure 6 shows a signalling flow for an example implementation in a 5G system.
- step Tl an apparatus of the 5GC causes a paging message to be sent to the NG-
- step T2 an apparatus of the NG-RAN causes a paging message to be sent to the UE.
- step T3 the random access procedure is performed between the UE and NG-RAN.
- an apparatus of the UE is configured to cause a service request to be sent from the UE to the 5GC relayed by the NG-RAN.
- This service request may be a NAS (non access stratum service request).
- step T5 the apparatus of the NG-RAN is configured to cause a message to be sent from the NG-RAN to the 5GC.
- This message may be a NG-AP initial UE message containing the previous NAS message.
- step T6 the apparatus of the 5GC is configured to cause a message to be sent from the 5GC to the NG-RAN.
- This may be an NG-AP initial context setup request.
- An LTE-M request indicator IE is included in the initial context setup request message from the 5GC to the NG-RAN.
- the initial context setup request may additionally comprise one or more of the following:
- step T7 the apparatus of the NG-RAN causes a message to be sent from the NG- RAN to the UE.
- This may be a reconfiguration request.
- This may be an RRC message.
- step T8 the apparatus of the UE causes a message to be sent from the UE to the NG- RAN.
- This may be a reconfiguration complete message.
- This may be a RRC message.
- the apparatus of the NG-RAN causes a message to be sent from the NG- RNA to the 5GC.
- This may be an initial context setup response.
- This may be an NG-AP initial context setup response.
- the initial context setup response sent from the NG-RAN to the 5GC includes the LTE-M indicator.
- the indicator may be optional.
- the NG-RAN gets this information from the UE radio capabilities which are included in the initial context setup request from the AMF.
- the AMF may not be radio aware and as such may not be able to decode the UE radio capabilities.
- the AMF only stores the UE radio capabilities as a container whose contents is not relevant for the AMF operation, and the AMF cannot examine the content of an RRC information element without intervening NG-RAN protocol contents.
- the apparatus of the NG-RAN is able to decode the UE radio capabilities to provide the LTE-M indicator to the NG-RAN.
- the indication may in some embodiments comprise two values: “LTE-M UE” or “not LTE-M UE”. Therefore, the AMF will be able to differentiate the case where the eNB does not support the provision of the LTE-M indicator (LTE-M indicator IE will not be included in the initial context setup response) from the case where the UE is not an LTE-M UE (the LTE-M Indicator IE will be included in the initial context setup response but set to the value “not LTE- M”).
- the initial context setup response may comprise the RAN UE signalling connection ID.
- Figure 7 shows a signalling flow for another example implementation in a 5G system.
- Figure 7 shows a signalling flow for a further example embodiment in which LTE-M request indicator IE and a LTE-M indicator IE are included as part of a separate procedure which is triggered just before the initial context setup request.
- step Al an apparatus of the 5GC causes a paging message to be sent to the NG-
- step A2 an apparatus of the NG-RAN causes a paging message to be sent to the UE.
- step A3 the random access procedure is performed between the UE and NG-RAN.
- an apparatus of the UE is configured to cause a service request to be sent from the UE to the NAS relayed by the NG-RAN.
- This service request may be a NAS (non access stratum service request).
- step A5 the apparatus of the NG-RAN is configured to cause a message to be sent from the NG-RAN to the 5GC.
- This message may be a NG-AP initial UE message containing the previous NAS message.
- the apparatus of the 5GC is configured to cause a message to be sent from the 5GC to the NG-RAN.
- This may be a message to request the LTE-M capabilities.
- This may be a NG-AP request message.
- This message may comprise an LTE-M request indicator.
- the message may comprise one or more of the AMF UE signalling connection ID and UE radio capabilities.
- the apparatus of the NG-RAN causes a message to be sent from the NG- RAN to the 5GC.
- This may be an LTE-M response message.
- This may be an NG-AP response.
- the response sent from the NG-RAN to the 5GC includes the LTE-M indicator.
- the indicator may be optional.
- the apparatus of the NG-RAN may get this information from the UE radio capabilities which are included in the message to request the LTE-M indicator from the AMF
- the indication may in some embodiments comprise two values: “LTE-M UE” or “not LTE-M UE”. Therefore, the AMF will be able to differentiate the case where the NG-RAN node does not support the provision of the LTE-M indicator (LTE-M indicator IE will not be included in the initial context setup response) from the case where the UE is not an LTE-M UE (the LTE-M Indicator IE will be included in the initial context setup response but set to the value “not LTE-M”).
- the response may comprise the RAN UE signalling connection ID.
- step A8 the apparatus of the 5GC is configured to cause a message to be sent from the 5GC to the NG-RAN.
- This may be an NG-AP initial context setup request.
- step A9 the apparatus of the NG-RAN causes a message to be sent from the NG- RAN to the UE.
- This may be a reconfiguration request.
- This may be an RRC message.
- step A 10 the apparatus of the UE causes a message to be sent from the UE to the NG-RAN.
- This may be a reconfiguration complete message.
- This may be an RRC message.
- step A11 the apparatus of the NG-RAN causes a message to be sent from the NG- RAN to the 5GC.
- This may be an initial context setup response.
- This may be an NG-AP initial context setup response.
- Some embodiments cause an apparatus of a core network entity (for example the MME or the AMF) to provide a request which causes the apparatus of the base station to decode the UE radio capabilities. If the CatMl/M2 capabilities are present, the apparatus of the base station will provide a response to the request comprising the LTE-M indicator to make the core network entity aware of LTE-M access.
- the request may be the initial context setup request message or a separate request.
- the response may be the initial context setup response or a separate response. This specific request or “trigger” in the request message may avoid that the base station would at every initial context setup request received obtain the UE radio capabilities, extract the CatMl/M2 capabilities out, before replying with the LTE-M indicator into the initial context setup response. This may avoid unnecessary processing given that most of the time the core network entity already has the LTE-M indication stored when it sends the UE radio capabilities.
- the method may be performed using an apparatus.
- the apparatus may be provided by the core network entity.
- the apparatus may be in the core network entity.
- the apparatus may be the core network entity.
- the core network entity may be an AMF or a MME.
- 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 to perform the method of Figure 8.
- step Bl the method comprises causing a request to be provided from a core network entity to a radio access node for information indicating if a communications device is using or supporting a communications mode associated with one or more given communication categories.
- step B2 the method comprises receiving a response comprising an indication from the radio access node which indicates that the communication device is using or supporting the communications mode when said communications device is using or supporting said communications mode.
- the method may be performed using an apparatus.
- the apparatus may be provided by the radio access node.
- the apparatus may be in the radio access node.
- the apparatus may be the radio access node.
- the method may be performed at an eNB or a ng-gNB of an NG RAN.
- 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 to perform the method of Figure 9.
- step Cl the method comprises receiving a request from a core network entity to a radio access node for information indicating if a communications device is using or supporting a communications mode associated with one or more given communication categories.
- step C2 the method comprises causing a response comprising an indication to be provided from the radio access node to the core network entity which indicates that the communication device is using or supporting the communications mod when said communications device is using said communications mode.
- the above aspects are not limited to 5GS and are not limited to E-UTRA.
- some embodiments may apply to NR new radio or any other suitable technology. These aspects may be transposed to other radio access technology systems.
- LTE-M indicator Reference has been made to a LTE-M indicator. It should be appreciated that other embodiments may be used with any other type of category which may for example require a different charging to another type of category and/or handling in a different way.
- the indicator may be an indicator to indicate that the UE is in an IoT communication mode or a machine type communication mode or any other suitable type of mode.
- An indicator other than a LTE-M indicator may alternatively or additionally be used.
- some embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof.
- 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.
- 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.
- 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 Figures 5 to 9 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.
- 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.
- 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.
- circuitry may refer to one or more or all of the following:
- 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.
- software e.g., firmware
- 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.
- circuitry also covers, for example integrated device.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
There is provided an apparatus, comprising 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 are configured, with the at least one processor, to cause the apparatus at least to cause a request to be provided from a core network entity to a radio access node for information indicating if a communications device is using or supporting a communications mode associated with one or more given communication categories and receive a response comprising an indication from the radio access node which indicates that the communication device is using or supporting the communications mode when said communications device is using or supporting said communications mode.
Description
APPARATUS, METHODS, AND COMPUTER PROGRAMS
Field of the disclosure
The present disclosure relates to an apparatus, methods, and computer programs and in particular but not exclusively for apparatus, methods and computer programs to be used in a communications system.
Background
A communication system can be seen as a facility that enables communication sessions between two or more entities such as user terminals, base stations/access points and/or other nodes by providing carriers between the various entities involved in the communications path.
A communication system can be provided for example by means of a communication network and one or more compatible communications devices.
Access to the communication system may be by means of an appropriate communications device or terminal. A communications device is provided with an appropriate signal receiving and transmitting apparatus for enabling communications, for example enabling access to a communication network or communications directly with other communications device. The communications device may access a carrier provided by a station or access point, and transmit and/or receive communications on the carrier.
The communication system and associated devices typically operate in accordance with a given standard or specification which sets out what the various entities associated with the system are permitted to do and how that should be achieved.
Summary
According to an aspect, there is provided an apparatus comprising 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: cause a request to be provided from a core network entity to a radio access node for information indicating if a communications device is using or supporting a communications mode associated with one or more given communication categories; and receive a response comprising an indication from the radio access node which indicates that the communication device is using or supporting the communications mode when said communications device is using or supporting said communications mode.
The at least one memory and the computer code may be configured, with the at least one processor, to cause the apparatus to determine if the information is already available to
said apparatus and only providing said request if said information is not already available to said apparatus.
The communications mode may comprise one or more of a machine communications mode or an IoT communications mode.
The communications mode may comprise a LTE-M.
The one or more communication categories may comprise one or more of category Ml and category M2.
The at least one memory and the computer code may be configured, with the at least one processor, to cause the apparatus to provide to the radio access node radio capabilities of said communications device from which said radio access node is able to determine the indication.
The at least one memory and the computer code may be configured, with the at least one processor, to cause the apparatus causing the request and said radio capabilities to be provided in a same message.
At least one of said request and said response may be provided in a respective dedicated message.
At least one of said request and said response may be provided in a message with at least one other information element.
The message may be an N2 message.
The message may be an S 1 message.
At least one of said request and said response may be provided by a context setup request and response, respectively.
The response may comprise information from the radio access node indicating that said radio access node does not support the communication mode when the radio access node does not support the communications mode.
The core network entity may be a mobility management entity and the radio access node may be a base station
The core network entity may be an access and mobility management function and the radio access node is a base station.
The apparatus may be provided in the core network entity. The apparatus may comprise the core network entity.
According to an aspect, there is provided an apparatus comprising means for: causing a request to be provided from a core network entity to a radio access node for information indicating if a communications device is using or supporting a communications mode
associated with one or more given communication categories; and receiving a response comprising an indication from the radio access node which indicates that the communication device is using or supporting the communications mode when said communications device is using or supporting said communications mode.
The means may be for determining if the information is already available to said apparatus and only providing said request if said information is not already available to said apparatus.
The communications mode may comprise one or more of a machine communications mode or an IoT communications mode.
The communications mode may comprise a LTE-M.
The one or more communication categories may comprise one or more of category Ml and category M2.
The means may be for causing the apparatus to provide to the radio access node radio capabilities of said communications device from which said radio access node is able to determine the indication.
The means may be for causing the request and said radio capabilities to be provided in a same message.
At least one of said request and said response may be provided in a respective dedicated message.
At least one of said request and said response may be provided in a message with at least one other information element.
The message may be an N2 message.
The message may be an S 1 message.
At least one of said request and said response may be provided by a context setup request and response, respectively.
The response may comprise information from the radio access node indicating that said radio access node does not support the communication mode when the radio access node does not support the communications mode.
The core network entity may be a mobility management entity and the radio access node may be a base station
The core network entity may be an access and mobility management function and the radio access node is a base station.
The apparatus may be provided in the core network entity. The apparatus may comprise the core network entity.
According to another aspect, there is provided a method performed by an apparatus, said method comprising: causing a request to be provided from a core network entity to a radio access node for information indicating if a communications device is using or supporting a communications mode associated with one or more given communication categories; and receiving a response comprising an indication from the radio access node which indicates that the communication device is using or supporting the communications mode when said communications device is using or supporting said communications mode.
The method may comprise determining if the information is already available to said apparatus and only providing said request if said information is not already available to said apparatus.
The communications mode may comprise one or more of a machine communications mode or an IoT communications mode.
The communications mode may comprise a LTE-M.
The one or more communication categories may comprise one or more of category Ml and category M2.
The method may comprise causing the radio access node radio capabilities of said communications device to be provided to the radio access node from which said radio access node is able to determine the indication.
The method may comprise causing the request and said radio capabilities to be provided in a same message.
At least one of said request and said response may be provided in a respective dedicated message.
At least one of said request and said response may be provided in a message with at least one other information element.
The message may be an N2 message.
The message may be an S 1 message.
At least one of said request and said response may be provided by a context setup request and response, respectively.
The response may comprise information from the radio access node indicating that said radio access node does not support the communication mode when the radio access node does not support the communications mode.
The core network entity may be a mobility management entity and the radio access node may be a base station
The core network entity may be an access and mobility management function and the radio access node is a base station.
The method may be performed by apparatus provided in the core network entity. The apparatus may comprise the core network entity.
According to another aspect, there is provided an apparatus comprising 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: receive a request from a core network entity to a radio access node for information indicating if a communications device is using or supporting a communications mode associated with one or more given communication categories; and cause a response comprising an indication to be provided from the radio access node to the core network entity which indicates that the communication device is using or supporting the communications mode when said communications device is using s or supporting aid communications mode.
The communications mode may comprise one or more of a machine communications mode or an IoT communications mode.
The communications mode may comprises a LTE-M.
The one or more communication categories may comprise one or more of category Ml and category M2.
The at least one memory and the computer code may be configured, with the at least one processor, to cause the apparatus to receive radio capabilities of said communications device and to determine the indication from the radio capabilities of said communications device.
The at least one memory and the computer code may be configured, with the at least one processor, to cause the apparatus to receive the request and said radio capabilities in a same message.
At least one of said request and said response is provided in a respective dedicated message.
At least one of said request and said response may be provided in a message with at least one other information element.
The message may be an N2 message.
The message may be an SI message.
At least one of said request and said response may be provided by a context setup request and response, respectively.
The core network entity may be a mobility management entity and the radio access node may be a base station
The core network entity may be an access and mobility management function and the radio access node may be a base station.
The apparatus may be provided in a radio access node. The apparatus may be a radio access node.
According to another aspect, there is provided an apparatus comprising means for: receiving a request from a core network entity to a radio access node for information indicating if a communications device is using or supporting a communications mode associated with one or more given communication categories; and causing a response comprising an indication to be provided from the radio access node to the core network entity which indicates that the communication device is using or supporting the communications mode when said communications device is using or supporting said communications mode.
The communications mode may comprise one or more of a machine communications mode or an IoT communications mode.
The communications mode may comprises a LTE-M.
The one or more communication categories may comprise one or more of category Ml and category M2.
The means may be for causing the apparatus to receive radio capabilities of said communications device and to determine the indication from the radio capabilities of said communications device.
The means may be for causing the apparatus to receive the request and said radio capabilities in a same message.
At least one of said request and said response is provided in a respective dedicated message.
At least one of said request and said response may be provided in a message with at least one other information element.
The message may be an N2 message.
The message may be an SI message.
At least one of said request and said response may be provided by a context setup request and response, respectively.
The core network entity may be a mobility management entity and the radio access node may be a base station
The core network entity may be an access and mobility management function and the radio access node may be a base station.
The apparatus may be provided in a radio access node. The apparatus may be a radio access node.
According to another aspect, there is provided a method performed by an apparatus, said method comprising: receiving a request from a core network entity to a radio access node for information indicating if a communications device is using or supporting a communications mode associated with one or more given communication categories; and causing a response comprising an indication to be provided from the radio access node to the core network entity which indicates that the communication device is using or supporting the communications mode when said communications device is using or supporting said communications mode.
The communications mode may comprise one or more of a machine communications mode or an IoT communications mode.
The communications mode may comprises a LTE-M.
The one or more communication categories may comprise one or more of category Ml and category M2.
The method may comprise receiving radio capabilities of said communications device and determining the indication from the radio capabilities of said communications device.
The method may comprise receiving the request and said radio capabilities in a same message.
At least one of said request and said response is provided in a respective dedicated message.
At least one of said request and said response may be provided in a message with at least one other information element.
The message may be an N2 message.
The message may be an S 1 message.
At least one of said request and said response may be provided by a context setup request and response, respectively.
The core network entity may be a mobility management entity and the radio access node may be a base station
The core network entity may be an access and mobility management function and the radio access node may be a base station.
The method may be performed by apparatus in a radio access node. The method may be performed by an apparatus which is a radio access node.
According to an aspect there is provided a computer program comprising computer executable code which when run on at least one processor is configured to cause any of the previously described methods to be performed.
According to an aspect there is provided a computer program comprising computer executable code which when run on at least one processor of an apparatus is configured to cause any of the previously described methods to be performed.
According to an aspect, there is provided a computer readable medium comprising program instructions stored thereon for performing at least one of the above methods.
According to an aspect, there is provided a non-transitory computer readable medium comprising program instructions stored thereon for performing at least one of the above methods.
According to an aspect, there is provided a non-volatile tangible memory medium comprising program instructions stored thereon for performing at least one of the above methods.
In the above, many different aspects have been described. It should be appreciated that further aspects may be provided by the combination of any two or more features from one or more of the aspects described above. These combinations of features may be additional to the features combinations discussed as examples later.
Various other aspects are also described in the following detailed description and in the attached claims.
Brief description of Figures
Some embodiments will now be described in further detail, by way of example only, with reference to the following examples and accompanying drawings, in which:
Figure 1 shows a schematic representation of a communication system;
Figure 2 shows a schematic representation of a communications device;
Figure 3 shows a schematic representation of an apparatus;
Figure 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;
Figure 5 shows a first signal flow;
Figure 6 shows a second signal flow;
Figure 7 shows a third signal flow;
Figure 8 shows a method of some embodiments; and
Figure 9 shows another method of some embodiments.
Detailed description
As is known, wireless systems can be divided into cells, and are therefore often referred to as cellular systems. Typically, a base station provides at least one cell. The cellular system can support communications between user equipment (UE). The present disclosure relates to cellular radio implementation, including 2G, 3G, 4G, and 5G radio access networks (RANs); cellular internet of things (IoT) RAN; and cellular radio hardware.
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 Figures 1 to 4 to assist in understanding the technology underlying the described examples.
An example of wireless communication systems are architectures standardized by the 3rd Generation Partnership Project (3GPP). A latest 3 GPP 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 3 GPP forum.
Reference is made to Figure 1 which shows an example system 100 in which some embodiments may be provided. The system may be a wireless communications. It should be appreciated that the system of Figure 1 is a 5G or a LTE system but other embodiments may be used in association with any other suitable standard or system. In the system of Figure 1 , a communications device such as a UE (user equipment) 104 is configured to communicate via a radio connection with a RAN (radio access network) 106. The RAN may comprise a wireless access point such as a base station. In LTE, a base station is sometimes referred to as an eNodeB and 5G, a base station is sometimes referred as a gNodeB. The RAN 106 is configured to communicate with a core network 102 which comprises one or more core network functions.
Figure 2 illustrates an example of a communications device 300, such as the wireless communications device 104 shown on Figure 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.
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 Figure 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.
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 302a.
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.
The device may optionally have a user interface such as key pad 305, touch sensitive screen or pad, combinations thereof or the like.
Optionally one or more of a display, a speaker and a microphone may be provided depending on the type of the device.
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.
An example apparatus is shown in Figure 3. Figure 3 shows an example of an apparatus 200 for a radio access node or a core network entity such as described later. . 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 21 lb.
Figure 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.
One or more of the following aspects relate to an LTE system (Evolved Packet System -EPS) or 5G system (5GS). For 5GS, some embodiments may relate to E-UTRA (evolved universal mobile telecommunications system (UMTS) terrestrial radio access) radio. However it will be understood that some embodiments may be used with any other suitable other radio access technology systems such as NR (new radio). Some embodiments may be suitable to other systems such as UTRAN UMTS (terrestrial radio access network) of the UMTS and/or any other suitable system.
Some embodiments may be provided in the context of machine type communication (MTC). It should be appreciated that other embodiments may be provided in different contexts, for example contexts where narrowband (NB) is used.
MTC capable communication equipment refers to a category of communication devices that perform or are capable of providing IoT (internet of things) or machine-to-machine (M2M) communication.
LTE-Machine Type Communication (LTE-M) is a 3 GPP low power wide area network (LPWAN) radio technology standard developed to enable machine-to-machine and Intemet- of-Things (IoT) applications. LTE-M may be LTE CatMl or LTE Cat M2. This may be as defined in TS 36.306 or TS 36.331. LTE-M may be used as a 3 GPP RAT (radio access technology) type identifier used in the core network. This may be a sub-type E-UTRAN RAT type, and in EPS, it is defined to identify in the core network the E-UTRAN when used by a UE indicating Category M in its UE radio capability. The LTE-M indication may indicate that the UE is a LTE-M UE and the UE radio access capability includes LTE Cat- Ml or LTE Cat-Mi and LTE Cat-M2.
3 GPP release 15 as introduced in 4G provides means to notify the EPC (evolved packet core) at registration that a UE is a category M1/M2 device. This allows for specific charging. In particular, traffic associated with UE accessing via LTE-M or NB-IoT may be associated with a different charging policy than “normal” traffic over other access technology, such as speech or video traffic or the like.
In some situations, a UE is not permitted to indicate both a Cat.M and a “normal” LTE UE category at the same time,
Therefore, in some situations, a Cat.M UE needs to detach and re-attach if it changes to another UE category. A Cat.M 1/M2 UE may can only successfully attach to a LTE-M network.
When the base station receives the UE radio capability, the eNB may extract the cat- M1/M2 information. When an eNB receives an initial UE context setup request message, which does not contain the UE radio capabilities, the eNB fetches the UE radio capabilities from the UE and extracts the Cat M1/M2 (LTE-M) information from the UE radio capabilities. The eNB sends both the UE Radio Capabilities and the LTE-M indication within the S 1AP UE capability info indication message to a MME (mobility management entity) in separate information elements (IE).
The MME stores this Cat M1/M2 (LTE-M) information until the UE detaches. The MME provides this Cat M1/M2 (LTE-M) information to S/P-GW (serving/packet gateway) as a new RAT (radio access technology) type. In case of a change in MME serving the UE, the source MME provides the LTE-M indication to a target MME.
CIoT in a 5GS may also benefit from a requirement to identify a UE’s LTE-M access for possible policy and charging decisions in the network.
It has been proposed that the CN node (MME or AMF (access and mobility management function) derives the LTE-M access indication from the UE radio capabilities when they are received from the RAN. The LTE-M indication may be sent to the MME together with the UE radio Capabilities in a UE capability info indication message. This means that when the eNB does not send this message there may be no means for an MME to get the LTE- M indication if the LTE-M indication is not available at the MME.
For example, if the MME already has the UE radio capabilities, the MME typically includes the UE radio capabilities in every initial context setup request message towards the eNB. By receiving the UE radio capabilities in the initial context setup request message the eNB infers that the MME already has the UE radio capabilities. The eNB thus does not query the UE to retrieve the UE radio capabilities and deliver the UE radio capabilities back to MME. Therefore, the eNB does not send the UE capability info indication message to the MME in this scenario and has no means to deliver the LTE-M indication.
That is, in this scenario, whenever the MME has the UE radio capabilities and not the LTE-M indication, the MME may not be able to retrieve the LTE-M and charging will not be accurate.
Such a scenario may exist, for example, when the UE attaches first via a legacy eNB (e.g. pre-release 15) which does not support sending the LTE-M indication, or the UE attaches to an MME which does not support the LTE-M indication. At subsequent handover this MME would thus transfer to a target MME the UE radio capabilities only and the target MME has no means to retrieve the LTE-M indicator even if target MME supports this LTE-M indication feature.
One option is for the MME itself to determine from the UE radio capabilities whether the UE is Cat M1/M2. The MME would need to support RRC PDU (radio resource control packet data unit) encoding in order to decode the UE Radio Capabilities that are only stored in the MME as a container, but not for the MME internal use.
An alternative proposal is that the eNB always include the LTE-M indicator in every initial UE Message from eNB to MME whenever the UE connects to EPC or, for 5G, from NG-RAN (next generation RAN) node to AMF. The UE may include the LTE-M indication within the RRC setup Complete message (also called Message 5). This may entail a security risk because it relies on the UE itself to provide the information relating to the use of LTE-M resources and the UE may be biased to influence the charging. Another option may be for the eNB to infer the planned use of LTE-M resources by the UE using dedicated RACH resources. In that proposal, the information of which RACH resources to be used would be assumed to be broadcasted beforehand over SIB 1. Having dedicated RACH resources may be costly. Also, because the same RACH resources are used by normal UEs in CE mode and LTE-M UEs, clear differentiation may be problematic.
Some embodiments may provide a specific MME “request” in an initial context setup request message. In the case of a 4G system, this may enable the MME to request the eNB to decode the UE radio capabilities. If the CatMl/M2 capabilities are indicated as supported, the eNB may respond to the MME request by including the LTE-M indicator into the initial context setup response so that the MME is aware of LTE-M access. This specific request or “trigger” in the request message avoids the eNB, at every initial context setup request received, determining from the UE Radio Capabilities the CatMl/M2 capabilities before replying with the LTE-M indicator into the initial context setup response. This may be redundant processing given that the MME may already have the LTE-M Indication stored when it sends the UE radio capabilities.
Figure 5 shows a signalling flow for an example implementation in a 4G system. In this example embodiment, a LTE-M Request indicator IE is included in a Sl-AP initial context setup request message.
In step SI, an apparatus of the MME causes a paging message to be sent to the eNB.
In step S2, an apparatus of the eNB causes a paging message to be sent to the UE.
In step S3, the random access procedure is performed between the UE and eNB.
In step S4 an apparatus of the UE is configured to cause a service request to be sent from the UE to the MME relayed by the eNB. This service request may be a NAS (non access stratum service request).
In step S5, the apparatus of the eNB is configured to cause a message to be sent from the eNB to the MME. This message may be a Sl-AP initial UE message containing the previous NAS message.
In step S6, the apparatus of the MME is configured to cause a message to be sent from the MME to the eNB. This may be an Sl-AP initial context setup request.
An LTE-M request indicator IE is included in the initial context setup request message from the MME to the eNB. This will only be included in the message if the MME requires this information.
The initial context setup request may additionally comprise one or more of the following:
NAS message;
MME UE signalling connection ID; security context; and
UE radio capabilities.
In step S7, the apparatus of the eNB causes a message to be sent from the eNB to the UE. This may be a radio bearer setup message. This may be a RRC message. The message may contain a NAS message.
In step S8, the apparatus of the UE causes a message to be sent from the UE to the eNB. This may be a radio bearer setup complete message. This may be a RRC message.
In step S9, the apparatus of the eNB causes a message to be sent from the eNB to the MME. This may be an initial context setup response. This may be an Sl-AP initial context setup response. The initial context setup response sent from the eNB to the MME includes the LTE-M indicator. The indicator may be optional. The eNB gets this information from the UE radio capabilities which are included in the Initial Context Setup Request from the MME. The MME may not be radio aware and as such may not be able to decode the UE radio capabilities. The MME may not be permitted to examine the content of an RRC information element. The apparatus of the eNB is able to decode the UE radio capabilities to provide the LTE-M indicator to the eNB.
The indication may in some embodiments comprise two values: “LTE-M UE” or “not LTE-M UE”. Therefore, the MME will be able to differentiate the case where the eNB does not support the provision of the LTE-M indicator (LTE-M indicator EE will not be included in the initial context setup response) from the case where the UE is not an LTE-M UE (the LTE- M Indicator IE will be included in the initial context setup response but set to the value “not LTE-M”). The indication may indicate the category, for example Cat Ml or Cat M2.
The initial context setup response may comprise the eNB UE signalling connection ID.
Figure 6 shows a signalling flow for an example implementation in a 5G system.
In step Tl, an apparatus of the 5GC causes a paging message to be sent to the NG-
RAN.
In step T2, an apparatus of the NG-RAN causes a paging message to be sent to the UE.
In step T3, the random access procedure is performed between the UE and NG-RAN.
In step T4 an apparatus of the UE is configured to cause a service request to be sent from the UE to the 5GC relayed by the NG-RAN. This service request may be a NAS (non access stratum service request).
In step T5, the apparatus of the NG-RAN is configured to cause a message to be sent from the NG-RAN to the 5GC. This message may be a NG-AP initial UE message containing the previous NAS message.
In step T6, the apparatus of the 5GC is configured to cause a message to be sent from the 5GC to the NG-RAN. This may be an NG-AP initial context setup request.
An LTE-M request indicator IE is included in the initial context setup request message from the 5GC to the NG-RAN.
The initial context setup request may additionally comprise one or more of the following:
NAS message;
AMF UE signalling connection ID; security context; and
UE radio capabilities.
In step T7, the apparatus of the NG-RAN causes a message to be sent from the NG- RAN to the UE. This may be a reconfiguration request. This may be an RRC message.
In step T8, the apparatus of the UE causes a message to be sent from the UE to the NG- RAN. This may be a reconfiguration complete message. This may be a RRC message.
In step T9, the apparatus of the NG-RAN causes a message to be sent from the NG- RNA to the 5GC. This may be an initial context setup response. This may be an NG-AP initial
context setup response. The initial context setup response sent from the NG-RAN to the 5GC includes the LTE-M indicator. The indicator may be optional.
The NG-RAN gets this information from the UE radio capabilities which are included in the initial context setup request from the AMF. The AMF may not be radio aware and as such may not be able to decode the UE radio capabilities. The AMF only stores the UE radio capabilities as a container whose contents is not relevant for the AMF operation, and the AMF cannot examine the content of an RRC information element without intervening NG-RAN protocol contents. The apparatus of the NG-RAN is able to decode the UE radio capabilities to provide the LTE-M indicator to the NG-RAN.
The indication may in some embodiments comprise two values: “LTE-M UE” or “not LTE-M UE”. Therefore, the AMF will be able to differentiate the case where the eNB does not support the provision of the LTE-M indicator (LTE-M indicator IE will not be included in the initial context setup response) from the case where the UE is not an LTE-M UE (the LTE-M Indicator IE will be included in the initial context setup response but set to the value “not LTE- M”).
The initial context setup response may comprise the RAN UE signalling connection ID.
Figure 7 shows a signalling flow for another example implementation in a 5G system. Figure 7 shows a signalling flow for a further example embodiment in which LTE-M request indicator IE and a LTE-M indicator IE are included as part of a separate procedure which is triggered just before the initial context setup request.
In step Al, an apparatus of the 5GC causes a paging message to be sent to the NG-
RAN.
In step A2, an apparatus of the NG-RAN causes a paging message to be sent to the UE.
In step A3, the random access procedure is performed between the UE and NG-RAN.
In step A4 an apparatus of the UE is configured to cause a service request to be sent from the UE to the NAS relayed by the NG-RAN. This service request may be a NAS (non access stratum service request).
In step A5, the apparatus of the NG-RAN is configured to cause a message to be sent from the NG-RAN to the 5GC. This message may be a NG-AP initial UE message containing the previous NAS message.
In step A6, the apparatus of the 5GC is configured to cause a message to be sent from the 5GC to the NG-RAN. This may be a message to request the LTE-M capabilities. This may be a NG-AP request message. This message may comprise an LTE-M request indicator. The
message may comprise one or more of the AMF UE signalling connection ID and UE radio capabilities.
In step A7, the apparatus of the NG-RAN causes a message to be sent from the NG- RAN to the 5GC. This may be an LTE-M response message. This may be an NG-AP response. The response sent from the NG-RAN to the 5GC includes the LTE-M indicator. The indicator may be optional. The apparatus of the NG-RAN may get this information from the UE radio capabilities which are included in the message to request the LTE-M indicator from the AMF
The indication may in some embodiments comprise two values: “LTE-M UE” or “not LTE-M UE”. Therefore, the AMF will be able to differentiate the case where the NG-RAN node does not support the provision of the LTE-M indicator (LTE-M indicator IE will not be included in the initial context setup response) from the case where the UE is not an LTE-M UE (the LTE-M Indicator IE will be included in the initial context setup response but set to the value “not LTE-M”).
The response may comprise the RAN UE signalling connection ID.
In step A8, the apparatus of the 5GC is configured to cause a message to be sent from the 5GC to the NG-RAN. This may be an NG-AP initial context setup request.
In step A9, the apparatus of the NG-RAN causes a message to be sent from the NG- RAN to the UE. This may be a reconfiguration request. This may be an RRC message.
In step A 10, the apparatus of the UE causes a message to be sent from the UE to the NG-RAN. This may be a reconfiguration complete message. This may be an RRC message.
In step A11, the apparatus of the NG-RAN causes a message to be sent from the NG- RAN to the 5GC. This may be an initial context setup response. This may be an NG-AP initial context setup response.
It should be appreciated that the procedure described in relation to Figure 7 may also be applied in a 4G scenario i.e. in a case involving an eNB and an MME. The signal flow such as shown in Figure 5 may be modified such that a separate S1AP procedure is triggered just before the initial context setup request between MME and eNB.
Some embodiments cause an apparatus of a core network entity (for example the MME or the AMF) to provide a request which causes the apparatus of the base station to decode the UE radio capabilities. If the CatMl/M2 capabilities are present, the apparatus of the base station will provide a response to the request comprising the LTE-M indicator to make the core network entity aware of LTE-M access. The request may be the initial context setup request message or a separate request. The response may be the initial context setup response or a separate response.
This specific request or “trigger” in the request message may avoid that the base station would at every initial context setup request received obtain the UE radio capabilities, extract the CatMl/M2 capabilities out, before replying with the LTE-M indicator into the initial context setup response. This may avoid unnecessary processing given that most of the time the core network entity already has the LTE-M indication stored when it sends the UE radio capabilities.
Reference is made to Figure 8 which shows a method of some embodiments. The method may be performed using an apparatus. The apparatus may be provided by the core network entity. Thus the apparatus may be in the core network entity. The apparatus may be the core network entity. The core network entity may be an AMF or a MME. 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 to perform the method of Figure 8.
In step Bl, the method comprises causing a request to be provided from a core network entity to a radio access node for information indicating if a communications device is using or supporting a communications mode associated with one or more given communication categories.
In step B2, the method comprises receiving a response comprising an indication from the radio access node which indicates that the communication device is using or supporting the communications mode when said communications device is using or supporting said communications mode.
Reference is made to Figure 9 which shows a method of some embodiments. The method may be performed using an apparatus. The apparatus may be provided by the radio access node. Thus the apparatus may be in the radio access node. The apparatus may be the radio access node. The method may be performed at an eNB or a ng-gNB of an NG RAN. 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 to perform the method of Figure 9.
In step Cl, the method comprises receiving a request from a core network entity to a radio access node for information indicating if a communications device is using or supporting a communications mode associated with one or more given communication categories.
In step C2, the method comprises causing a response comprising an indication to be provided from the radio access node to the core network entity which indicates that the
communication device is using or supporting the communications mod when said communications device is using said communications mode.
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 and are not limited to E-UTRA. For example, some embodiments may apply to NR new radio or any other suitable technology. These aspects may be transposed to other radio access technology systems.
Reference has been made to a LTE-M indicator. It should be appreciated that other embodiments may be used with any other type of category which may for example require a different charging to another type of category and/or handling in a different way.
The indicator may be an indicator to indicate that the UE is in an IoT communication mode or a machine type communication mode or any other suitable type of mode. An indicator other than a LTE-M indicator may alternatively or additionally be used.
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.
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 Figures 5 to 9 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.
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.
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.
As used in this application, the term “circuitry” may refer to one or more or all of the following:
(a) hardware-only circuit implementations (such as implementations in only analogue and/or digital circuitry);
(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
(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.
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.
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.
Claims
1. An apparatus comprising 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: cause a request to be provided from a core network entity to a radio access node for information indicating if a communications device is using or supporting a communications mode associated with one or more given communication categories; and receive a response comprising an indication from the radio access node which indicates that the communication device is using or supporting the communications mode when said communications device is using or supporting said communications mode.
2. An apparatus as claimed in claim 1 , wherein the at least one memory and the computer code are configured, with the at least one processor, to cause the apparatus to determine if the information is already available to said apparatus and only providing said request if said information is not already available to said apparatus.
3. An apparatus as claimed in claim 1 or 2, wherein the communications mode comprises one or more of a machine communications mode or an IoT communications mode.
4. An apparatus as claimed in any preceding claim, wherein said communications mode comprises a LTE-M.
5. An apparatus as claimed in any preceding claim, wherein said one or more communication categories comprise one or more of category Ml and category M2.
6. An apparatus as claimed in any preceding claim, wherein the at least one memory and the computer code are configured, with the at least one processor, to cause the apparatus to provide to the radio access node radio capabilities of said communications device from which said radio access node is able to determine the indication.
7. An apparatus as claimed in claim 6, wherein the at least one memory and the computer code are configured, with the at least one processor, to cause the apparatus causing the request and said radio capabilities to be provided in a same message.
8. An apparatus as claimed in any preceding claim wherein at least one of said request and said response is provided in a respective dedicated message.
9. An apparatus as claimed in any one of claims 1 to 7, wherein at least one of said request and said response is provided in a message with at least one other information element.
10. An apparatus as claimed in claim 7, 8 or 9, wherein the message is one of an S 1 message and an N2 message.
11. An apparatus as claimed in claimed in any preceding claim wherein at least one of said request and said response is provided by a context setup request and response, respectively.
12. An apparatus as claimed in any preceding claim, wherein the response comprises information from the radio access node indicating that said radio access node does not support the communication mode when the radio access node does not support the communications mode.
13. An apparatus as claimed in any preceding claim, wherein the core network entity is mobility management entity or an access and mobility management function and the radio access node is a base station
14. An apparatus comprising 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: receive a request from a core network entity to a radio access node for information indicating if a communications device is using or supporting a communications mode associated with one or more given communication categories; and cause a response comprising an indication to be provided from the radio access node to the core network entity which indicates that the communication device is using or supporting the communications mode when said communications device is using or supporting said communications mode.
15. An apparatus as claimed in claim 14, wherein the communications mode comprises one or more of a machine communications mode or an IoT communications mode.
16. An apparatus as claimed in claim 14 or 15, wherein said communications mode comprises a LTE-M.
17. An apparatus as claimed in any of claims 14 to 16, wherein said one or more communication categories comprise one or more of category Ml and category M2.
18. An apparatus as claimed in any of claims 14 to 17, wherein the at least one memory and the computer code are configured, with the at least one processor, to cause the apparatus to receive radio capabilities of said communications device and to determine the indication from the radio capabilities of said communications device.
19. An apparatus as claimed in claim 18, wherein the at least one memory and the computer code are configured, with the at least one processor, to cause the apparatus to receive the request and said radio capabilities in a same message.
20. An apparatus as claimed in any of claims 14 to 19, wherein at least one of said request and said response is provided in a respective dedicated message.
21. An apparatus as claimed in any one of claims 14 to 19, wherein at least one of said request and said response is provided in a message with at least one other information element.
22. An apparatus as claimed in claim 19, 20 or 21, wherein the message is one of an SI message and an N2 message.
23. An apparatus as claimed in claimed in any of claims 14 to 22, wherein at least one of said request and said response is provided by a context setup request and response, respectively.
24. A method performed by an apparatus, said method comprising: causing a request to be provided from a core network entity to a radio access node for information indicating if a communications device is using or supporting a communications mode associated with one or more given communication categories; and
receiving a response comprising an indication from the radio access node which indicates that the communication device is using or supporting the communications mode when said communications device is using or supporting said communications mode.
25. The method as claimed in claim 24, comprising determining if the information is already available to said apparatus and only providing said request if said information is not already available to said apparatus.
26. The method as claimed in claim 24 or 25, where the communications mode comprises one or more of a machine communications mode or an IoT communications mode.
27. The method as claimed in any of claims 24 to 26, wherein the communications mode comprises a LTE-M.
28. The method as claimed in any of claims 24 to 27, wherein the one or more communication categories comprise one or more of category Ml and category M2.
29. The method as claimed in any claims 24 to 28, wherein the method comprises causing the radio access node radio capabilities of said communications device to be provided to the radio access node from which said radio access node is able to determine the indication.
30. The method as claimed in claim 29, wherein the method comprises causing the request and said radio capabilities to be provided in a same message.
31. The method as claimed in any claims 24 to 30, wherein at least one of said request and said response is provided in a respective dedicated message.
32. The method as claimed in any claims 24 to 30, wherein at least one of said request and said response is provided in a message with at least one other information element.
33. The method as claimed in claims 30, 31 or 32, wherein the message is one of an SI message and an N2 message.
34. The method as claimed in any of claims 24 to 33, wherein at least one of said request and said response is provided by a context setup request and response, respectively.
35. The method as claimed in any of claims 24 to 34, wherein the response comprises information from the radio access node indicating that said radio access node does not support the communication mode when the radio access node does not support the communications mode.
36. A method performed by an apparatus, said method comprising: receiving a request from a core network entity to a radio access node for information indicating if a communications device is using or supporting a communications mode associated with one or more given communication categories; and causing a response comprising an indication to be provided from the radio access node to the core network entity which indicates that the communication device is using or supporting the communications mode when said communications device is using or supporting said communications mode.
37. The method as claimed in claim 36, where the communications mode comprises one or more of a machine communications mode or an IoT communications mode.
38. The method as claimed in claim 36 or 37, wherein the communications mode comprises a LTE-M.
39. The method as claimed in any of claims 36 to 38, wherein the one or more communication categories comprise one or more of category Ml and category M2.
40. The method as claimed in any of claims 36 to 39, comprising receiving radio capabilities of said communications device and determining the indication from the radio capabilities of said communications device.
41. The method as claimed in claim 40, wherein the method comprises causing the request and said radio capabilities to be provided in a same message.
42. The method as claimed in any claims 36 to 41, wherein at least one of said request and said response is provided in a respective dedicated message.
43. The method as claimed in any claims 36 to 41, wherein at least one of said request and said response is provided in a message with at least one other information element.
44. The method as claimed in claims 41, 42 or 43, wherein the message is one of an SI message and an N2 message.
45. The method as claimed in any of claims 36 to 44, wherein at least one of said request and said response is provided by a context setup request and response, respectively.
46. A computer program product comprising computer executable code which when run on at least one processor of an apparatus causes the apparatus to perform the method of any one of claims 24 to 45.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/EP2019/071871 WO2021028050A1 (en) | 2019-08-14 | 2019-08-14 | Apparatus, methods, and computer programs |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/EP2019/071871 WO2021028050A1 (en) | 2019-08-14 | 2019-08-14 | Apparatus, methods, and computer programs |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2021028050A1 true WO2021028050A1 (en) | 2021-02-18 |
Family
ID=67660553
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/EP2019/071871 Ceased WO2021028050A1 (en) | 2019-08-14 | 2019-08-14 | Apparatus, methods, and computer programs |
Country Status (1)
| Country | Link |
|---|---|
| WO (1) | WO2021028050A1 (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2018164528A1 (en) * | 2017-03-09 | 2018-09-13 | 엘지전자 주식회사 | Method for transferring user equipment capability and apparatus for supporting same |
-
2019
- 2019-08-14 WO PCT/EP2019/071871 patent/WO2021028050A1/en not_active Ceased
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2018164528A1 (en) * | 2017-03-09 | 2018-09-13 | 엘지전자 주식회사 | Method for transferring user equipment capability and apparatus for supporting same |
| EP3579594A1 (en) * | 2017-03-09 | 2019-12-11 | LG Electronics Inc. -1- | Method for transferring user equipment capability and apparatus for supporting same |
Non-Patent Citations (1)
| Title |
|---|
| ERICSSON: "LTE-M Devices", vol. RAN WG3, no. Xian, P.R. China; 20190408 - 20190412, 6 April 2019 (2019-04-06), XP051702975, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings%5F3GPP%5FSYNC/RAN3/Docs/R3%2D191704%2Ezip> [retrieved on 20190406] * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| RU2566981C2 (en) | Transmission of small data volumes in wireless communication network | |
| US11943674B2 (en) | Conditional handover of master node in the presence of secondary node | |
| CA2861483C (en) | Handling dual priority configurations in a wireless communication network | |
| US9801225B2 (en) | System and method for controlling a licensed shared access radio | |
| EP3799514B1 (en) | Rate control methods, devices, computer program and system | |
| US20200084613A1 (en) | Status switching method and apparatus | |
| US20240080340A1 (en) | Security for Groupcast Message in D2D Communication | |
| EP3963933B1 (en) | Method, apparatus, computer program product and computer program | |
| CN112637785B (en) | Method and apparatus for multicast transmission | |
| WO2019091307A1 (en) | Communication method and device | |
| KR101669165B1 (en) | Method for providing private network service and mobility management entity for the same | |
| WO2022218343A1 (en) | Method and apparatus for session management function reselection | |
| JP2024535453A (en) | Communication method and apparatus | |
| US11943673B2 (en) | Method and apparatus for tracking area topology | |
| US11991516B2 (en) | Session migration method and apparatus | |
| CN116074828A (en) | Method and apparatus for managing security context | |
| EP3634031B1 (en) | Method for controlling network congestion, terminal device, and network device | |
| WO2023020382A1 (en) | Method and apparatus for session management | |
| WO2021028050A1 (en) | Apparatus, methods, and computer programs | |
| KR20210076958A (en) | Device and method for deleting user equipment capability identifier | |
| US20240340752A1 (en) | Apparatus, method and computer program | |
| WO2020155174A1 (en) | Information transmission method and communication device | |
| CN120752966A (en) | Apparatus, method and computer program | |
| WO2020253948A1 (en) | Session management function selection policy with limited assistance information provided by a user equipment | |
| WO2021004606A1 (en) | Apparatus, method, and computer program for performing access check with a cellular network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 19755594 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 19755594 Country of ref document: EP Kind code of ref document: A1 |