Atletico Madrid close to making their first signing of 2020
by BeSoccerAtletico Madrid are thinking about the winter transfer window and about how they can improve their squad. They are close to making their first transfer of 2020. Bruno Guimaraes wants to play until 'Cholo' Simeone.
Renan Lodi arrived from Athletico Paranaense to occupy the place that Filipe Luis left when they lost all their defenders. The full back has started well at the Wanda, he is growing quickly and adapting to what Simeone has aked of him.
Atletico were spot on in signing the defender and they now want to do the same with Bruno Guimaraes. Precisely, 'Los Colchoneros' reached an agreement with Athletico Paraense to have preference over getting the midfielder until 2020.
It is for that reason Atletico have got a move on. 'AS' reports that Bruno Guimaraes' agent was in Madrid last week with the intention of sealing the final details of his potential contract.
Featured links
- Madrid now waits for Neymar
- The latest football transfers news and rumours
- Who has the most free-kicks goals: Messi or Cristiano?
- Luis Enrique returns to Spain national team
The player could move in January for around 30 million euros. Flamengo, at this moment in time, are trying to deflect attention from Bruno Guimaraes in order to keep hold of him and prevent Atletico signing him.
But the midfielder is attracted by the opportunity to make the step up to Europe, He has turned down a contract renewal especially because his former teammate Renan Lodi is at Atleti. Last season, Bruno Guimaraes started 40 matches, scored five goals and gave four assists at 22.
With this signing, Atletico will gain youth and a player who he can easily go forward in attack. He is capable of performing from the off like Renan Lodi.


Toggle navigation
topiq
Loading, please hold on.
You do not need to refresh, this web page reconnects automatically and tracks all state offline. If you find any bugs, please report them
here.


{% extends "global/Page.html" %} {% load staticfiles otree_tags %} {% block title %} You have made your decisions for today {% endblock %} {% block content %}
We remind you that this experiment consists of six stages that will take place over 36 days. You have completed the first 5 stages today. Come back tomorrow at 10:00am to make your decisions in the sixth stage. It will take a few minutes a day to complete.
You will be paid at the end of this experiment. Your payment will be the sum of what you earn in each stage. Every 10 points that you earn will be turned into €1. The amount you earn will depend partly on your choices, partly on the choices of the other participants, and partly on chance. You will be paid directly on your PayPal account so that none of the other participants will know how much you earned. There will be additional instructions about your earnings.
If you do not finish your choices today or you miss {{ inactive_threshold }} decisions during the experiment you will be automatically and permanently excluded from the experiment. If you are excluded you will not be paid. Contact {{ email }} if you have any questions.


A condition holds across a range of data
Invertable
reverse (reverse x) === x
Associative
a + (b + c) === (a + b) + c
Commutative
a + b === b + a
Idempotent
logout >> logout === logout
Round Tripping
parse (print x) === x
Generated not hard coded
Built from composable primitive generators
Filtering for desired traits
All my code examples will be written using
with some minor handwaving
text' = Gen.text
(Range.linear 1 10)
(Gen.filter (/= '\0') Gen.unicode)
@Provide
Arbitrary<String> text() {
return Arbitraries.strings().all().excludeChars('\u0000')
.ofMinLength(1).ofMaxLength(10);
}
This is telling the testing library to make a string of 1 to 10 unicode characters, excluding the null character
If your code breaks on funky characters like direction indicators, bells, or backspace this will find it
Generated data is composed to make larger structures
You start by describing the smallest part of your data, what it needs, and then use that generator in the next level up
genPassword = Password <$> text'
genEmail = Email <$> text'
genUser = User <$> genEmail <*> genPassword
@Provide
Arbitrary<Password> genPassword() {
Arbitrary<String> password = Arbitraries.strings().all()
.ofMinLength(3).ofMaxLength(21);
return Combinators.combine(password)
.as((pass) -> new Password(pass))
}
@Provide
Arbitrary<User> genUser() {
Arbitrary<Email> email = ...
Arbitrary<Password> password = ...
return Combinators.combine(email, password)
.as((e, p) -> new User(e, p))
}
Now that we can generate our various inputs we need to test our code
What to test against if we don't know the answer ahead of time?
Known good functions
Mathematical properties
If you can say a general thing about a function you can test that
list = Gen.list (Range.linear 0 100) Gen.unicode
prop_reverse =
property $ do
xs <- forAll list
reverse (reverse xs) === xs
@Property
boolean listReversal(@ForAll List<int> list) {
List<int> list2 = new List(list);
Collections.reverse(list2);
Collections.reverse(list2);
return Arrays.equals(
list.toArray(new int[0]),
list2.toArray(new int[0])
);
}
Handful of base assertions
plus anything language specific
Checking data structures
isRight (Left _) = failure
isRight (Right _) = success
prop_alwaysRight = property $ do
e <- forAll $ Gen.either Gen.unicode Gen.bool
isRight e
// Either<a, b> I'm using is from functionaljava
@Property
boolean alwaysRight(@ForAll Either<a, b> e) {
return either.isRight(e);
}
When a failing input is found for a property several things happen
If a smaller value cannot be generated the testing stops with the last failing value found.
✗ failed at test/foo.hs:7:21
after 2 tests and 1 shrink.
┏━━ test/foo.hs ━━━
7 ┃ isRight (Left _) = failure
┃ ^^^^^^^^^^^^^^^^^^^^^^^^^^^
8 ┃ isRight (Right _) = success
┏━━ test/foo.hs ━━━
10 ┃ prop_alwaysRight = property $ do
11 ┃ e <- forAll $ Gen.either Gen.unicode Gen.bool
┃ │ Left '\NUL'
12 ┃ isRight e
Stateful applications require a bit more effort
Model the state of the target application
Updates, deletes, etc
Run the state changes for app and model
Check that expected and actual state match
Excellent blog post on this at the end
Testing Model
data TestUser (v :: * -> *) = TestUser
{ _userEmail :: Email
, _userGivenName :: GivenName
, _userSurname :: Surname
...
}
newtype AuthState (v :: * -> *) = AuthState
{ _authUsers :: Map Email (TestUser v)
} deriving (Eq, Show)
State machine command
cNewUser env =
Command gen (newUserExe env)
[ Update newUserUpdate
, Ensure newUserEnsure
]
where
emailNotUsed s e =
not . any (ilike e) . M.keys $ s ^. authUsers
gen state = pure $ AuthNewUser
<$> Gen.filter (emailNotUsed state) genEmail
<*> fmap GivenName text'
<*> fmap Surname text'
<*> fmap Expired Gen.bool
<*> genPassword
State machines for jqwik are similar
Taken from
https://jqwik.net/docs/current/user-guide.html#stateful-testing
class PopAction implements Action<MyStringStack> {
public boolean precondition(MyStringStack stack) {
return !stack.isEmpty();
}
public MyStringStack run(MyStringStack stack) {
int sizeBefore = stack.size();
String topBefore = stack.top();
String popped = stack.pop();
Assertions.assertThat(popped).isEqualTo(topBefore);
Assertions.assertThat(stack.size())
.isEqualTo(sizeBefore - 1);
return stack;
}
}
While wonderful what do I use?
QuickCheck Manual
jqwik User Guide
Introduction to state machine testing: part 1
by Andrew McMiddlin
Property based state machine testing
by Andrew McMiddlin


'Inspirational': Marcin gets top honour for devotion to family
by Fiona DillonWork of four young carers is also recognised
A father of two who looks after his wife who has locked-in syndrome, leaving her unable to move, has been named as the National Carer of the Year.
Marcin Filak, from Kildalkey, Co Meath, who was described as "inspirational", was presented with the overall award by broadcasters Marty Whelan and Mary Kennedy at a gala ceremony in the Westin Hotel in Dublin yesterday.
He cares for his wife Ola and their two children, the eldest of whom Piotr (13) has autism.
Ola suffered a catastrophic brain stem stroke three weeks after the birth of the couple's daughter Anastasia (2), resulting in locked-in syndrome. Her condition means she is aware of her surroundings but cannot move or speak and now communicates through eye movements.
Please log in or register with Independent.ie for free access to this article.
New to Independent.ie? Create an account
The couple are originally from Poland but moved to Ireland in 2016.
Throughout Ola's 18 months in hospital, Marcin was by her side every day and always maintained that he would make her dream to come home a reality.
He quit his job as a farm equipment engineer and undertook extensive training in order to be able meet his wife's care needs at home.
Ola and the St Pat's team from the National Rehabilitation Hospital nominated Marcin to say thank you for the extraordinary care he provides for his family.
Now in their 13th year, the Netwatch Carer of the Year Awards seek to recognise the contribution of Ireland's 355,000 family carers, almost two-thirds of whom provide over 100 hours of care a week.
Speaking at the ceremony, Catherine Cox of Family Carers Ireland said that Marcin's commitment to his family "is an inspiration to us all".
She also paid tribute to the four young carers of the year, who were also announced yesterday at the event, praising the maturity and dedication they show in helping care for their loved ones.
One of these awards was given to Lily Power (18), from Ballincollig, Co Cork, who has been caring from a very young age for her mum who has Parkinson's.
Áine Grant (20), from Bridgend, Co Donegal, who cares for her mum Nuala who was diagnosed with early onset dementia two years ago, was also given an award.
Matthew McCartin (17), from Gorey, Co Wexford, who has been caring for his dad since he was five years old, was another award winner. His dad now has advanced Parkinson's with dementia and is wheelchair bound.
Hailey Golden (11), from Breaffy, Castlebar, Co Mayo, who has three brothers with special needs, was also honoured.


|
SGCoreCs
v1.3.1
SenseGlove C# API
|
Sensor Data coming from a Fino, converted into useful values. More...
Public Member Functions | |
| Nova_SensorData (Vect3D[] values, int numberOfVals, Quat imuRot, bool imuComplete, float battLvl, bool charging) | |
| override string | ToString () |
| Create a readable string representation of this Sensor Data More... | |
| bool | Equals (Nova_SensorData other) |
| Returns true if this sensor data contains the same values as another. More... | |
| string | Serialize () |
| Convert this sensor data into a string so it can be stored on disk. More... | |
Static Public Member Functions | |
| static Nova_SensorData | Empty () |
| Generates empty data More... | |
| static Nova_SensorData | Parse (string rawData, ref Nova_GloveInfo gloveInfo) |
| Parse the bytes as they come in from the device into useable values. More... | |
| static Nova_SensorData | Deserialize (string serializedString) |
| Convert this sensor data into ta string representation. More... | |
Properties | |
| Vect3D[] | SensorValues [get, set] |
| Pronation/Supination, Flexion/Extension and Abduction/Adduction values for each finger. More... | |
| Quat | IMURotation [get, set] |
| Quaternion rotation relative to magnetic north. More... | |
| int | ParsedValues [get, set] |
| The number of values that were parsed from the sensor string. More... | |
| bool | IMUParsed [get, set] |
| Whether or not the IMU values were all succesfully parsed. More... | |
| bool | IsCharging [get, set] |
| Returns true if this NovaGlove is connected to a power source More... | |
| float | BatteryLevel [get, set] |
| A value between 0..1 that represents the battery level of this Nova Glove (0 .. 100%). Returns -1 if the value wasn't received. More... | |
Sensor Data coming from a Fino, converted into useful values.
| SGCore.Nova.Nova_SensorData.Nova_SensorData | ( | Vect3D[] | values, |
| int | numberOfVals, | ||
| Quat | imuRot, | ||
| bool | imuComplete, | ||
| float | battLvl, | ||
| bool | charging | ||
| ) |
| values | |
| numberOfVals | |
| imuRot | |
| imuComplete | |
| battLvl | |
| charging |
|
static |
Convert this sensor data into ta string representation.
| serializedString |
|
static |
Generates empty data
| bool SGCore.Nova.Nova_SensorData.Equals | ( | Nova_SensorData | other | ) |
Returns true if this sensor data contains the same values as another.
| other |
|
static |
Parse the bytes as they come in from the device into useable values.
| rawData | |
| gloveInfo |
| string SGCore.Nova.Nova_SensorData.Serialize | ( | ) |
Convert this sensor data into a string so it can be stored on disk.
| override string SGCore.Nova.Nova_SensorData.ToString | ( | ) |
Create a readable string representation of this Sensor Data
|
getset |
A value between 0..1 that represents the battery level of this Nova Glove (0 .. 100%). Returns -1 if the value wasn't received.
|
getset |
Whether or not the IMU values were all succesfully parsed.
|
getset |
Quaternion rotation relative to magnetic north.
|
getset |
Returns true if this NovaGlove is connected to a power source
|
getset |
The number of values that were parsed from the sensor string.
|
getset |
Pronation/Supination, Flexion/Extension and Abduction/Adduction values for each finger.


