Methods and nodes for transferring a service identifier from a packet core network to a radio network

Abstract

A method in a Gateway General packet radio service Support Node, GGSN, for transferring a service identifier from a packet core network to a radio network is provided. The GGSN adds a service identifier in a General packet radio service Tunneling Protocol for User Plane, GTP-U, header extension of a data packet. The service identifier comprises information about what service and/or traffic pattern that the packet concerns. The GGSN sends the data packet with the GTP-U header extension to a radio network.

Claims

1. A method in a Serving General packet radio service Support Node (SGSN) for transferring a service identifier from a packet core network to a radio network, wherein the radio network is a Base Station Subsystem (BSS), the method comprising: receiving the service identifier in a General packet radio service Tunneling Protocol for User Plane (GTP-U) header extension of a data packet from a Gateway General packet radio service Support Node (GGSN) which the service identifier is identifying a type of service for the data packet; mapping the service identifier to an information element in a BSS General Packet Radio Service (GPRS) Protocol (BSSGP) DownLink Unitdata Protocol Data Unit (DL-UNITDATA PDU) that includes a Logical Link Control (LLC) PDU comprising the data packet or a portion of the data packet; and transferring the service identifier in the DL-UNITDATA PDU from the SGSN to the BSS.

2. The method according to claim 1, wherein the information element is expanded to differentiate subscription and/or device information from service information.

3. The method according to claim 1, further comprising: receiving information about support for the service identifier in a feature bitmap information that is exchanged between the SGSN and the BSS during a BSSGP Virtual Connection (BVC) BVC-RESET procedure.

4. A Serving General packet radio service Support Node (SGSN) for transferring a service identifier from a packet core network to a radio network, wherein the radio network is a Base Station Subsystem (BSS), the SGSN comprising: a receiver, configured to receive the service identifier in a General packet radio service Tunneling Protocol for User Plane (GTP-U) header extension of a data packet from a Gateway General packet radio service Support Node (GGSN) which the service identifier is identifying a type of service for the data packet; a mapping unit, configured to map the service identifier to an information element in a BSS General Packet Radio Service (GPRS) Protocol (BSSGP) Down Link unitdata Protocol Data Unit (DL-UNITDATA PDU) that includes a Logical Link Control (LLC) PDU comprising the data packet or a portion of the data packet; and a transferring unit, configured to transfer the service identifier in the DL-UNITDATA PDU from the SGSN to the BSS.

5. The SGSN according to claim 4, wherein the information element is expanded to differentiate subscription and/or device information from service information.

6. The SGSN according to claim 4, wherein the receiver is further configured to receive information about support for the service identifier in a feature bitmap information that is exchanged between the SGSN and the BSS during a BSSGP Virtual Connection (BVC) BVC-RESET procedure.

7. A method in a Base Station Subsystem (BSS) for receiving a service identifier from a packet core network, the method comprising: receiving the service identifier in a BSS General Packet Radio Service (GPRS) Protocol (BSSGP) DownLink unitdata Protocol Data Unit (DL-UNITDATA PDU) that includes a Logical Link Control (LLC) PDU comprising a data packet or a portion of the data packet from a Serving General packet radio service Support Node (SGSN) which service identifier is identifying a type of service for the data packet, wherein receiving the service identifier in the DL-UNITDATA PDU comprises receiving, within a header of the DL-UNITDATA PDU, a value corresponding to the service identifier; and adding information about support for the service identifier to a feature bitmap information that is exchanged between the SGSN and the BSS during a BSSGP Virtual Connection (BVC) BVC-RESET procedure.

8. The method according to claim 7, further comprising: deciding a radio resource management, which deciding comprises using the received service identifier.

9. A Base Station Subsystem (BSS) for receiving a service identifier from a packet core network, the BSS node comprising: a receiver configured to receive the service identifier in a BSS General Packet Radio Service (GPRS) Protocol (BSSGP) DownLink unitdata Protocol Data Unit (DL-UNITDATA PDU) that includes a Logical Link Control (LLC) PDU comprising a data packet or a portion of the data packet from a Serving General packet radio service Support Node (SGSN) which service identifier is identifying a type of service for the data packet, wherein receiving the service identifier in the DL-UNITDATA PDU comprises receiving, within a header of the DL-UNITDATA PDU, a value corresponding to the Service Identifier; and an adding unit configured to add information about support for the service identifier to a feature bitmap information that is exchanged between the SGSN and the BSS during a BSSGP Virtual Connection (BVC) BVC-RESET procedure.

