Yota PCRF. Subscriber Management Interface Description. Product version: 3.6 Document version: 2.5 Status: development

Transcription

1 Yota PCRF Subscriber Management Interface Product version: 3.6 Document version: 2.5 Status: development Yota 2013

2 Revision History Date Version Author Revision Max Kumskoy Document created Max Kumskoy Interface URL changed Max Kumskoy Supported product version changed to 2.2 Added new attribute immediate and changed behavior of management methods. Added description attribute to subscriber profile; Max Kumskoy Updated methods updatesubscriber, updateservice: To set start time and stop time to NULL start_time and stop_time parameters should be sent without a value, i.e. &start_time=&stop_time= Max Kumskoy IMSI and MAC address format explained Max Kumskoy New method addserviceext Max Kumskoy Minor corrections Max Kumskoy Max Kumskoy Provisioning guidelines and error handling suggestions added Added AVPs support for services. New AVPs Zone, DL_BW, UL_BW Added provisioning guidelines Max Kumskoy xxxserviceattribute - > xxsubscriberserviceattribute Max Kumskoy getsubscriber, getservice, getallservices, getactiveservices new request parameter "show_attributes" to display AVPs Max Kumskoy Corrected section "Operations on attributes" Evgenia Martynyuk Supported product version changed to Evgenia Martynyuk Supported product version changed to 3.3. Added BS_ID, LAST_ONLINE, LAST_REGION_ID, VISTED_REGIONS parameters to subscriber profile output Evgenia Martynyuk Supported product version changed to Evgenia Martynyuk Supported product version changed to Evgenia Martynyuk BS_ID -> LAST_LOCATION. Supported product version changed to Evgenia Martynyuk Subscriber_ID format -> Int64. Added custom attributes commands description. Added ENABLE parameter to addaccum and updateaccum methods. Added setaccumvalue method. Supported product version changed to Evgenia Martynyuk Supported product version changed to 3.6. No parameter State for Subscriber Profile Management Commands Yota

3 Table of Contents Introduction... 5 Related documents... 5 Interface description Subscriber Profile Management Commands addsubscriber deletesubscriber updatesubscriber getsubscriber Services Management Commands addservice addserviceext deleteservice deleteallservices getservice getallservices getactiveservices updateservice Custom Attributes Commands setsubscriberserviceattribute getsubscriberserviceattribute getallsubscriberserviceattributes deletesubscriberserviceattribute deleteallsubscriberserviceattributes setsubscriberattribute getsubscriberattribute getallsubscriberattributes deletesubscriberattribute deleteallsubscriberattributes Accumulators Management Commands addaccum deleteaccum getaccum getallaccums updateaccum setaccumvalue deleteallaccums Yota

4 1.5 Other Commands addevent Provisioning Guidelines Provisioning Services Provisioning Attributes Error Handling Yota

5 Introduction Yota PCRF 3.6 Subscriber Management Interface This document describes Subscriber Management Interface. In order for PCRF to manage subscribers, their profiles, services and accumulators in policy decision process they should be provisioned to SPR. Subscribers are referenced by id, which can be any subscriber station identification parameter that is used in core network signaling for instance, subscriber id can be IMSI (LTE). IMSI is usually 15 digits long. For example subscriber_id= Before associating subscriber with services or accumulators they should be provisioned to SPR dictionaries. Dedicated configuration interface is used for such purposes. See Configuration Interface Specification [2]. When update* commands are used, new values should be send inside request URL. Values will not be modified for those parameters that are not preset in URL. By default all add*, update* and delete* methods call Policy Engine to re-calculate policy decision after the method is processed. Parameter immediate should be included and set to 0 (disable) to change this behavior. In case immediate=0 (it is disabled), a method addevent should be used to launch Policy Engine. This offers two approaches to change SPR data and call for Event: 1. Transactional: method 1(immediate = 0), method 2(immediate = 0), method 3 (immediate = 0), addevent. 2. Non-Transactional: immediate = 1 or not present in request URL. Result codes are described in "Yota PCRF 3.6 Provisioning common principles.docx". Related documents 1. Yota PCRF 3.6 Provisioning common principles.docx [1] of main provisioning conventions and error codes. 2. Yota PCRF 3.6 SPR configuration Interface.docx [2] SPR configuration interface specification. Yota

6 Interface description Yota PCRF 3.6 Subscriber Management Interface Interface URL: Default port: 80 on PCRF nodes 8080 on DDF nodes. Request format REST, GET method (HTTP) format JSON Yota