Hi!
I would like to monitor my family's pv plant with 20 inverters, so I thought to use some arduino boards with the ct sensors (15 ct sensors in the arduino mega or 7 in the arduino pro mini ) but I have some doubts if I should use several 9V power supplies or if I can use just one and connect it to each board. Does anyone could help me?
I prefer to use the minimum pieces as possible ;)
Thank you.
Could I use only one 9V power supply for many devices?
Submitted by Guest on Sat, 28/02/2015 - 15:59»
Re: Could I use only one 9V power supply for many devices?
You can use one 9vac adapter for many devices IF they do not take their power from that source. The 9vac adapters are closely matched to the emonTx v3x power requirements and any increase will effect the accuracy of the readings. So if you were to have 1 x 9vac and 1 x 5vdc supply you could power several emonTx's (how many depends on how much power the 5vdc supply compares to your demands). You should still use 1 9vac per phase if not single phase. Using separate dc and ac adapters will be more cost efficient with any 3 or more emonTx's on any one phase.
Paul
Re: Could I use only one 9V power supply for many devices?
Thanks Paul for your quick reply!
I drew this schema to explain the idea:
I put one 5v dc power supply but I know maybe I need more, it depends on the demands. In this case, should I use just a 9v ac power supply or I need anything else? Or maybe in this case I don't need a 9vac but I would like to read accurate measurements.
Re: Could I use only one 9V power supply for many devices?
Markinhos, please do not continue to repost the same thing when your posts are are being held in a moderation queue - Didn't you see the warning message on screen?
Re: Could I use only one 9V power supply for many devices?
I see nothing wrong with you diagram that will work.
The 9vac adapter provides information on phase and voltage that is vital to an accurate reading, which is why you must off load the power demands on to the 5vdc to use it for more than one device.
It's only really viable if using more than 2 devices. running 2 emonTx v3's each from it own 9vac would be (almost) the same as your diagram but without the hassle of splicing the power connections.
Re: Could I use only one 9V power supply for many devices?
I didn't see the warning message and I thought it was some problem with my browser or my inet connection, sorry Paul! (moderator)
And thank you so much Paul, all my doubts were resolved. The inverters of the pv plant are located in a very small cabin in the middle of the countryside, and we've just one wall socket. (we are using the mains only for the air conditioner, because during the summer it's too hot inside). In the picture, the white small cabin is where we have all the inverters.
Another problem is the inet connection and exporting the data. Currently, I've running EmomCMS on a VPS where I've my blog and others, and the idea is to use a script to send the data. For that I can use a 3G USB dongle on a Raspberry Pi.
Thanks!


Login
motherland naija
Quick Links
motherland naija
Politics
Career
Travel
Sports
Education
Market Place
Family
Entertainment
Others


Been working so hard I'm punching my card
Eight hours for what?


|
BatchingRPCServer
|
Top level namespace for this project. More...
Classes | |
| struct | BindArgs |
| A virtual wrapper for arguments used to bind a Servable. More... | |
| struct | FileBindArgs |
| class | MXNetServable |
| struct | RawBindArgs |
| class | Servable |
| Delimits the public API for a Servable object. More... | |
| class | TBServer |
| Implements the BatchingServer::Service, providing the transport/RPC layer. More... | |
Enumerations | |
| enum | ReturnCodes { OK = 1, NEED_BIND_CALL = 2, SHAPE_INCORRECT = 3, NEXT_BATCH = 4, BATCH_TOO_LARGE = 5, NO_SUITABLE_BIND_ARGS = 6 } |
| Possible return codes for a Servable object. More... | |
Top level namespace for this project.
Defines the namespace within which all the code in this project resides. Protobuf generates code under this namespace so for uniformity everything lives under this namespace. No subdivisions exist as of 26/12/2017.
| enum Serving::ReturnCodes |
Possible return codes for a Servable object.
These are the return codes that each Servable object may return. Some codes will only be returned by certain functions.
| Enumerator | |
|---|---|
| OK | Function exited normally. |
| NEED_BIND_CALL | Bind was not called on the Servable, typically done before construction of TBServer. See Servable::Bind(BindArgs&). |
| SHAPE_INCORRECT | The shape of the input was incorrect, check the shape and retry. |
| NEXT_BATCH | The current batch is too full to process the request, retry. |
| BATCH_TOO_LARGE | The request's size is too large for the Servable's set batch size, caller should subdivide and try again or increase the batch size. |
| NO_SUITABLE_BIND_ARGS | Bind has failed because the Servable was unable to cast the BindArgs instance to a usable type. |
Definition at line 46 of file Servable.hpp.


Destroydrop
»
Javascripts
»
Tree
Example
open all
|
close all
My example tree
Node 1
Node 1.1
Node 2
Node 3
©2002-2003 Geir Landrö


Colour intensity
Speed
Width
Mode
Rotating rainbow/fixed colour
Clock
Moving lights
Sectors
Air quality monitor with LuftDaten
Touch only
Luftdaten
ID of the sensor to display


Flireh1291.github.io
Download the Canary Setup Guide. Protector the Protectors event with the Frisco Police Department. Protector the Protectors event with the Frisco.
Canary Flex Benutzerhandbuch and Omnitronic SD-28 Bedienungsanleitung herunterladen.