10. The BSS according to claim 9, further comprising: a deciding unit configured to decide a radio resource management, which deciding comprises using the received Service Identifier.

11. The method of claim 1, wherein mapping the Service Identifier to the information element in the DL-UNITDATA PDU comprises inserting, within a header of the DL-UNITDATA PDU, a value corresponding to the Service Identifier.

12. The SGSN according to claim 4, wherein the mapping unit is configured to map the Service Identifier to the information element in the DL-UNITDATA PDU by inserting, within a header of the DL-UNITDATA PDU, a value corresponding to the Service Identifier.

13. The method of claim 7, further comprising: performing radio resource management mechanisms that are specific to the type of service which corresponds to the received Service Identifier.

14. The BSS according to claim 9, further comprising: a deciding unit configured to decide a radio resource management mechanism to perform that is specific to the type of service which corresponds to the received Service Identifier.

15. The method of claim 1, wherein the DL-UNITDATA PDU is transferred from the SGSN to the BSS over a Gb interface.

16. The method of claim 7, wherein the DL-UNITDATA PDU is received from the SGSN at the BSS over a Gb interface.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) FIG. 1 is a schematic block diagram illustrating an embodiment of a telecommunications system.

(2) FIG. 2 is a combined signalling scheme and flowchart illustrating embodiments in a telecommunications system.

(3) FIG. 3 is a flowchart depicting embodiments of a method in a GGSN.

(4) FIG. 4 is a schematic block diagram illustrating embodiments of a GGSN.

(5) FIG. 5 is a flowchart depicting embodiments of a method in a SGSN.

(6) FIG. 6 is a schematic block diagram illustrating embodiments of a SGSN.

(7) FIG. 7 is a flowchart depicting embodiments of a method in a BSS.

(8) FIG. 8 is a schematic block diagram illustrating embodiments of a BSS.

DETAILED DESCRIPTION

(9) FIG. 1 depicts a telecommunications system 100. The telecommunications system 100 may be for example a GSM type telecommunications system.

(10) The telecommunications system 100 comprises a packet core network 105, sometimes also referred to as a core network. The packet core network 105 comprises a Gateway GPRS Support Node, GGSN, 110 and a Serving GPRS Support Node, SGSN, 115.

(11) The telecommunications system 100 further comprises a radio network 120, which in this example is a base station subsystem, BSS 120. The radio network 120 may sometimes also be referred to as a radio access network.

(12) The BSS 120 comprises base stations of which one, base station 125, is shown in the FIG. 1. The base stations are sometimes referred to as Base Transceiver Stations (BTS).

(13) The radio network 120 also comprises a base station controller, BSC, 130 controlling one or more or more of the base stations, such as the base station 125.

(14) In another radio network type, there may be a Radio Network Controller (RNC) instead of a BSC.

(15) The base station 125 communicates with mobile stations, also referred to as user equipments, within its range. A mobile station is a terminal by which a subscriber can access services offered by an operator's core network. Mobile stations may be for example communication devices such as mobile telephones, cellular telephones, laptops or tablet computers, sometimes referred to as surf plates, with wireless capability. The mobile stations may be portable, pocket-storable, hand-held, computer-comprised, or vehicle-mounted mobile devices, enabled to communicate voice and/or data, via the radio access network, with another entity, such as another mobile station or a server. In the FIG. 1, one such mobile station, mobile station 135, is shown. The mobile station 135 may also be represented by a stationary device or machine that communicates via the radio network 120.

(16) The communication involves the sending and receiving of data packets between the various nodes in the telecommunications system 100.

(17) FIG. 2 illustrates how a method for transferring a service identifier from the packet core network 105 to the radio network 120 may be implemented in the telecommunications system 100 according to some embodiments herein.

(18) The method will be further elaborated in the following.

(19) When the GGSN 110 handles a data packet to be sent towards the SGSN 115, or the radio network 120, or the mobile station 135, it shall according to embodiments herein add information about what type of service the packet concerns, a so called service identifier, in the General packet radio service Tunneling Protocol for User Plane, GTP-U, header of the data packet.

(20) The GGSN 110 then adds this service identifier as a header extension in the GTP-U header for the data packet, when it sends it to the SGSN 115.

(21) Action 201 in FIG. 2 is an example of how this may be done by the GGSN 110. In this action, the traffic pattern and/or type of service for the data flow for a user or device is detected and mapped to a predefined service identifier value. The value is included in a new GTP-U Extension Header together with for the data flow.

(22) It is thus here added a GTP-U Extension Header type to indicate what service the contained packet concerns. The GGSN 110 may retrieve information about the concerned service, or traffic pattern, in different ways e.g. by analyzing the actual data packets or their IP header.

