From 5fdf0178bd600d4a7ccde1a9a626efbbf6f0370d Mon Sep 17 00:00:00 2001 From: wangllei6 Date: Thu, 6 Mar 2025 02:35:07 +0000 Subject: [PATCH 1/3] typo corrections --- .../stage-3/06_Connection_Control/06.01 Connection Setup.md | 2 +- .../06_Connection_Control/asn1/Uu-6G-ConnectionControl.asn | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md b/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md index 6aa1fa2..370288a 100644 --- a/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md +++ b/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md @@ -20,7 +20,7 @@ The purpose of this procedure is to establish an RRC connection between the UE a #### 6.1.1.2 Initiation -The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in RRC_IDLE and it has acquired essential system information. +The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in RRC_IDLE state and it has acquired essential system information. The UE shall ensure having valid and up to date essential system information as specified in clause 5.2.2.2 before initiating this procedure. diff --git a/specification/stage-3/06_Connection_Control/asn1/Uu-6G-ConnectionControl.asn b/specification/stage-3/06_Connection_Control/asn1/Uu-6G-ConnectionControl.asn index 102ee1e..aca3bb5 100644 --- a/specification/stage-3/06_Connection_Control/asn1/Uu-6G-ConnectionControl.asn +++ b/specification/stage-3/06_Connection_Control/asn1/Uu-6G-ConnectionControl.asn @@ -7,7 +7,7 @@ ConnectionSetupRequest ::= SEQUENCE { /* If upper layers provide a 5G-S-TMSI, the UE shall set this field to the ng-5G-S-TMSI-Part1 (note: upper layers provide the 5G-S-TMSI if the UE is registered in the TA of the current cell.). Else, the UE shall set the field to a uniformly drawn random value in the range 0..549755813887. */ ue-Identity InitialUE-Identity, - /* If the UE establishmes the RRC connection as a result of release with redirect with mpsPriorityIndication, it shall set this field to "mps-PriorityAccess". Else, the UE shall set the field in accordance with the information received from upper layers. + /* If the UE establishmes the RRC connection due to the release with redirect with mpsPriorityIndication, it shall set this field to "mps-PriorityAccess". Else, the UE shall set the field in accordance with the information received from upper layers. NOTE: The network does not reject an RRCSetupRequest if the UE chooses a cause value that is unknown to the network. */ establishmentCause EstablishmentCause, -- GitLab From feb12651bfeed1a598985990aacbad08ea644c48 Mon Sep 17 00:00:00 2001 From: wangllei6 Date: Thu, 6 Mar 2025 05:05:00 +0000 Subject: [PATCH 2/3] Update .gitlab-ci.yml file --- .gitlab-ci.yml | 49 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 49 insertions(+) create mode 100644 .gitlab-ci.yml diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml new file mode 100644 index 0000000..64b372d --- /dev/null +++ b/.gitlab-ci.yml @@ -0,0 +1,49 @@ +# This file is a template, and might need editing before it works on your project. +# This is a sample GitLab CI/CD configuration file that should run without any modifications. +# It demonstrates a basic 3 stage CI/CD pipeline. Instead of real tests or scripts, +# it uses echo commands to simulate the pipeline execution. +# +# A pipeline is composed of independent jobs that run scripts, grouped into stages. +# Stages run in sequential order, but jobs within stages run in parallel. +# +# For more information, see: https://docs.gitlab.com/ee/ci/yaml/index.html#stages +# +# You can copy and paste this template into a new `.gitlab-ci.yml` file. +# You should not add this template to an existing `.gitlab-ci.yml` file by using the `include:` keyword. +# +# To contribute improvements to CI/CD templates, please follow the Development guide at: +# https://docs.gitlab.com/ee/development/cicd/templates.html +# This specific template is located at: +# https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Getting-Started.gitlab-ci.yml + +stages: # List of stages for jobs, and their order of execution + - build + - test + - deploy + +build-job: # This job runs in the build stage, which runs first. + stage: build + script: + - echo "Compiling the code..." + - echo "Compile complete." + +unit-test-job: # This job runs in the test stage. + stage: test # It only starts when the job in the build stage completes successfully. + script: + - echo "Running unit tests... This will take about 60 seconds." + - sleep 60 + - echo "Code coverage is 90%" + +lint-test-job: # This job also runs in the test stage. + stage: test # It can run at the same time as unit-test-job (in parallel). + script: + - echo "Linting code... This will take about 10 seconds." + - sleep 10 + - echo "No lint issues found." + +deploy-job: # This job runs in the deploy stage. + stage: deploy # It only runs when *both* jobs in the test stage complete successfully. + environment: production + script: + - echo "Deploying application..." + - echo "Application successfully deployed." -- GitLab From bc6296730eb4ee7a378ccb53b77b63719f5c976f Mon Sep 17 00:00:00 2001 From: wangllei6 Date: Thu, 6 Mar 2025 10:07:27 +0000 Subject: [PATCH 3/3] Update file .gitlab-ci.yml --- .gitlab-ci.yml | 49 ------------------------------------------------- 1 file changed, 49 deletions(-) delete mode 100644 .gitlab-ci.yml diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml deleted file mode 100644 index 64b372d..0000000 --- a/.gitlab-ci.yml +++ /dev/null @@ -1,49 +0,0 @@ -# This file is a template, and might need editing before it works on your project. -# This is a sample GitLab CI/CD configuration file that should run without any modifications. -# It demonstrates a basic 3 stage CI/CD pipeline. Instead of real tests or scripts, -# it uses echo commands to simulate the pipeline execution. -# -# A pipeline is composed of independent jobs that run scripts, grouped into stages. -# Stages run in sequential order, but jobs within stages run in parallel. -# -# For more information, see: https://docs.gitlab.com/ee/ci/yaml/index.html#stages -# -# You can copy and paste this template into a new `.gitlab-ci.yml` file. -# You should not add this template to an existing `.gitlab-ci.yml` file by using the `include:` keyword. -# -# To contribute improvements to CI/CD templates, please follow the Development guide at: -# https://docs.gitlab.com/ee/development/cicd/templates.html -# This specific template is located at: -# https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Getting-Started.gitlab-ci.yml - -stages: # List of stages for jobs, and their order of execution - - build - - test - - deploy - -build-job: # This job runs in the build stage, which runs first. - stage: build - script: - - echo "Compiling the code..." - - echo "Compile complete." - -unit-test-job: # This job runs in the test stage. - stage: test # It only starts when the job in the build stage completes successfully. - script: - - echo "Running unit tests... This will take about 60 seconds." - - sleep 60 - - echo "Code coverage is 90%" - -lint-test-job: # This job also runs in the test stage. - stage: test # It can run at the same time as unit-test-job (in parallel). - script: - - echo "Linting code... This will take about 10 seconds." - - sleep 10 - - echo "No lint issues found." - -deploy-job: # This job runs in the deploy stage. - stage: deploy # It only runs when *both* jobs in the test stage complete successfully. - environment: production - script: - - echo "Deploying application..." - - echo "Application successfully deployed." -- GitLab