| 6.15.1 | S2-1900677 | DISCUSSION | Agreement | Revisited conclusion on 5GLAN Group Management | Intel | Rel-16 | Vertical_LAN | Group manage | |
| 6.15.1 | S2-1900240 | CR | Approval | 23.501 CR0787 (Rel-16, 'B'): 5G LAN Group Management | Samsung | Rel-16 | Vertical_LAN | Group manage | |
| 6.15.1 | S2-1900242 | CR | Approval | 23.502 CR0897 (Rel-16, 'B'): 5G LAN Group Management Procedure | Samsung | Rel-16 | Vertical_LAN | Group manage | |
| 6.15.1 | S2-1900674 | CR | Approval | 23.502 CR0987 (Rel-16, 'B'): 5GLAN group management procedures | Huawei, HiSilicon | Rel-16 | Vertical_LAN | Group manage | |
| 6.15.1 | S2-1900243 | CR | Approval | 23.502 CR0898 (Rel-16, 'B'): 5G LAN Group Subscription Data | Samsung | Rel-16 | Vertical_LAN | Group subscr | |
| 6.15.1 | S2-1900244 | CR | Approval | 23.502 CR0899 (Rel-16, 'B'): 5G LAN Group Communication Procedure | Samsung | Rel-16 | Vertical_LAN | Communication procedures | |
| 6.15.1 | S2-1900358 | CR | Approval | 23.503 CR0199 (Rel-16, 'B'): N6-based traffic routing for 5GLAN communication | KDDI | Rel-16 | Vertical_LAN | Traffic steering | |
| 6.15.1 | S2-1900365 | DISCUSSION | Decision | Mobility Considerations in a 5G LAN-Type Unified Architecture | Interdigital Inc. | Rel-16 | Vertical_LAN | Some SM aspects, some one-to-many | |
| 6.15.1 | S2-1900366 | CR | Approval | 23.501 CR0822 (Rel-16, 'B'): Mobility Considerations in a 5G LAN-Type Unified Architecture | InterDigital Inc. | Rel-16 | Vertical_LAN | Some SM aspects, cover sheet! | |
| 6.15.1 | S2-1900596 | CR | Approval | 23.501 CR0887 (Rel-16, 'B'): Support one to many communication for 5GLAN | Huawei, HiSilicon | Rel-16 | Vertical_LAN | One to many | |
| 6.15.1 | S2-1900597 | CR | Approval | 23.502 CR0965 (Rel-16, 'B'): Support one to many communication for 5GLAN | Huawei, HiSilicon | Rel-16 | Vertical_LAN | One to many | |
| 6.15.1 | S2-1900367 | DISCUSSION | Decision | IP/MAC addresses update over a 5GLAN connection to support indirect communications mode | InterDigital Inc. | Rel-16 | Vertical_LAN | Indirect communication | |
| 6.15.1 | S2-1900331 | CR | Approval | 23.501 CR0816 (Rel-16, 'B'): 5GLAN communication for Ethernet | KDDI, ETRI | Rel-16 | Vertical_LAN | V-LAN tag | |
| 6.15.2 | - | - | - | 5GS Enhanced support of Vertical and LAN Services - TSN aspects | - | - | {Frank} | - | - |
| 6.15.2 | S2-1900408 | CR | Approval | 23.734 CR0002 (Rel-16, 'B'): Unified Method for time synchronisation using TSN (key issue 3.2) | Samsung | Rel-16 | FS_Vertical_LAN | Postponed. Solution time sync | Postponed |
| 6.15.2 | S2-1900285 | CR | Approval | 23.734 CR0001 (Rel-16, 'F'): Time synchronisation using TSN directly in RAN | QUALCOMM Incorporated | Rel-16 | Vertical_LAN | Revised in parallel session to S2-1901148. Solution time sync | Revised |
| 6.15.2 | S2-1901148 | CR | Approval | 23.734 CR0001R1 (Rel-16, 'F'): Time synchronisation using TSN directly in RAN | QUALCOMM Incorporated | Rel-16 | Vertical_LAN | Revision of S2-1900285. | OPEN |
| 6.15.2 | S2-1900676 | CR | Approval | 23.734 CR0005 (Rel-16, 'F'): Solution of Time Synchronization in Multiple TSN Clock Domains | Huawei, HiSilicon | Rel-16 | Vertical_LAN | No CR cover sheet!. Revised in parallel session to S2-1901149. Solution time sync | Revised |
| 6.15.2 | S2-1901149 | CR | Approval | 23.734 CR0005R1 (Rel-16, 'F'): Solution of Time Synchronization in Multiple TSN Clock Domains | Huawei, HiSilicon | Rel-16 | Vertical_LAN | Revision of S2-1900676. | OPEN |
| 6.15.2 | S2-1900609 | CR | Approval | 23.734 CR0003 (Rel-16, 'C'): TSN QoS and traffic scheduling in 5GS | Ericsson | Rel-16 | FS_Vertical_LAN | Revised in parallel session to S2-1901150. Solution TSN QoS | Revised |
| 6.15.2 | S2-1901150 | CR | Approval | 23.734 CR0003R1 (Rel-16, 'C'): TSN QoS and traffic scheduling in 5GS | Ericsson | Rel-16 | FS_Vertical_LAN | Revision of S2-1900609. | OPEN |
| 6.15.2 | S2-1900610 | CR | Approval | 23.734 CR0004 (Rel-16, 'C'): Additional TSN traffic pattern for RAN optimization | Ericsson | Rel-16 | FS_Vertical_LAN | Revised in parallel session to S2-1901151. Solution time sync | Revised |
| 6.15.2 | S2-1901151 | CR | Approval | 23.734 CR0004R1 (Rel-16, 'C'): Additional TSN traffic pattern for RAN optimization | Ericsson | Rel-16 | FS_Vertical_LAN | Revision of S2-1900610. | OPEN |
| 6.15.2 | S2-1900557 | CR | Approval | 23.501 CR0870 (Rel-16, 'B'): TSC definitions | Nokia, Nokia Shanghai Bell | Rel-16 | Vertical_LAN | Revised in parallel session to S2-1901152. Defs TSN TSC | Revised |
| 6.15.2 | S2-1901152 | CR | Approval | 23.501 CR0870R1 (Rel-16, 'B'): TSC definitions | Nokia, Nokia Shanghai Bell | Rel-16 | Vertical_LAN | Revision of S2-1900557. | OPEN |
| 6.15.2 | S2-1900558 | CR | Approval | 23.501 CR0871 (Rel-16, 'B'): TSC Architecture | Nokia, Nokia Shanghai Bell | Rel-16 | Vertical_LAN | Revised in parallel session to S2-1901153. Architecture TSC | Revised |
| 6.15.2 | S2-1901153 | CR | Approval | 23.501 CR0871R1 (Rel-16, 'B'): TSC Architecture | Nokia, Nokia Shanghai Bell | Rel-16 | Vertical_LAN | Revision of S2-1900558. | OPEN |
| 6.15.2 | S2-1900144 | DISCUSSION | Agreement | This discussion paper discusses how to support TSN QoS requirement | Vivo | Rel-16 | Vertical_LAN | Noted in parallel session. QoS various things | Noted |
| 6.15.2 | S2-1900405 | DISCUSSION | Agreement | Enhancements to 5GS QoS framework for support of deterministic services | Samsung | Rel-16 | Noted in parallel session. Deterministic Delay QoS class | Noted | |
| 6.15.2 | S2-1900517 | DISCUSSION | Discussion | Discussion on the Enhancements to 5GS QoS framework for support of deterministic services | ZTE | Rel-16 | Vertical_LAN | Noted in parallel session. QoS for deterministic service | Noted |
| 6.15.2 | S2-1900559 | DISCUSSION | Agreement | TSN - QoS | Nokia, Nokia Shanghai Bell | Rel-16 | Vertical_LAN | Noted in parallel session. QoS framework | Noted |
| 6.15.2 | S2-1900407 | CR | Approval | 23.501 CR0830 (Rel-16, 'B'): Deterministic QoS Class | Samsung | Rel-16 | Vertical_LAN | Postponed. Deterministic Delay QoS class | Postponed |
| 6.15.2 | S2-1900288 | CR | Approval | 23.501 CR0809 (Rel-16, 'B'): Support of UP based QoS negotiation between 3GPP and TSN networks | Huawei, Hisilicon | Rel-16 | Vertical_LAN | Postponed. QoS negotiation | Postponed |
| 6.15.2 | S2-1900590 | DISCUSSION | Agreement | Discussion on system enhancement for TSN logical bridge management | Huawei, HiSilicon | Rel-16 | Vertical_LAN | Noted in parallel session. TSN logical bridge management | Noted |
| 6.15.2 | S2-1900591 | CR | Approval | 23.501 CR0885 (Rel-16, 'B'): System enhancement for TSN logical bridge management | Huawei, HiSilicon | Rel-16 | Vertical_LAN | TSN logical bridge management | |
| 6.15.2 | S2-1900592 | CR | Approval | 23.502 CR0963 (Rel-16, 'B'): System enhancement for TSN logical bridge management | Huawei, HiSilicon | Rel-16 | Vertical_LAN | TSN logical bridge management | |
| 6.15.3 | - | - | - | 5GS Enhanced support of Vertical and LAN Services - type a/b aspects | - | - | {Frank} | - | - |
| 6.15.3 | S2-1900015 | LS In | Information | LS from RAN WG1: LS on study item completion of NR-U | RAN WG1 () | Rel-16 | FS_NR_unlic | Postponed S2-1811977 from S2#129BIS. Noted in parallel session | Noted |
| 6.15.3 | S2-1900121 | DISCUSSION | Approval | Further considerations for Non-Public Networks | Ericsson | Vertical_LAN | Noted in parallel session. Various things | Noted | |
| 6.15.3 | S2-1900061 | CR | Approval | 23.501 CR0734 (Rel-16, 'B'): Introducing Non-public network | Qualcomm Incorporated | Rel-16 | Vertical_LAN | Revised in parallel session, merging S2-1900157 and S2-1900362, to S2-1901109. What makes an NPN | Revised |
| 6.15.3 | S2-1901109 | CR | Approval | 23.501 CR0734R1 (Rel-16, 'B'): Introducing Non-public network | Qualcomm Incorporated | Rel-16 | Vertical_LAN | Revision of S2-1900061, merging S2-1900157 and S2-1900362. | OPEN |
| 6.15.3 | S2-1900122 | CR | Approval | 23.501 CR0757 (Rel-16, 'B'): Introducing support for Non-Public Networks | Ericsson | Rel-16 | Vertical_LAN | Revised in parallel session to S2-1901110. What makes an NPN | Revised |
| 6.15.3 | S2-1901110 | CR | Approval | 23.501 CR0757R1 (Rel-16, 'B'): Introducing support for Non-Public Networks | Ericsson | Rel-16 | Vertical_LAN | Revision of S2-1900122. | OPEN |
| 6.15.3 | S2-1900157 | CR | Approval | 23.501 CR0766 (Rel-16, 'B'): CR to TS 23.501 on Identification, Discovery and Network Selection for NPN | Tencent | Rel-16 | Vertical_LAN | Merged into S2-1901109. What makes an NPN | OPEN |
| 6.15.3 | S2-1900362 | CR | Approval | 23.501 CR0821 (Rel-16, 'B'): Introduction to non-public network | Intel | Rel-16 | Vertical_LAN | Merged into S2-1901109. What makes an NPN | OPEN |
| 6.15.3 | S2-1900123 | LS OUT | Approval | [DRAFT] LS on considerations due to introduction of Non-Public Networks | Ericsson | Rel-16 | Vertical_LAN | Revised in parallel session to S2-1901111. | Revised |
| 6.15.3 | S2-1901111 | LS OUT | Approval | [DRAFT] LS on considerations due to introduction of Non-Public Networks | Ericsson | Rel-16 | Vertical_LAN | Revision of S2-1900123. | OPEN |
| 6.15.3 | S2-1900145 | DISCUSSION | Agreement | Discussion on the QoS issue when accessing to PLMN services via NPN and vice versa | Vivo | Rel-16 | Vertical_LAN | QoS aspects | |
| 6.15.3 | S2-1900146 | CR | Approval | 23.502 CR0885 (Rel-16, 'B'): Introducing support for accessing to PLMN services via NPN and vice versa | Vivo | Rel-16 | Vertical_LAN | Access to services | |
| 6.15.3 | S2-1900374 | DISCUSSION | Decision | QoS flow mapping for accessing PLMN via NPN | Interdigital Inc. | Rel-16 | Vertical_LAN | Access to services | |
| 6.15.3 | S2-1900429 | CR | Approval | 23.501 CR0836 (Rel-16, 'B'): NPN support for PLMN services via N3IWF | Qualcomm Incorporated | Rel-16 | Vertical_LAN | Access to services | |
| 6.15.3 | S2-1900580 | CR | Approval | 23.501 CR0879 (Rel-16, 'B'): Introducing protocol stacks for accessing to PLMN services via NPN and vice versa | Vivo | Rel-16 | Vertical_LAN | Access to services | |
| 6.15.3 | S2-1900438 | CR | Approval | 23.501 CR0841 (Rel-16, 'B'): FQDN format of N3IWF in a standalone non-public network | Samsung | Rel-16 | Vertical_LAN | NPN N3IWF identification | |
| 6.15.3 | S2-1900518 | DISCUSSION | Discussion | Discussion on the open issues of CAG functionality introduced in 5GS. | ZTE | Rel-16 | Vertical_LAN | CAG issues | |
| 6.15.3 | S2-1900554 | CR | Approval | 23.501 CR0869 (Rel-16, 'C'): DN authorization for NPN offered services | Samsung | Rel-16 | Vertical_LAN | DN authorisation | |
| 6.16 | - | - | - | Study on System enhancements for Provision of Access to Restricted Local Operator Services by Unauthenticated UEs (PARLOS_SA2) | - | - | {Puneet} | - | - |
| 6.16 | S2-1900039 | LS In | Action | LS from TSG RAN: LS on PARLOS RAN impacts | TSG RAN (RP-182843) | Rel-16 | PARLOS_SA2 | ||
| 6.16 | S2-1900154 | CR | Approval | 23.401 CR3491 (Rel-16, 'B'): Support for Restricted Local Operator Services in EPC. | Ericsson, Qualcomm Incorporated, Samsung | Rel-16 | PARLOS_SA2 | ||
| 6.16 | S2-1900155 | CR | Approval | 23.203 CR1125 (Rel-16, 'B'): Support for Restricted Local Operator Services in 23.203 | Ericsson | Rel-16 | PARLOS_SA2 | ||
| 6.16 | S2-1900156 | CR | Approval | 23.228 CR1193 (Rel-16, 'B'): Support for RLOS in IMS | Ericsson | Rel-16 | PARLOS_SA2 | ||
| 6.16 | S2-1900227 | CR | Approval | 23.401 CR3492 (Rel-16, 'B'): Introduction of Restricted Local Operator Services feature | Nokia, Nokia Shanghai Bell | Rel-16 | PARLOS_SA2 | ||
| 6.16 | S2-1900248 | CR | Approval | 23.221 CR0182 (Rel-16, 'B'): Introduction of PaRLOS | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell | Rel-16 | PARLOS | ||
| 6.16 | S2-1900428 | DISCUSSION | Discussion | Updating Requirements for RLOS reporting | OTD | Rel-16 | |||
| 6.16 | S2-1900431 | CR | Approval | 23.401 CR3495 (Rel-16, 'B'): Updating Requirements for RLOS reporting | OTD | Rel-16 | PARLOS | ||
| 6.16 | S2-1900436 | CR | Approval | 23.401 CR3496 (Rel-16, 'B'): Update on Attach and other related procedures for RLOS | Samsung | Rel-16 | PARLOS_SA2 | ||
| 6.16 | S2-1900476 | CR | Approval | 23.401 CR3497 (Rel-16, 'B'): Procedure updates for RLOS-attached UEs | Samsung | Rel-16 | PARLOS_SA2 | ||
| 6.16 | S2-1900679 | LS OUT | Approval | [DRAFT] LS reply on PARLOS RAN impacts | Motorola Mobility, Lenovo | FS_PARLOS_SA2 | Response to S2-1900039 | ||
| 6.17 | - | - | - | Study on EPC support for Mobility with Low Latency Communication (FS_LLC_Mob) | - | - | {Not_on_agenda} | - | - |
| 6.18 | - | - | - | Study on enhancement of systems using EPS for Ultra Reliability and Availability using commodity equipment (FS_EPS_URACE) | - | - | {Not_on_agenda} | - | - |
| 6.19 | - | - | - | Enhancements to the Service-Based 5G System Architecture (eSBA) | - | - | {Frank} | - | - |
| - | - | - | - | Work planning | - | - | - | - | - |
| 6.19 | S2-1900457 | DISCUSSION | Information | ESBA normative work plan for SA WG2#130 | China Mobile | Rel-16 | FS_eSBA | LATE DOC: Rx 15/01, 17:10. Noted in parallel session | Noted |
| - | - | - | - | Context transfer | - | - | - | - | - |
| 6.19 | S2-1900076 | CR | Approval | 23.501 CR0739 (Rel-16, 'B'): NF Service Context Transfer | Tencent | Rel-16 | 5G_eSBA | Postponed | Postponed |
| - | - | - | - | Indirect communication & general implicit discovery to TS 23.501 | - | - | - | - | - |
| 6.19 | S2-1900142 | CR | Approval | 23.501 CR0763 (Rel-16, 'B'): Addition of the service framework related functionalities | Tencent | Rel-16 | 5G_eSBA | Merged into S2-1901105. | Merged |
| 6.19 | S2-1900585 | CR | Approval | 23.501 CR0880 (Rel-16, 'B'): Adding SFSF function for eSBA | ZTE | Rel-16 | 5GS_Ph1 | Merged into S2-1901105. | Merged |
| 6.19 | S2-1900281 | CR | Approval | 23.501 CR0805 (Rel-16, 'B'): New inter NF service communication means due to FS_eSBA | Ericsson, NTT DOCOMO, Sprint | Rel-16 | 5G_eSBA | Merged into S2-1901105. | Merged |
| 6.19 | S2-1900064 | CR | Approval | 23.501 CR0736 (Rel-16, 'B'): Introduction of indirect communication of NF services | Deutsche Telekom AG | Rel-16 | 5G_eSBA | Revised in parallel session, merging S2-1900142, S2-1900585, S2-1900281, S2-1900147 and part of S2-1900587, to S2-1901105. | Revised |
| 6.19 | S2-1901105 | CR | Approval | 23.501 CR0736R1 (Rel-16, 'B'): Introduction of indirect communication of NF services | Deutsche Telekom AG | Rel-16 | 5G_eSBA | Revision of S2-1900064, merging S2-1900142, S2-1900585, S2-1900281, S2-1900147 and part of S2-1900587. | OPEN |
| 6.19 | S2-1900275 | CR | Approval | 23.501 CR0799 (Rel-16, 'B'): ESBA communication schemas related to general discovery and selection | Ericsson, Oracle, Sprint | Rel-16 | 5G_eSBA | Revised in parallel session, merging part of S2-1900587, to S2-1901106. | Revised |
| 6.19 | S2-1901106 | CR | Approval | 23.501 CR0799R1 (Rel-16, 'B'): ESBA communication schemas related to general discovery and selection | Ericsson, Oracle, Sprint | Rel-16 | 5G_eSBA | Revision of S2-1900275, merging part of S2-1900587. | OPEN |
| 6.19 | S2-1900586 | CR | Approval | 23.501 CR0881 (Rel-16, 'B'): Adding indirect communication for eSBA | ZTE | Rel-16 | 5GS_Ph1 | Revised in parallel session to S2-1901107. | Revised |
| 6.19 | S2-1901107 | CR | Approval | 23.501 CR0881R1 (Rel-16, 'B'): Adding indirect communication for eSBA | ZTE | Rel-16 | 5GS_Ph1 | Revision of S2-1900586. | OPEN |
| 6.19 | S2-1900147 | CR | Approval | 23.501 CR0764 (Rel-16, 'B'): Update of NRF functionalities and NF service discovery | Tencent | Rel-16 | 5G_eSBA | Merged into S2-1901105 | Merged |
| 6.19 | S2-1900587 | CR | Approval | 23.501 CR0882 (Rel-16, 'B'): Adding implicit discovery for eSBA | ZTE | Rel-16 | 5GS_Ph1 | Merged into S2-1901105 and S2-1901106. | Merged |
| 6.19 | S2-1900439 | CR | Approval | 23.501 CR0842 (Rel-16, 'B'): Service registration and discovery for distributed service framework | China Mobile | Rel-16 | 5G_eSBA | Functional principles to be covered by S2-1901106. Noted in parallel session | Noted |
| 6.19 | S2-1900562 | CR | Approval | 23.501 CR0873 (Rel-16, 'B'): ESBA communication schema co-existence | Nokia, Nokia Shanghai Bell | Rel-16 | 5G_eSBA | Revised in parallel session to S2-1901108. | Revised |
| 6.19 | S2-1901108 | CR | Approval | 23.501 CR0873R1 (Rel-16, 'B'): ESBA communication schema co-existence | Nokia, Nokia Shanghai Bell | Rel-16 | 5G_eSBA | Revision of S2-1900562. | OPEN |
| - | - | - | - | Implicit discovery specifics to TS 23.501 | - | - | - | - | - |
| 6.19 | S2-1900430 | DISCUSSION | Discussion | Discussion about Implicit Discovery by the Common Services Framework | Oracle | Rel-16 | 5G_eSBA | ||
| 6.19 | S2-1900277 | CR | Approval | 23.501 CR0801 (Rel-16, 'B'): ESBA communication schemas related to SMF discovery and selection | Ericsson, NTT DOCOMO, Sprint | Rel-16 | 5G_eSBA | ||
| 6.19 | S2-1900279 | CR | Approval | 23.501 CR0803 (Rel-16, 'B'): ESBA communication schemas related to AUSF discovery and selection | Ericsson, NTT DOCOMO | Rel-16 | 5G_eSBA | ||
| 6.19 | S2-1900280 | CR | Approval | 23.501 CR0804 (Rel-16, 'B'): ESBA communication schemas related to AMF discovery and selection | Ericsson, NTT DOCOMO | Rel-16 | 5G_eSBA | ||
| 6.19 | S2-1900278 | CR | Approval | 23.501 CR0802 (Rel-16, 'B'): ESBA communication schemas related to PCF discovery and selection | Ericsson, NTT DOCOMO, Sprint | Rel-16 | 5G_eSBA | ||
| 6.19 | S2-1900276 | CR | Approval | 23.501 CR0800 (Rel-16, 'B'): ESBA communication schemas related to UDM and UDR discovery and selection | Ericsson, NTT DOCOMO | Rel-16 | 5G_eSBA | ||
| - | - | - | - | Indirect communication & general implicit discovery to TS 23.502 | - | - | - | - | - |
| 6.19 | S2-1900065 | CR | Approval | 23.502 CR0867 (Rel-16, 'B'): Introduction of indirect communication between NF services and imlicit discovery | Deutsche Telekom AG, NTT DOCOMO | Rel-16 | 5G_eSBA | ||
| 6.19 | S2-1900274 | CR | Approval | 23.502 CR0903 (Rel-16, 'B'): ESBA communication schemas related to discovery and selection | Ericsson, Oracle | Rel-16 | 5G_eSBA | ||
| 6.19 | S2-1900617 | CR | Approval | 23.502 CR0969 (Rel-16, 'B'): Delegated service discovery from a different PLMN | NTT DOCOMO | Rel-16 | 5G_eSBA | ||
| 6.19 | S2-1900561 | CR | Approval | 23.502 CR0957 (Rel-16, 'B'): ESBA communication schema Model C | Nokia, Nokia Shanghai Bell | Rel-16 | 5G_eSBA | ||
| - | - | - | - | Service Zone, Set concept, Bindings | - | - | - | - | - |
| 6.19 | S2-1900608 | DISCUSSION | Discussion | NF Service Zone, definition | NTT DOCOMO, Sprint, AT&T | Rel-16 | |||
| 6.19 | S2-1900273 | DISCUSSION | Agreement | DP on the NF/NF service set | Ericsson | Rel-16 | 5G_eSBA | ||
| 6.19 | S2-1900605 | DISCUSSION | Agreement | NF Service Instance Set, definition | NTT DOCOMO, Sprint, AT&T | Rel-16 | |||
| 6.19 | S2-1900611 | CR | Approval | 23.501 CR0888 (Rel-16, 'B'): Introduction of the concepts of NF Service instance Set and Service Zone | NTT DOCOMO, Sprint, AT&T | Rel-16 | 5G_eSBA | ||
| 6.19 | S2-1900272 | CR | Approval | 23.501 CR0798 (Rel-16, 'B'): Extending the boundaries of a NF and allow reselection of service instances across NFs sharing context data. | Ericsson | Rel-16 | 5G_eSBA | ||
| 6.19 | S2-1900502 | CR | Approval | 23.501 CR0858 (Rel-16, 'B'): Addition of the NF/NF service instance set | Tencent | Rel-16 | 5G_eSBA | ||
| 6.19 | S2-1900563 | CR | Approval | 23.501 CR0874 (Rel-16, 'B'): Introducing NF/NF service instance set | Nokia, Nokia Shanghai Bell | Rel-16 | 5G_eSBA | ||
| 6.19 | S2-1900441 | CR | Approval | 23.501 CR0844 (Rel-16, 'B'): Introduction of high network reliability | Huawei, HiSilicon | Rel-16 | 5G_eSBA | ||
| 6.19 | S2-1900614 | CR | Approval | 23.502 CR0968 (Rel-16, 'B'): Bindings between the consumer and producer | NTT DOCOMO | Rel-16 | 5G_eSBA | ||
| 6.20 | - | - | - | Enhancement of URLLC supporting in 5GC (5G_URLLC) | - | - | {Frank} | - | - |
| 6.20 | S2-1900014 | LS In | Action | LS from RAN WG1: Response to LS on redundant transmission for URLLC | RAN WG1 () | Rel-16 | Postponed S2-1811976 from S2#129BIS | ||
| 6.20 | S2-1900017 | LS In | Action | LS from RAN WG2: Reply LS on redundant transmission for URLLC | RAN WG2 () | Rel-16 | FS_NR_IIOT | Postponed S2-1812446 from S2#129BIS | |
| 6.20 | S2-1900342 | CR | Approval | 23.725 CR0003 (Rel-16, 'F'): URLLC KI#1 Solution 1 - Updates related to the URLLC support by the network | NEC | Rel-16 | FS_5G_URLLC | Soln 1 | |
| 6.20 | S2-1900471 | CR | Approval | 23.725 CR0004 (Rel-16, 'B'): Solution 8 Updates for QoS monitoring solution based on time synchronization | Huawei, HiSilicon, China Telecom | Rel-16 | FS_5G_URLLC | Soln 8 | |
| 6.20 | S2-1900488 | DISCUSSION | Discussion | New solutions for Key Issue #6: Division of E2E PDB | Qualcomm Incorporated | Rel-16 | 5G_URLLC | Soln new | |
| 6.20 | S2-1900490 | CR | Approval | 23.725 CR0006 (Rel-16, 'F'): Update solution #15 for Key issue 6 | Qualcomm Incorporated | Rel-16 | 5G_URLLC | Soln 15 | |
| 6.20 | S2-1900491 | CR | Approval | 23.725 CR0007 (Rel-16, 'B'): Accurate time stamping based solution for Key issue #6 | Qualcomm Incorporated | Rel-16 | 5G_URLLC | Soln new | |
| 6.20 | S2-1900493 | CR | Approval | 23.725 CR0008 (Rel-16, 'F'): Update solution#8 for Key Issue #4: QoS Monitoring | Qualcomm Incorporated | Rel-16 | 5G_URLLC | Soln 8 | |
| 6.20 | S2-1900495 | CR | Approval | 23.725 CR0009 (Rel-16, 'F'): Update Solution #16 for Key Issue #7 | Qualcomm Incorporated | Rel-16 | 5G_URLLC | Soln 16 | |
| 6.20 | S2-1900496 | CR | Approval | 23.725 CR0010 (Rel-16, 'B'): New Solution for Key Issue #7 | Qualcomm Incorporated | Rel-16 | 5G_URLLC | Soln new | |
| 6.20 | S2-1900532 | CR | Approval | 23.725 CR0011 (Rel-16, 'B'): KI#7: Extending notification control for QoS flow setup and handover | CATT | Rel-16 | FS_5G_URLLC | Soln new | |
| 6.20 | S2-1900539 | CR | Approval | 23.725 CR0013 (Rel-16, 'B'): New solution for KI#7 | LG Electronics | Rel-16 | FS_5G_URLLC | Soln new | |
| 6.20 | S2-1900542 | CR | Approval | 23.725 CR0014 (Rel-16, 'B'): New solution for KI#6 | LG Electronics | Rel-16 | FS_5G_URLLC | Soln new | |
| 6.20 | S2-1900570 | CR | Approval | 23.725 CR0015 (Rel-16, 'B'): New Solution for Key Issue #7-URLLC Always on Control for the GBR QoS Flow | Tencent | Rel-16 | 5G_URLLC | Soln new | |
| 6.20 | S2-1900649 | CR | Approval | 23.725 CR0017 (Rel-16, 'F'): Updates to Solution #16 for automated GBR service recovery after handover into congested cell | Vodafone | Rel-16 | FS_5G_URLLC | Soln 16 | |
| 6.20 | S2-1900294 | CR | Approval | 23.725 CR0001 (Rel-16, 'B'): Evaluation of Solution#15 on PDB division | Huawei, Hisilicon | Rel-16 | FS_5G_URLLC | Soln 15 evaluation | |
| 6.20 | S2-1900470 | DISCUSSION | Agreement | Evaluate the relevant solutions addressing the QoS Monitoring issue | Huawei, HiSilicon, China Telecom | Rel-16 | FS_5G_URLLC | evaluation | |
| 6.20 | S2-1900472 | CR | Approval | 23.725 CR0005 (Rel-16, 'B'): Conclusion proposal for Key Issue #4 | Huawei, HiSilicon, China Telecom, Motorola Mobility?, Lenovo? | Rel-16 | FS_5G_URLLC | Confirm sources!. Conclusion KI4 | |
| 6.20 | S2-1900295 | CR | Approval | 23.725 CR0002 (Rel-16, 'B'): Conclusion of the E2E PDB division | Huawei, Hisilicon | Rel-16 | FS_5G_URLLC | Conclusion KI6 | |
| 6.20 | S2-1900579 | CR | Approval | 23.725 CR0016 (Rel-16, 'B'): Conclusion proposal for the E2E PDB division | OPPO | Rel-16 | FS_5G_URLLC | Conclusion KI6 | |
| 6.20 | S2-1900289 | CR | Approval | 23.501 CR0810 (Rel-16, 'B'): New clause for URLLC supporting | Huawei, Hisilicon | Rel-16 | 5G_URLLC | Intro | |
| 6.20 | S2-1900113 | CR | Approval | 23.501 CR0753 (Rel-16, 'B'): General description of solution 1 in 23.725 for user plane redundancy | Ericsson | Rel-16 | 5G_URLLC | Add soln 1 | |
| 6.20 | S2-1900114 | CR | Approval | 23.502 CR0877 (Rel-16, 'B'): Procedure updates for solution 1 in 23.725 for user plane redundancy | Ericsson | Rel-16 | 5G_URLLC | Add soln 1 | |
| 6.20 | S2-1900115 | CR | Approval | 23.501 CR0754 (Rel-16, 'B'): Description of solution 2 in 23.725 for redundancy as an informational annex. | Ericsson | Rel-16 | 5G_URLLC | Add soln 2 | |
| 6.20 | S2-1900290 | CR | Approval | 23.501 CR0811 (Rel-16, 'B'): Add description of solution 4 in 23.725 to 23.501 | Huawei, Hisilicon | Rel-16 | 5G_URLLC | Add soln 4 | |
| 6.20 | S2-1900291 | CR | Approval | 23.502 CR0905 (Rel-16, 'B'): Update procedure of 23.502 to adopt solution 4 in 23.725 | Huawei, HiSilicon | Rel-16 | 5G_URLLC | Add soln 4 | |
| 6.20 | S2-1900300 | CR | Approval | 23.501 CR0813 (Rel-16, 'B'): Introduction of TR 23.725 solution 6 for session continuity upon UL CL relocation | Intel | Rel-16 | 5G_URLLC | Add soln 6 | |
| 6.20 | S2-1900646 | CR | Approval | 23.501 CR0897 (Rel-16, 'B'): Sol#6 specific updates to <IP_ADDRESS> | NEC | Rel-16 | 5G_URLLC | Add soln 6 | |
| 6.20 | S2-1900301 | CR | Approval | 23.502 CR0906 (Rel-16, 'B'): Introduction of TR 23.725 solution 6 for session continuity upon UL CL relocation | Intel | Rel-16 | 5G_URLLC | Add soln 6 | |
| 6.20 | S2-1900473 | CR | Approval | 23.502 CR0941 (Rel-16, 'B'): Forwarding tunnel between source and target UL CL for service continuity | Huawei, HiSilicon | Rel-16 | 5G_URLLC | Add soln 6 | |
| 6.20 | S2-1900658 | CR | Approval | 23.502 CR0980 (Rel-16, 'B'): Updates to <IP_ADDRESS>, based on TR Sol# 6 | NEC | Rel-16 | 5G_URLLC | Add Soln 6 | |
| 6.20 | S2-1900671 | CR | Approval | 23.502 CR0986 (Rel-16, 'B'): Updates to 4.3.6, based on Solutions #6 & #13 | NEC | Rel-16 | 5G_URLLC | Add soln 6, 13 | |
| 6.20 | S2-1900560 | CR | Approval | 23.501 CR0872 (Rel-16, 'B'): Description of solution 7 in 23.725 as replication framework | Nokia, Nokia Shanghai Bell | Rel-16 | 5G_URLLC | Add soln 7 | |
| 6.20 | S2-1900116 | CR | Approval | 23.501 CR0755 (Rel-16, 'B'): Description of solution 11 in 23.725 for Ethernet anchor relocation. | Ericsson, Nokia | Rel-16 | 5G_URLLC | Add soln 11 | |
| 6.20 | S2-1900117 | CR | Approval | 23.502 CR0878 (Rel-16, 'B'): Procedure for solution 11 in 23.725 for Ethernet anchor relocation | Ericsson, Nokia | Rel-16 | 5G_URLLC | Add soln 11 | |
| 6.20 | S2-1900292 | CR | Approval | 23.501 CR0812 (Rel-16, 'B'): Add description of solution 13 in 23.725 to TS 23.501 | Huawei, HiSilicon | Rel-16 | 5G_URLLC | Add soln 13 | |
| 6.20 | S2-1900293 | CR | Approval | 23.503 CR0192 (Rel-16, 'B'): Update 23.503 to support solution 13 in 23.725 | Huawei, HiSilicon | Rel-16 | 5G_URLLC | Add soln 13 | |
| 6.20 | S2-1900475 | DRAFTCR | Approval | Support of coodination between 5GC and AFs_501 | CATT | Rel-16 | 5G_URLLC | ||
| 6.20 | S2-1900480 | CR | Approval | 23.501 CR0854 (Rel-16, 'B'): New parameter for AF request for maintaining UE IP address | Samsung Electronics | Rel-16 | 5G_URLLC | ||
| 6.20 | S2-1900486 | DRAFTCR | Approval | Support of coodination between 5GC and AFs_502 | CATT | Rel-16 | 5G_URLLC | ||
| 6.20 | S2-1900489 | CR | Approval | 23.502 CR0945 (Rel-16, 'B'): User event notification procedure for session and service continuity | Samsung Electronics | Rel-16 | FS_5G_URLLC, 5G_URLLC | ||
| 6.21 | - | - | - | Enhancement of Network Slicing (eNS) | - | - | {Frank} | - | - |
| 6.21 | S2-1900297 | DISCUSSION | Agreement | KI#1 conclusions | Nokia, Nokia Shanghai Bell, Convida Wireless, ZTE, Telecom Italia, Samsung KDDI | Rel-16 | FS_eNS | ||
| 6.21 | S2-1900606 | DISCUSSION | Agreement | Conclusion for FS_eNS KI#1 | Huawei, HiSilicon | Rel-16 | eNS | ||
| 6.21 | S2-1900607 | CR | Approval | 23.740 CR0001 (Rel-16, 'F'): Documenting the conclusion for FS_eNS KI#1 | Huawei, HiSilicon | Rel-16 | eNS | ||
| 6.21 | S2-1900318 | CR | Approval | 23.501 CR0814 (Rel-16, 'C'): Support of mutually exclusive access to Network Slices | Ericsson | Rel-16 | eNS | ||
| 6.21 | S2-1900221 | CR | Approval | 23.501 CR0782 (Rel-16, 'F'): ENS-IDLE mobility | ZTE | Rel-16 | eNS | ||
| 6.21 | S2-1900222 | CR | Approval | 23.502 CR0895 (Rel-16, 'F'): ENS-IDLE mobility | ZTE | Rel-16 | eNS | ||
| 6.21 | S2-1900453 | CR | Approval | 23.501 CR0850 (Rel-16, 'B'): Enhancement on slice interworking--501 | Huawei, Hisillicon | Rel-16 | eNS | ||
| 6.21 | S2-1900454 | CR | Approval | 23.502 CR0938 (Rel-16, 'B'): Enhancement on slice interworking--502 | Huawei, Hisillicon | Rel-16 | eNS | ||
| 6.22 | - | - | - | Study on Application Awareness Interworking between LTE and NR (FS_AAI_LTE_NR) | - | - | {Not_on_agenda} | - | - |
| 6.23 | - | - | - | Single radio voice continuity from 5GS to 3G (5G_SRVCC) | - | - | {Krisztian} | - | - |
| 6.23 | S2-1900507 | CR | Approval | 23.216 CR0352 (Rel-16, 'B'): Adding 5G SRVCC description to scope and definition to 23.216 | ZTE, China Unicom, intel, vivo | Rel-16 | 5G_SRVCC | Revised in parallel session to S2-1900759. | Revised |
| 6.23 | S2-1900759 | CR | Approval | 23.216 CR0352R1 (Rel-16, 'B'): Adding 5G SRVCC description to scope and definition to 23.216 | ZTE, China Unicom, intel, vivo | Rel-16 | 5G_SRVCC | Revision of S2-1900507. | OPEN |
| 6.23 | S2-1900524 | CR | Approval | 23.216 CR0354 (Rel-16, 'B'): 5G-SRVCC procedure | Qualcomm Incorporated, China Unicom, Nokia, Nokia Shanghai Bell, ZTE | Rel-16 | 5G_SRVCC | Revised in parallel session to S2-1900760. | Revised |
| 6.23 | S2-1900760 | CR | Approval | 23.216 CR0354R1 (Rel-16, 'B'): 5G-SRVCC procedure | Qualcomm Incorporated, China Unicom, Nokia, Nokia Shanghai Bell, ZTE | Rel-16 | 5G_SRVCC | Revision of S2-1900524. | OPEN |
| 6.23 | S2-1900508 | CR | Approval | 23.216 CR0353 (Rel-16, 'B'): Enable the 5G SRVCC in 5GS. | ZTE, China Unicom, intel, vivo | Rel-16 | 5G_SRVCC | Revised in parallel session to S2-1900761. | Revised |
| 6.23 | S2-1900761 | CR | Approval | 23.216 CR0353R1 (Rel-16, 'B'): Enable the 5G SRVCC in 5GS. | ZTE, China Unicom, intel, vivo | Rel-16 | 5G_SRVCC | Revision of S2-1900508. | OPEN |
| 6.23 | S2-1900505 | CR | Approval | 23.501 CR0859 (Rel-16, 'B'): Adding 5G SRVCC description to 23.501 | ZTE, China Unicom, vivo, intel | Rel-16 | 5G_SRVCC | Revised in parallel session to S2-1900762. | Revised |
| 6.23 | S2-1900762 | CR | Approval | 23.501 CR0859R1 (Rel-16, 'B'): Adding 5G SRVCC description to 23.501 | ZTE, China Unicom, vivo, intel | Rel-16 | 5G_SRVCC | Revision of S2-1900505. | OPEN |
| 6.23 | S2-1900506 | CR | Approval | 23.502 CR0946 (Rel-16, 'B'): Adding 5G SRVCC description to 23.502 | ZTE, China Unicom, vivo, intel | Rel-16 | 5G_SRVCC | Revised in parallel session to S2-1900763. | Revised |
| 6.23 | S2-1900763 | CR | Approval | 23.502 CR0946R1 (Rel-16, 'B'): Adding 5G SRVCC description to 23.502 | ZTE, China Unicom, vivo, intel | Rel-16 | 5G_SRVCC | Revision of S2-1900506. | OPEN |
| 6.23 | S2-1900509 | CR | Approval | 23.237 CR0507 (Rel-16, 'B'): Adding UDM update the STN-SR to AMF | ZTE, China Unicom | Rel-16 | 5G_SRVCC | Revised in parallel session to S2-1900764. | Revised |
| 6.23 | S2-1900764 | CR | Approval | 23.237 CR0507R1 (Rel-16, 'B'): Adding UDM update the STN-SR to AMF | ZTE, China Unicom | Rel-16 | 5G_SRVCC | Revision of S2-1900509. | OPEN |
| 6.24 | - | - | - | Study on architecture aspects for using satellite access in 5G (FS_5GSAT_ARCH) | - | - | {Puneet} | - | - |
| - | - | - | - | Key Issue Update | - | - | - | - | - |
| 6.24 | S2-1900141 | P-CR | Approval | 23.737: Clarification on key issue on Multi connectivity with satellite access | SES, Avanti, iDirect, Hughes Network Systems, OneWeb | Rel-16 | FS_5GSAT_ARCH | ||
| - | - | - | - | New Key Issue | - | - | - | - | - |
| 6.24 | S2-1900322 | P-CR | Approval | 23.737: Key issue on Network Slicing over satellite backhaul links | SES, Avanti Communications Ltd, vT iDirect Solutions Ltd, Hughes Network Systems, OneWeb | Rel-16 | FS_5GSAT_ARCH | ||
| 6.24 | S2-1900323 | P-CR | Approval | 23.737: Key issue on the impact of secure non 3GPP satellite backhaul links | SES, Avanti Communications Ltd, vT iDirect Solutions Ltd, Hughes Network Systems, OneWeb | Rel-16 | FS_5GSAT_ARCH | ||
| 6.24 | S2-1900324 | P-CR | Approval | 23.737: Key issue on the Management and Orchestration of satellite backhaul | SES, Avanti Communications Ltd, vT iDirect Solutions Ltd, Hughes Network Systems, OneWeb | Rel-16 | FS_5GSAT_ARCH | ||
| 6.24 | S2-1900326 | P-CR | Approval | 23.737: The role of satellite backhaul in content distribution towards the edge | SES, Avanti Communications Ltd, vT iDirect Solutions Ltd, Hughes Network Systems, OneWeb | Rel-16 | FS_5GSAT_ARCH | ||
| - | - | - | - | Solutions | - | - | - | - | - |
| 6.24 | S2-1900487 | P-CR | Approval | 23.737: Solution for support of correlated PDU sessions via SAT RAN and TER RAN | CATT | Rel-16 | FS_5GSAT_ARCH | ||
| 6.24 | S2-1900523 | P-CR | Approval | 23.737: KI#5:QoS control for satellite backhaul scenario | CATT | Rel-16 | FS_5GSAT_ARCH | ||
| 6.25 | - | - | - | Study on supporting Flexible Local Area Data Network | - | - | {Not_on_agenda} | - | - |
| 6.26 | - | - | - | Study on system architecture for next generation real time communication services | - | - | {Not_on_agenda} | - | - |
| 6.27 | - | - | - | 5GS Transfer of Policies for Background Data Transfer | - | - | {Not_on_agenda} | - | - |
| 6.28 | - | - | - | Study on optimisations on UE radio capability signalling (FS_RACS) | - | - | {Puneet} | - | - |
| 6.28 | S2-1900304 | P-CR | Approval | 23.743: RACS with Filter | Sony | Rel-16 | FS_RACS | ||
| 6.28 | S2-1900286 | P-CR | Approval | 23.743: Update of interim conclusions | Nokia, Nokia Shanghai Bell | Rel-16 | FS_RACS | ||
| 6.28 | S2-1900616 | P-CR | Approval | 23.743: Interim Conclusions to include filter | Sony | Rel-16 | FS_RACS | ||
| 6.28 | S2-1900672 | P-CR | Approval | 23.743: Update of solution #14 on Backward Compatibility and correction of conclusions on Backwards Compatibility | Vodafone | Rel-16 | FS_RACS | ||
| 6.28 | S2-1900526 | P-CR | Approval | 23.743: KI2 KI3 solution4 update - UE capability signalling using UDR | Samsung | Rel-16 | FS_RACS | Revision of S2-1812319 from S2#129BIS | |
| 6.28 | S2-1900208 | P-CR | Approval | 23.743: RACS_Update paper on solution #12 | OPPO | Rel-16 | FS_RACS | ||
| 6.28 | S2-1900109 | P-CR | Approval | 23.743: Evaluation of solution 9, delta signalling | Ericsson | Rel-16 | FS_RACS | ||
| 6.28 | S2-1900612 | P-CR | Approval | 23.743: Solution #9 with delta for temporary unavailable capabilities | Sony | Rel-16 | FS_RACS | ||
| 6.28 | S2-1900108 | P-CR | Approval | 23.743: KI#1 - Definition separation of PLMN assigned and manufacturer assigned UE Capability ID | Ericsson | Rel-16 | FS_RACS | ||
| 6.28 | S2-1900107 | P-CR | Approval | 23.743: KI#3 - Co-existence and priority order between PLMN assigned and manufacturer assigned UE Capability ID | Ericsson | Rel-16 | FS_RACS | ||
| 6.28 | S2-1900110 | P-CR | Approval | 23.743: PLMN assigned ID with distributed database | Ericsson | Rel-16 | FS_RACS | ||
| 6.28 | S2-1900111 | P-CR | Approval | 23.743: KI#1, KI#2 - Database corruption risk with manufacturer-assigned UE Capability ID | Ericsson | Rel-16 | FS_RACS | ||
| 6.28 | S2-1900112 | LS OUT | Approval | [DRAFT] LS on radio capability database corruption attack | Ericsson | Rel-16 | FS_RACS | ||
| 6.28 | S2-1900209 | P-CR | Approval | 23.743: Update interim conclusion for KI #2 | OPPO | Rel-16 | FS_RACS | ||
| 6.28 | S2-1900615 | P-CR | Approval | 23.743: Discussion on RAN related issues and conclusion clarification | Vivo | Rel-16 | FS_RACS | ||
| 6.28 | S2-1900330 | P-CR | Approval | 23.743: Update of maximum IE size for 5GCore | Vodafone | Rel-16 | FS_RACS | Revision of S2-1811865 from S2#129BIS | |
| 6.28 | S2-1900106 | P-CR | Approval | 23.743: Evaluation of Solution 7 | Ericsson | Rel-16 | FS_RACS | ||
| 6.28 | S2-1900325 | P-CR | Approval | 23.743: Update solution 5 | Qualcomm Incorporated | Rel-16 | FS_RACS | ||
| 6.29 | - | - | - | Study on User Data Interworking and Coexistence (FS_UDICoM) | - | - | {Krisztian} | - | - |
| 6.29 | S2-1900298 | P-CR | Approval | 23.732: Solution #2 - Stand-alone clarification | Hewlett Packard Enterprise, Affirmed Networks | Rel-16 | FS_UDICoM | ||
| 6.29 | S2-1900060 | P-CR | Approval | 23.732: FS_UDICOM Adding figures text | Vodafone | Rel-16 | FS_UDICoM | ||
| 6.29 | S2-1900066 | P-CR | Approval | 23.732: FS_UDICOM Editorial | Vodafone | Rel-16 | FS_UDICoM | ||
| 6.29 | S2-1900305 | P-CR | Approval | 23.732: Evaluation of solutions 1. | Nokia, Nokia Shanghai Bell | Rel-16 | FS_UDICoM | ||
| 6.29 | S2-1900555 | P-CR | Approval | 23.732: Evaluation of Solution 1 | Motorola Mobility, Lenovo, | Rel-16 | FS_UDICoM | ||
| 6.29 | S2-1900303 | P-CR | Approval | 23.732: Evaluation of solutions 3. | Nokia, Nokia Shanghai Bell | Rel-16 | FS_UDICoM | ||
| 6.29 | S2-1900067 | P-CR | Approval | 23.732: FS_UDICOM Evaluations for solutions #4 and #5 | Vodafone | Rel-16 | FS_UDICoM | ||
| 6.29 | S2-1900307 | P-CR | Approval | 23.732: Evaluation of solutions 4 and 5 | Nokia, Nokia Shanghai Bell | Rel-16 | FS_UDICoM | ||
| 6.29 | S2-1900153 | P-CR | Approval | 23.732: Update to solution 6 | Ericsson | Rel-16 | FS_UDICoM | ||
| 6.29 | S2-1900057 | P-CR | Approval | 23.732: FS_UDICOM evaluation of solutions | Vodafone | Rel-16 | FS_UDICoM | ||
| 6.29 | S2-1900056 | DISCUSSION | Endorsement | FS_UDICOM proposed conclusions | Vodafone | Rel-16 | Revised in S2-1900665 | Revised | |
| 6.29 | S2-1900665 | DISCUSSION | Endorsement | FS_UDICOM proposed conclusions | Vodafone | Rel-16 | Revision of S2-1900056 | ||
| 6.29 | S2-1900058 | P-CR | Approval | 23.732: FS_UDICOM - Conclusion for KI#1 | Vodafone, Verizon, Motorola Mobility, Lenovo | Rel-16 | FS_UDICoM | ||
| 6.29 | S2-1900059 | P-CR | Approval | 23.732: FS_UDICOM - Conclusion for KI#2 | Vodafone | Rel-16 | FS_UDICoM | ||
| 6.29 | S2-1900068 | WID NEW | Approval | UDICOM WID proposal | Vodafone | Rel-16 | |||
| 6.31 | - | - | - | TEI16 Category B/C - Enhancements and Improvements only. 3GPP Packet Access | - | - | {Not_on_agenda} | - | - |
| 6.32 | - | - | - | TEI16 Category B/C - Enhancements and Improvements only. PCC/QoS | - | - | {Not_on_agenda} | - | - |
| 6.33 | - | - | - | TEI16 Category B/C - Enhancements and Improvements only. Non-3GPP Access | - | - | {Not_on_agenda} | - | - |
| 6.34 | - | - | - | TEI16 Category B/C - Enhancements and Improvements only. IMS, IMS-Related, Emergency, Other | - | - | {Not_on_agenda} | - | - |
| 7 | - | - | - | Project Planning and Management | - | - | {Frank} | - | - |
| 7.1 | - | - | - | New and Revised Work Items, Cover sheets for completed work items, TEI16 proposals | - | - | {Frank} | - | - |
| 7.1 | S2-1900633 | SID NEW | Approval | Architectural enhancements for 5G multicast-broadcast services | Huawei, HiSilicon, Telecom Italia, One2many, Expway, Convida Wireless, CATT, China Telecom, China Unicom, China Mobile | Revised to S2-1900684. | Revised | ||
| 7.1 | S2-1900684 | SID NEW | Approval | Architectural enhancements for 5G multicast-broadcast services | Huawei, HiSilicon, Telecom Italia, One2many, Expway, Convida Wireless, CATT, China Telecom, China Unicom, China Mobile | Revision of S2-1900633. | OPEN | ||
| 7.1 | S2-1900528 | DISCUSSION | Agreement | Mission Critical Services Support over 5GS | CATT | Rel-16 | |||
| 7.1 | S2-1900527 | SID NEW | Approval | Study on System enhancement for Mission Critical services in 5GS | CATT, Telecom Italia, CAICT, China Telecom, Tencent, OPPO | Rel-16 | Revised to S2-1900685. | Revised | |
| 7.1 | S2-1900685 | SID NEW | Approval | Study on System enhancement for Mission Critical services in 5GS | CATT, Telecom Italia, CAICT, China Telecom, Tencent, OPPO | Rel-16 | Revision of S2-1900527. | OPEN | |
| 7.1 | S2-1900581 | SID NEW | Information | A new SID proposal for supporting NCIS service | OPPO, Tencent, CATT | Rel-17 | Noted | Noted | |
| 7.1 | S2-1900178 | DISCUSSION | Agreement | Return to NG-RAN after EPS/RAT Fallback | Ericsson, T-Mobile USA, AT&T, China Unicom, OPPO, CATT, CAICT?, China Mobile?, China Telecom?, Huawei?, ZTE?, VIVO? | Rel-16 | Confirm sources!. Noted | Noted | |
| 7.1 | S2-1900433 | DISCUSSION | Agreement | Handling of slice based overload control at NG-RAN | NEC Europe Ltd, Interdigital, AT&T, KDDI, NICT, Convida Wireless | Rel-16 | Revised to S2-1900686. | Revised | |
| 7.1 | S2-1900686 | DISCUSSION | Agreement | Handling of slice based overload control at NG-RAN | NEC Europe Ltd, Interdigital, AT&T, KDDI, NICT, Convida Wireless | Rel-16 | Revision of S2-1900433. | OPEN | |
| 7.1 | S2-1900434 | CR | Approval | 23.501 CR0838 (Rel-16, 'F'): 5G-AN sending a wait time for each congested slice (option 1) | NEC, Interdigital, AT&T, KDDI, NICT, Convidawireless | Rel-16 | 5GS_Ph1 | ||
| 7.1 | S2-1900435 | CR | Approval | 23.501 CR0839 (Rel-16, 'F'): 5G-AN sending one wait time for all congested slices (option 2) | NEC, Interdigital, AT&T, KDDI, NICT, Convidawireless | Rel-16 | 5GS_Ph1 | ||
| 7.1 | S2-1900455 | DISCUSSION | Discussion | Enhancement of Monitoring Event Configuration | Huawei, HiSilicon, AT&T, CAICT, CATT, China Telecom | TEI16 | OPEN | ||
| 7.1 | S2-1900456 | CR | Approval | 23.682 CR0426 (Rel-16, 'B'): Enhancement of Monitoring Event configuration | Huawei, HiSilicon, , AT&T, CAICT, CATT, China Telecom | Rel-16 | TEI16 | ||
| 7.1 | S2-1900460 | DISCUSSION | Approval | PCF selection for the same S-NSSAI and DNN | Huawei, HiSilicon, AT&T, China Mobile, China Telecom | Rel-16 | Revised to S2-1900687. | Revised | |
| 7.1 | S2-1900687 | DISCUSSION | Approval | PCF selection for the same S-NSSAI and DNN | Huawei, HiSilicon, AT&T, China Mobile, China Telecom | Rel-16 | Revision of S2-1900460. | OPEN | |
| 7.1 | S2-1900332 | SID REVISED | Approval | Revised SID: Study on system enablers for multi-SIM devices | Intel | Rel-17 | FS_MuSIM | Revised to S2-1900688. | Revised |
| 7.1 | S2-1900688 | SID REVISED | Approval | Revised SID: Study on system enablers for multi-SIM devices | Intel | Rel-17 | FS_MuSIM | Revision of S2-1900332. Approved. | Approved |
| 7.2 | - | - | - | Review of the Work Plan | - | - | {Frank} | - | - |
| 7.3 | - | - | - | Planning future meetings | - | - | {Frank} | - | - |
| 8 | - | - | - | AOB | - | - | {Frank} | - | - |
| 9 | - | - | - | Close of the Meeting | - | - | {Frank} | - | - |
| 99 | - | - | - | Withdrawn and reserved documents | - | - | {Withdrawn} | - | - |
| 99 | S2-1900042 | LS In | Information | LS from SA WG6: LS response on API invoker onboarding | SA WG6 (S6-181848) | Rel-15 | CAPIF | Not addressed to SA WG2. WITHDRAWN | Withdrawn |
| 99 | S2-1900368 | CR | Approval | 23.501 CR0823 (Rel-16, 'B'): IP/MAC addresses update over a 5GLAN connection to support indirect communications mode | InterDigital Inc. | Rel-16 | Vertical_LAN | WITHDRAWN | Withdrawn |
| 99 | S2-1900232 | P-CR | Approval | 23.794: Additional services over N5 | Nokia, Nokia Shanghai Bell | Rel-16 | FS_eIMS5G | WITHDRAWN | Withdrawn |
| 99 | S2-1900075 | CR | Approval | 23.501 CR0738 (Rel-16, 'B'): URLLC Always on Control for the GBR QoS Flow | Tencent | Rel-16 | 5G_URLLC | WITHDRAWN | Withdrawn |
| 99 | S2-1900537 | CR | Approval | 23.725 CR0012 (Rel-16, 'F'): Clarification on packet bicasting for URLLC solution#3 and 5 IN 23.725-pCR | OPPO | Rel-16 | FS_5G_URLLC | WITHDRAWN | Withdrawn |
| 99 | S2-1900210 | P-CR | Approval | 23.743: Update interim conclusion for KI #3 | OPPO | Rel-16 | FS_RACS | WITHDRAWN | Withdrawn |
| 99 | S2-1900055 | DISCUSSION | Decision | Introduction of support of multiple EATF instances in Emergency SRVCC procedures | ORANGE | Rel-16 | WITHDRAWN | Withdrawn |
Created: 2019-01-22 14:24     END OF LIST
Total documents: 853