(23) For example, in the SGSN 115, the data is packed into Logical Link Control (LLC) Protocol Data Units (PDUs), which are sent to the BSS 120 in order to be transferred over the radio interface to the concerned mobile station 135. The information that is received in the GTP-U Extension Header about the current type of service is included in the message from the SGSN 115 to the BSS 120. It is then included in the Base Station Subsystem GPRS Protocol (BSSGP) header of the message containing the corresponding LLC PDU(s), i.e. in the DL-UNITDATA PDU(s). The DL-UNITDATA PDU is sent to the BSS 120 to transfer an LLC-PDU across the radio interface to the mobile station 135.

(24) The DL-UNITDATA PDU may be sent over a Gb interface. This interface connects the BSS 110 and the SGSN 115 to transfer control and user plane, in the direction from the SGSN 115 to the BSS 120, that is, the service identifier is then included in a GTP-U Extension Header sent over the Gn interface.

(25) Action 202 in FIG. 2 is an example of how this may be performed by the SGSN 115. In this action, the SGSN 115 reads the received Service Identifier in the GTP-U Extension Header and includes it in a new IE in the DL-UNITDATA PDU header where the data packet is sent as an LLC PDU to the BSS 120. The service identifier is included in the DL-UNITDATA PDU Header and sent over a Gb interface from the SGSN 115 to the BSS 120.

(26) In action 203, the BSS 120 reads the received Service Identifier in the incoming DL-UNITDATA PDU and uses that information to perform appropriate radio resource management actions. The actions can then be related to the traffic pattern and/or type of service for this data flow.

(27) The Service Identifier Information Element (IE) indicates the type of service that the LLC PDU included in the DL-UNITDATA PDU is related to.

(28) The table below shows an example of a Service Identifier IE:

(29) TABLE-US-00001 8 7 6 5 4 3 2 1 octet 1 IEI octet 2, 2a Length Indicator octet 3 Service Identifier Value part

(30) The numbers 1-8 define bit positions in the given octet. An octet is a unit of digital information comprising eight bits. IEI stands for Information Element Identifier which is a codeword that uniquely identifies a particular Information Element. Length Indicator is the number of valid octets following the Length Indicator.

(31) The table below illustrates an example of a Service Identifier Value part coding.

(32) TABLE-US-00002 coding bits 87654321 Semantic 00000000 Service type no 1 00000001 Service type no 2 . . . . . . 11111111 Service type no 256
Service Identifier Value defines the values that can be assigned to different services/traffic patterns. As can be seen in this table, there are eight coding bit in this example, and hence 256 different service types, or values, may be coded. The term semantic may be referred to as the meaning of the coded information.

(33) Note that the above mentioned information element is merely an example, and may in some embodiments be expanded to differentiate subscription/device information and actual service information.

(34) The introduced information element may of course also be defined with more octets than in the above example, thus allowing more service types. For example, by using one more octet, up to 65536 service types may be supported.

(35) To avoid that the service identifier information element is included from the SGSN 115 to a BSS 120 that does not support service identifier information, or is not making use of it, the support for this service identifier may be added to a Feature Bitmap Information. The Feature Bitmap Information is an element that indicates features supported by the BSS 120 that need to be negotiated with the SGSN 115 over the Gb interface, e.g. in an Extended Feature Bitmap IE that is exchanged between the SGSN 110 and the BSS 120 during a BVC-RESET procedure.

(36) BVC stands for BSSGP Virtual Connection. BVCs provide communication paths between BSSGP entities. Each BVC is used in the transport of BSSGP PDUs between peer point-to-point (PTP) functional entities, peer point-to-multipoint (PTM) functional entities and peer signalling functional entities.

(37) The BVC Reset procedure is performed to synchronise the initialization of GPRS BVC related contexts at a BSS 120 and SGSN 115. This enables the BSS 120 and SGSN 115 to begin communication in known states. The Feature bitmap information is exchanged between the BSS 120 and the SGSN 115 when the reset is for a signalling BVC. The Feature bitmap information is sent so that each network service entity, that is BSS 120 and SGSN 115, informs what optional features it supports.

(38) The received service identifier may then be used by the BSS 120 to perform e.g. different radio resource management mechanisms that are specific for the traffic pattern or type of service.

(39) An advantage of embodiments herein is that they provide means for the operator to transfer explicit info about a particular service and/or traffic pattern to the BSS 120 where it can be used for specific resource management for example to improve resource utilization and/or end user experience. The indicated services may e.g. be such used for Machine Type of Communication, which will typically require a different radio resource management behavior.

