Backlog refinement is the ongoing work of getting the next stories ready: splitting them, adding acceptance criteria, answering open questions and estimating. A BA often leads much of it with the product owner, a sprint or two ahead of the team.
Many teams agree a definition of ready: a story is not pulled into a sprint until, for example, it has acceptance criteria, it is small enough, its dependencies are known, the team has estimated it and nobody has an open question about it.
Teams often estimate in story points: relative sizes ("this is about twice that one"), not hours. The total points a team finishes per sprint is its velocity. Velocity turns a sized backlog into a forecast: 120 points of stories at about 30 points a sprint is about 4 sprints. It is a forecast, not a promise, and it only works with the same team's own past velocity.
The product owner orders the backlog; refinement makes the top of it ready.