Space Mountain: 1 Death
On August 14, 1979, a 31-year-old woman became ill after riding Space Mountain. At the unload area, she was unable to exit the vehicle. Although employees told her to stay seated while the vehicle was removed from the track, other ride operators did not realize that her vehicle was supposed to be removed and accidentally sent her through the ride a second time. She arrived at the unloading zone semi-conscious. The victim was subsequently taken to Palm Harbor Hospital where she remained in a coma and died one week later. The coroner's report attributed the death to natural causes: a heart tumor had dislodged and entered her brain. A subsequent lawsuit against the park was dismissed.


The Beginning
The internet begun in it's most basic form as a DARPA project called Arpanet in the 1960's designed to ensure that the American goverment could still communicate in the event of a nuclear strike.
1965: Two computers at MIT Lincoln Lab communicate with one another using packet-switching technology. Follow this in 1969 Beranek and Newman, Inc. (BBN) unveils the final version of the Interface Message Processor (IMP) specifications. BBN wins ARPANET contract. On Oct. 29, UCLA’s Network Measurement Center, Stanford Research Institute (SRI), University of California-Santa Barbara and University of Utah install nodes. The first message is “LO,” which was an attempt by student Charles Kline to “LOGIN” to the SRI computer from the university. However, the message was unable to be completed because the SRI system crashed.
1965: Two computers at MIT Lincoln Lab communicate with one another using packet-switching technology. Follow this in 1969 Beranek and Newman, Inc. (BBN) unveils the final version of the Interface Message Processor (IMP) specifications. BBN wins ARPANET contract. On Oct. 29, UCLA’s Network Measurement Center, Stanford Research Institute (SRI), University of California-Santa Barbara and University of Utah install nodes. The first message is “LO,” which was an attempt by student Charles Kline to “LOGIN” to the SRI computer from the university. However, the message was unable to be completed because the SRI system crashed.


