EP3520514B1 - Appareils et procédés de télécommunications sans fil - Google Patents

Appareils et procédés de télécommunications sans fil Download PDF

Info

Publication number
EP3520514B1
EP3520514B1 EP17781100.7A EP17781100A EP3520514B1 EP 3520514 B1 EP3520514 B1 EP 3520514B1 EP 17781100 A EP17781100 A EP 17781100A EP 3520514 B1 EP3520514 B1 EP 3520514B1
Authority
EP
European Patent Office
Prior art keywords
paging
identifier
terminal
relay
base station
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.)
Active
Application number
EP17781100.7A
Other languages
German (de)
English (en)
Other versions
EP3520514A1 (fr
Inventor
Brian Alexander Martin
Yuxin Wei
Vivek Sharma
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sony Europe BV United Kingdom Branch
Sony Group Corp
Original Assignee
Sony Europe Ltd
Sony Corp
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Sony Europe Ltd, Sony Corp filed Critical Sony Europe Ltd
Publication of EP3520514A1 publication Critical patent/EP3520514A1/fr
Application granted granted Critical
Publication of EP3520514B1 publication Critical patent/EP3520514B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/005—Transmission of information for alerting of incoming communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/047—Public Land Mobile systems, e.g. cellular systems using dedicated repeater stations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user

Definitions

  • the present disclosure relates to wireless telecommunications apparatus and methods.
  • Third and fourth generation mobile telecommunication systems such as those based on the 3GPP defined UMTS and Long Term Evolution (LTE) architecture, are able to support more sophisticated services than simple voice and messaging services offered by previous generations of mobile telecommunication systems. For example, with the improved radio interface and enhanced data rates provided by LTE systems, a user is able to enjoy high data rate applications such as mobile video streaming and mobile video conferencing that would previously only have been available via a fixed line data connection.
  • the demand to deploy third and fourth generation networks is therefore strong and the coverage area of these networks, i.e. geographic locations where access to the networks is possible, is expected to increase rapidly.
  • Future wireless communications networks will be expected to efficiently support communications with a wider range of devices associated with a wider range of data traffic profiles and types than current systems are optimised to support. For example it is expected future wireless communications networks will be expected to efficiently support communications with devices including reduced complexity devices, machine type communication devices, high resolution video displays, virtual reality headsets and so on. Some of these different types of devices may be deployed in very large numbers, for example low complexity devices for supporting the "The Internet of Things", and may typically be associated with the transmissions of relatively small amounts of data with relatively high latency tolerance, whereas other types of device, for example supporting high-definition video streaming, may be associated with transmissions of relatively large amounts of data with relatively low latency tolerance.
  • a single device type might also be associated with different traffic profiles depending on the applications it is running. For example, different consideration may apply for efficiently supporting data exchange with a smartphone when it is running a video streaming application (high downlink data) as compared to when it is running an Internet browsing application (sporadic uplink and downlink data).
  • the network infrastructure needs to know the relevant characteristics of the terminal devices' operation - i.e. the characteristics which may impact how communications with the terminal device should be handled to improve efficiency.
  • the relevant characteristics of a terminal device's operation may be broadly considered to fall into two categories of information.
  • a first category which may be referred to herein as capability information, includes information which relates to the fundamental ability of the terminal device to access the radio network, for example in terms of the radio access technologies it supports, its operating bandwidth and frequencies, MIMO support, carrier aggregation support, and so on.
  • Capability information may thus broadly be considered to relate to characteristics of the device which are generally set by hardware and which determine how the terminal device can access the physical layer. The use of such capability information in configuring communications in wireless telecommunications systems is well established.
  • a second category of information which may be referred to herein as application information or device context information, includes information which relates to higher-layer operations of the terminal device (i.e. layers higher than the physical later), for example including information relating to software applications the device supports / is currently running, and the nature of the device and how it is being used, for example in terms of whether the device is a static device, a mobile device, a wearable device, and so on.
  • Application information / device context information may thus be considered to include information representing parameters / characteristics that relate to a current mode of operation for a mobile device, its environment and mobility, and other information which is separate from the capability information relating to how the terminal device may physically access the radio interface.
  • WO 2016/019528 A1 discusses a terminal, network equipment, paging method and regional information update method.
  • EP 1244321 A1 discusses a method of registering position of mobile communication terminal, general calling method for mobile communication terminal and mobile communication system.
  • the present disclosure can help address or mitigate at least some of the issues discussed above.
  • Figure 1 provides a schematic diagram illustrating some basic functionality of a mobile telecommunications network / system 100 operating generally in accordance with LTE principles but which may also support other radio access technologies and which may implement embodiments of the disclosure as described herein.
  • Various elements of Figure 1 and their respective modes of operation are well-known and defined in the relevant standards administered by the 3GPP (RTM) body, and also described in many books on the subject, for example, Holma H. and Toskala A [1]. It will be appreciated that operational aspects of the telecommunications network which are not specifically described below may be implemented in accordance with any known techniques, for example according to the relevant standards and previously proposed modifications and additions to the relevant standards.
  • the network 100 includes a plurality of base stations 101 connected to a core network 102.
  • Each base station provides a coverage area 103 (i.e. a cell) within which data can be communicated to and from terminal devices 104.
  • Data is transmitted from base stations 101 to terminal devices 104 within their respective coverage areas 103 via a radio downlink.
  • Data is transmitted from terminal devices 104 to the base stations 101 via a radio uplink.
  • the core network 102 routes data to and from the terminal devices 104 via the respective base stations 101 and provides functions such as authentication, mobility management, charging and so on.
  • Terminal devices may also be referred to as mobile stations, user equipment (UE), user terminal, mobile radio, communications device, and so forth.
  • Base stations which are an example of network infrastructure equipment, may also be referred to as transceiver stations / nodeBs / e-nodeBs, and so forth.
  • FIG. 2 schematically shows some further details of a telecommunications system 500 according to an example of the present disclosure.
  • the telecommunications system 500 in this example is based broadly around an LTE-type architecture and the telecommunications system may also support other radio access technologies, either using the same hardware as represented in Figure 2 with appropriately configured functionality or separate hardware configured to operate in association with the hardware represented in Figure 2 .
  • Many aspects of the operation of the telecommunications system / network 500 are known and understood and are not described here in detail in the interest of brevity. Operational aspects of the telecommunications system 500 which are not specifically described herein may be implemented in accordance with any known techniques, for example according to the current LTE-standards and other proposals for operating wireless telecommunications systems.
  • the telecommunications system 500 comprises a core network part (evolved packet core) 502 coupled to a radio network part.
  • the radio network part comprises a base station (evolved-nodeB) 504 coupled to a terminal device 508.
  • a base station 504 and one terminal device 508 are represented in Figure 2 .
  • the radio network part will typically comprise a plurality of base stations serving a larger number of terminal devices across various communication cells, as well as potentially including transceiver stations supporting radio communications with terminal devices on cells operating in accordance with other radio access technologies, such as UTRAN, GERAN, WLAN or a 5G new RAT.
  • UTRAN UTRAN
  • GERAN GERAN
  • WLAN wireless local area network
  • the terminal device 508 is arranged to communicate data to and from the base station (transceiver station) 504.
  • the base station is in turn communicatively connected to a serving gateway, S-GW, (not shown) in the core network part which is arranged to perform routing and management of mobile communications services to the terminal device in the telecommunications system 500 via the base station 504.
  • S-GW serving gateway
  • the core network part 502 also includes a mobility management entity, MME, (not shown) which manages the enhanced packet service, EPS, connections with the terminal device 508 operating in the communications system based on subscriber information stored in a home subscriber server, HSS.
  • MME mobility management entity
  • Other network components in the core network include a policy charging and resource function, PCRF, and a packet data network gateway, PDN-GW, which provides a connection from the core network part 502 to an external packet data network, for example the Internet.
  • PCRF policy charging and resource function
  • PDN-GW packet data network gateway
  • the operation of the various elements of the communications system 500 shown in Figure 2 may be conventional apart from where modified to provide functionality in accordance with examples of the present disclosure as discussed herein.
  • this disclosure may in general be implemented in wireless communications systems operating in accordance with different radio access technologies, for example , who one or more of UTRAN, GERAN, WLAN or a 5G new RAT (NR) networks, and these other radio access technologies will not necessarily incorporate the same network infrastructure components as for an LTE implementation (e.g. there may be no serving gateway in new RAT networks).
  • the terminal device 508 is adapted to support operations in accordance with examples of the present disclosure when communicating with the base station 504 as discussed further herein.
  • the terminal device 508 comprises transceiver circuitry 508a (which may also be referred to as a transceiver / transceiver unit) for transmission and reception of wireless signals and processor circuitry 508b (which may also be referred to as a processor / processor unit) configured to control the terminal device 508.
  • the processor circuitry 508b may comprise various sub-units / sub-circuits for providing functionality in accordance with examples of the present disclosure as described herein. These sub-units may be implemented as discrete hardware elements or as appropriately configured functions of the processor circuitry.
  • the processor circuitry 508b may comprise circuitry which is suitably configured / programmed to provide the desired functionality described herein using conventional programming / configuration techniques for equipment in wireless telecommunications systems.
  • the transceiver circuitry 508a and the processor circuitry 508b are schematically shown in Figure 2 as separate elements for ease of representation.
  • the functionality of these circuitry elements can be provided in various different ways, for example using one or more suitably programmed programmable computer(s), or one or more suitably configured application-specific integrated circuit(s) / circuitry / chip(s) / chipset(s).
  • the terminal device 508 will in general comprise various other elements associated with its operating functionality, for example a power source, user interface, and so forth, but these are not shown in Figure 2 in the interests of simplicity.
  • the base station 504 comprises transceiver circuitry 504a (which may also be referred to as a transceiver / transceiver unit) for transmission and reception of wireless signals and processor circuitry 504b (which may also be referred to as a processor / processor unit) configured to control the base station 504 to operate in accordance with examples of the present disclosure as described herein.
  • transceiver circuitry 504a which may also be referred to as a transceiver / transceiver unit
  • processor circuitry 504b which may also be referred to as a processor / processor unit
  • the processor circuitry 504b may again comprise various sub-units, such as a scheduling unit, for providing functionality in accordance with examples of the present disclosure as explained further below. These sub-units may be implemented as discrete hardware elements or as appropriately configured functions of the processor circuitry. Thus, the processor circuitry 504b may comprise circuitry which is suitably configured / programmed to provide the desired functionality described herein using conventional programming / configuration techniques for equipment in wireless telecommunications systems.
  • the transceiver circuitry 504a and the processor circuitry 504b are schematically shown in Figure 2 as separate elements for ease of representation.
  • circuitry elements can be provided in various different ways, for example using one or more suitably programmed programmable computer(s), or one or more suitably configured application-specific integrated circuit(s) / circuitry / chip(s) / chipset(s).
  • the base station 504 will in general comprise various other elements associated with its operating functionality, such as a scheduler.
  • the processor circuitry 504b may comprise scheduling circuitry, that is to say the processor circuitry 504b may be configured / programmed to provide the scheduling function for the base station 504.
  • Figure 3 schematically represents some aspects of a wireless telecommunications network comprising a relay node.
  • the base station 201 can communicate directly with the relay ide ("RN") 211 but not with the terminal ("UE") 212 that is out of reach of the base station as it sits outside the cell 202 provided by the base station 201.
  • RN 211 is configured to relay communications between the terminal 212 and the base station 211, then the terminal 212 can communicate with the base station 201, as illustrated with the dotted line in Figure 3 .
  • Figure 3 illustrates the general principle of relaying, implementing such an arrangement in a mobile network can be challenging due to for example the security requirements, the existing procedures already in place (which may not for example facilitate the setup of a relaying configuration).
  • Figure 3 is for illustrative purposes only and that other relaying configurations are possible and considered under the present disclosure, such as for example a case where the terminal 212 is within the cell 202 but still uses the relay 211 for communicating with or via the base station 201. This is particularly relevant to cases where the terminal 212 is on the edge of the cell 202.
  • the current arrangement for relaying is one where the base station is not aware of the presence of the terminal but, as far as it is concerned it is only communicating with the relay.
  • the relay can then determine to whom the data should actually be sent, whether it will be itself or to another element, for example to a terminal for which it is acting as a relay.
  • the base station in the event that the base station is intending to exchange data with the terminal, it will in fact exchange the data with the relay node and the relay node will then be able to exchange the data with the terminal.
  • Figure 4 schematically represents a signalling ladder diagram representing a conventional paging procedure and is a signalling ladder diagram representing a conventional paging procedure for a terminal device 104 operating within the example LTE-type network schematically represented in Figure 1 .
  • Figure 4 schematically represents signalling and operating functions associated with the terminal device 104, the base stations 101A, 101B comprising the tracking area 107, and the core network, in particular the MME 105.
  • the respective cells of base stations 101A and 101B will hereinafter be referred to as cell 103A and cell 103B for brevity.
  • the UE 104 has attached to the network through base station 101A within the tracking area 107.
  • the specific base station through which the terminal device initially attaches may be determined from reference signal measurements, and so forth, whereby the terminal device determines which base station is most appropriate.
  • the core network assigns an IP address for the UE. From this point onwards the core network will recognise the existence of the terminal device and keep track of its location at a tracking area level as discussed above.
  • the core network identifies the terminal device as being within tracking area 107 (because the terminal device has accessed the network through base station 101A, which is within tracking area 107).
  • the UE 104 has not moved to a different tracking area and so has not provided any tracking area update.
  • the core network 102 continues to assume that the terminal device is located somewhere within tracking area 107.
  • the UE 104 Having attached to the network, the UE 104 enters RRC idle mode.
  • an idle device periodically checks for paging messages broadcast on a paging channel, with a frequency set by the cycle of the Discontinuous Receive (DRX) mode so that a check happens each time the device wakes up for its DRX active time. This is known as a paging occasion, and in it the UE decodes resource allocation information in a Physical Downlink Control Channel (PDCCH) and finds the paging message in an associated Physical Downlink Shared Channel (PDSCH).
  • PDCCH Physical Downlink Control Channel
  • PDSCH Physical Downlink Shared Channel
  • the MME 105 recognises that a paging instance has arisen for the UE 104 which is in idle mode.
  • the specific reason for the paging requirement is not significant, and may, for example be because a third party is seeking to place a telephone call to the UE 104.
  • the MME thus initiates a paging procedure to contact the UE 104.
  • the MME 105 in the core network 102 can recognise that the UE 104 is located in one of the communication cells 103A and 103B which comprise tracking area 107, but the MME 105 does not know which one. Accordingly, in step S1, the MME 105 sends a paging request message over the S1-AP interface to each of the base stations 101A and 101B associated with the tracking area 107. Thus, in this example the MME 105 sends paging request messages to both base stations 101A and 101B. The MME 105 does not send a paging request message to the base station 101C serving communication cell 103C because communication cell 103C is not within tracking area 107 in which the terminal device is taken as being located.
  • All base stations receiving a paging request message from the MME 105 are configured to then transmit paging signalling to seek to establish contact with the required terminal device 104.
  • This is schematically represented in Figure 4 in step S2.
  • the paging signalling is an RRC: Paging message format, since this communication stage is between the eNB and the UE.
  • the idle UE 104 has remained within the coverage area 103A of base station 101A, and will be checking for paging messages. It therefore receives the paging signalling transmitted in step S2 by base station 101A, as a paging occasion.
  • the paging signalling sent in step S2 by base station 101B is of course not received by the UE 104, and so this is in effect wasted signalling.
  • Random Access being an RRC connection establishment procedure initiated by a UE, comprises a RRC Connection Request message from the UE to the eNB, a RRC Connection Set-up message from the eNB back to the UE, and a RRC Connection Complete message from the UE to the eNB.
  • the UE 104 has now transitioned in an RRC_CONNECTED state.
  • step S4 the eNB 101A uses the S1 interface to send a Service Request message to the MME 105. This informs the MME that the UE has been successfully contacted and is able to receive data.
  • the network e.g. the base station
  • the terminal is assigned an identifier for the relay to be able to monitor paging massages for the terminal.
  • the identifier can be included in the paging messages for the terminal and, in some cases, can be used to determine a paging occasion associated with the terminal, namely, the timing of the paging message transmission is derived from the identifier (in other cases an identifier for the relay may for example be used to derive the paging occasion).
  • the identifier for the terminal is the terminal's UE identity (e.g. IMSI or TMSI) or based on the terminal's UE identity (e.g. IMSI mod 1024) while in other cases it can be, or be based on, a "resume" ID associated with a suspended RRC connection, as will be clear from the discussion below.
  • the identifier for the terminal as included in the paging message to identify the recipient of the paging message, is the IMSI or TMSI and the paging occasion is derived from either the IMSI/TMSI (as appropriate), or from an identifier for the relay node in the event that the paging is carried out on the relay paging times.
  • the identifier for the relay node may also be an IMSI or TMSI for the relay in some examples.
  • Figure 5 schematically represents some aspects of a paging method in a wireless telecommunications network comprising a relay node in accordance with a first example of the present disclosure.
  • the network is able to page the terminal using the terminal identifier ("UE ID") and using the relay paging occasion (that is the paging occasion calculated based on the relay UE identity).
  • the base station pages the terminal using a paging occasion that is not for the terminal.
  • the paging message can be received by and forwarded by the relay and/or received directly by the remote UE in the event that it is within coverage of the base station and that it monitors the paging occasions for the relay.
  • the terminal may be notified of the relay UE paging occasions, it can monitor for paging using the relay UE paging occasion.
  • the terminal can be notified of the paging occasions for the relay for example by being notified of an identifier for the relay and where the terminal can then derive the paging occasions from the relay identifier.
  • This example can assist the terminal in receiving the paging messages ultimately addressed to itself in case of mobility for example, where it may no longer be connected to the from relay and thus unable to receiving the paging message via the relay.
  • this figure illustrates an example procedure as follows.
  • the terminal establishes a connection with the relay. This is likely to occur while the relay is RRC connected to the network or to trigger an RRC connection between the relay and network (for example such that the network can authorize and/or be notified of the relaying).
  • the terminal can provide its identifier "UE-ID" (e.g. IMSI) or, alternatively, a temporary ID may be allocated (e.g. RNTI, resume ID or likewise).
  • UE-ID e.g. IMSI
  • a temporary ID may be allocated (e.g. RNTI, resume ID or likewise).
  • the relay can inform and/or negotiate the terminal's connection with the network.
  • the base station is aware of the presence of the terminal associated with UE-ID, of its identifier UE-ID and of the identity of its relay.
  • the network can then send a paging message to the terminal, the message being addressed to the UE-ID and, in this first example, being scheduled to correspond to the paging occasions for the relay for the terminal (see 53).
  • the base station is then using the relay device paging occasions for paging the remote UE.
  • the relay device can go or remain in an idle mode to save power while still monitoring its own paging occasions.
  • the relay can check for its own identifier and also for the UE-ID for any remote UEs it is acting for as a relay (54).
  • the relay can maintain a paging record of UE-ID of any remote UEs it is serving, so the paging messages can be forwarded to the relevant terminal.
  • the paging record list comprises identifiers that may be used in a paging message and can for example contain a list of IMSI or TMSI for identifying the remote UE, that is, the ultimate terminal for which the paging message is intended.
  • identifiers for addressing the remote UEs via a relay may be used, for example in the event that it would be preferable for the relay not to be aware of the IMSI or TMSI for the remote UE.
  • the relay can then page the terminal, e.g. by relaying the paging message with the UE-ID (55).
  • the relay can use the appropriate timing/scheduling. For example it may be sent on paging occasions for the relay to page the terminal.
  • the terminal Once the terminal has been paged, it can wake up (55) to set up the necessary connections to connect directly or indirectly (via the relay) with the base station that has paged it via the relay.
  • the terminal no longer needs to use the relay is now able to communicate directly with the base station (e.g. if it has moved and is now closer to the base station or further from the relay), it can disconnect from the relay and camp on the cell provided by the base station.
  • the terminal can then monitor the relay device paging occasions, for checking paging addressed to its own identifier. This can be done until for example until the terminal connects directly to the base station (the base station can then revert to normal paging) or connects to a different base station.
  • the terminal With this type of paging monitoring by the terminal, the terminal will be informed of the ID for the relay; part of the ID for the relay and/or of an indication what paging occasions to use so that it can monitor the relevant paging occasions. Preferably the terminal will be notified of this relay paging occasions information prior to a disconnection from the relay (e.g. it can be informed as soon as it is connected to the relay).
  • Figure 7 schematically represents some aspects of a paging method in a wireless telecommunications network comprising a relay node.
  • the illustration of Figure 7 provides a more detailed example implementation of the method discussed in respect of Figure 5 above where the method comprises the following steps:
  • This option limits the power consumption for the relay node, in particular in cases where the relay serves several remote terminals.
  • the relay only monitors its own paging occasions and does not have to "wake up" at different occasions to monitor paging messages.
  • this example requires changes in how the network/base stations page the terminals as the paging messages would have to be transmitted to the terminal (using an identifier for the terminal) but at a paging occasion that correspond to a different identifier / mobile node, namely the relay.
  • the paging information is sent on paging occasions that correspond to the remote UE.
  • This case is similar to that discussed above, for example in respect of Figure 5 and 7 , but where the base station sends the paging message at a scheduled time that is for the ultimate destination (e.g. at a time derived from the UE-ID) but wherein the paging message will effectively be monitored, received and forwarded by the relay.
  • the relay UE can thus monitor paging occasions of the remote UE(s) as well as its own paging occasions.
  • FIG. 6 schematically represents some aspects of a paging method a wireless telecommunications network comprising a relay node.
  • the initial steps are similar to those previously discussed in respect of the first example such that, in the interest of conciseness, they will not be repeated again.
  • the base station can send a paging message. If the paging message is for the terminal, it is sent with the UE-ID and at a paging occasion for the terminal (63a) while, of the paging message is for the relay, it is sent with an identifier for the relay and at a paging occasion for the relay (63b).
  • the relay monitors both paging occasions so that it can receive all paging messages and if it detects one for the terminal, it can forward the paging information to the terminal (65) so that the terminal can wake up from an idle mode and set up a connection with the base station (via the relay if appropriate).
  • the relay is expected to monitor several paging occasions and will thus use more power -and even more so if the relay is serving a large number of terminals.
  • this other example requires minimal modifications to the network elements such as the base station that can page a terminal being relayed in a conventional way (despite the terminal not communicating with the base station directly).
  • the paging occasions will be calculated using the appropriate method for deriving a paging timing from at least an identifier. This is discussed in particular in 36.304 "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode” [2], in sections 7.1 and 7.3.
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • UE User Equipment
  • the remote UE can adjust its paging occasions to be aligned with those of the relay UE.
  • the terminal can do so as soon as it is aware of the paging occasions for the relay or only when it expect that it will be able to reliable receive paging messages from the base station and/or to no longer be serviced by the relay.
  • the terminal can monitor the relay paging occasions so that it can disconnect from the relay and camp on the cell of the base station, in a conventional manner, without having to inform the network that it is no longer relying on the relay but only on the base station directly, to communicate with the network.
  • the terminal UE-ID (or at least the IMSI or the IMSI modulo 1024 so that the paging occasion can be derived) may be shared with the remote UE so that the relay can monitor the paging occasions corresponding to the terminal's identifier.
  • the relay UE or base station might generate a temporary UE-ID to provide to the remote UE. This temporary ID could be used both in the paging record list, as well as for calculation of paging occasion.
  • the temporary identifier is selected such that its corresponding paging occasions are identical to those of the terminal.
  • the temporary ID may be selected such that it has the same mod 1024 value and additionally comprise other random or otherwise values to make a full identifier in accordance with the appropriate standard or expectations of the network or terminal.
  • some of the parameters which come from paging occasion calculation could be provided to the remote UE, for example SFN mod T and i_s (see [2]) such that an appropriate temporary can be selected such that the true identifier for the terminal does not have to be communicated but such that the paging occasions would not be altered.
  • This example could be used as long as the UE is on the same cell as the relay, or if the terminal reselects another cell using the same DRX length and parameters.
  • the UE may have to perform a connection establishment to inform the network of its location, and revert to using its own paging occasions as well as the regular UE-ID in the paging record list (if another one was being used).
  • it can set up a new temporary identifier that is adapted for the terminal and the new cell.
  • the relay UE can monitor the paging occasions associated with the remote UE, where the UE-ID (e.g. IMSI mod 1024, or temporary ID) of the remote UE is provided to the relay.
  • This communications can thus be handled locally between the remote UE and the relay without necessarily updating for example the base station and MME.
  • this example may be less disruptive to the existing network elements and require minimal changes.
  • this example implies an increased power consumption for the relay, especially in case the paging occasions are all different.
  • the relay can be configured to always forward some or all of paging messages to some or all of the remote UEs, or to forward the paging messages containing the recognizable part of the UE ID (e.g. IMSI mod 1024). Although this would simplify the checking process for the relay, this would also likely increase power consumption for both the relay and the remote UE. If for example the relay forwards all paging messages to all remote UEs, each remote UE will likely receive paging messages that are not addressed to itself and will then receive more paging messages than it requires. The remote UE will then have to check all the messages and thus increase its power consumption compared to a case where only the relevant paging messages -or more relevant paging message- are forwarded to the remote UE.
  • the ID for the terminal can be an ID that is already shared between the terminal and base station and that is associated with a suspended connection between the base station and terminal.
  • the skilled person is for example directed to PCT application PCT/EP2016/066958 filed 15 July 2016 , the content of which may be of interest.
  • a common ID may be used for alignment of paging occasions by sharing, with the relay, the "resume ID" used when performing the connection suspend/resume procedure.
  • Connection suspend/resume was introduced for CiOT optimisation in Release 13 of 3GPP wherein, rather than releasing the RRC Connection, the UE can be sent to an idle mode and can store AS related context information (e.g. security related parameters).
  • the resume ID can be sent to the network in a resume request such that the context can be automatically retrieved by the network to re-establish the connection with the terminal.
  • "light connection" is being discussed wherein a resume ID may be used in the paging message and which can thus be used by the RAN to perform paging to a device.
  • the context information will be known to the base and the remote UE, and the shared/resume ID does not allow the relay to interpret any of the forwarded data (because the security context exists between the remote UE and network and the relay does not have access to it) and it can prevent sharing of the IMSI.
  • a remote terminal may not need to notify the network (e.g. the base station or via the base station) when it drops its connection to the relay device and reselects a cell to camp on it in a conventional manner, as it may be able to continue monitoring paging occasions for the relay device. Accordingly, signalling overhead savings can thereby be achieved. And the network can still reach the UE directly using normal paging (with different paging occasion and potentially different form of UE-ID)
  • the terminal is configured to communicate with the base station via the relay node, the method comprising the base station transmitting a paging message for the terminal wherein: the paging message comprises a paging identifier for identifying the terminal; and the paging message is transmitted at a paging time for a destination identifier.
  • the terminal can be paged in a relay environment with a method that assist with reducing overhead and that can enable the base station to address the terminal directly.
  • the "paging" identifier used for identifying the terminal is any suitable identifier for the terminal that can be used in the paging message.
  • the paging identifier will be (or be based on) either an existing identifier for the terminal (e.g. the IMSI, the TMSI, a IMSI- or TMSI-based identifier), a temporary identifier (e.g. the RNTI or resume-ID for a terminal having a suspended RRC connection), or any other suitable identifier that will enable the base station and terminal to identify and address the terminal specifically.
  • the paging time may be any appropriate time for paging the terminal. In current systems, this is typically a messaging occasion/time/schedule that is derived from one or more identifiers such that the paged terminal/device will be aware of when paging messages will be transmitted, if any.
  • steps discussed herein may be carried out in any suitable order and not necessarily in the order in which they are listed.
  • steps may be carried out in an order which differs from an order used in the examples discussed above or from an indicative order used anywhere else for listing steps (e.g. in the claims), whenever possible or appropriate.
  • some steps may be carried out in a different order, or simultaneously (entirely or in part) or in the same order. So long as an order for carrying any of the steps of any method discussed herein is technically feasible, it is explicitly encompassed within the present disclosure.
  • transmitting information or a message to an element may involve sending one or more messages to the element and may involve sending part of the information separately from the rest of the information.
  • the number of "messages" involved may also vary depending on the layer or granularity considered. For example transmitting a message may involve using several resource elements in an LTE environment such that several signals at a lower layer correspond to a single message at a higher layer.
  • transmissions from one terminal to another may relate to the transmission of any one or more of user data, discovery information, control signalling and any other type of information to be transmitted.
  • any suitable element or elements that can carry out the function can be configured to carry out this function or step.
  • any one or more of a mobile terminal, a base station or any other mobile unit may be configured accordingly if appropriate, so long as it is technically feasible and not explicitly excluded.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Claims (14)

  1. Procédé de radiomessagerie d'un terminal (104, 212, 508), par une station de base (101, 201, 504) et par l'intermédiaire d'un nœud relais (211), le terminal étant configuré pour communiquer avec la station de base par l'intermédiaire du nœud relais, caractérisé en ce que le procédé comprend :
    la notification au nœud relais d'un identifiant de radiomessagerie pour identifier le terminal au moins dans des radiomessages dans lesquels l'identifiant de radiomessagerie est l'un i) d'un identifiant attribué antérieurement associé à une connexion mise en suspens avec la station de base pour reprendre une connexion de commande de ressources radio et ii) d'un identifiant temporaire qui diffère d'un identifiant permanent du terminal et qui est associé au même temps de radiomessagerie que l'identifiant permanent ; et
    la transmission par la station de base d'un radiomessage adressé au terminal ;
    dans lequel :
    le radiomessage comprend l'identifiant de radiomessagerie ; et
    le radiomessage est transmis à un temps de radiomessagerie d'un identifiant de destination ; et
    le procédé comprend en outre la surveillance par le nœud relais du temps de radiomessagerie de l'identifiant de destination à la recherche de radiomessages comprenant l'identifiant de radiomessagerie.
  2. Procédé selon n'importe quelle revendication précédente dans lequel l'identifiant de destination est l'un de l'identifiant de radiomessagerie et d'un identifiant du nœud relais.
  3. Procédé selon la revendication 1 comprenant en outre :
    l'attribution d'un identifiant de terminal au terminal ;
    et
    l'utilisation de l'identifiant de terminal en tant qu'identifiant de destination ou identifiant de radiomessagerie, ou les deux.
  4. Procédé selon la revendication 3 dans lequel l'attribution d'un identifiant de terminal comprend la détermination par le terminal ou la station de base d'un identifiant et la notification au nœud relais de l'identifiant de terminal du terminal.
  5. Procédé selon la revendication 1 comprenant en outre :
    la surveillance par le terminal du temps de radiomessagerie d'un identifiant de relais du nœud relais à la recherche de radiomessages comprenant l'identifiant de radiomessagerie.
  6. Procédé selon n'importe quelle revendication précédente comprenant en outre :
    la surveillance par le nœud relais du temps de radiomessagerie de l'identifiant de destination à la recherche de radiomessages adressés au terminal ; et
    la surveillance par le nœud relais du temps de radiomessagerie d'un identifiant de relais du nœud relais à la recherche de radiomessages adressés au nœud relais.
  7. Procédé selon la revendication 1 comprenant en outre :
    la réception par le nœud relais du radiomessage transmis ;
    et
    le relais par le nœud relais du radiomessage au terminal.
  8. Station de base (101, 201, 504) destinée à la radiomessagerie d'un terminal (104, 212, 508) par l'intermédiaire d'un nœud relais (211), le terminal étant configuré pour communiquer avec la station de base par l'intermédiaire du nœud relais,
    caractérisée en ce que la station de base est configurée pour :
    notifier au nœud relais un identifiant de radiomessagerie pour identifier le terminal au moins dans des radiomessages dans lesquels l'identifiant de radiomessagerie étant l'un i) d'un identifiant attribué antérieurement associé à une connexion mise en suspens avec la station de base pour reprendre une connexion de commande de ressources radio et ii) d'un identifiant temporaire qui diffère d'un identifiant permanent du terminal et qui est associé au même temps de radiomessagerie que l'identifiant permanent ; et
    transmettre un radiomessage au terminal,
    dans lequel :
    le radiomessage comprend l'identifiant de radiomessagerie ; et
    le radiomessage est transmis à un temps de radiomessagerie d'un identifiant de destination.
  9. Procédé d'aide à la radiomessagerie d'un terminal (104, 212, 508), par une station de base (101, 201, 504) et par l'intermédiaire du nœud relais (211), le terminal étant configuré pour communiquer avec la station de base par l'intermédiaire du nœud relais, caractérisé en ce que le procédé comprend par le nœud relais :
    la réception d'une notification d'un identifiant de radiomessagerie pour identifier le terminal au moins dans des radiomessages dans lesquels l'identifiant de radiomessagerie est l'un i) d'un identifiant attribué antérieurement associé à une connexion mise en suspens avec la station de base pour reprendre une connexion de commande de ressources radio et ii) d'un identifiant temporaire qui diffère d'un identifiant permanent du terminal et qui est associé au même temps de radiomessagerie que l'identifiant permanent ;
    la surveillance du temps de radiomessagerie d'un identifiant de destination à la recherche de radiomessages adressés au terminal, le terminal étant identifié par l'identifiant de radiomessagerie dans les radiomessages addressés au terminal ; et
    la surveillance du temps de radiomessagerie d'un identifiant de relais du nœud relais à la recherche de radiomessages adressés au nœud relais.
  10. Procédé selon la revendication 9 comprenant en outre la réception d'une notification de l'identifiant de destination pour le terminal.
  11. Nœud relais (211) d'aide à la radiomessagerie d'un terminal (104, 212, 508), par une station de base (101, 201, 504) et par l'intermédiaire du nœud relais, dans lequel le terminal est configuré pour communiquer avec la station de base par l'intermédiaire du nœud relais, caractérisé en ce que le nœud relais est configuré pour recevoir une notification d'un identifiant de radiomessagerie pour identifier le terminal au moins dans des radiomessages dans lesquels l'identifiant de radiomessagerie est l'un i) d'un identifiant attribué antérieurement associé à une connexion mise en suspens avec la station de base pour reprendre une connexion de commande de ressources radio et ii) d'un identifiant temporaire qui diffère d'un identifiant permanent du terminal et qui est associé au même temps de radiomessagerie que l'identifiant permanent ; surveiller le temps de radiomessagerie d'un identifiant de destination à la recherche de radiomessages adressés au terminal, le terminal étant identifié par l'identifiant de radiomessagerie dans les radiomessages adressés au terminal ; et
    surveiller le temps de radiomessagerie d'un identifiant de relais du nœud relais à la recherche de radiomessages adressés au nœud relais.
  12. Procédé de réception de radiomessages par un terminal (104, 212, 508) et depuis une station de base (101, 201, 504), caractérisé en ce que le procédé comprend :
    la surveillance par le terminal du temps de radiomessagerie d'un identifiant de relais d'un nœud relais (211) à la recherche de radiomessages comprenant un identifiant de radiomessagerie, l'identifiant de radiomessagerie servant à identifier le terminal au moins dans des radiomessages et dans lequel l'identifiant de radiomessagerie est l'un i) d'un identifiant attribué antérieurement associé à une connexion mise en suspens avec la station de base pour reprendre une connexion de commande de ressources radio et ii) d'un identifiant temporaire qui diffère d'un identifiant permanent du terminal et qui est associé au même temps de radiomessagerie que l'identifiant permanent.
  13. Procédé selon la revendication 12 dans lequel le nœud relais est un relais qui relayait antérieurement des communications entre le terminal et la station de base.
  14. Terminal (104, 212, 508) destiné à recevoir des radiomessages à partir d'une station de base (101, 201, 504), caractérisé en ce que le terminal est configuré pour :
    surveiller le temps de radiomessagerie d'un identifiant de relais d'un nœud relais (211) à la recherche de radiomessages comprenant un identifiant de radiomessagerie, l'identifiant de radiomessagerie servant à identifier le terminal au moins dans des radiomessages et l'identifiant de radiomessagerie étant l'un i) d'un identifiant attribué antérieurement associé à une connexion mise en suspens avec la station de base pour reprendre une connexion de commande de ressources radio et ii) d'un identifiant temporaire qui diffère d'un identifiant permanent du terminal et qui est associé au même temps de radiomessagerie que l'identifiant permanent.
