Skip to content

Commit 2641dfd

Browse files
Merge pull request #250569 from James-Green-Microsoft/4g-s1-handover
Add support for 4G S1 handover
2 parents 86f219d + 6e8fe4a commit 2641dfd

File tree

2 files changed

+2
-1
lines changed

2 files changed

+2
-1
lines changed

articles/private-5g-core/private-mobile-network-design-requirements.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -126,7 +126,7 @@ If you are affected by this issue, it is strongly recommended to configure the R
126126

127127
The UEs must be able to communicate with the RAN from any location at the site. This means that the signals must propagate effectively in the environment, including accounting for obstructions and equipment, to support UEs moving around the site (for example, between indoor and outdoor areas).
128128

129-
You should perform a site survey with your RAN partner and the enterprise to make sure that the coverage is adequate. Make sure that you understand the RAN units’ capabilities in different environments and any limits (for example, on the number of attached UEs that a single unit can support). If your UEs are going to move around the site, you should also confirm that the RAN supports X2 (4G) or Xn (5G) handover, which allows for the UE to transition seamlessly between the coverage provided by two RAN units. Note that UEs cannot use these handover techniques to roam between a private enterprise network and the public cellular network offered by a telecommunications operator.
129+
You should perform a site survey with your RAN partner and the enterprise to make sure that the coverage is adequate. Make sure that you understand the RAN units’ capabilities in different environments and any limits (for example, on the number of attached UEs that a single unit can support). If your UEs are going to move around the site, you should also confirm that the RAN supports X2 (4G) or Xn (5G) handover, which allows for the UE to transition seamlessly between the coverage provided by two RAN units. If the RAN doesn't support X2 (4G) or Xn (5G), then RAN must support S1 (4G) and N2 (5G) for UE mobility. Note that UEs cannot use these handover techniques to roam between a private enterprise network and the public cellular network offered by a telecommunications operator.
130130

131131
### SIMs
132132

articles/private-5g-core/statement-of-compliance.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,7 @@ All packet core network functions are compliant with Release 15 of the 3GPP spec
4343

4444
- TS 23.401: General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access:
4545
- 5.5.1.1 X2-based handover.
46+
- 5.5.1.2 S1-based handover.
4647

4748
### Policy and charging control (PCC) framework
4849

0 commit comments

Comments
 (0)