Interactive media design is a two year program that specializes in arts and design including motion graphics and coding. It gives students the practical hands on skills they need to code, use video and work with graphic design. First year is broad, introducing students to the many disciplines this program has to offer. It is more so focused on the planning and development process, making students familiar with the creating process. Second year on the other hand is more specific and introduces students to more of a real world, course based atmosphere. Individualistic and teachers courses take place, giving students an idea of what to expect in the real world, while carrying out courses start to finish. A Co-Op term is also offered to high achieving students. Second year also gives the students choices as to whether they want to specialize more so in coding or video. A mandatory motion graphics course is also included, which applies to those who have a passion for graphic design.
Thanks to the exponentional growth of web activity, students must learn to design for a platform that keeps evolving each and every day
Learning how to work in these fields of multimedia is crucial nowadays. Students will learn how to take professional shots, as well as tweak and edit them later on
What is the use of coming up with a great idea if you won't share it. Building bonds with your fellow students and working alongside them will prepare you for the outside world
Motion Graphics, CMS I/II
Hussein is a very enthusiatic teacher. He loves to make his students laugh, but never strays away from teaching the content the students need. He is also very generous when it comes to marking
Design Foundations
Katie is a very experienced professor. She is educated in Communications from Ottawa University and is a graduate from this very program. With an ambition to learn and teach others, Katie strives to motivate and educate her students
Web Production
Robert is a very smart teacher thanks to his years of experience in the field of web design. He also founded and worked with a handful of companies, so you can count on him for any business advice. He is also an avid fan of coffee.