EP17781100.7A 2016-11-03 2017-10-09 Appareils et procédés de télécommunications sans fil Active EP3520514B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP16197181 2016-11-03
PCT/EP2017/075607 WO2018082869A1 (fr) 2016-11-03 2017-10-09 Appareils et procédés de télécommunications sans fil

Publications (2)

Publication Number Publication Date
EP3520514A1 EP3520514A1 (fr) 2019-08-07
EP3520514B1 true EP3520514B1 (fr) 2021-02-17

Family

ID=57281011

Family Applications (1)

Application Number Title Priority Date Filing Date
EP17781100.7A Active EP3520514B1 (fr) 2016-11-03 2017-10-09 Appareils et procédés de télécommunications sans fil

Country Status (3)

Country Link
US (3) US11102754B2 (fr)
EP (1) EP3520514B1 (fr)
WO (1) WO2018082869A1 (fr)

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11012972B2 (en) * 2017-02-15 2021-05-18 Lg Electronics Inc. Method for relaying paging and relay user equipment, and paging reception method and remote user equipment
WO2018164821A1 (fr) * 2017-03-10 2018-09-13 Intel IP Corporation Équipement utilisateur (ue), nœud b évolué (enb) et procédés de radiomessagerie selon un agencement de relais
WO2018223401A1 (fr) * 2017-06-09 2018-12-13 华为技术有限公司 Procédé d'envoi de message de radiomessagerie, procédé de réception de message de radiomessagerie, terminal et système
WO2019137848A1 (fr) * 2018-01-11 2019-07-18 Sony Corporation Dispositif et procédé de communication sans fil
EP3804427A1 (fr) 2018-06-01 2021-04-14 Telefonaktiebolaget Lm Ericsson (Publ) Dispositif de communication, hôte et procédés associés pour gérer une radiomessagerie et un échange de données dans un système de communication sans fil
US20200120010A1 (en) * 2018-10-12 2020-04-16 Tyco Electronics Uk Ltd Communication network for monitoring a chain based network
US11283566B2 (en) * 2019-01-18 2022-03-22 Huawei Technologies Co., Ltd. Systems and methods for user equipment cooperation
WO2021022432A1 (fr) * 2019-08-03 2021-02-11 Zte Corporation Procédé et dispositif de transmission de données dans un réseau sans fil
CN115336337A (zh) * 2019-12-19 2022-11-11 交互数字专利控股公司 使用中继寻呼远程ue
US11683793B2 (en) * 2020-06-11 2023-06-20 Qualcomm Incorporated Sidelink power control using shared resources
JP2023534310A (ja) * 2020-07-21 2023-08-08 アップル インコーポレイテッド リモート無線デバイスについてのページングを中継無線デバイスに提供すること
US20220303942A1 (en) * 2020-07-21 2022-09-22 Apple Inc. Paging Forwarding for a Remote Wireless Device
CN113973358A (zh) * 2020-07-24 2022-01-25 华为技术有限公司 一种通信方法及装置
CN113973359A (zh) * 2020-07-24 2022-01-25 华为技术有限公司 一种通信方法及装置
US11705959B2 (en) * 2020-10-02 2023-07-18 Qualcomm Incorporated Identification and utilization of assisting nodes
US11979853B2 (en) * 2020-10-23 2024-05-07 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving a signal in the wireless communication system
CN114531717A (zh) * 2020-11-23 2022-05-24 华硕电脑股份有限公司 获取系统信息和经由ue到网络的中继寻呼的方法和设备

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE60108609T2 (de) * 2000-11-16 2005-12-22 Ntt Docomo Inc. Verfahren zur registrierung der position eines mobilen kommunikationsendgerätes, allgemeines rufverfahren für ein mobiles kommunikationsendgerät und mobiles kommunikationssystem
KR101537604B1 (ko) * 2008-10-15 2015-07-17 엘지전자 주식회사 페이징 캐리어 할당방법
JP5084951B2 (ja) * 2009-04-28 2012-11-28 三菱電機株式会社 移動体通信システム
US20120238208A1 (en) * 2011-03-17 2012-09-20 Maik Bienas Mobile radio communication devices and servers
US20160057738A1 (en) * 2013-05-09 2016-02-25 Lg Electronics Inc. Method for monitoring paging occasions in a wireless communication system and device therefor
WO2016008657A1 (fr) * 2014-07-15 2016-01-21 Sony Corporation Dispositif de communication, appareil de communication faisant office de nœud relais, équipement d'infrastructure et procédés associés
CN105493622B (zh) * 2014-08-06 2020-04-14 华为技术有限公司 终端、网络设备、寻呼方法和区域信息更新方法
US11672044B2 (en) * 2015-11-17 2023-06-06 Telefonaktiebolaget Lm Ericsson (Publ) UE identifier in RRC resume
US20170202051A1 (en) * 2016-01-12 2017-07-13 Electronics And Telecommunications Research Institute Method and apparatus for reusing access stratum context through unique base station identifier, and method and apparatus for resuming radio resource control (rrc) connection by using the same
WO2017135676A1 (fr) * 2016-02-02 2017-08-10 Lg Electronics Inc. Procédé et appareil de radiomessagerie avec un id de reprise pour un équipement d'utilisateur interrompu dans un système de communication sans fil
US10129877B2 (en) * 2016-03-16 2018-11-13 Qualcomm Incorporated Paging for machine type communication devices
CN109479333A (zh) 2016-07-15 2019-03-15 索尼移动通讯有限公司 建立或恢复无线通信网络中的无线通信连接
JP6600102B2 (ja) * 2016-09-21 2019-10-30 京セラ株式会社 通信制御方法及びユーザ装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
US20230276406A1 (en) 2023-08-31
US20190261309A1 (en) 2019-08-22
US20210368474A1 (en) 2021-11-25
WO2018082869A1 (fr) 2018-05-11
US11102754B2 (en) 2021-08-24
US11665666B2 (en) 2023-05-30
EP3520514A1 (fr) 2019-08-07