(40) Another advantage of embodiments herein is that they are not dependent of Quality of Service procedures. They may thus be used also for mobile stations that do not support the Packet Flow Identifier(s) (PFI).

(41) Embodiments herein, relating to a method in the GGSN, 110 for transferring a service identifier from the packet core network 105 to the radio network 120 will now be further elaborated and described with reference to the flowchart depicted in FIG. 3. In some embodiments, the radio network 120 is a Base Station Subsystem, BSS.

(42) The method comprises the following actions, which actions may be taken in any suitable order.

(43) In action 301, which is an optional action, the GGSN 110 detects the traffic pattern and/or the type of service for the data packet.

(44) The GGSN 110 may retrieve information about the concerned service, or traffic pattern, in different ways e.g. by analyzing the actual data packets or their IP header.

(45) In action 302, which is also optional, the GGSN 110 then maps the traffic pattern and/or the type of service to a predefined service identifier value.

(46) In action 303, the GGSN 110 adds a service identifier in a General packet radio service Tunneling Protocol for User Plane, GTP-U, header extension of a data packet. The service identifier comprises information about what service and/or traffic pattern that the packet concerns.

(47) In action 304, the GGSN 110 sends the data packet with the GTP-U header extension to the radio network 120.

(48) In some embodiments, the sending is performed via a Serving General packet radio service Support Node, SGSN 115.

(49) Since the GTP-U header extension contains the Service Identifier, the service identifier is hence transferred to the radio network.

(50) To perform the actions above for transferring a service identifier from a packet core network 105 to a radio network 120, the GGSN 110 comprises an arrangement schematically depicted in FIG. 4.

(51) In some embodiments, the radio network 120 is a Base Station Subsystem, BSS.

(52) The GGSN 110 comprises an adding unit 400. The adding unit 400 is configured to add a service identifier in a GTP-U header extension of a data packet. The service identifier comprises information about what service and/or traffic pattern that the packet concerns.

(53) The GGSN 110 further comprises a sending unit 410. The sending unit 410 is configured to send the data packet with the GTP-U header extension to a radio network.

(54) In some embodiments, the sending unit 410 is configured to perform the sending via the SGSN 115.

(55) In some embodiments, the GGSN 110 further comprises a detecting unit 420 configured to detect the traffic pattern and/or the type of service for the data packet.

(56) In some embodiments, the GGSN 110 further comprises a mapping unit 430 configured to map the traffic pattern and/or the type of service to a predefined service identifier value.

(57) The embodiments of the GGSN 110 for transferring a service identifier from the packet core network 105 to the radio network 120 may be implemented through one or more processors, such as a processor 440 in the GGSN 110 depicted in FIG. 4, together with computer program code for performing the actions of embodiments herein.

(58) The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the GGSN 110.

(59) One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the GGSN 110 e.g. remotely.

(60) The GGSN 110 may further comprise a memory 450 comprising one or more memory units. The memory 450 may be arranged to be used to store data and/or applications to perform the actions of the embodiments herein when being executed in the GGSN 110.

(61) Embodiments herein, relating to a method in the SGSN, 115 for transferring a service identifier from a packet core network 105 to a radio network 120 will now be further elaborated and described with reference to the flowchart depicted in FIG. 5. In these embodiments, the radio network 120 is a BSS. The method comprises the following actions, which actions may be taken in any suitable order.

(62) In action 501, which is an optional action, the SGSN 115 receives support for, i.e. information about a support for, the service identifier in a feature bitmap information that is exchanged between the SGSN 115 and the BSS 120 during a BVC-RESET procedure.

(63) This is advantageous, since it avoids that the service identifier is included from the SGSN 115 to a BSS 120 that does not support it, or is not making use of it.

(64) In action 502, the SGSN 115 receives the service identifier in a GTP-U header extension of a data packet from the GGSN 110. The service identifier is related to a traffic pattern and/or to a type of service for the data packet.

(65) In action 503, the SGSN 115 maps the service identifier to an information element in DL-UNITDATA PDU of a message containing the data packet.

(66) In some embodiments, the information element is expanded to differentiate subscription and/or device information and service information.

(67) In action 504 the SGSN 115 transfers the service identifier in the DL-UNITDATA PDU to the BSS 120.

(68) To perform the actions above for transferring a service identifier from a packet core network 105 to a radio network 120, wherein the radio network 120 is a BSS, the SGSN comprises an arrangement schematically depicted in FIG. 6.