The <md-radio-group>
directive identifies a grouping
container for the 1..n grouped radio buttons; specified using nested
<md-radio-button>
tags.
As per the material design spec
the radio button is in the accent color by default. The primary color palette may be used with
the md-primary
class.
Note: <md-radio-group>
and <md-radio-button>
handle tabindex differently
than the native <input type='radio'>
controls. Whereas the native controls
force the user to tab through all the radio buttons, <md-radio-group>
is focusable, and by default the <md-radio-button>
s are not.
| Parameter | Type | Description |
|---|---|---|
* ng-model
string
|
string |
Assignable angular expression to data-bind to. |
md-no-ink
boolean
|
boolean |
Use of attribute indicates flag to disable ink ripple effects. |


Professional History
I discovered a love of data through an internship and part-time gig at the National Priorities Project, a non-profit dedicated to making the federal budget accessible to every day citizens. I've continued my data work as a Grants Researcher at Springfield Technical Community College, where I find, analyze, and prepare federal, state, and local demographic and labor market data for inclusion in grant proposals, among other duties.
Education
I began my academic career as a German major at the former Las Vegas Academy of International Studies, Performing, and Visual Arts, a magnet high school in my hometown of Las Vegas. I continued on to the University of Nevada - Las Vegas, majoring in anthropology, and finished with a bachelor's degree in Political Science from the University of Massachusetts - Amherst. I am currently a student in the Master of Science in Government Analytics degree program at The Johns Hopkins University, concentrating in Statistical Analysis.
Extracurriculars
When I'm not working at STCC or on grad school work, I like to sing (either karaoke or with the Rock Voices choir), read (find me on Goodreads), travel, and hang out with my husband and two cats.