7 id start_time stop_time immediate description show_attributes Subscriber Profile Management Commands 1.1 Subscriber Profile Management Commands Supported methods: Method\ Parameter addsubscriber M O O O O - deletesubscriber M - - O - - updatesubscriber M O O O O - getsubscriber M O Input parameters types: Parameter Type Value range ID Int64 - START_TIME STOP_TIME IMMEDIATE YYYYMMDDHHMMSS YYYYMMDDHHMMSS Int If provided an empty value then start time is set to null. If provided an empty value, then start time is set to null. 1 Enable. Launch Policy Engine. 0 Disable. Do not launch Policy Engine. Default value NULL NULL DESCRIPTION String Length: 0~256 NULL SHOW_ATTRI BUTES Int 1- display attributes 0 hide attributes 1 0 Comment IMSI, or any other internal subscriber identifier. IMSI, i.e The time since when the subscriber profile can be active. If not specified it means that subscriber profile could be active from infinite time in the past The time until when the subscriber profile can be active. If not specified, then it means that subscriber profile can be "active" infinite time in the future If IMMEDIATE parameter is enabled, then Policy Engine is triggered right after the command is executed Any additional explanatory text If SHOW_ATTRIBUTE parameter with value "1" is provided in request then subscriber attributes are included in the response. Yota

8 Yota PCRF 3.6 Subscriber Management Interface If not provided attributes are not returned Output parameters types: Parameter Type Value range Comment Result Int32 Error code. See description in [1] ErrMsg String Error description. See description in [1] ID Int64 IMSI or any other internal subscriber identifier DESCRIPTION String Length:1~256 Any additional explanatory text LAST_LOCATION String Length:1~32 Last location (BS ID) of the subscriber LAST_REGION_ID String Length:1~32 Last Region of the subscriber LAST_ONLINE String Length:1~256 Last time online VISITED_REGIONS String Length:1~512 The list of visited region codes The time since when the subscriber profile can be active. If not specified START_TIME YYYYMMDDHHMMSS it means that subscriber profile could be active from infinite time in the past STOP_TIME YYYYMMDDHHMMSS The time until when the subscriber profile can be active. If not specified, then it means that subscriber profile can be "active" infinite time in the future ATTRIBUTES An array of subscriber attribute in Group: the form of ATTRIBUTE and VALUE <Id>, <Value> pairs Yota

9 Subscriber Profile Management Commands addsubscriber A command to create a new subscriber profile in SPR &stop_time= &description=test_subscriber&immediate=0 "errmsg": "ERROR_MSG", deletesubscriber A command to delete a subscriber from SPR. When a subscriber is deleted, all services assigned to him are deleted as well. "errmsg": "ERROR_MSG", updatesubscriber Command to change attributes of a subscriber in SPR. Sent parameters overwrite existing ones in the database. Parameters that are not mentioned in the request are not changed. To set subscriber profile start and stop time to NULL, parameters start_time and/or stop_time should be provided without a value (for example, /spr/sm/updatesubscriber?id=test&start_time=&stop_time=). Example request: &stop_time= &description=test_subscriber&immediate=0 "errmsg": "ERROR_MSG", Yota