(69) The SGSN 115 comprises a receiver 600, configured to receive a service identifier in a GTP-U header extension of a data packet from the GGSN 110. The service identifier is related to a traffic pattern and/or to a type of service for the data packet. In some embodiments, the receiver 600 is further configured to receive a support, i.e. information about support, for the service identifier in a feature bitmap information that is exchanged between the SGSN and the BSS during a BVC-RESET procedure.

(70) The SGSN 115 further comprises a mapping unit 610, configured to map the service identifier to an information element in a DL-UNITDATA PDU of a message containing the data packet.

(71) The SGSN 115 further comprises a transferring unit 620, configured to transfer the service identifier in the DL-UNITDATA PDU to the BSS 120.

(72) In some embodiments, the information element is expanded to differentiate subscription and/or device information and service information.

(73) The embodiments of the SGSN 115 for transferring a service identifier from the packet core network 105 to the radio network 120 may be implemented through one or more processors, such as a processor 630 in the SGSN 115 depicted in FIG. 6, together with computer program code for performing the actions of embodiments herein.

(74) The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the SGSN 115.

(75) One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the SGSN 115 e.g. remotely.

(76) The SGSN 115 may further comprise a memory 640 comprising one or more memory units. The memory 640 may be arranged to be used to store data and/or applications to perform the actions of the embodiments herein when being executed in the SGSN 115.

(77) Embodiments herein, relating to the BSS 120 for receiving a service identifier from the packet core network 105, will now be further elaborated and described with reference to the flowchart depicted in FIG. 7. The method comprises the following actions, which actions may be taken in any suitable order.

(78) In action 701, which is an optional action, the BSS 120 adds a support, i.e. an information about a support, for the service identifier to a feature bitmap information that is exchanged between the SGSN 115 and the BSS 120 during a BVC-RESET procedure.

(79) This is advantageous, to avoid that the service identifier is included from the SGSN 115 to a BSS 120 that does not support it, or is making use of it.

(80) In action 702, the BSS 120 receives a service identifier in a DL-UNITDATA PDU of a message containing a data packet from a SGSN 115. The service identifier is related to a traffic pattern and/or to a type of service for the data packet.

(81) In action 703, which is an optional action, the BSS 120 decides a radio resource management. The deciding comprises using the received service identifier.

(82) To perform the actions above for receiving a service identifier from the packet core network 105, the BSS 120 comprises an arrangement schematically depicted in FIG. 8.

(83) The BSS 120 comprises a receiver 800 configured to receive a service identifier in a DL-UNITDATA PDU of a message containing a data packet from the SGSN 115. The service identifier is related to a traffic pattern and/or to a type of service for the data packet.

(84) The BSS 120 further comprises a deciding unit 810 configured to decide a radio resource management, which deciding comprises using the received service identifier.

(85) In some embodiments, the BSS 120 further comprises an adding unit 820 configured to add a support for the service identifier to a feature bitmap information that is exchanged between the SGSN 115 and the BSS 120 during a BVC-RESET procedure.

(86) The embodiments of the BSS 120 for receiving a service identifier from the packet core network 105 may be implemented through one or more processors, such as a processor 830 in the BSS 120 depicted in FIG. 8, together with computer program code for performing the actions of embodiments herein.

(87) The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the BSS 120.

(88) One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the BSS 120 e.g. remotely.

(89) The BSS 120 may further comprise a memory 840 comprising one or more memory units. The memory 840 may be arranged to be used to store data and/or applications to perform the actions of the embodiments herein when being executed in the BSS 120.

(90) As has been described above, it is an object of embodiments herein to provide a method and arrangement for transferring a service identifier from the packet core network 105, i.e. the GGSN 110, to a BSS 120.

(91) This object is further achieved by a method and arrangement according to some embodiments that includes the steps of and provides means to: transfer service identifiers in the GTP-U header extensions IE from the GGSN 110 to the SGSN 115 mapping these service identifiers in the SGSN 115 from GTP-U header extension IE into an IE added to the BSSGP protocol in the DL-UNITDATA PDU transferring the service identifiers in an IE added to the BSSGP protocol to the DL-UNITDATA PDU utilizing the service identifiers in the BSS 120 for radio resource management decisions based on internal implementation choice.

(92) When using the word “comprise” or “comprising” it shall be interpreted as non-limiting, i.e. meaning “consist at least of”.

(93) The term “configured to” used herein may also be referred to as “arranged to”.

(94) The embodiments herein are not limited to the above described embodiments. Various alternatives, modifications and equivalents may be used. Therefore, the above embodiments should not be taken as limiting the scope of the invention, which is defined by the appending claims.