Initial Access
The adversary is trying to get into your network.
Initial Access consists of techniques that use various entry vectors to gain their initial foothold within a network. Techniques used to gain a foothold include targeted spearphishing and exploiting weaknesses on public-facing web servers. Footholds gained through initial access may allow for continued access, like valid accounts and use of external remote services, or may be limited-use due to changing passwords.
Techniques
Techniques: 11
| ID | Name | Description |
|---|---|---|
| T1189 | Drive-by Compromise |
A drive-by compromise is when an adversary gains access to a system through a user visiting a website over the normal course of browsing. With this technique, the user's web browser is targeted for exploitation. |
| T1190 | Exploit Public-Facing Application |
The use of software, data, or commands to take advantage of a weakness in an Internet-facing computer system or program in order to cause unintended or unanticipated behavior. The weakness in the system can be a bug, a glitch, or a design vulnerability. These applications are often websites, but can include databases (like SQL) , standard services (like SMB or SSH), and any other applications with Internet accessible open sockets, such as web servers and related services. Depending on the flaw being exploited this may include Exploitation for Defense Evasion. |
| T1133 | External Remote Services |
Remote services such as VPNs, Citrix, and other access mechanisms allow users to connect to internal enterprise network resources from external locations. There are often remote service gateways that manage connections and credential authentication for these services. Services such as Windows Remote Management can also be used externally. |
| T1200 | Hardware Additions |
Computer accessories, computers, or networking hardware may be introduced into a system as a vector to gain execution. While public references of usage by APT groups are scarce, many penetration testers leverage hardware additions for initial access. Commercial and open source products are leveraged with capabilities such as passive network tapping , man-in-the middle encryption breaking , keystroke injection , kernel memory reading via DMA , adding new wireless access to an existing network , and others. |
| T1091 | Replication Through Removable Media |
Adversaries may move onto systems, possibly those on disconnected or air-gapped networks, by copying malware to removable media and taking advantage of Autorun features when the media is inserted into a system and executes. In the case of Lateral Movement, this may occur through modification of executable files stored on removable media or by copying malware and renaming it to look like a legitimate file to trick users into executing it on a separate system. In the case of Initial Access, this may occur through manual manipulation of the media, modification of systems used to initially format the media, or modification to the media's firmware itself. |
| T1193 | Spearphishing Attachment |
Spearphishing attachment is a specific variant of spearphishing. Spearphishing attachment is different from other forms of spearphishing in that it employs the use of malware attached to an email. All forms of spearphishing are electronically delivered social engineering targeted at a specific individual, company, or industry. In this scenario, adversaries attach a file to the spearphishing email and usually rely upon User Execution to gain execution. |
| T1192 | Spearphishing Link |
Spearphishing with a link is a specific variant of spearphishing. It is different from other forms of spearphishing in that it employs the use of links to download malware contained in email, instead of attaching malicious files to the email itself, to avoid defenses that may inspect email attachments. |
| T1194 | Spearphishing via Service |
Spearphishing via service is a specific variant of spearphishing. It is different from other forms of spearphishing in that it employs the use of third party services rather than directly via enterprise email channels. |
| T1195 | Supply Chain Compromise |
Supply chain compromise is the manipulation of products or product delivery mechanisms prior to receipt by a final consumer for the purpose of data or system compromise. |
| T1199 | Trusted Relationship |
Adversaries may breach or otherwise leverage organizations who have access to intended victims. Access through trusted third party relationship exploits an existing connection that may not be protected or receives less scrutiny than standard mechanisms of gaining access to a network. |
| T1078 | Valid Accounts |
Adversaries may steal the credentials of a specific user or service account using Credential Access techniques or capture credentials earlier in their reconnaissance process through social engineering for means of gaining Initial Access. |


"Resettlement is the transfer of refugees from an asylum country to another State that has agreed to admit them and ultimately grant them permanent settlement."


