2008-12-23 20:25:15 +00:00
|
|
|
#ifndef _GSM_04_08_H
|
|
|
|
#define _GSM_04_08_H
|
|
|
|
|
2011-03-22 15:47:59 +00:00
|
|
|
#include <osmocom/gsm/gsm48.h>
|
2011-07-23 08:53:30 +00:00
|
|
|
#include <osmocom/gsm/gsm_utils.h>
|
|
|
|
#include <osmocom/gsm/protocol/gsm_04_08.h>
|
|
|
|
|
2008-12-25 23:28:35 +00:00
|
|
|
struct msgb;
|
|
|
|
struct gsm_bts;
|
2009-06-10 15:11:52 +00:00
|
|
|
struct gsm_network;
|
2009-07-23 19:13:03 +00:00
|
|
|
struct gsm_trans;
|
rename gsm_subscriber_connection to ran_conn
In preparation for inter-BSC and inter-MSC handover, we need to separate the
subscriber management logic from the actual RAN connections. What better time
to finally rename gsm_subscriber_connection.
* Name choice:
In 2G, this is a connection to the BSS, but even though 3GPP TS commonly talk
of "BSS-A" and "BSS-B" when explaining handover, it's not good to call it
"bss_conn": in 3G a BSS is called RNS, IIUC.
The overall term for 2G (GERAN) and 3G (UTRAN) is RAN: Radio Access Network.
* Rationale:
A subscriber in the MSC so far has only one RAN connection, but e.g. for
inter-BSC handover, a second one needs to be created to handover to. Most of
the items in the former gsm_subscriber_connection are actually related to the
RAN, with only a few MM and RTP related items. So, as a first step, just rename
it to ran_conn, to cosmetically prepare for moving the not strictly RAN related
items away later.
Also:
- Rename some functions from msc_subscr_conn_* to ran_conn_*
- Rename "Subscr_Conn" FSM instance name to "RAN_conn"
- Rename SUBSCR_CONN_* to RAN_CONN_*
Change-Id: Ic595f7a558d3553c067f77dc67543ab59659707a
2018-11-29 21:37:51 +00:00
|
|
|
struct ran_conn;
|
2014-01-19 10:47:44 +00:00
|
|
|
struct amr_multirate_conf;
|
2015-09-24 09:30:58 +00:00
|
|
|
struct amr_mode;
|
2008-12-25 23:28:35 +00:00
|
|
|
|
2010-12-23 22:00:21 +00:00
|
|
|
#define GSM48_ALLOC_SIZE 2048
|
|
|
|
#define GSM48_ALLOC_HEADROOM 256
|
2010-05-01 12:22:44 +00:00
|
|
|
|
2016-01-25 21:03:25 +00:00
|
|
|
static inline struct msgb *gsm48_msgb_alloc_name(const char *name)
|
2010-05-01 12:22:44 +00:00
|
|
|
{
|
|
|
|
return msgb_alloc_headroom(GSM48_ALLOC_SIZE, GSM48_ALLOC_HEADROOM,
|
2016-01-25 21:03:25 +00:00
|
|
|
name);
|
2010-05-01 12:22:44 +00:00
|
|
|
}
|
|
|
|
|
rename gsm_subscriber_connection to ran_conn
In preparation for inter-BSC and inter-MSC handover, we need to separate the
subscriber management logic from the actual RAN connections. What better time
to finally rename gsm_subscriber_connection.
* Name choice:
In 2G, this is a connection to the BSS, but even though 3GPP TS commonly talk
of "BSS-A" and "BSS-B" when explaining handover, it's not good to call it
"bss_conn": in 3G a BSS is called RNS, IIUC.
The overall term for 2G (GERAN) and 3G (UTRAN) is RAN: Radio Access Network.
* Rationale:
A subscriber in the MSC so far has only one RAN connection, but e.g. for
inter-BSC handover, a second one needs to be created to handover to. Most of
the items in the former gsm_subscriber_connection are actually related to the
RAN, with only a few MM and RTP related items. So, as a first step, just rename
it to ran_conn, to cosmetically prepare for moving the not strictly RAN related
items away later.
Also:
- Rename some functions from msc_subscr_conn_* to ran_conn_*
- Rename "Subscr_Conn" FSM instance name to "RAN_conn"
- Rename SUBSCR_CONN_* to RAN_CONN_*
Change-Id: Ic595f7a558d3553c067f77dc67543ab59659707a
2018-11-29 21:37:51 +00:00
|
|
|
void cm_service_request_concludes(struct ran_conn *conn,
|
2016-06-19 16:06:02 +00:00
|
|
|
struct msgb *msg);
|
|
|
|
|
2008-12-31 18:52:11 +00:00
|
|
|
/* config options controlling the behaviour of the lower leves */
|
2010-12-22 22:17:50 +00:00
|
|
|
void gsm0408_clear_all_trans(struct gsm_network *net, int protocol);
|
rename gsm_subscriber_connection to ran_conn
In preparation for inter-BSC and inter-MSC handover, we need to separate the
subscriber management logic from the actual RAN connections. What better time
to finally rename gsm_subscriber_connection.
* Name choice:
In 2G, this is a connection to the BSS, but even though 3GPP TS commonly talk
of "BSS-A" and "BSS-B" when explaining handover, it's not good to call it
"bss_conn": in 3G a BSS is called RNS, IIUC.
The overall term for 2G (GERAN) and 3G (UTRAN) is RAN: Radio Access Network.
* Rationale:
A subscriber in the MSC so far has only one RAN connection, but e.g. for
inter-BSC handover, a second one needs to be created to handover to. Most of
the items in the former gsm_subscriber_connection are actually related to the
RAN, with only a few MM and RTP related items. So, as a first step, just rename
it to ran_conn, to cosmetically prepare for moving the not strictly RAN related
items away later.
Also:
- Rename some functions from msc_subscr_conn_* to ran_conn_*
- Rename "Subscr_Conn" FSM instance name to "RAN_conn"
- Rename SUBSCR_CONN_* to RAN_CONN_*
Change-Id: Ic595f7a558d3553c067f77dc67543ab59659707a
2018-11-29 21:37:51 +00:00
|
|
|
int gsm0408_dispatch(struct ran_conn *conn, struct msgb *msg);
|
2008-12-31 18:52:11 +00:00
|
|
|
|
2011-04-18 15:04:00 +00:00
|
|
|
int gsm0408_rcvmsg(struct msgb *msg, uint8_t link_id);
|
2011-07-23 08:53:30 +00:00
|
|
|
/* don't use "enum gsm_chreq_reason_t" to avoid circular dependency */
|
2010-09-06 01:36:02 +00:00
|
|
|
void gsm_net_update_ctype(struct gsm_network *net);
|
2008-12-25 23:28:35 +00:00
|
|
|
|
rename gsm_subscriber_connection to ran_conn
In preparation for inter-BSC and inter-MSC handover, we need to separate the
subscriber management logic from the actual RAN connections. What better time
to finally rename gsm_subscriber_connection.
* Name choice:
In 2G, this is a connection to the BSS, but even though 3GPP TS commonly talk
of "BSS-A" and "BSS-B" when explaining handover, it's not good to call it
"bss_conn": in 3G a BSS is called RNS, IIUC.
The overall term for 2G (GERAN) and 3G (UTRAN) is RAN: Radio Access Network.
* Rationale:
A subscriber in the MSC so far has only one RAN connection, but e.g. for
inter-BSC handover, a second one needs to be created to handover to. Most of
the items in the former gsm_subscriber_connection are actually related to the
RAN, with only a few MM and RTP related items. So, as a first step, just rename
it to ran_conn, to cosmetically prepare for moving the not strictly RAN related
items away later.
Also:
- Rename some functions from msc_subscr_conn_* to ran_conn_*
- Rename "Subscr_Conn" FSM instance name to "RAN_conn"
- Rename SUBSCR_CONN_* to RAN_CONN_*
Change-Id: Ic595f7a558d3553c067f77dc67543ab59659707a
2018-11-29 21:37:51 +00:00
|
|
|
int gsm48_tx_simple(struct ran_conn *conn,
|
2018-06-11 23:20:34 +00:00
|
|
|
uint8_t pdisc, uint8_t msg_type);
|
rename gsm_subscriber_connection to ran_conn
In preparation for inter-BSC and inter-MSC handover, we need to separate the
subscriber management logic from the actual RAN connections. What better time
to finally rename gsm_subscriber_connection.
* Name choice:
In 2G, this is a connection to the BSS, but even though 3GPP TS commonly talk
of "BSS-A" and "BSS-B" when explaining handover, it's not good to call it
"bss_conn": in 3G a BSS is called RNS, IIUC.
The overall term for 2G (GERAN) and 3G (UTRAN) is RAN: Radio Access Network.
* Rationale:
A subscriber in the MSC so far has only one RAN connection, but e.g. for
inter-BSC handover, a second one needs to be created to handover to. Most of
the items in the former gsm_subscriber_connection are actually related to the
RAN, with only a few MM and RTP related items. So, as a first step, just rename
it to ran_conn, to cosmetically prepare for moving the not strictly RAN related
items away later.
Also:
- Rename some functions from msc_subscr_conn_* to ran_conn_*
- Rename "Subscr_Conn" FSM instance name to "RAN_conn"
- Rename SUBSCR_CONN_* to RAN_CONN_*
Change-Id: Ic595f7a558d3553c067f77dc67543ab59659707a
2018-11-29 21:37:51 +00:00
|
|
|
int gsm48_tx_mm_info(struct ran_conn *conn);
|
|
|
|
int gsm48_tx_mm_auth_req(struct ran_conn *conn, uint8_t *rand,
|
2017-01-26 23:25:47 +00:00
|
|
|
uint8_t *autn, int key_seq);
|
rename gsm_subscriber_connection to ran_conn
In preparation for inter-BSC and inter-MSC handover, we need to separate the
subscriber management logic from the actual RAN connections. What better time
to finally rename gsm_subscriber_connection.
* Name choice:
In 2G, this is a connection to the BSS, but even though 3GPP TS commonly talk
of "BSS-A" and "BSS-B" when explaining handover, it's not good to call it
"bss_conn": in 3G a BSS is called RNS, IIUC.
The overall term for 2G (GERAN) and 3G (UTRAN) is RAN: Radio Access Network.
* Rationale:
A subscriber in the MSC so far has only one RAN connection, but e.g. for
inter-BSC handover, a second one needs to be created to handover to. Most of
the items in the former gsm_subscriber_connection are actually related to the
RAN, with only a few MM and RTP related items. So, as a first step, just rename
it to ran_conn, to cosmetically prepare for moving the not strictly RAN related
items away later.
Also:
- Rename some functions from msc_subscr_conn_* to ran_conn_*
- Rename "Subscr_Conn" FSM instance name to "RAN_conn"
- Rename SUBSCR_CONN_* to RAN_CONN_*
Change-Id: Ic595f7a558d3553c067f77dc67543ab59659707a
2018-11-29 21:37:51 +00:00
|
|
|
int gsm48_tx_mm_auth_rej(struct ran_conn *conn);
|
|
|
|
int gsm48_tx_mm_serv_ack(struct ran_conn *conn);
|
|
|
|
int gsm48_tx_mm_serv_rej(struct ran_conn *conn,
|
2013-10-31 14:36:41 +00:00
|
|
|
enum gsm48_reject_value value);
|
2009-02-06 21:55:37 +00:00
|
|
|
int gsm48_send_rr_release(struct gsm_lchan *lchan);
|
2009-10-05 12:00:14 +00:00
|
|
|
int gsm48_send_rr_ciph_mode(struct gsm_lchan *lchan, int want_imeisv);
|
rename gsm_subscriber_connection to ran_conn
In preparation for inter-BSC and inter-MSC handover, we need to separate the
subscriber management logic from the actual RAN connections. What better time
to finally rename gsm_subscriber_connection.
* Name choice:
In 2G, this is a connection to the BSS, but even though 3GPP TS commonly talk
of "BSS-A" and "BSS-B" when explaining handover, it's not good to call it
"bss_conn": in 3G a BSS is called RNS, IIUC.
The overall term for 2G (GERAN) and 3G (UTRAN) is RAN: Radio Access Network.
* Rationale:
A subscriber in the MSC so far has only one RAN connection, but e.g. for
inter-BSC handover, a second one needs to be created to handover to. Most of
the items in the former gsm_subscriber_connection are actually related to the
RAN, with only a few MM and RTP related items. So, as a first step, just rename
it to ran_conn, to cosmetically prepare for moving the not strictly RAN related
items away later.
Also:
- Rename some functions from msc_subscr_conn_* to ran_conn_*
- Rename "Subscr_Conn" FSM instance name to "RAN_conn"
- Rename SUBSCR_CONN_* to RAN_CONN_*
Change-Id: Ic595f7a558d3553c067f77dc67543ab59659707a
2018-11-29 21:37:51 +00:00
|
|
|
int gsm48_send_rr_app_info(struct ran_conn *conn, uint8_t apdu_id,
|
2011-04-18 15:04:00 +00:00
|
|
|
uint8_t apdu_len, const uint8_t *apdu);
|
|
|
|
int gsm48_send_rr_ass_cmd(struct gsm_lchan *dest_lchan, struct gsm_lchan *lchan, uint8_t power_class);
|
2009-12-16 23:25:18 +00:00
|
|
|
int gsm48_send_ho_cmd(struct gsm_lchan *old_lchan, struct gsm_lchan *new_lchan,
|
2011-04-18 15:04:00 +00:00
|
|
|
uint8_t power_command, uint8_t ho_ref);
|
2008-12-25 23:28:35 +00:00
|
|
|
|
2010-12-22 22:57:45 +00:00
|
|
|
int mncc_tx_to_cc(struct gsm_network *net, int msg_type, void *arg);
|
2009-06-10 15:11:52 +00:00
|
|
|
|
2009-02-16 22:53:52 +00:00
|
|
|
/* convert a ASCII phone number to call-control BCD */
|
2011-04-18 15:04:00 +00:00
|
|
|
int encode_bcd_number(uint8_t *bcd_lv, uint8_t max_len,
|
2009-06-10 04:08:54 +00:00
|
|
|
int h_len, const char *input);
|
2011-04-18 15:04:00 +00:00
|
|
|
int decode_bcd_number(char *output, int output_len, const uint8_t *bcd_lv,
|
2009-06-10 04:08:54 +00:00
|
|
|
int h_len);
|
2009-02-16 22:53:52 +00:00
|
|
|
|
2011-04-18 15:04:00 +00:00
|
|
|
int send_siemens_mrpci(struct gsm_lchan *lchan, uint8_t *classmark2_lv);
|
2010-05-15 17:07:20 +00:00
|
|
|
int gsm48_extract_mi(uint8_t *classmark2, int length, char *mi_string, uint8_t *mi_type);
|
2011-04-18 15:04:00 +00:00
|
|
|
int gsm48_paging_extract_mi(struct gsm48_pag_resp *pag, int length, char *mi_string, uint8_t *mi_type);
|
2009-08-21 02:57:35 +00:00
|
|
|
|
2011-04-18 15:04:00 +00:00
|
|
|
int gsm48_lchan_modify(struct gsm_lchan *lchan, uint8_t lchan_mode);
|
2009-10-22 13:23:11 +00:00
|
|
|
int gsm48_rx_rr_modif_ack(struct msgb *msg);
|
2009-11-29 18:07:28 +00:00
|
|
|
|
2010-06-15 11:39:27 +00:00
|
|
|
struct msgb *gsm48_create_mm_serv_rej(enum gsm48_reject_value value);
|
2010-06-15 11:40:05 +00:00
|
|
|
struct msgb *gsm48_create_loc_upd_rej(uint8_t cause);
|
2010-06-14 20:26:10 +00:00
|
|
|
void gsm48_lchan2chan_desc(struct gsm48_chan_desc *cd,
|
|
|
|
const struct gsm_lchan *lchan);
|
2009-10-22 13:13:00 +00:00
|
|
|
|
rename gsm_subscriber_connection to ran_conn
In preparation for inter-BSC and inter-MSC handover, we need to separate the
subscriber management logic from the actual RAN connections. What better time
to finally rename gsm_subscriber_connection.
* Name choice:
In 2G, this is a connection to the BSS, but even though 3GPP TS commonly talk
of "BSS-A" and "BSS-B" when explaining handover, it's not good to call it
"bss_conn": in 3G a BSS is called RNS, IIUC.
The overall term for 2G (GERAN) and 3G (UTRAN) is RAN: Radio Access Network.
* Rationale:
A subscriber in the MSC so far has only one RAN connection, but e.g. for
inter-BSC handover, a second one needs to be created to handover to. Most of
the items in the former gsm_subscriber_connection are actually related to the
RAN, with only a few MM and RTP related items. So, as a first step, just rename
it to ran_conn, to cosmetically prepare for moving the not strictly RAN related
items away later.
Also:
- Rename some functions from msc_subscr_conn_* to ran_conn_*
- Rename "Subscr_Conn" FSM instance name to "RAN_conn"
- Rename SUBSCR_CONN_* to RAN_CONN_*
Change-Id: Ic595f7a558d3553c067f77dc67543ab59659707a
2018-11-29 21:37:51 +00:00
|
|
|
void release_security_operation(struct ran_conn *conn);
|
|
|
|
void allocate_security_operation(struct ran_conn *conn);
|
2012-01-23 15:40:24 +00:00
|
|
|
|
2017-05-27 11:18:50 +00:00
|
|
|
int gsm48_multirate_config(uint8_t *lv, const struct amr_multirate_conf *mr, const struct amr_mode *modes);
|
2014-01-19 10:47:44 +00:00
|
|
|
|
2017-04-09 10:32:51 +00:00
|
|
|
int gsm48_tch_rtp_create(struct gsm_trans *trans);
|
rename gsm_subscriber_connection to ran_conn
In preparation for inter-BSC and inter-MSC handover, we need to separate the
subscriber management logic from the actual RAN connections. What better time
to finally rename gsm_subscriber_connection.
* Name choice:
In 2G, this is a connection to the BSS, but even though 3GPP TS commonly talk
of "BSS-A" and "BSS-B" when explaining handover, it's not good to call it
"bss_conn": in 3G a BSS is called RNS, IIUC.
The overall term for 2G (GERAN) and 3G (UTRAN) is RAN: Radio Access Network.
* Rationale:
A subscriber in the MSC so far has only one RAN connection, but e.g. for
inter-BSC handover, a second one needs to be created to handover to. Most of
the items in the former gsm_subscriber_connection are actually related to the
RAN, with only a few MM and RTP related items. So, as a first step, just rename
it to ran_conn, to cosmetically prepare for moving the not strictly RAN related
items away later.
Also:
- Rename some functions from msc_subscr_conn_* to ran_conn_*
- Rename "Subscr_Conn" FSM instance name to "RAN_conn"
- Rename SUBSCR_CONN_* to RAN_CONN_*
Change-Id: Ic595f7a558d3553c067f77dc67543ab59659707a
2018-11-29 21:37:51 +00:00
|
|
|
int gsm48_conn_sendmsg(struct msgb *msg, struct ran_conn *conn, struct gsm_trans *trans);
|
2018-12-03 10:00:04 +00:00
|
|
|
struct msgb *gsm48_create_mm_info(struct gsm_network *net);
|
2017-04-09 10:32:51 +00:00
|
|
|
|
2008-12-23 20:25:15 +00:00
|
|
|
#endif
|