Similar Documents

Publication Publication Date Title
US11665666B2 (en) Wireless telecommunications apparatuses and methods
US10405364B2 (en) Method and apparatus for transmitting information for D2D operation in wireless communication system
US11765687B2 (en) Telecommunications apparatus and methods for paging of a mobile device
EP3357296B1 (fr) Appareils et procédés de télécommunication
US9775105B2 (en) Optimization on network assisted proximity services discovery management
US20200245291A1 (en) Telecommunications apparatus and methods
US11963134B2 (en) Communication based on plurality of SIMs
EP3490300B1 (fr) Procédé pour commande d'accès à l'aide d'un équipement utilisateur de relais et appareil associé
US11812509B2 (en) Communication related to configuration update
WO2013111191A1 (fr) Système de communication sans fil, station de base radio, terminal radio et procédé de communication sans fil
WO2016162047A1 (fr) Simplification de fonctionnement de réseau sans fil isolé efficace
WO2023069665A1 (fr) Activation d'occasion de radiomessagerie d'un état de veille pour l'état inactif
WO2023196486A1 (fr) Gestion de transmission de petites données avec un réseau
KR20240036025A (ko) 멀티캐스트 및 브로드캐스트 서비스에 대한 페이징 관리
EP4353029A1 (fr) Gestion de radiorecherche pour un dispositif utilisateur
JP2024523569A (ja) ユーザデバイスのためのページングの管理
WO2022236123A1 (fr) Communication de données précoce sur des parties de bande passante
KR20140055058A (ko) 응급호와 일반호를 가진 단말이 서비스 불가능한 TA로 이동한 경우, 일반호를 처리하는 방법 및 Forbidden TA 리스트 관리 방법

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20190503

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
17Q First examination report despatched

Effective date: 20200124

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 84/04 20090101ALN20200730BHEP

Ipc: H04W 88/04 20090101ALN20200730BHEP

Ipc: H04W 68/00 20090101AFI20200730BHEP

Ipc: H04W 8/26 20090101ALN20200730BHEP

Ipc: H04W 76/14 20180101ALN20200730BHEP

INTG Intention to grant announced

Effective date: 20200828

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602017032798

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1363205

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210315

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: FP

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

RAP4 Party data changed (patent owner data changed or rights of a patent transferred)

Owner name: SONY EUROPE LIMITED

Owner name: SONY GROUP CORPORATION

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210517

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210217

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210617

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210517

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210217

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210217

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210518

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1363205

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210217

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210217

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210217

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210217

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210217

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210617

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210217

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210217

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210217

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210217

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602017032798

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210217

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210217

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210217

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20211118

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210217

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210217

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210217

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210217

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210617

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20211031

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210217

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211009

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211031

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211031

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211031

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211009

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210217

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230606

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20171009

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20230922

Year of fee payment: 7

Ref country code: GB

Payment date: 20230920

Year of fee payment: 7

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20230920

Year of fee payment: 7

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20230920

Year of fee payment: 7

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210217