ozpIwc.CommonApiBase Class
The Common API Base implements the API Common Conventions. It is intended to be subclassed by the specific API implementations.
Constructor
ozpIwc.CommonApiBase
-
config
Parameters:
-
config
Object-
participant
Participantthe participant used for the Api communication
-
Item Index
Methods
- addDynamicNode
- becameLeader
- createKey
- defaultHandler
- findHandler
- findNodeForServerResource
- findOrMakeValue
- formatServerData
- handleBulkget
- handleDelete
- handleEventChannelConnect
- handleEventChannelDisconnect
- handleEventChannelDisconnectImpl
- handleEventChannelDisconnectImpl
- handleGet
- handleSet
- handleUnwatch
- handleWatch
- hasKey
- isLeader
- isLeader
- isPermitted
- leaderSync
- loadFromEndpoint
- loadFromServer
- loadLinkedObjectsFromServer
- makeValue
- newLeader
- notifyWatchers
- persistNodes
- rootHandleList
- routeEventChannel
- routePacket
- setState
- setToLeader
- startElection
- unloadState
- updateDynamicNode
- updateResourceFromServer
- updateResourceFromServerIterative
- validateContextType
- validatePreconditions
- validateResource
Properties
Methods
becameLeader
()
Handles taking over control of the API's participant group as the leader.
createKey
-
prefix
Generates a key name that does not already exist and starts with a given prefix.
Parameters:
-
prefix
StringThe prefix resource string.
Returns:
The prefix resource string with an appended generated Id that is not already in use.
defaultHandler
-
node
-
packetContext
The default handler for the api when receiving packets. This handler is called when no handler was found for the given packet context's action.
Parameters:
-
node
ozpIwc.CommonApiValue@TODO is a node needed? or is this intended for subclass purposes
-
packetContext
ozpIwc.TransportPacketContextThe packet context being handled.
findHandler
-
packetContext
Determines which handler in the api is needed to process the given packet.
Parameters:
-
packetContext
ozpIwc.TransportPacketContextThe packet context to find a proper handler for.
Returns:
The handler for the given packet context.
findNodeForServerResource
-
serverObject
-
objectPath
-
rootPath
Finds or creates the corresponding node to store a server loaded resource.
Parameters:
-
serverObject
ozpIwc.TransportPacketThe object to be stored.
-
objectPath
StringThe full path resource of the object including it's root path.
-
rootPath
StringThe root path resource of the object.
Returns:
The node that is now holding the data provided in the serverObject parameter.
findOrMakeValue
-
packet
For a given packet, return the value if it already exists, otherwise create the value using makeValue()
Parameters:
-
packet
ozpIwc.TransportPacketThe data that will be used to either find or create the api node.
formatServerData
-
the
A middleware function used to format server data to be deserialized into Api nodes
Parameters:
-
the
Objectdata to format.
Returns:
}
handleBulkget
-
node
-
packetContext
Common handler for packet contexts with bulkGet
actions.
Parameters:
-
node
ozpIwc.CommonApiValueThe api node to retrieve. (Not used, bulk get searches the api's data object instead)
-
packetContext
ozpIwc.TransportPacketContextThe packet context containing the bulk get action.
handleDelete
-
node
-
packetContext
Common handler for packet contexts with delete
actions.
Parameters:
-
node
ozpIwc.CommonApiValue@TODO (DOC)
-
packetContext
ozpIwc.TransportPacketContext@TODO (DOC)
handleEventChannelConnect
-
packetContext
Handles connect messages received over the $bus.multicast group.
Parameters:
-
packetContext
ozpIwc.TransportPacketContext
handleEventChannelDisconnect
-
packetContext
Handles disconnect messages received over the $bus.multicast group.
Parameters:
-
packetContext
ozpIwc.TransportPacketContext
handleEventChannelDisconnectImpl
-
packetContext
Intended to be overridden by subclass.
Parameters:
-
packetContext
ozpIwc.TransportPacketContext
handleEventChannelDisconnectImpl
-
packetContext
Intended to be overridden by subclass.
Parameters:
-
packetContext
ozpIwc.TransportPacketContext
handleGet
-
node
-
packetContext
Common handler for packet contexts with get
actions.
Parameters:
-
node
ozpIwc.CommonApiValueThe api node to retrieve.
-
packetContext
ozpIwc.TransportPacketContextThe packet context containing the get action.
handleSet
-
node
-
packetContext
Common handler for packet contexts with set
actions.
Parameters:
-
node
ozpIwc.CommonApiValueThe api node to store the packet contexts' data in.
-
packetContext
ozpIwc.TransportPacketContextThe packet context containing the set action.
handleUnwatch
-
node
-
packetContext
Common handler for packet contexts with unwatch
actions.
Parameters:
-
node
ozpIwc.CommonApiValueThe api node to remove a watch registration from.
-
packetContext
ozpIwc.TransportPacketContextThe packet context containing the unwatch action.
handleWatch
-
node
-
packetContext
Common handler for packet contexts with watch
actions.
Parameters:
-
node
ozpIwc.CommonApiValueThe api node to register a watch on.
-
packetContext
ozpIwc.TransportPacketContextThe packet context containing the watch action.
hasKey
-
resource
Determines if the given resource exists.
Parameters:
-
resource
StringThe path of the resource in question.
Returns:
Returns true if there is a node with a corresponding resource in the api.
isLeader
()
Boolean
Returns true if this API instance is a leadership election.
Returns:
isLeader
()
Boolean
Returns true if this API instance is a leader.
Returns:
isPermitted
-
packetContext
-
node
Determines whether the action implied by the packet is permitted to occur on node in question.
Parameters:
-
packetContext
ozpIwc.TransportPacketContextThe packet of which permission is in question.
-
node
ozpIwc.CommonApiValueThe node of the api that permission is being checked against
Returns:
An asynchronous response, the response will call either success or failure depending on the result of the check.
Example:
foo.isPermitted(node,packetContext)
.success(function(){
...
}).failure(function(){
...
});
leaderSync
()
Handles the syncronizing of API data from previous leaders.
loadFromEndpoint
-
endpointName
-
[Object]
-
requestHeaders.name
-
requestHeaders.value
TO BE DEPRECATED - This is the recursive tree scanning approach. Replaced by iterative loadFromEndpointIterative. Loads api data from a specific endpoint.
Parameters:
-
endpointName
StringThe name of the endpoint to load from the server.
-
[Object]
Object optionalrequestHeaders
-
requestHeaders.name
String -
requestHeaders.value
String
loadFromServer
()
Loads api data from the server. Intended to be overrided by subclasses to load data when this instance becomes a leader without receiving data from the previous leader.
loadLinkedObjectsFromServer
-
endpoint
-
data
-
[Object]
-
headers.name
-
headers.value
Traverses through HAL data from the server and updates api resources based on the data it finds.
Parameters:
-
endpoint
ozpIwc.Endpointthe endpoint of the HAL data.
-
data
Objectthe HAL data.
-
[Object]
Object optionalheaders
-
headers.name
String -
headers.value
String
makeValue
-
packet
Creates a new value for the given packet's request. Subclasses must override this function to return the proper value based upon the packet's resource, content type, or other parameters.
Parameters:
-
packet
ozpIwc.TransportPacket
Returns:
an object implementing the commonApiValue interfaces
newLeader
()
Handles a new leader being assigned to this API's participant group.
Fires:
- ozpIwc.leaderGroupParticipant/#newLeader:event
notifyWatchers
-
node
-
changes
Turn an event into a list of change packets to be sent to the watchers.
Parameters:
-
node
ozpIwc.CommonApiValueThe node being changed.
-
changes
ObjectThe changes to the node.
persistNodes
()
rootHandleList
-
node
-
packetContext
Common handler for packet contexts with a list
action but no resource.
Parameters:
-
node
ozpIwc.CommonApiValue@TODO is a node needed? or is this intended for subclass purposes
-
packetContext
ozpIwc.TransportPacketContextThe packet context of the received request.
routeEventChannel
-
packetContext
Routes event channel messages.
Parameters:
-
packetContext
ozpIwc.TransportPacketContext
routePacket
-
packetContext
Route a packet to the appropriate handler. The routing path is based upon the action and whether a resource is defined. If the handler does not exist, it is routed to defaultHandler(node,packetContext)
Has Resource: handleAction(node,packetContext)
No resource: rootHandleAction(node,packetContext)
Where "Action" is replaced with the packet's action, lowercase with first letter capitalized (e.g. "doSomething" invokes "handleDosomething") Note that node will usually be null for the rootHandlerAction calls.
- Pre-routing checks
- Permission check
- ACL Checks (todo)
- Precondition checks
- Post-routing actions
- Reply to requester
- If node version changed, notify all watchers
Parameters:
-
packetContext
ozpIwc.TransportPacketContextThe packet to route.
setState
-
state
Sets the APIs data property. Removes current values, then constructs each API value anew.
Parameters:
-
state
ObjectThe object containing key value pairs to set as this api's state.
setToLeader
()
Handles setting the API's participant to the leader state.
Fires:
- ozpIwc.leaderGroupParticipant/#becameLeader:event
startElection
()
Puts the API's participant into it's election state.
unloadState
()
Called when the leader participant fires its beforeUnload state. Releases the Api's data property to be consumed by all, then used by the new leader.
updateResourceFromServer
-
object
-
path
-
endpoint
Updates an Api node with server loaded HAL data.
Parameters:
-
object
ozpIwc.TransportPacketThe object retrieved from the server to store.
-
path
StringThe path of the resource retrieved.
-
endpoint
ozpIwc.Endpointthe endpoint of the HAL data.
updateResourceFromServerIterative
-
object
-
path
-
endpoint
Updates an Api node with server loaded HAL data. (Was updateResourceFromServer, modified to be iterative, not recursive)
Parameters:
-
object
ozpIwc.TransportPacketThe object retrieved from the server to store.
-
path
StringThe path of the resource retrieved.
-
endpoint
ozpIwc.Endpointthe endpoint of the HAL data.
validateContextType
-
node
-
packetContext
Checks that the given packet context's contextType meets the requirements of the api. Subclasses should override this method as it performs no check by default.
Parameters:
-
node
CommonApiValue@TODO is a node needed to validate?
-
packetContext
ozpIwc.TransportPacketContextThe packetContext with the contextType to be validated.
Returns:
- always returns true.
validatePreconditions
-
node
-
packetContext
Checks the given packet context's ifTag
against the desired api node's version
. Throws ApiError if ifTag exists
and doesn't match.
Parameters:
-
node
ObjectThe api node being checked against.
-
packetContext
ObjectThe packet context to validate.
validateResource
-
node
-
packetContext
Checks that the given packet context's resource meets the requirements of the api. Subclasses should override this method as it performs no check by default.
Parameters:
-
node
CommonApiValue@TODO is a node needed to validate?
-
packetContext
ozpIwc.TransportPacketContextThe packetContext with the resource to be validated.
Returns:
always returns true.
Properties
data
Object
Key value storage for the API. each element of the object is a node of the API.
Default: {}
dynamicNodes
Array
Api nodes that are updated based on other api nodes. Used for keeping dynamic lists of related resources.
Default: []
events
Event
An events module for the API.
participant
Participant
The participant used for the Api communication on the bus.
Default: {}


Custom Software Development Services
Solve your project’s problems with our Dedicated
Teams services, build a mobile app that ticks all
boxes, finish the digital transformation with our
spot-on IT consulting. Intellectsoft’s software
development services use the latest tech to help you
reach your IT objectives within today’s demanding
timeframes.
DEDICATED DEVELOPMENT TEAM
Cannot hire the right local tech talent on time?
Unhappy with high attrition rate on your in-house
team? Scale your delivery capacity with dedicated
developers and teams. Over the past decade, our
customers succeeded by leveraging Intellectsoft’s
process of building, motivating, and managing
software development teams.
IMPACTFUL MOBILE APP DEVELOPMENT SERVICES
Going mobile will help your business streamline
operations, bring value to the demanding modern
customers, and help you tackle Big Data. Whether it
is your first app or fifth, our decade-long
expertise in mobile app development will help you
succeed with your mobile strategy.
ENTERPRISE SOFTWARE DEVELOPMENT
Need a solid software foundation for your business?
Uncoordinated mobile apps and software stress out
your employees and impede your productivity?
Leverage our decade-long expertise in enterprise
software development, API integration, modernising
legacy systems, and consolidating app portfolios.
QA SERVICES
Our QA services will help you establish concrete
control over your product’s life cycle, monitor
every development stage, and give you accurate
product quality information. For over a decade, our
QA experts have been using the latest practices and
technologies to ensure efficient performance and
high-quality project implementation for the world’s
largest enterprises, aiding in delivering solid
software on time.
IT CONSULTING SERVICES
Use the expertise and deep tech background of the
best minds at Intellectsoft to create a
comprehensive IT strategy for a digital and
technological transformation of your organization
that goes in line with your business objectives. Our
strategic IT consulting will help you automate and
digitalise operations, optimise the software
portfolio, and implement the latest technologies.
UI AND UX DESIGN SERVICES
Want to build your product with a team that
establishes a clear design process, meets deadlines,
and delivers a spot-on end result? Turn to
Intellectsoft’s UI and UX services. Our design team
is a small design studio within a large software
company that will help you build an engaging product
easily and quickly.
IMPACTFUL DEVOPS
Need to ensure fast, continuous delivery and a
consistently high level of software quality? An
approach to software that establishes close
collaboration between software engineers and IT
operations employees, DevOps will help you achieve
this by automating and optimising your IT processes.
Our expert DevOps engineers will help you attune the
delivery, deployment, development, security, and
support of any high-load, fail-safe system with
microservices architecture — so your business
strategy can always rely on high-quality software.


SULOGIN
Section: Linux System Administrator's Manual (8)Updated: 17 Jan 2006
Index Return to Main Contents
NAME
sulogin - Single-user loginSYNOPSIS
sulogin [ -e ] [ -p ] [ -t SECONDS ] [ TTY ]DESCRIPTION
sulogin can be invoked by init(8) when the system goes into single user mode. (This is done through an entry in inittab(5).) Init also tries to execute sulogin when the boot loader (e.g., grub(8)) passes it the -b option.The user is prompted
-
Give root password for system maintenance
(or type Control-D for normal startup):
sulogin will be connected to the current terminal, or to the optional device that can be specified on the command line (typically /dev/console).
If the -t option is used then the program only waits the given number of seconds for user input.
If the -p option is used then the single-user shell is invoked with a dash as the first character in argv[0]. This causes the shell process to behave as a login shell. The default is not to do this, so that the shell will not read /etc/profile or $HOME/.profile at startup.
After the user exits the single-user shell, or presses control-D at the prompt, the system will (continue to) boot to the default runlevel.
ENVIRONMENT VARIABLES
sulogin looks for the environment variable SUSHELL or sushell to determine what shell to start. If the environment variable is not set, it will try to execute root's shell from /etc/passwd. If that fails it will fall back to /bin/sh.This is very valuable together with the -b option to init. To boot the system into single user mode, with the root file system mounted read/write, using a special "fail safe" shell that is statically linked (this example is valid for the LILO bootprompt)
boot: linux -b rw sushell=/sbin/sash
FALLBACK METHODS
sulogin checks the root password using the standard method (getpwnam) first. Then, if the -e option was specified, sulogin examines these files directly to find the root password:
/etc/passwd,
/etc/shadow (if present)
If they are damaged or nonexistent, sulogin will start a root shell without asking for a password. Only use the -e option if you are sure the console is physically protected against unauthorized access.
AUTHOR
Miquel van Smoorenburg<EMAIL_ADDRESS>ALSO
init(8), inittab(5).
Index
This document was created by man2html, using the manual pages.
Time: 05:34:30 GMT, December 24, 2015


import { FileSelectorModule } from '@sbb-esta/angular-public';
FileSelectorTypesService
| formatFileSize | |
|---|---|
|
Returns the file size with the correct unit of measure. |
|
| Parameters | |
|
fileSizeBytes number
|
File size in bytes. |
| Returns | |
string
|
File size with the correct unit of measure. |
| getAcceptString | |
|---|---|
|
Returns all formats accepted. |
|
| Parameters | |
|
typeCats FileTypeCategory | FileTypeCategory[]
|
File type category/ies. |
| Returns | |
string
|
All formats accepted. |
| getFileExtensionFromFileName | |
|---|---|
|
Returns the specific file with the name in input. |
|
| Parameters | |
|
fileName string
|
File name. |
| Returns | |
string
|
File with the name in input. |
| getFileNameNoExtension | |
|---|---|
|
Returns the file extension of the file with name in input. |
|
| Parameters | |
|
fileName string
|
File name. |
| Returns | |
string
|
File extension. |
| getFileTypeCategoryByMimeType | |
|---|---|
|
Returns the file type category/ies with mime Type in input. |
|
| Parameters | |
|
mimeType string
|
Mime type of a file. |
| Returns | |
FileTypeCategory
|
File type category/ies. |
FileSelectorComponent
Selector: sbb-file-selector
| Name | Description |
|---|---|
|
@Input()
|
Categories of file types accepted by sbb-file-selector component. |
|
@Input()
|
Attribute whose state specifies the preferred facing mode for the media capture mechanism. |
|
@Input()
|
Mode to disable the choice of files to upload. |
|
@Input()
|
Identifier of a sbb-file-selector component. |
|
@Input()
|
Mode on file selector component to chose more files to upload. |
|
@Input()
|
Set if the component should add files on top of the already selected ones or keep default input file behaviour. |
|
@Output()
|
Event emitted to a change on file selector component (for example the uploading of files). |
|
|
File type category available. |
|
|
List of files uploaded. |
|
|
Property that listens changes on file selector. |
|
|
Property that catches the interaction with user. |
| applyChanges | |
|---|---|
|
Applies changes on sbb-file-selector. |
|
| Parameters | |
|
files File[]
|
Files uploaded. |
|
action "add" | "remove" = 'add'
|
|
| fileChange | |
|---|---|
|
Applies changes on the list of files uploaded. |
|
| Parameters | |
|
files FileList
|
Files uploaded. |
| getFileTypeCat | |
|---|---|
|
Returns the file type category by the file type in input. |
|
| Parameters | |
|
file File
|
File. |
| Returns | |
FileTypeCategory
|
File type category of the file type in input. |
| removeFile | |
|---|---|
|
Returns the list of files without the file deleted. |
|
| Parameters | |
|
file File
|
File to delete. |
FileSelectorOptions
| Name | Description |
|---|---|
|
|
Categories of file types accepted by sbb-file-selector component. It is optional. |
|
|
Attribute whose state specifies the preferred facing mode for the media capture mechanism. The attribute's keywords are user and environment, which map to the respective states user and environment. It is optional. |
|
|
Mode on file selector component to chose more files to upload. It is optional. |
|
|
Set if the component should add files on top of the already selected ones or keep default input file behaviour |


Budget Calculator
Total Income
✕
Daily
Weekly
Bi-Weekly
Monthly
Yearly
Employment Income
Investment Income
Rental Income
Tax Refund
Other
add
Living Expenses
✕
Daily
Weekly
Bi-Weekly
Monthly
Yearly
Mortgage/Rent
Maintenance
Utilities
Phone/TV/Internet
Groceries
Clothes
Other
add
Transportation
✕
Daily
Weekly
Bi-Weekly
Monthly
Yearly
Vehicle
Gas
Transit Costs
Other
add
Financial
✕
Daily
Weekly
Bi-Weekly
Monthly
Yearly
TFSA contributions
RESP contributions
RRSP contributions
Credit Card Payments
Loan Payments
Insurance
Other
add
Child Care
✕
Daily
Weekly
Bi-Weekly
Monthly
Yearly
School/Day care
Activity/Clubs
Other
add
Health Care
✕
Daily
Weekly
Bi-Weekly
Monthly
Yearly
Doctor Appointments
Prescription Drugs
vision
Dental
Other
add
Leisure
✕
Daily
Weekly
Bi-Weekly
Monthly
Yearly
Club Memberships
Subscriptions
Travel
Dining out
Pets
Other
add
Summary:
sd


| DOSE: T+ 0:00 |
16 mg |
oral |
2C-I |
(powder / crystals) |
| T+ 1:30 |
1 hit |
oral |
LSD |
(blotter / tab) |
I've taken 2C-I about 10 times. I find it to be one of the most positive, yet most gentle, psychedelics out there. Extremely intense visuals without ever being overwhelming. I've followed a progression from a safe, home environment to outdoors, at art festivals, to having this substance in a club setting, surrounded by sweaty people in crowds, and the worst side effect I've ever had was getting very hungry. I've even started to experiment-- taking MDMA towards the aftereffects.
2C-I is so slow and gentle, I've had people at T+2 hours insisting that it isn't working, but they're giggling at the trash on the sidewalk. Seriously: don't drive. I initially thought that the 2C-I experience lasted about 4-6 hours, though I'm thinking now that it's more along the lines of 8-10-- incredibly slow and gentle in the come-on and the come-down.
This particular evening, I'd planned to go to an outdoor arts festival, with music, costume, lights... I was covered in fur and expecting an excellent time, and I thought that 2C-I was a perfect experience for the evening.
About 1730, I dropped a gelcap with ~16-18 mg of 2C-I powder in it. At about 1845, I was just on the edge of feeling warm, loved, extra-sensitive to its effects-- and all the art (incredibly cool while sober) was just getting nicer and cooler. As stated earlier, I think this is a tough material to judge 'where you're at', but I'd say I was at a nice, pleasant, +1/+1.5.
A friend showed up, who had recently failed to procure a quantity of LSD. Unknown to me, however, he had managed to get a small quantity, and a small square of paper was placed right on my tongue. My judgement was a bit impaired, and it was a Sunday night (I have a day job...), but I figured: you only live once, so let's do it right. Onwards and upwards.
Now some folks have a bit of stomach cramps with 2C-I, some folks get a bit queasy. I have none of that. Within 30 minutes I was feeling about a +2.5, and everything had just gone completely amazing. Certainly a part of this was set and setting (art, great people, etc.), but my entire world just went completely positive. I'd put it at a +3 or +3.5 within an hour. I stayed there for at least two hours, and quite possibly longer (it being impossible to keep track of time at this point), talking to people, dancing, and mostly wandering through the crowd, finding incredible friends, new and old to talk to.
There were photos that pretended as if they were blacklight photos, but they weren't. There was an incredible sense-- somewhat like the first time I did MDMA, when hugging friends-- of some sort of spiral energy signature going through both bodies. There was a Gigeresque alien playing with puddles of light on the ground. Fortunately, photos proved that this was a man in costume later. I remember thinking 'well, I'm on drugs, and it looks pretty cool, so I'm just going to accept it'.
Important to note: I'd had about 8 hours' sleep in 3 days. I'd been out clubbing with an inordinate amount of mdma 2 nights before, and had had a small abount of 5-MEO-dipt the night before that. I hadn't expected to feel as marvelous as I did.
I've had a pretty wide range of experience with psychedelics: 5-meo-dmt, 5-meo-dipt, 2ci, mdma, mbdb, lsd, psylocybin, thc and cannabis, etc. This is, quite possibly, the highest I've ever been. Caveat: I've been a lot higher before, however, at any of those points, I started to become less and less functional -- floppy and tired yet wired (foxy, E), or plain wandering in other universes (5-meo-dmt).
At about T+8 hours, we packed up our art installation, got someone who hadn't been indulging to drive us home, and chilled and chatted for ~ 3 hours.  I really think that if we hadn't both had a 7AM alarm impending, we wouldn't have had a bad time at all.
All in all, I'd have to say that this is a combo that I am willing to try, again.
and again.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.