WO2016037641A1 - Procédure optimisée de récupération d'identificateur d'équipement d'utilisateur - Google Patents

Procédure optimisée de récupération d'identificateur d'équipement d'utilisateur Download PDF

Info

Publication number
WO2016037641A1
WO2016037641A1 PCT/EP2014/069173 EP2014069173W WO2016037641A1 WO 2016037641 A1 WO2016037641 A1 WO 2016037641A1 EP 2014069173 W EP2014069173 W EP 2014069173W WO 2016037641 A1 WO2016037641 A1 WO 2016037641A1
Authority
WO
WIPO (PCT)
Prior art keywords
cell
entity
identifier
base station
management entity
Prior art date
Application number
PCT/EP2014/069173
Other languages
English (en)
Inventor
Rainer Liebhart
Devaki Chandramouli
Martin Oettl
Original Assignee
Nokia Solutions And Networks Oy
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 Nokia Solutions And Networks Oy filed Critical Nokia Solutions And Networks Oy
Priority to PCT/EP2014/069173 priority Critical patent/WO2016037641A1/fr
Publication of WO2016037641A1 publication Critical patent/WO2016037641A1/fr

Links

Classifications

    • 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
    • H04W8/12—Mobility data transfer between location registers or mobility servers
    • 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/06—Registration at serving network Location Register, VLR or user mobility server
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support