10 1.1.4 getsubscriber Yota PCRF 3.6 Subscriber Management Interface Command to get subscriber data and the list of services assigned to him. "result": 0, "errmsg": "OK", "SUBSCRIBER": "ID": " ", "DESCRIPTION": "Test subscriber", "LAST_LOCATION": " E600", "LAST_REGION_ID": "RUS_CNT_BLG", "START_TIME": " :00:01", "STOP_TIME": " :00:00", "LAST_ONLINE": " :43:39", "VISITED_REGIONS": "78, 60", "ATTRIBUTES": [ "ID" : "ZONE", "VALUE" : "ZONE_1", "ID" : "BW_DL", "VALUE" : "512000". Subscriber information Yota

11 subscriber_id service_id start_time stop_time duration mode immediate show_attributes Services Management Commands 1.2 Services Management Commands Supported methods: Method/ Parameter addservice M M O O - - O - addserviceext M M - - M O O - deleteservice M M O - deleteallservices M O - updateservice M M O O - - O - getservice M M O addevent M getallservices M O getactiveservices M M O Input parameters types: Parameter Type Value range SUBSCRIBER_ID Int64 - SERVICE_ID String Length:1~32 - START_TIME STOP_TIME DURATION YYYYMMDDHHMM SS YYYYMMDDHHMM SS Int32 If provided an empty value, then start time is set to null. If provided an empty value, then start time is set to null. 0 parameter is ignored; >0 service validity time period in seconds default; override; append; Default value Null Null Null Comment IMSI, MSISDN or any other internal subscriber identifier. IMSI, i.e Service ID in service dictionary Time when the service takes effect. Null service effective from infinite time in the past Time when the service stops. Null service effective infinite time in the future A period of time in seconds to calculate start and stop time for service validity Mode parameter specifies MODE String 0 how service stop and start times are calculated. IMMEDIATE Int 1 Enable. 1 If IMMEDIATE parameter is Yota

12 Yota PCRF 3.6 Subscriber Management Interface Launch Policy enabled, then Policy Engine. Engine is triggered right 0 Disable. Do after the command is not launch Policy executed Engine. SHOW_ATTRIBU TES Int 1 include subscriber service attributes to response; 0 hide subscriber service attributes 0 If SHOW_ATTRIBUTE parameter with value "1" is provided in request, then subscriber attributes are included in response. If not provided attributes are not returned Output parameters types: Parameter Type Value range Comment Result Int32 Error code. See description in [1] ErrMsg String Error description. See description in [1] SERVICE_ID String Length:1~32 Service identifier START_TIME String YYYY-MM-DD hh:mm:ss or null Time when the service takes effect. Null service effective from infinite time in the past STOP_TIME ATTRIBUTES String Group: Attribute, Value YYYY-MM-DD hh:mm:ss or null Time when the service stops. Null service effective infinite time in the future An array of subscriber attribute in the form of ATTRIBUTE and VALUE pairs. Yota

13 Services Management Commands addservice Command to add a service to a subscriber. srv_1&start_time= &stop_time= &immediate=0 "errmsg": "ERROR_MSG", addserviceext Command addserviceext should be used to add service with a specific duration or modify validity period for an existing service. Validity time is an absolute time interval, during which the service is considered as active. This interval is calculated using DURATION parameter and MODE parameter. DURATION parameter defines the time period in seconds. It must be more than 0. MODE defines how the validity time is calculated. Mode is an optional parameter. If it is not present default mode is used. Important If DURATION value is less or equal to zero, then exception "Invalid parameter specified" (10004) is returned. Usage guidelines: 1. When adding a new or existing service but its start and stop time is not set: Disregarding the MODE value: START_TIME = current time; STOP_TIME = current time + DURATION. Example 1: No services for Subscriber ID /spr/sm/addserviceext?subscriber_id= &service_id=service&duration =3600 Result: "result": 0, "errmsg": "OK" Yota

14 Yota PCRF 3.6 Subscriber Management Interface Information Server time is UTC. 2. When modifying validity time for existing service with defined start and/or stop time: If method is called before or within the start-stop interval: If MODE = default or not present, then: Exception "Service already exists" (10002) is returned. If MODE = override, then: START_TIME = current_time; STOP_TIME = current_time + DURATION; If MODE = append, then: START_TIME is not changed; STOP_TIME = old STOP_TIME + DURATION; If method is called after the start-stop interval: Disregarding the MODE value: Example 2: START_TIME = current_time; STOP_TIME = current_time + DURATION; Subscriber has one service SERVICE, start and stop times are defined. Method is called within start-stop interval. /spr/sm/addserviceext?subscriber_id= &service_id=service&duration =3600 Result: "result": 10002, "errmsg": " Service [SERVICE] already exists " d=srv_1&immediate=0&duration=60&mode=override "errmsg": "ERROR_MSG", Yota

15 Services Management Commands deleteservice Command to delete a service assigned to a subscriber profile in SPR. =srv_&immediate=0 "errmsg": "ERROR_MSG", deleteallservices Command to delete all services assigned to a subscriber profile in SPR. diate=0 "errmsg": "ERROR_MSG", getservice Command to get parameters of a specific subscriber s service from SPR. ervice_1&show_attributes=1 "errmsg": "ERROR_MSG" "SERVICE": "SERVICE_ID": "Service1", "START_TIME": " :04:05", "STOP_TIME": " :04:05", "ATTRIBUTES": [ "ID" : "ZONE", "VALUE" : "ZONE_1", A service was obtained successfully Yota

16 "ID" : "BW_DL", "VALUE" : "512000" ] Yota PCRF 3.6 Subscriber Management Interface getallservices Command to get parameters of all subscriber services that are present in SPR. ributes=1 "errmsg": "ERROR_MSG" "SERVICES": [ "SERVICE_ID": "Service1", "START_TIME": " :04:05", "STOP_TIME": " :04:05", "ATTRIBUTES": [ "ID" : "ZONE", "VALUE" : "ZONE_1", "ID" : "BW_DL", "VALUE" : "512000" ], "SERVICE_ID": "Service3", "START_TIME": null, "STOP_TIME": null, "ATTRIBUTES": [ "ID" : "ZONE", "VALUE" : "ZONE_1", "ID" : "BW_DL", "VALUE" : "512000" ] ] All services were obtained successfully getactiveservices Command to get parameters of subscriber s active services from SPR. Yota

17 Services Management Commands _attributes=1 "errmsg": "ERROR_MSG" "SERVICES": [ "SERVICE_ID": "Service1", "START_TIME": " :04:05", "STOP_TIME": " :04:05", "ATTRIBUTES": [ "ATTRIBUTE" : "ZONE", "VALUE" : "ZONE_1", "ATTRIBUTE" : "BW_DL", "VALUE" : ], "SERVICE_ID": "Service4", "START_TIME": null, "STOP_TIME": null, "ATTRIBUTES": [ "ID" : "ZONE", "VALUE" : "ZONE_1", "ID" : "BW_DL", "VALUE" : "512000" ] ] Active services were obtained successfully updateservice Command to update service parameters. Sent parameters overwrite existing ones in the database. Parameters that are not mentioned in the request are not changed. To set service start and stop time to NULL, parameters start_time and/or stop_time should be provided without a value (for example /spr/sm/updateservice?subscriber_id=test&service_id=test&start_time=&stop_time=). =srv_1&start_time= &stop_time= &immediate=0. Yota

18 "errmsg": "ERROR_MSG", Yota PCRF 3.6 Subscriber Management Interface Yota

19 Method/ Parameter subscriber_id service_id attribute_id value Custom Attributes Commands 1.3 Custom Attributes Commands Supported methods: Subscriber Service attributes: setsubscriberserviceattribute M M M M Sets the attribute value. Modifies value If attribute already exists. getsubscriberserviceattribute M M M - Returns attribute value getallsubscriberserviceattributes M M - - Returns all service attributes and their values deletesubscriberserviceattribute M M M - Removes specific attribute value deleteallsubscriberserviceattributes M M - - Removes all service attributes Subscriber attributes: setsubscriberattribute M - M M Sets the attribute value. Modifies value If attribute already exists. getsubscriberattribute M - M - Returns attribute value getallsubscriberattributes M Returns all subscriber attributes and their values deletesubscriberattribute M - M - Removes specific attribute value deleteallsubscriberattributes M Removes all subscriber attributes Input parameters types: Parameter Type Value range Default value Comment subscriber_id Int64 - IMSI, MSISDN or any other internal subscriber identifier service_id String Length:1~32 - Service ID attribute_id String Length:1~32 - Attribute ID value String Length:1~32 - Attribute value setsubscriberserviceattribute Command to set an attribute to the subscriber service &service_id=speed_512&attribute_id=DL&value=512 "result": 0, "errmsg": "OK" Yota

20 1.3.2 getsubscriberserviceattribute Command to get a subscriber service attribute. Yota PCRF 3.6 Subscriber Management Interface &service_id=speed_512&attribute_id=DL "result": 0, "errmsg": "OK", "ATTRIBUTE": "ID": "DL", "VALUE": "512" Attribute was obtained successfully getallsubscriberserviceattributes Command to &service_id=speed_512 "result": 0, "errmsg": "OK", "ATTRIBUTES": [ "ID": "DL", "VALUE": "512", "ID": "UL", "VALUE": "256" ] Attributes were obtained successfully deletesubscriberserviceattribute Command to delete an attribute from subscriber service. Yota

21 Custom Attributes Commands &service_id=speed_512&attribute_id=DL "result": 0, "errmsg": "OK" deleteallsubscriberserviceattributes Command to delete all attributes from subscriber service &service_id=speed_512 "result": 0, "errmsg": "OK" setsubscriberattribute Command to set an attribute to subscriber. &attribute_id=ma&value=msk "result": 0, "errmsg": "OK" getsubscriberattribute Command to set an attribute from subscribe profile &attribute_id=ma Yota

22 "result": 0, "errmsg": "OK", "ATTRIBUTE": "ID": "MA", "VALUE": "MSK" Yota PCRF 3.6 Subscriber Management Interface Attribute was obtained successfully getallsubscriberattributes Command to get all subscriber attributes. 5 "result": 0, "errmsg": "OK", "ATTRIBUTES": [ "ID": "MA", "VALUE": "MSK", "ID": "ZONE", "VALUE": "Center" ] Attributes were obtained successfully deletesubscriberattribute Command to delete a subscriber attribute. 5&attribute_id=MA "result": 0, "errmsg": "OK" Yota

23 deleteallsubscriberattributes Command to delete all subscriber attributes. Custom Attributes Commands "result": 0, "errmsg": "OK" Yota

24 subscriber_id accum_id scheme_id immediate Value enable Yota PCRF 3.6 Subscriber Management Interface 1.4 Accumulators Management Commands Supported methods: Method/ Parameter addaccum M M O O - O deleteaccum M M - O - - getaccum M M getallaccums M updateaccum M M O O - O setaccumvalue M M - O M - deleteallaccums M - - O - - Input parameters types: Parameter Type Value range SUBSCRIBER_ID Int64 - ACCUM_ID String Length:1~32 - SCHEME_ID* IMMEDIATE String Int32 Length:1~32 NULL_SCHEME 1 Enable. Launch Policy Engine. 0 Disable. Do not launch Policy Engine Default value - 1 Comment IMSI, MSISDN or any other internal subscriber identifier Accumulator ID in Accumulators dictionary Scheme ID in schemes dictionary. If parameter value is NULL_SCHEME then a threshold scheme for given accumulator is not specified If IMMEDIATE parameter is enabled, then Policy Engine is triggered right after the command is executed VALUE Int64 Value of an accumulator 1 Enable. ENABLE Int16 Enable the If ENABLE parameter is set accumulator. the PCEF will be sending 0 Disable. subscriber usage reports. Disable the accumulator Yota

25 Accumulators Management Commands Output parameters types: Parameter Type Value range Comment Result Int32 Error code ErrMsg String Error description SUBSCRIBER_ID String Length:1~64 IMSI, MSISDN or any other internal subscriber identifier. IMSI, i.e ACCUM_ID String Length:1~32 Accumulator ID in Accumulators dictionary SCHEME_ID START_TIME RESET_TIME String String String Length:1~32 NULL_SCHEME YYYY-MM-DD hh:mm:ss or null YYYY-MM-DD hh:mm:ss or null Scheme ID in schemes dictionary. If parameter value is NULL_SCHEME then a threshold scheme for given accumulator is not specified The time since when the reset period is being counted. The value " :00:00" means, that the time is not set. The value null means, that accumulator is not periodically reset The time when accumulator value is reset. The value " :00:00" means that the time is not set. The value null means that accumulator is not periodically reset. VALUE Int64 Accumulated value in Bytes ENABLE Boolean True\False If the accumulator is enabled or not LEVEL Signed Int64 The level of threshold scheme was reached SCHEME_ID If scheme ID value is not specified then an accumulator will be added with the default scheme id, which is specified in the accumulators dictionary. If the default scheme in the accumulators dictionary is not specified, accumulator will be added without a scheme. At the same time SCHEME_ID value in the DB takes the special value NULL_SCHEME addaccum Command to assign an accumulator to a subscriber. ww&scheme_id=www_limit&immediate=1&enable=1 "errmsg": "ERROR_MSG", Yota

26 1.4.2 deleteaccum Yota PCRF 3.6 Subscriber Management Interface Command to delete an accumulator from a subscriber profile. =www&immediate=1 "errmsg": "ERROR_MSG", getaccum Command to get data about specific accumulator of a subscriber. ww "result": 0, "errmsg": "OK", "ACCUM": "SUBSCRIBER_ID": " ", "ACCUM_ID": "www", "SCHEME_ID": "www", "START_TIME": " :42:39", "RESET_TIME": " :42:39", "VALUE": 121, "ENABLED": true, "LEVEL": "100" Object ACCUM contains accumulators data getallaccums Command to get data about all accumulators of a subscriber. "errmsg": "ERROR_MSG", Accumulators info Yota

27 Accumulators Management Commands "ACCUMS": [ "SUBSCRIBER_ID": , "ACCUM_ID": "www", "SCHEME_ID": "www_default", "VALUE": "121", "START_TIME": " :04:05", "RESET_TIME": " :04:05", "ENABLED": true, "LEVEL": "100", "SUBSCRIBER_ID": , "ACCUM_ID": "p2p", "SCHEME_ID": "p2p_default", "VALUE": "0", "START_TIME": " :04:05", "RESET_TIME": " :04:05", "ENABLED": false, "LEVEL": "0" ] updateaccum Command to change accumulator parameters for a subscriber. Only sent parameters are changed. =www&scheme_id=www_limit&immidiate=1&enable=1 "errmsg": "ERROR_MSG", setaccumvalue Command to set value for an accumulator. d=www&value=1063&immidiate=1 "errmsg": "ERROR_MSG", Yota

28 1.4.7 deleteallaccums Yota PCRF 3.6 Subscriber Management Interface Command to delete all accumulators from a subscriber profile. "errmsg": "ERROR_MSG", Yota

29 1.5 Other Commands addevent Other Commands This command triggers PCRF to launch Policy Engine and if necessary perform session modification procedures. "errmsg": "ERROR_MSG", Yota

30 Provisioning Guidelines 1.6 Provisioning Services 1. Transactional approach: Yota PCRF 3.6 Subscriber Management Interface Goal: modify subscriber profile to switch subscriber to Full Access from Guest Access. To do so BSS should: first remove Guest Access services, and then add Full Access services with immediate flag set to 0. This will not trigger Policy Engine to start policy selection process before the provisioning transaction is logically complete. send addevent command to complete the transaction, and to notify PCRF that subscriber profile modification is finished. Example: BSS PCRF/DDF /spr/sm/deleteservice?subscriber_id= &service_id=guest_access&immediate=0 HTTP 200 OK Result=0 ErrMsg=OK /spr/sm/addservice?subscriber_id= &service_id=full_access&immediate=0 HTTP 200 OK Result=0 ErrMsg=OK /spr/sm/addevent?subscriber_id= HTTP 200 OK Result=0 ErrMsg=OK NOTE1: Before service id can be used in Subscriber Management commands it should be defined in Service Info Dictionary by PCRF administrator (command addserviceinfo). Otherwise Error Code "10005 Service not found" will be returned. 2. Non-transactional approach: Goal: add additional service to subscriber profile without immediate flag. This will trigger Policy Engine to select policy, if a subscriber is online. Yota

31 Provisioning Attributes Example: BSS PCRF/DDF /spr/sm/addservice?subscriber_id= &service_id=full_access_turbo HTTP 200 OK Result=0 ErrMsg=OK 1.7 Provisioning Attributes Goal: To subscribe a user to Full Access tariff with downlink bandwidth 10Mbit/s and marketing zone SPB. To do so BSS should: Add service with immediate flag set to 0, Set service attributes and their values one by one, Send AddEvent to complete the transaction. Example: BSS PCRF/DDF /spr/sm/addservice?subscriber_id= &service_id=full_access&immediate=0 HTTP 200 OK Result=0 ErrMsg=OK /spr/sm/ setsubscriberserviceattribute?subscriber_id= &service_id=full_access&attribute=zone&value=zone_1 HTTP 200 OK Result=0 ErrMsg=OK /spr/sm/ setsubscriberserviceattribute?subscriber_id= &service_id=full_access&attribute=dl_bw&value=10000 HTTP 200 OK Result=0 ErrMsg=OK /spr/sm/addevent?subscriber_id= HTTP 200 OK Result=0 ErrMsg=OK NOTE2: Before an attribute can be used in Subscriber Management commands it should be defined in Service Info Dictionary by PCRF administrator (command addserviceattributeinfo). Otherwise Error Code "10005 Service attribute not found" will be returned. Yota

32 1.8 Error Handling Yota PCRF 3.6 Subscriber Management Interface Loss of HTTP response from PCRF. It is known that due to physical link errors between BSS and regional PCRF HTTP response from PCRF can be lost. BSS will make another attempt to send the command after a certain timeout. If BSS retransmits add or delete command it will fail because the command was performed last time. In this case, after second attempt, BSS may receive an error response with Result (ErrMsg=Entity not found) or Result=10002 (ErrMsg=Entity already exists). BSS should not treat this as a logical error. In case BSS receives or error after the first attempt, it should treat the response as an indication of error. The error might have occurred due to logical mistake or information inconsistency between the two systems. Example: BSS PCRF/DDF /spr/sm/addservice?subscriber_id= &service_id=full_access HTTP 200 OK Result=0 ErrMsg=OK /spr/sm/addservice?subscriber_id= &service_id=full_access HTTP 200 OK Result=10002 ErrMsg = Service already exists Yota