WO2014124668A1 - Gestion de support pour des groupes - Google Patents
Gestion de support pour des groupes Download PDFInfo
- Publication number
- WO2014124668A1 WO2014124668A1 PCT/EP2013/052871 EP2013052871W WO2014124668A1 WO 2014124668 A1 WO2014124668 A1 WO 2014124668A1 EP 2013052871 W EP2013052871 W EP 2013052871W WO 2014124668 A1 WO2014124668 A1 WO 2014124668A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- group
- control device
- packet data
- address
- connection
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
- H04W8/186—Processing of subscriber group data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
Definitions
- the present invention relates to an apparatus, a method and a computer program product for carrying out bearer management for groups.
- AAA Authentication, authorization and accounting APN Access point name
- Embodiments of the present invention relate to 3GPP accesses (e.g. LTE, LTE-A, WCDMA and GSM accesses) and to non-3GPP accesses (e.g. WLAN, CDMA and WiMAX accesses) and in more detail to handling of groups.
- Group specific features are currently under standardization in 3GPP R12.
- 3GPP is currently working on standardisation of group policing / usage monitoring and other group features may be standardized later (e.g. group charging, group messaging, etc.).
- Users belong to a group or multiple groups and functionalities such as policing, charging and/or messaging are performed in the network per group.
- Grouping is relevant e.g. for M2M devices and for family members.
- group members are served by the same PGW/GGSN. Each group member is assumed to perform attach (and PDP context activation in 3G) but should be served by the same PGW/GGSN. PDN connections / PDP contexts of the group members are assumed to be managed in the same PGW/GGSN. At PDN connection / PDP context creation, a PGW/GGSN is selected for the PDN connection / PDP context.
- PGW/GGSN selection is done separately for each member of a group and thus group members may be served by different PGW/GGSNs.
- Embodiments of the present invention address this situation and aim to overcome the above-described problem and to reduce the amount of signaling in connection with PDN connection / PDP context creation.
- an apparatus which comprises a connection unit configured to provide a connection to a network, and a processor configured to receive, via the connection unit, a request to create a packet data connection from a user equipment of a group, and to select a group control device for the group based on information related to the group.
- an apparatus which comprises a memory configured to store subscription-related information, a connection unit configured to provide a connection to a network, and a processor configured to handle subscriber-related information for a group by referring to an address of a group control device stored for the group in the memory.
- an apparatus which comprises a connection unit configured to provide a connection to a network, and a processor configured to handle control of a group of user equipments, and to forward information regarding the group together with the address of the apparatus to an authentication, authorization and accounting entity.
- an apparatus which comprises a memory, a connection unit configured to provide a connection to a network, and a processor configured to control authentication, authorization and accounting in a network, and to handle authentication, authorization and accounting for a packet data connection related to a group by referring to an address of a group control device stored for the group in the memory.
- a method which comprises receiving a request to create a packet data connection from a user equipment of a group, and selecting a group control device for the group based on information related to the group.
- a method which comprises storing subscription-related information in a memory, and handling subscriber-related information for a group by referring to an address of a group control device stored for the group in the memory.
- a method which comprises handling control of a group of user equipments, and forwarding information regarding the group together with the address of an apparatus carrying out the method to an authentication, authorization and accounting entity.
- a method which comprises controlling authentication, authorization and accounting in a network, and handling authentication, authorization and accounting for a packet data connection related to a group by referring to an address of a group control device stored for the group in the memory.
- a computer program product which comprises code means for performing a method according to any one of the fifth to eighth aspects and/or their modifications when run on a processing means or module.
- the computer program product may be embodied on a computer-readable medium.
- bearer management for a group is performed on a group basis. That is, for example PGW/GGSN selection can be performed per group.
- PGW/GGSN selection can be performed per group.
- Fig. 1 shows simplified structures of network elements involved in a bearer management for groups of according to an embodiment of the present invention
- Fig. 2 shows a signal flow illustrating example for PDN connection / PDP context creation for a first member of a group according to an embodiment of the present invention
- Fig. 3 shows a signal flow illustrating example for PDN connection / PDP context creation for a next member of a group according to an embodiment of the present invention.
- Figs. 4 and 5 show signal flows illustrating examples for group control according to an embodiment of the present invention
- Fig. 6 shows a PCRF as a group control device according to a further embodiment of the present invention.
- Fig. 7 shows a signal flow illustrating example for PDN connection / PDP context creation for a first member of a group according to the further embodiment of the present invention.
- PGW/GGSN selection happens separately when a PDN connection / primary PDP context for the UE is created.
- operators deploy multiple PGWs and/or GGSNs and then UEs are served by those.
- Group members are not served by the same PGW/GGSN.
- Some group features become too complicated or even impossible if group members are not in the same PGW/GGSN.
- group bandwidth management becomes far too complicated if there is one bandwidth limit (e.g. Group APN-AMBR) which is enforced in many PGW/GGSNs.
- embodiments of the present invention are directed to overcome the problems mentioned above.
- Fig. 1 shows several elements involved in the procedure according to embodiments of the present invention.
- Fig. 1 shows a MME/SGSN 1 , a PGW/GGSN 2, a AAA 3 and a HSS 4.
- the MME/SGSN 1 is an example for an apparatus, e.g., a network access apparatus, applying an embodiment of the present invention.
- Other examples may include MME and SGSN separately, an Access GW (e.g. Trusted WiFi Access GW or HSGW) or ePDG.
- the apparatus may also be only a part of the corresponding network element
- the MME/SGSN 1 comprises a processor 1 1 and a connection unit 12.
- the connection unit 12 is configured to provide a connection to a network, e.g., a (mobile) communication network.
- the processor 1 1 is configured to receive, via the connection unit, a request to create a packet data connection (e.g. PDN connection / PDP context) from a user equipment of a group, and to select a group control device (such as a packet data network gateway device (e.g., PGW 2) for the group, or a PCRF) based on information related to the group.
- a packet data connection e.g. PDN connection / PDP context
- PGW 2 packet data network gateway device
- the PGW/GGSN 2 is an example for an apparatus, e.g., a group control device, applying an embodiment of the present invention.
- Other examples may include a GGSN or PGW separately, for example.
- the apparatus may also be only a part of the PGW/GGSN.
- the PGW/GGSN 2 comprises a connection unit 22 configured to provide a connection to a network and a processor 21 .
- the processor 21 is configured to configured to handle control of a group of user equipments, and to forward information regarding the group together with the address of the apparatus (of the PGW/GGSN in this example) to an authentication, authorization and accounting entity (e.g., AAA 3).
- AAA 3 authentication, authorization and accounting entity
- the apparatus described above is a packet data network gateway device (PGW/GGSN).
- the processor is further configured to receive, via the connection unit, a request to create a packet data connection (e.g. PDN connection / PDP context) for a user equipment related to the group, and to create the packet data connection (e.g., PDN connection / PDP context).
- a packet data connection e.g. PDN connection / PDP context
- the processor will then forward information regarding the group together with the address of the packet data network gateway device to the authentication, authorization and accounting entity (e.g., AAA 3).
- AAA 3 authentication, authorization and accounting entity
- the MME/SGSN 1 and the PGW/GGSN 2 respectively may further comprise memories 13 and 23 for storing data and programs, by means of which the respective processors 1 1 and 21 may carry out their corresponding functions.
- the AAA 3 is an example for an apparatus, e.g., an authentication, authorization and accounting entity, applying an embodiment of the present invention. Moreover, the apparatus may also be only a part of the AAA.
- the AAA 3 comprises a memory 23, a connection unit 22 configured to provide a connection to a network, and a processor 21.
- the processor 21 is configured to control authentication, authorization and accounting in a network, and to handle authentication, authorization and accounting for a packet data connection related to a group by referring to an address of a group control device stored for the group in the memory 32.
- the HSS 4 is an example for an apparatus, e.g., a subscription management device, or a home subscriber server, applying an embodiment of the present invention.
- Other examples may include HLR (home location register).
- the apparatus may also be only a part of the HSS.
- the HSS 4 comprises a memory 43 configured to store subscription-related information, a connection unit 42 configured to provide a connection to a network, and a processor 41.
- the processor 31 is configured to handle subscriber-related information for a group by referring to an address of a group control device stored for the group in the memory 43.
- the AAA 3 and the HSS 4 respectively may further comprise additional memories for storing data and programs (or store these in the memories 33 and 43), by means of which the respective processors 31 and 41 may carry out their corresponding functions.
- PGW/GGSN selection a new option for PGW/GGSN selection is described, namely PGW/GGSN selection per group.
- group specific PGW/GGSN selection for LTE/3G/2G access but also for non-3GPP accesses (e.g. WiFi, CDMA, WiMAX) is possible.
- bearer management for groups can be optimized.
- the embodiment relates in particular to a network architecture as indicated in Fig. 1 described above. It is noted that between the HSS 4 and the AAA 3, an interface SWx is defined, and between the PGW 2 and the AAA 3, an interface S6b is defined. Between the MME/SGSN and the HSS, an interface S6a/S6d is defined. In more detail, the interface between MME and HSS is defined as S6a, and the interface between SGSN and HSS is defined as S6d.
- the S6b interface standardized in 3GPP is standardized for mobility between 3GPP and non-3GPP accesses.
- the PGW address is sent from the PGW to the AAA.
- the PGW address is sent to the HSS on the SWx interface. In this way, the PGW address is stored in the HSS and is available from the HSS for PGW selection when the user moves from one access to another access.
- the present embodiment it is proposed to re-use the S6b/SWx interfaces for group based bearer management, e.g. to select the PGW/GGSN for a group or release PDN connections / PDP contexts of a group.
- PGW/GGSN When a PDN connection / PDP context for the first group member (which is assumed to be identified with group Id) is created, it is possible to select a PGW/GGSN supporting the requested APN dynamically e.g. based on APN and/or group Id. Dynamic PGW/GGSN is commonly seen important by operators because it allows load sharing between multiple PGW/GGSNs supporting the requested APN. In 3GPP access, PGW/GGSN selection happens in the MME or SGSN. In non-3GPP access, PGW/GGSN selection happens e.g. in the Access GW (e.g. Trusted WiFi Access GW or HSGW) or ePDG.
- Access GW e.g. Trusted WiFi Access GW or HSGW
- the PGW/GGSN When signalling for PDN connection / PDP context creation is received by the PGW/GGSN, the PGW/GGSN signals with the AAA in order to store the PGW/GGSN Address per group.
- the group Id is added to S6b signalling.
- the AAA forwards the PGW/GGSN Address and group Id in SWx signalling to the HSS.
- Fig. 2 shows an example for 3GPP access, that is, a PDN connection is requested by the UE by sending a PDP context creation.
- a UE1 (the UE of the first group member) performs an attach procedure with a MME/SGSN. During the attach procedure, the MME/SGSN also contacts the HSS in order to obtain subscriber information, as indicated in A1 1 and A12.
- the MME/SGSN includes the group Id into the inquiry in A1 1. Since in the present case it is assumed that the UE1 is of the first group member, no association between group Id and a PGW/GGSN is stored yet, so that no PGW address will be returned in the response in A12. It is noted that in the following, the address of the PGW/GGSN is referred to as PGW address.
- the UE sends a PDP context creation request to the MME/SGSN.
- This request contains the group Id.
- the MME/SGSN selects an appropriate PGW/GGSN.
- the MME/SGSN forwards the PDP context creation request including the group Id to the selected PGW/GGSN.
- the PGW/GGSN creates the PDP context in A5 and forwards the group Id (via the S6b interface) to the AAA entity in A6. It is noted that at this point the PGW/GGSN knows that this is the first PDN connection / PDP context for a group as no other PDN connection / PDP context exists in the PGW/GGSN with the same Group Id.
- the AAA entity stores the PGW address per group (i.e., together with the group Id), and in A8, it forwards the PGW address and the group Id to the HSS.
- the HSS stores the PGW address together with the group Id in A9.
- the PGW address per group Id is available in the HSS and can be sent to the node performing PGW/GGSN selection (e.g. MME, SGSN, Access GW, ePDG).
- PGW/GGSN selection e.g. MME, SGSN, Access GW, ePDG.
- the correct PGW/GGSN gets selected for the next group member.
- there is no need to signal on S6b/SWx because the PGW address was sent to the HSS already earlier (when the PDN connection / PDP context of the first group member was created).
- a UE2 (the UE of the next group member) performs an attach procedure with a MME/SGSN (which is not necessarily the same as the MME/SGSN shown in Fig. 2), including the group Id.
- the MME/SGSN contacts the HSS in order to obtain subscriber information, as indicated in B1 1 and B12.
- the MME/SGSN includes the group Id into the inquiry in B1 1 . Since in the present case it is assumed that the UE1 is of the next group member, an association between group Id and the PGW/GGSN is stored in the HSS. Thus, the PGW address of the PGW/GGSN will be returned in the response in B12.
- the UE sends a PDP context creation request to the MME/SGSN.
- This request contains the group Id.
- the MME/SGSN selects an appropriate PGW/GGSN.
- the MME/SGSN forwards the PDP context creation request including the group Id to the selected PGW/GGSN, and the PGW/GGSN creates the PDP context in B4. Since the PGW address and the Group Id are already stored together in the HSS, there is no need to forward the information to the AAA and the HSS, so that A6 to A9 of Fig. 2 can be omitted.
- Figs. 2 and 3 show a simplified procedure, and only the main signaling is illustrated.
- the actual signaling path between MME/SGSN and PGW is carried out via a serving gateway (SGW). That is, the messages in A4 and B4 are always conveyed via the SGW.
- SGW serving gateway
- the SGW is omitted for simplifying the illustration.
- the above procedure was described for GSM/WCDMA access.
- the procedure in LTE is similar, however, then a PDN connection is created. This is already done during the attach procedure (i.e., during A1 and B1 ). Thus, there is not need for the UE to send a separate PDN connection request.
- the procedure shown in Figs. 2 and 3 for LTE access differs in that step A2/B2 would be omitted, and that in A4 and A5 or in B4 and B5 a PDN connection instead of a PDP context is request and created, respectively.
- PDN connections / PDP contexts of group members get released.
- the PGW/GGSN signals with the AAA to remove the PGW/GGSN Address.
- the AAA forwards this signalling to the HSS.
- Group Id is added to S6b/SWx signalling. This allows selecting the PGW/GGSN dynamicly when at some point a PDN connection / PDP context is again created for the first group member.
- the HSS/AAA may trigger release of PDN connections / PDP contexts per group e.g. in case of subscription changes (e.g. if the group subscription is removed).
- group Id needs to be added in S6b/SWx signalling.
- the relevant PDN connections / PDP contexts have to be released one by one and this means more signalling on S6b/SWx.
- Fig. 4 shows an example regarding a subscription change.
- the HSS sends a notification on subscription information change including the group Id to the AAA.
- the AAA forwards in C2 a re-authorization request including the group Id and updated parameters etc. to the PGW/GGSN.
- the PGW/GGSN sends a response to the AAA in order to confirm receipt, and in C4 the PGW/GGSN performs the relevant actions per group / PDP context(s) / PDN connection(s) / bearer(s).
- Fig. 5 shows an example in which the subscription is removed, i.e., the group is to be canceled.
- the HSS sends a notification on subscription information removal including the group Id to the AAA.
- the AAA forwards an abort request including the group Id to the PGW/GGSN, to which the PGW/GGSN responds in C3 in order to confirm the request.
- the PGW/GGSN performs the relevant actions per group / PDP context(s) / PDN connection(s) / bearer(s), which include in this case triggering removal of bearer(s) etc.
- group related actions can easily be coordinated since a single network device (such as the PGW/GGSN) is designated as the group control device for the particular group.
- a single network device such as the PGW/GGSN
- the group control device was described as the PGW/GGSN.
- the invention is not limited to this, and, for example, the group control device may also be a PCRF. This is described in the following by referring to Fig. 6.
- the PGW/GGSN selection may happen as currently (resulting in serving group members by different PGW/GGSNs), but there is a common element in the network serving the group members, namely the PCRF per group.
- the PCRF 5 comprises a connection unit 52 configured to provide a connection to a network and a processor 51.
- the processor 51 is configured to configured to handle control of a group of user equipments, and to forward information regarding the group together with the address of the apparatus (of the PCRF in this example) to an authentication, authorization and accounting entity (e.g., AAA 3 shown in Fig. 1 ).
- AAA 3 shown in Fig. 1
- the PCRF 5 may further comprise a memory 53 for storing data and programs, by means of which the processor 51 may carry out its corresponding functions.
- the PCRF 5 carries out the group control similar as the PGW/GGSN 2 shown in Fig. 1. That is, instead of the PGW/GGSN, the PCRF 5 is associated to the group, so that the address of the PCRF 5 is stored together with the group Id in the HSS and AAA.
- a plurality of PGW/GGSN may serve the group members, as indicated in Fig. 6 by PGW1 and PGW2.
- the PCRF when performing controls such as described above in connection with Figs. 4 and 5, the PCRF will receive corresponding subscription change/removal notifications from the HSS and will forward them to the corresponding PGW/GGSNs.
- the PGW/GGSN commonly selects the PCRF.
- the PCRF may be selected dynamically for the first group member.
- Group Id and PCRF Address should be stored e.g. to the HSS so that it is available from the HSS when PCRF selection happens for the next group member.
- the PGW/GGSN could send Group Id and PCRF Address to the AAA which forwards these parameters to the HSS.
- Fig. 7 shows the procedure for the first group member.
- the procedure is similar to that as shown in Fig. 2, so that in the following only the main differences are described.
- the attach procedure in E1 is similar to A1 , wherein, however, no group related inquiry is sent to the HSS. Nevertheless, an inquiry may sent to the HSS in order to obtain subscription information related to the particular user.
- the MME/SGSN selects a PGW in E3, but not commonly for the group but only for the particular UE1 , e.g., based on subscription information received from the HSS.
- the PDP context creation request including the group Id is then forwarded to the PGW/GGSN, which creates the PDP context in E5, but also selects the PCRF for the group. It is noted that at this point the PGW/GGSN knows that this is the first PDN connection / PDP context for a group as no other PDN connection / PDP context exists in the PGW/GGSN with the same Group Id. The address of this selected PCRF together with the group Id is forwarded to the AAA
- the PGW/GGSN For obtaining the address of the PCRF which is selected/associated to the group, the PGW/GGSN sends a signaling message (with Group Id) to the AAA which forwards a signaling message (with Group Id) to the HSS to retrieve PCRF Address of the group.
- the HSS replies to the AAA by sending PCRF Address and the AAA forwards PCRF Address to the PGW/GGSN.
- the above signaling is needed if the PCRF address is not stored by the PGW/GGSN, e.g., when all group members are not served by the same PGW/GGSN. If all group members are served by the same PGW/GGSN, this signaling is not needed because PCRF address can be stored to the PGW/GGSN.
- the PCRF address is sent from the HSS to the AAA which forwards the PCRF address to the PGW/GGSN serving the next group member.
- the PGW/GGSN can inform the AAA which informs the HSS. That is, when all PDP contexts / PDN connections of the group have been released, the HSS can remove PCRF Address of the relevant group.
- S6b/SWx there are also other functionalities, e.g. sending a QoS Profile and/or APN- AMBR for the PDN connection / PDP context or trigger tracing.
- S6b/SWx functionalities are not commonly used because there are other ways to achieve the same functionality. If an operator decides to use S6b/SWx for these functionalities, It is possible to enhance these functionalities to provide the QoS Profile and/or APN-AMBR per group or trigger tracing per group by sending relevant parameters per group.
- the MME or SGSN can send the PGW address to the HSS (S6a, S6d).
- the Access GW or ePDG can not send the PGW address to the HSS via the AAA but enhancements to the STa and SWm interfaces would be needed (group Id and PGW address on STa/SWm). Sending these parameters from the PGW as described above makes the overall solution simpler as there is only one node in the architecture for the functionality (i.e. no need to update e.g. the SGSN, Access GW or ePDG in the operator network).
- the PGW is the node releasing bearers.
- the solution described above is aligned with this and in addition, optimizes signalling on S6b/SWx. It would be possible to enhance also the MME - HSS and SGSN - HSS interfaces for optimized bearer release per group in the same way as described above but this is not preferred. The same applies to the Access GW - AAA and ePDG - AAA interfaces.
- the group control device was described as a PGW/GGSN or a PCRF.
- suitable network elements can be applied as a group control device, as long as they can provide the corresponding control signaling.
- a dedicated stand-alone group network control element could be used.
- apparatuses and methods are provided by which a group control device for controlling a group of user equipments is selected.
- the group control device for the group is selected based on information related to the group.
- Information regarding the group control device and the information related to the group are stored in a subscription management device.
- information regarding the group control device is obtained from the subscription management device.
- an apparatus which comprises means for receiving a request to create a packet data connection from a user equipment of a group, and means for selecting a group control device for the group based on information related to the group.
- an apparatus which comprises means for storing subscription-related information in a memory, and means for handling subscriber-related information for a group by referring to an address of a group control device stored for the group in the memory.
- an apparatus which comprises means for handling control of a group of user equipments, and means for forwarding information regarding the group together with the address of an apparatus carrying out the method to an authentication, authorization and accounting entity.
- an apparatus which comprises means for controlling authentication, authorization and accounting in a network, and means for handling authentication, authorization and accounting for a packet data connection related to a group by referring to an address of a group control device stored for the group in the memory.
- an access technology via which signaling is transferred to and from a network element may be any technology by means of which a network element or sensor node can access another network element or node (e.g. via a base station or generally an access node).
- Any present or future technology such as WLAN (Wireless Local Access Network), WiMAX (Worldwide Interoperability for Microwave Access), LTE, LTE-A, Bluetooth, Infrared, and the like may be used; although the above technologies are mostly wireless access technologies, e.g. in different radio spectra, access technology in the sense of the present invention implies also wired technologies, e.g. IP based access technologies like cable networks or fixed lines but also circuit switched access technologies; access technologies may be distinguishable in at least two categories or access domains such as packet switched and circuit switched, but the existence of more than two access domains does not impede the invention being applied thereto,
- stations and transmission nodes may be or comprise any device, apparatus, unit or means by which a station, entity or other user equipment may connect to and/or utilize services offered by the access network; such services include, among others, data and/or (audio-) visual communication, data download etc.;
- a user equipment or communication network element may be any device, apparatus, unit or means by which a system user or subscriber may experience services from an access network, such as a mobile phone or smart phone, a personal digital assistant PDA, or computer, or a device having a corresponding functionality, 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;
- any method step is suitable to be implemented as software or by hardware without changing the idea of the invention in terms of the functionality implemented;
- MOS Metal Oxide Semiconductor
- 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 computer program product comprising executable software code portions 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.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
L'invention concerne des appareils et des procédés au moyen desquels un dispositif de commande de groupe pour commander un groupe d'équipements d'utilisateur est sélectionné. Lorsqu'une connexion de données par paquets pour un premier équipement d'utilisateur du groupe est créé, le dispositif de commande de groupe pour le groupe est sélectionné sur la base d'informations relatives au groupe. Les informations concernant le dispositif de commande de groupe et les informations relatives au groupe sont stockées dans un dispositif de gestion d'abonnement. Lorsqu'un équipement d'utilisateur suivant demande la création d'une connexion de données par paquets, des informations concernant le dispositif de commande de groupe sont obtenues à partir du dispositif de gestion d'abonnement.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/EP2013/052871 WO2014124668A1 (fr) | 2013-02-13 | 2013-02-13 | Gestion de support pour des groupes |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/EP2013/052871 WO2014124668A1 (fr) | 2013-02-13 | 2013-02-13 | Gestion de support pour des groupes |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014124668A1 true WO2014124668A1 (fr) | 2014-08-21 |
Family
ID=47714108
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/EP2013/052871 WO2014124668A1 (fr) | 2013-02-13 | 2013-02-13 | Gestion de support pour des groupes |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2014124668A1 (fr) |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2011019125A (ja) * | 2009-07-09 | 2011-01-27 | Nippon Telegr & Teleph Corp <Ntt> | 通信制御装置、通信制御方法および通信制御プログラム |
-
2013
- 2013-02-13 WO PCT/EP2013/052871 patent/WO2014124668A1/fr active Application Filing
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2011019125A (ja) * | 2009-07-09 | 2011-01-27 | Nippon Telegr & Teleph Corp <Ntt> | 通信制御装置、通信制御方法および通信制御プログラム |
Non-Patent Citations (3)
Title |
---|
3GPP: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on S2a Mobility based On GTP & WLAN access to EPC (SaMOG); Stage 2 (Release 12)", 3GPP DRAFT; 23852-110_RM, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 1 June 2012 (2012-06-01), XP050625467 * |
HUAWEI ET AL: "Enforcing group level policy", vol. SA WG2, no. New Orleans, USA; 20121112 - 20121116, 6 November 2012 (2012-11-06), XP050683975, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_94_New_Orleans/Docs/> [retrieved on 20121106] * |
SAMSUNG: "The solution for key issue 5", vol. SA WG2, no. New Orleans, USA; 20121112 - 20121116, 6 November 2012 (2012-11-06), XP050683957, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_94_New_Orleans/Docs/> [retrieved on 20121106] * |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP6453973B2 (ja) | 無線通信システムにおける多重優先順位制御方法及び装置 | |
US11671831B2 (en) | Method and nodes for handling a user equipment's access to a mobile communications network | |
EP3262787B1 (fr) | Facturation et commande de services périphériques | |
KR101489418B1 (ko) | 혼잡/과부하 제어 방법 및 장치 | |
US20200154312A1 (en) | Terminal apparatus, mme, communication method of terminal apparatus, and communication method of mme | |
US9473971B2 (en) | Method and apparatus for managing QoS group in wireless communication system | |
EP2905990A1 (fr) | Procédé et dispositif de commande de multi-priorité dans un système de communication sans fil | |
CN115039425A (zh) | 通过使用情况监控事件扩展Npcf_EventExposure | |
US11197221B2 (en) | Terminal apparatus, control apparatus, and communication control method | |
EP3078186B1 (fr) | Attribution d'une adresse ip pour un ue dans 3gpp | |
US11483880B2 (en) | UE and communication method for same | |
US20200252979A1 (en) | Terminal apparatus, mobility management entity (mme), and communication control method | |
CN104854893A (zh) | 用于处理无线设备在Wi-Fi网络中的接入的系统 | |
EP3883325B1 (fr) | Équipement utilisateur et procédé de commande de communication | |
US20190230571A1 (en) | Terminal apparatus, control apparatus, and communication control method | |
US10326604B2 (en) | Policy and charging rules function (PCRF) selection | |
US20150237495A1 (en) | Method and system for differentiating between subscribers | |
KR20200088434A (ko) | Ue 및 ue의 통신 제어 방법 | |
US20220394596A1 (en) | Enforcement of maximum number of admitted terminals per network slice | |
EP3813477A1 (fr) | Équipement utilisateur et son procédé de communication | |
EP3952424A1 (fr) | Équipement utilisateur et procédé de commande de communication | |
WO2014124668A1 (fr) | Gestion de support pour des groupes | |
EP3755013A1 (fr) | Procédé et noeud de télécommunications pour commander l'état de connexion d'un équipement utilisateur | |
CN106489283B (zh) | 一种近距离业务通信方法、相关设备及系统 |
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: 13704108 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: 13704108 Country of ref document: EP Kind code of ref document: A1 |