Definitions

  • the present invention relates to apparatuses, methods, systems, computer programs, computer program products and computer-readable media regarding an optimized user equipment identifier retrieval procedure.
  • EPS is the Evolved Packet System, the successor of GPRS (General Packet Radio System). It provides new radio interface and new packet core network functions for broadband wireless data access.
  • EPS core network functions are the Mobility Management Entity (MME), Packet Data Network Gateway (P-GW) and Serving Gateway (S-GW).
  • MME Mobility Management Entity
  • P-GW Packet Data Network Gateway
  • S-GW Serving Gateway
  • a common packet domain Core Network (CN ) is used for all Radio Access Networks (RAN), GERAN, UTRAN and E-UTRAN.
  • the PCC (Policy Charging Control) architecture including DPI (Deep Packet Inspection) functionality in TDF (Traffic Detection Function ) and PCEF (Policy and Charging Enforcement Function) enhanced with ADC (Application Detection and Control) rules, extends the architecture of an I P-CAN (Internet Protocol Connectivity Access Network), where the PCEF is a functional entity in the gateway node (P-GW / GGSN) providing the IP access to the PDN (Packet Data Network).
  • DPI Deep Packet Inspection
  • TDF Traffic Detection Function
  • PCEF Policy and Charging Enforcement Function
  • ADC Application Detection and Control
  • Fig. 1 is a diagram illustrating the overall PCC architecture.
  • 3GPP 3 rd Generation Partnership Project
  • 3GPP TR 23.705 3GPP TR 23.705, which also documents an agreement to follow a so-called CN based solution by which congestion information from RAN is used in the core to perform congestion mitigation.
  • Normative text is captured in TS 23.002, TS 23.203, TS 23.060 and TS 23.401.
  • OAM Operation, Administration and Maintenance
  • Fig. 2 is an overview illustrating the reference architecture for RAN user plane congestion detection and reporting.
  • the interfaces between MME/SGSN and RCAF (Nq and Nq ) are specified in TS 23.401 and TS 23.060 and enables the RCAF to retrieve the list of UEs (respectively their IMSIs), which are currently camping in congested cells as reported by RAN's OAM system.
  • the PC RF receives congestion reports (called RUCI (RAN user plane congestion information)) from the RCAF via Np as another input for policy decisions as described in TS 23.203.
  • RUCI congestion reports
  • Nq and Nq' reference points causes one of those issues. Both interfaces were specified in TS 23.401 (Nq) and TS 23.060 (Nq') and enable the RCAF to retrieve the list of UEs (respectively their I MSIs), which are currently camping in congested ceils as reported by RAN's OAM system.
  • the problem hereby is that once the RCAF requests the MME (here and in the following text we use the SAE/LTE (System Architecture Evolution / Long Term Evolution ) terminology for simplification, but the issue applies for UMTS as well) by sending the list of congested cells to return the list of UEs in those cells.
  • the MME is required to query the eNBs hosting the ceils, as UEs might change ceils within an eNB without informing the MME about that cell change.
  • MME sends a Location Update (LU) Request for each UE to the eNB. If this UE has moved from cell X to cell Y within eNB coverage area, eNB will return the new cell to MME.
  • LU Location Update
  • the problem with this approach is that when the UE moves from cell X to cell Y, both served by the same eNB and eNB does not send a Path Switch request or Handover Notify indication to MME, so the last known cell in the MME is cell X. If ceil Y is reported as congested ceil, MME will first search in its context data for all UEs of which the last known cell is cell Y and then send LU Request for each of these UEs to eNB. So, MME will miss those UEs that have moved into the cell Y and eN B has not reported that cell change to MME, which is in line with current specifications.
  • GCS AS Group Communication System Application Server
  • the problem remains to find a suitable solution that allows the GCS AS or network identifying which or at least how many users are in a certain area (e.g. a cell).
  • eNB will always report cell changes to the MME, which in case of intra-eNB handover case implementation specific, or MME sends a LU request for all UEs where the congested cell is stored as last known cell in MME context data.
  • the location update request does not help identifying U Es that have moved i nto the congested cell .
  • it requires the MME to send one LU request for each UE found in the MME context data, thus increasing the sigaling overhead towards the eNB.
  • a method comprising: receiving, at a management entity, a query including at least a cell identifier of at least one cell to obtain a list of identifiers of user equipments camping in the cell,
  • a method comprising: receiving, at a base station, a query including at least a cell identifier of at least one cell served by the base station from an entity,
  • a method comprising: receiving, at an entity, information regarding a location area to obtain a list of identifiers of user equipments in the location area, mapping, at the entity, the information to network internal location parameters, forward in g , by the entity, th e network i nternal location parameters to a management entity, and receiving, at the entity, the list of identifiers of user equipments in the location area from the management entity.
  • a method comprising: receiving, at an entity, a query including at least a cell identifier of at least one cell to obtain a list of identifiers of user equipments camping in the cell, forwarding, by the entity, the cell identifier of the at least one cell to a management entity, and receiving, at the entity, the list of identifiers of user equipments camping in the at least one cell corresponding to the cell identifier from the management entity.
  • apparatus for use in a management entity comprising:
  • At least one processor and at least one memory for storing instructions to be executed by the processor, wherein the at least one memory and the instructions are configured to, with the at least one processor, cause the apparatus at least to perform: receiving, at the management entity, a query including at least a cell identifier of at least one cell to obtain a list of identifiers of user equipments camping in the cell,
  • apparatus for use in a base station comprising:
  • At least one processor and at least one memory for storing instructions to be executed by the processor, wherein the at least one memory and the instructions are configured to, with the at least one processor, cause the apparatus at least to perform:
  • a query including at least a cell identifier of at least one cell served by the base station from an entity
  • apparatus for use in an entity comprising:
  • apparatus for use in an entity, comprising:
  • At least one processor and at least one memory for storing instructions to be executed by the processor, wherein the at least one memory and the instructions are configured to, with the at least one processor, cause the apparatus at least to perform: receiving, at the entity, a query including at least a cell identifier of at least one cell to obtain a list of identifiers of user equipments camping in the cell, forwarding, by the entity, the cell identifier of the at least one cell to a management entity, and receiving, at the entity, the list of identifiers of user equipments camping in the at least one cell corresponding to the cell identifier from the management entity.
  • apparatus for use in a management entity comprising:
  • apparatus for use in a base station comprising:
  • apparatus for use in an entity comprising:
  • means for receiving, at the entity, information regarding a location area to obtain a list of identifiers of user equipments in the location area means for mapping, at the entity, the information to network internal location parameters, means for forwarding, by the entity, the network internal location parameters to a management entity, and means for receiving, at the entity, the list of identifiers of user equipments in the location area from the management entity.
  • apparatus for use in an entity comprising:
  • a computer program product comprising code means adapted to produce steps of any of the methods as described above when loaded into the memory of a computer.
  • a computer program product as defined above, wherein the computer program product comprises a computer- readable medium on which the software code portions are stored.
  • Fig. 1 is an overview illustrating the overall PCC architecture
  • Fig. 2 is an overview illustrating the reference architecture for RAN user plane congestion detection and reporting
  • Fig. 3 is a signaling diagram illustrating an example of a message exchange according to example versions of the present invention.
  • Fig. 4 is a signaling diagram illustrating another example of a message exchange according to example versions of the present invention
  • Fig. 5 is a signaling diagram illustrating another example of a message exchange according to example versions of the present invention.
  • Fig. 6 is a flowchart illustrating an example of a method according to example versions of the present invention.
  • Fig. 7 is a flowchart illustrating an example of another method according to example versions of the present invention.
  • Fig. 8 is a flowchart illustrating an example of another method according to example versions of the present invention.
  • Fig. 9 is a flowchart illustrating an example of another method according to example versions of the present invention.
  • Fig. 10 is block diagram illustrating an example of an apparatus according to example versions of the present invention.
  • the basic system arch itectu re of a com mu n ication network where exam ples of embodiments of the invention are applicable may comprise a commonly known architecture of one or more communication systems comprising a wired or wireless access network subsystem and a core network.
  • Such an architecture may comprise one or more communication network control elements, access network elements, radio access network elements, access service network gateways or base transceiver stations, such as a base station (BS), an access point or an eNB, which control a respective coverage area or cell and with which one or more communication elements or terminal devices such as a U E or another device having a similar function, such as a modem chipset, a chip, a module etc., which can also be part of a UE or attached as a separate element to a UE, or the like, are capable to communicate via one or more channels for transmitting several types of data.
  • core network elements such as gateway network elements, policy and charging control network elements, mobility management entities, operation and maintenance elements, and the like may be comprised.
  • the general functions and interconnections of the described elements are known to those skilled in the art and described in corresponding specifications, so that a detailed description thereof is omitted herein.
  • the communication network is also able to communicate with other networks, such as a public switched telephone network or the Internet.
  • the communication network may also be able to support the usage of cloud services.
  • BSs and/or eN Bs or their functionalities may be implemented by using any node, host, server or access node etc. entity suitable for such a usage.
  • the described network elements and communication devices such as terminal devices or user devices like UEs, communication network control elements of a cell, like a BS or an eN B, access network elements like APs and the like, as well as corresponding functions as described herein may be implemented by software, e.g. by a computer program product for a computer, and/or by hardware.
  • nodes or network elements may comprise several means, modules, units, components, etc. (not shown) which are required for control, processing and/or communication/signaling functionality.
  • Such means, modules, units and components may comprise, for example, one or more processors or processor units including one or more processing portions for executing instructions and/or programs and/or for processing data, storage or memory units or means for storing instructions, programs and/or data, for serving as a work area of the processor or processing portion and the like (e.g. ROM, RAM, EEPROM, and the like), input or interface means for inputting data and instructions by software (e.g. floppy disc, CD-ROM, EEPROM, and the like), a user interface for providing monitor and manipulation possibilities to a user (e.g. a screen, a keyboard and the like), other interface or means for establishing links and/or connections under the control of the processor unit or portion (e.g.
  • radio interface means comprising e.g. an antenna unit or the like, means for forming a radio communication part etc.) and the like, wherein respective means forming an interface, such as a radio communication part, can be also located on a remote site (e.g. a radio head or a radio station etc.).
  • a remote site e.g. a radio head or a radio station etc.
  • the MME once it retrieves a request with a list of cells (in form of ECGI s (E-UTRAN Cell Global Identifiers)) to obtain the list of UE(s) camping in each of the received cells, e.g. from OAM, RCAF, MBMS GW or GGSN / PGW, uses a new identifier retrieval procedure over the S1 -MME interface between the MME and the eNB (or via other interfaces like M3, M2) to retrieve the list of identifiers of UEs that are camping in one of these cells from the corresponding eNBs.
  • ECGI s E-UTRAN Cell Global Identifiers
  • the MME will send one request per eNB for all cells that are served by the eNB (ECGI contains the eNB ID). Each eNB will reply with identifiers of UEs that are connected to the eNB via one of the provided cells.
  • the returned UE identifier can be e.g. eNB UE S1AP ID (a unique identifier of the UE on the S1-MME interface at eNB side), MME UE S1 AP ID (a unique identifier of the UE on the S1 -MME interface at MME side) or any other UE related identifier that is available in eNB and MME or may be defined in future. This procedure can be used for the U PCON use case, but also in other scenarios where the users or number of users in certain cells is required.
  • the identifier retrieval procedure request can be initiated by the MME upon a request from RCAF.
  • the resulting information can then be used to determine the users camping in a congested cell, thus PCRF can update PCC rules for these users accordingly.
  • FIG. 3 An example of the flow for the procedure is illustrated in Fig. 3.
  • the RCAF queries the MME in a step S31 based on a list of ECGI(s) of congested cells in order to find out the users contributing to and/or being affected by the congestion .
  • the M ME queries the respective eN Bs identified by the eN B I D contained in the ECGI based on the list of ECGI(s).
  • Each eNB responds to the MME with a list of MME UE S1 AP ID and eNB UE S1 AP ID for each ECGI in the list in a step S33.
  • the MME maps each received eNB S1 AP ID and/ or MME S1 AP ID to its IMSI based on its stored context data and responds to the RCAF with list of IMSI(s) for each ECGI in the list in a step S35.
  • the RCAF obtains the IMSI list for the congested cells and forwards it to the PCRF, for example in a RUCi report.
  • the PCRF can then take respective measures (e.g. modify policy rules) in order to mitigate the congestion.
  • the request can be initiated by the GCSE Application Server (GCS AS).
  • GCS AS GCSE Application Server
  • the resulting information can be used to determine the users camping in a certain (not necessarily congested) cell in order to determine whether multicast, broadcast or unicast should be performed for group communication.
  • An example for such a procedure is illustrated in Fig. 4.
  • the GCS AS queries the BM-SC based on the list of ECGI (s) or latitude/longitude of a service area (or any other well known/configured geographical location area). Then, in a step S42, the BM-SC maps this to network internal location parameters (e.g. TAI, ECGI or SAI).
  • network internal location parameters e.g. TAI, ECGI or SAI.
  • the MBMS GW forwards the query to the MME/MCE (MBMS Coordination Entity), and the MME and/or the MCE query the eNB based on the list of ECGI(s) in a step S44.
  • the eNB responds to the MME directly or via MCE with the list of MME UE S1 AP I D and/or eNB UE S1 AP ID for each ECGI in the list.
  • the MME maps the eNB/MME S1 AP ID to I MSI and responds to the MBMS GW with a list of I MSI (s) for each ECGI in the list in a step S47.
  • the MBMS GW and BM-SC forward the list to GCS AS in a step S48.
  • the I MSI(s) can first be mapped to MSISDN(s) (e.g. by the BM-SC or the MME/MCE).
  • any Application Function that can access the EPS network via Rx interface can also initiate the newly proposed identifier retrieval procedure.
  • the resulting information can be used to determine the location of the user and this can be used for location based services.
  • An example of a flow for such a procedure is illustrated in Fig. 5.
  • the AF queries the PCRF based on list of ECGI(s) or latitude/longitude (or any other well known/configured geographical location area) and the PCRF receives such a query in a step S51 .
  • the PCRF forwards the query to the MME (e.g. via PGW/SGW) based on list of ECGI(s).
  • the MME queries the eNB based on list of ECGI(s) in a step S52 and the eNB responds to the MME with list of MME UE S1 AP ID and/or eN B U E S 1 AP I D for each ECGI in the list in a step S54.
  • the MME maps the eNB/MME S1 AP ID to IMSI in a step S55 and responds to the PCRF with a list of IMSI(s) for each ECGI in the list in a step S56.
  • the PCRF forwards the list to the AF.
  • operators can use the identifier retrieval procedure for other purposes as well, e.g. as input to network dimensioning.
  • retrieving the number of users in certain cells from the OAM can be used to calculate average number of users in these cells over a certain time period.
  • the identifier request message could be as follows: Identifier Request (
  • an input to the identifier request is a list of cell IDs (ECGI(s)).
  • Each ECGI consists of eNB ID and internal eNB cell ID.
  • the identifier response message could be as follows:
  • the identifier response returns per ECGI a list of found UE identifiers, e.g. MME UE S1AP ID and/or eNB UE S1AP ID and/or any other possible identifiers that might be defined.
  • the input to the request is a list of UTRAN Source Cell ID(s) (format defined in TS 25.413), each consisting of PLMN ID and Source Cell ID.
  • the response consists of a list of UE ID(s) known to RAN and SGSN, e.g. TMSI or P-TMSI.
  • Fig. 6 is a flowchart illustrating an example of a method according to example versions of the present invention.
  • the method may be implemented in a management entity, like e.g. a mobility management entity MME or the like, and comprises receiving, at a management entity, a query including at least a cell identifier of at least one cell in a step S61 .
  • the management entity derives an identifier of a base station serving the at least one cell corresponding to the cell identifier and forwards the cell identifier to the identified base station in a step S63.
  • the management entity receives from the identified base station a list of local identifiers of user equipments in the at least one cell served by the base station in a step S64.
  • the management entity derives a global identifier for each of the user equipments from the respective local identifier of each user equipment, and then forwards the global identifier of each user equipment in a step S66.
  • the at least one cell is a cell for which congestion has been detected, reported or predicted, or any other cell, like e.g. a cell belonging to a specific service area.
  • the query is received from an entity concerned with handling user plane congestion and the global identifier of each user equipment is forwarded to this entity.
  • the query is received from a group communication application server and the global identifier of each user equipment is forwarded to this entity.
  • the query is received from an application function and the global identifier of each user equipment is forwarded to this application function.
  • the query further includes geographical location area information regarding the at least one cell.
  • Fig. 7 is a flowchart illustrating another example of a method according to example versions of the present invention.
  • the method may be implemented in a base station, like e.g. an eNB or the like, and comprises receiving, at a base station, a query including at least a cell identifier of at least one cell served by the base station from an entity in a step S71 , retrieving, at the base station, local identifiers of user equipments in the at least one cell served by the base station in a step S72, and forwarding, by the base station, the retrieved local identifiers to the entity in a step S73.
  • a base station like e.g. an eNB or the like, and comprises receiving, at a base station, a query including at least a cell identifier of at least one cell served by the base station from an entity in a step S71 , retrieving, at the base station, local identifiers of user equipments in the at least one cell served by the base station in a step S72, and forwarding, by the base station, the retrieved local identifiers to the entity in a step S73
  • the at least one cell is a cell for which congestion has been detected , reported or predicted, or a cell belonging to a specific area
  • the entity is a coordination entity, like a MCE or a management entity, like a MME.
  • Fig. 8 is a flowchart illustrating another example of a method according to example versions of the present invention.
  • the method may be implemented in a congestion awareness function, a policy and charging rules function, a multicast broadcast service center, a multicast broadcast gateway or an application server, or the like, and comprises receiving, at an entity, information regarding a location area to obtain a list of identifiers of user equipments in the location area in a step S81 , mapping, at the entity, the information to network internal location parameters in a step S82, forwarding, by the entity, the network internal location parameters to a management entity in a step S83, and receiving, at the entity, the list of identifiers of user equipments in the location area from the management entity in a step S84.
  • the entity is a congestion awareness function , e.g. a RCAF, a policy and charging rules function , i .e. PC RF, a multicast broadcast service center, e.g. M BMS , a multicast broadcast gateway, e.g. MBMS GWor an application server, e.g. GCS AS.
  • a congestion awareness function e.g. a RCAF
  • a policy and charging rules function i .e. PC RF
  • M BMS multicast broadcast service center
  • M BMS multicast broadcast gateway
  • an application server e.g. GCS AS.
  • Fig. 9 is a flowchart illustrating still another example of a method according to example versions of the present invention.
  • the method may be implemented in a congestion awareness function , a policy and charging rules function , a multicast broadcast service center, a multicast broadcast gateway or an application server, or the like, and comprises receiving, at an entity, a query including at least a cell identifier of at least one cell to obtain a list of identifiers of user equipments camping in the cell in a step S91 , forwarding, by the entity, the cell identifier of the at least one cell to a management entity in a step S92, and receiving, at the entity, the list of identifiers of user equipments camping in the at least one cell corresponding to the cell identifier from the management entity in a step S93.
  • the at least one cell is a cell for which congestion has been detected , reported or pred icted , or a cell belonging to a specific area.
  • the entity is a congestion awareness function , e.g. a RCAF, a policy and charging rules function , i .e. PCRF, a multicast broadcast service center, e.g. M BMS , a multicast broadcast gateway, e.g. MBMS GWor an application server, e.g. GCS AS.
  • a congestion awareness function e.g. a RCAF
  • a policy and charging rules function i .e. PCRF
  • M BMS multicast broadcast service center
  • M BMS multicast broadcast gateway
  • e.g. MBMS GWor an application server e.g. GCS AS.
  • Fig. 1 0 is a block diagram showing an example of an apparatus according to example versions of the present invention.
  • a block circuit diagram illustrating a configuration of an apparatus 100 is shown, which is configured to implement the above described aspects of the invention.
  • the apparatus 100 shown in Fig. 10 may comprise several further elements or functions besides those described herein below, which are omitted herein for the sake of simplicity as they are not essential for understanding the invention.
  • the apparatus may be also another device having a similar function, such as a chipset, a chip, a module etc., which can also be part of an apparatus or attached as a separate element to the apparatus, or the like.
  • the apparatus 100 may comprise a processing function or processor 101 , such as a CPU or the like, which executes instructions given by programs or the like.
  • the processor 101 may comprise one or more processing portions dedicated to specific processing as described below, or the processing may be run in a single processor. Portions for executing such specific processing may be also provided as discrete elements or within one or further processors or processing portions, such as in one physical processor like a CPU or in several physical entities, for example.
  • Reference sign 102 denotes transceiver or input/output (I/O) units (interfaces) connected to the processor 101 .
  • the I/O units 102 may be used for communicating with one or more other network elements, entities, terminals or the like.
  • the I/O units 102 may be a combined unit comprising communication equipment towards several network elements, or may comprise a distributed structure with a plurality of different interfaces for different network elements.
  • Reference sign 1 03 denotes a memory usable, for example, for storing data and programs to be executed by the processor 101 and/or as a working storage of the processor 101.
  • the processor 101 is configured to execute processing related to the above described aspects.
  • the apparatus 100 may be implemented in or may be part of a management entity, like a mobility management entity MME or the like, and may be configured to perform a method as described in connection with Figs 6.
  • the processor 1 01 is configured to perform receiving, at a management entity, a query including at least a cell identifier of at least one cell, deriving, at the management entity, an identifier of a base station serving the at least one cell corresponding to the cell identifier, forwarding, by the management entity, the cell identifier to the identified base station, receiving, at the management entity from the identified base station, a list of local identifiers of user equipments in the at least one cell served by the base station, deriving, at the management entity, a global identifier for each of the user equipments from the respective local identifier of each user equipment, and forwarding, by the management entity, the global identifier of each user equipment.
  • the apparatus 100 may be implemented in or may be part of base station or the like, and may be configured to perform a method as described in connection with Fig. 7.
  • the processor 101 is configured to perform receiving, at a base station, a query including at least a cell identifier of at least one cell served by the base station from an entity, retrieving, at the base station, local identifiers of user equipments in the at least one cell served by the base station, and forwarding, by the base station, the retrieved local identifiers to the entity.
  • the apparatus 100 may be implemented in or may be part of a congestion awareness function, a policy and charging rules function, a multicast broadcast service center, a multicast broadcast gateway or an application server, or the like, and may be configured to perform a method as described in connection with Fig. 8.
  • the processor 101 is configured to perform receiving, at an entity, information regarding a location area to obtain a list of identifiers of user equipments in the location area, mapping, at the entity, the information to network internal location parameters, forwarding, by the entity, the network internal location parameters to a management entity, and receiving, at the entity, the list of identifiers of user equipments in the location area from the management entity.
  • the apparatus 100 may be implemented in or may be part of a congestion awareness function, a policy and charging rules function, a multicast broadcast service center, a multicast broadcast gateway or an application server, or the like, and may be configured to perform a method as described in connection with Fig. 9.
  • the processor 101 is configured to perform receiving, at an entity, a query including at least a cell identifier of at least one cell to obtain a list of identifiers of user equipments camping in the cell, forwarding, by the entity, the cell identifier of the at least one cell to a management entity, and receiving, at the entity, the list of identifiers of user equipments camping in the at least one cell corresponding to the cell identifier from the management entity.
  • the apparatus for use in a management entity, a base station or controller and the apparatus for use in a congestion awareness function, a policy and charging rules function, a multicast broadcast service center, a multicast broadcast gateway or an application server, or the like generally have the same structural components, wherein these components are configured to execute the respective functions of the base station or controller and the access point, respectively, as set out above.
  • UTRAN input to the identifier retrieval procedure request is a list of UTRAN Source Cell I D(s) (format defined in TS 25.413), each consisting of PLMN ID and Source Cell ID.
  • the response consists of a list of UE ID(s) known to RAN and SGSN, e.g. TMSI or P-T SI.
  • processor or corresponding circuitry potentially in cooperation with computer program code stored in the memory of the respective apparatus, is configured to cause the apparatus to perform at least the thus mentioned function.
  • function is to be construed to be equivalently implementable by specifically configured circuitry or means for performing the respective function (i.e. the expression "unit configured to” is construed to be equivalent to an expression such as "means for").
  • any method step is suitable to be implemented as software or by hardware without changing the idea of the aspects/embodiments and its modification in terms of the functionality implemented;
  • CMOS Complementary MOS
  • BiMOS Bipolar MOS
  • BiCMOS Bipolar CMOS
  • ECL emitter Coupled Logic
  • TTL Transistor-Transistor Logic
  • ASIC Application Specific IC
  • FPGA Field- programmable Gate Arrays
  • CPLD Complex Programmable Logic Device
  • DSP Digital Signal Processor
  • - devices, units or means can be implemented as individual devices, units or means, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device, unit or means is preserved;
  • an apparatus may be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of an apparatus or module, instead of being hardware implemented, be implemented as software in a (software) module such as a computer program or a com puter prog ra m prod u ct com prisi n g executable software code porti ons for execution/being run on a processor;
  • a device may be regarded as an apparatus or as an assembly of more than one apparatus, whether functionally in cooperation with each other or functionally independently of each other but in a same device housing, for example.
  • respective functional blocks or elements according to above-described aspects can be implemented by any known means, either in hardware and/or software, respectively, if it is only adapted to perform the described functions of the respective parts.
  • the mentioned method steps can be realized in individual functional blocks or by individual devices, or one or more of the method steps can be realized in a single functional block or by a single device.
  • any method step is suitable to be implemented as software or by hardware without changi ng the idea of the present invention .
  • Devices and means can be implemented as individual devices, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device is preserved. Such and similar principles are to be considered as known to a skilled person.
  • Software in the sense of the present description comprises software code as such comprising code means or portions or a computer program or a computer program product for performing the respective functions, as well as software (or a computer program or a computer program product) embodied on a tangible medium such as a computer-readable (storage) medium having stored thereon a respective data structure or code means/portions or embodied in a signal or in a chip, potentially during processing thereof.
  • a tangible medium such as a computer-readable (storage) medium having stored thereon a respective data structure or code means/portions or embodied in a signal or in a chip, potentially during processing thereof.
  • GGSN Gateway GPRS Support Node GPRS Global Packet Radio System
  • MME Mobility Management Entity MSISDN Mobile Subscriber I ntegrated Services Digital Network Number OA&M Operation , Admin istration and Mai ntenance

Landscapes

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

Abstract

La présente invention concerne des appareils, des procédés, des programmes d'ordinateur, des produits de programme d'ordinateur et des supports lisibles par ordinateur concernant une procédure optimisée de récupération d'identificateur d'équipement d'utilisateur. La présente invention comprend de recevoir, au niveau d'une entité de gestion, une requête comprenant au moins un identifiant de cellule d'au moins une cellule pour obtenir une liste d'identifiants d'équipements d'utilisateur domiciliés sur la cellule, de dériver, au niveau de l'entité de gestion, un identifiant d'une station de base desservant ladite au moins une cellule correspondant à l'identifiant de cellule, d'envoyer, par l'entité de gestion, l'identifiant de cellule à la station de base identifiée, de recevoir, au niveau de l'entité de gestion depuis la station de base identifiée, une liste d'identifiants locaux d'équipements d'utilisateur dans ladite au moins une cellule desservie par la station de base, de dériver, au niveau de l'entité de gestion, un identifiant global pour chacun des équipements d'utilisateur à partir de l'identifiant local respectif de chaque équipement d'utilisateur, et d'envoyer, par l'entité de gestion, l'identifiant global de chaque équipement d'utilisateur.
PCT/EP2014/069173 2014-09-09 2014-09-09 Procédure optimisée de récupération d'identificateur d'équipement d'utilisateur WO2016037641A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2014/069173 WO2016037641A1 (fr) 2014-09-09 2014-09-09 Procédure optimisée de récupération d'identificateur d'équipement d'utilisateur

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2014/069173 WO2016037641A1 (fr) 2014-09-09 2014-09-09 Procédure optimisée de récupération d'identificateur d'équipement d'utilisateur

Publications (1)

Publication Number Publication Date
WO2016037641A1 true WO2016037641A1 (fr) 2016-03-17

Family

ID=51492970

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2014/069173 WO2016037641A1 (fr) 2014-09-09 2014-09-09 Procédure optimisée de récupération d'identificateur d'équipement d'utilisateur

Country Status (1)

Country Link
WO (1) WO2016037641A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2472946A1 (fr) * 2010-12-28 2012-07-04 Tektronix, Inc. Contrôle adaptatif de transcodage vidéo dans les réseaux mobiles
WO2013016301A1 (fr) * 2011-07-22 2013-01-31 Powerwave Technologies, Inc. Coordination du brouillage intercellulaire dans les réseaux sans fil

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2472946A1 (fr) * 2010-12-28 2012-07-04 Tektronix, Inc. Contrôle adaptatif de transcodage vidéo dans les réseaux mobiles
WO2013016301A1 (fr) * 2011-07-22 2013-01-31 Powerwave Technologies, Inc. Coordination du brouillage intercellulaire dans les réseaux sans fil

Similar Documents

Publication Publication Date Title
US9351275B2 (en) Node and method for priority of application based handling of a paging request
US10575139B2 (en) Method for providing broadcast service in wireless communication system, and apparatus therefor
US9667481B2 (en) Correlation identifier for user plane congestion and other use cases
WO2020147681A1 (fr) Procédé et appareil de gestion d'étiquette pour dispositif terminal
US20190141486A1 (en) Service processing method, device, and system
US11463531B2 (en) Using cellular identifiers in intelligent transport systems communication infrastructure
EP2878162B1 (fr) Noeud et procédé d'établissement de priorité d'application basée sur le traitement d'une demande de radiomessagerie
WO2015005626A1 (fr) Procédé de commande de relais sur la base d'un service de proximité et dispositif associé
US20170238149A1 (en) Network sharing for multimedia broadcast multicast service
US9591689B2 (en) System and method for detachment in wireless communication system
US10149186B2 (en) Node and method for monitoring an ability of a wireless device to receive downlink data
US20150237495A1 (en) Method and system for differentiating between subscribers
US20160073236A1 (en) Method and apparatus for searching for proximity service so as to provide proximity service
KR102367331B1 (ko) 코어망을 선택하는 방법, 이를 수행하는 이동성 관리 장치 및 경로 관리 장치
WO2016037641A1 (fr) Procédure optimisée de récupération d'identificateur d'équipement d'utilisateur
WO2021260420A1 (fr) Procédure de relocalisation de fonction d'application
WO2022078575A1 (fr) Mécanisme pour exposition directe d'événement
EP2692196B1 (fr) Noeud, procédé et support de stockage lisible par un ordinateur pour un détachement dans un système de communication sans fil
WO2017054544A1 (fr) Procédé et appareil de mise en œuvre de service de diffusion/multidiffusion multimédia amélioré (embms)

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: 14761374

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: 14761374

Country of ref document: EP

Kind code of ref document: A1